Tell DLS: Twitter - what would you change?
We recently posted a piece about whether a URL should really count towards your 140 character limit. We also posted yesterday about Twitter's new re-tweet model and this set me thinking about what I like and don't like about Twitter and what i'd change.
Although Twitter's roots are in SMS - hence the 140 character limit - i'd love to see a standard for tweeting longer content. I would love to be able to tweet, say, 420 characters (i.e. 3 x 140) and have the Twitter systems able to deal with that. For people on SMS it could read (1/3), (2/3) etc, but the Twitter site itself and client applications could display the full message 'reconstructed'.
Ånother feature I would like to see on Twitter, which would probably need to be implemented by client developers, would be a spoiler tag. I read my Twitter feed very frequently, but one example of where this is inconvenient is when i've timeshifted some sport (e.g. F1!) and my tweets read like a running commentary! If my clients could support a spoiler tag, where I had to 'click to reveal' the content (and of course my friends were disciplined enough to use it) then that would solve the problem! I imagine a tweet would look something like "#f1 #spoiler Hamilton and Button just got taken out at the first corner!' - and all content after the #spoiler tag is hidden until I click.
As it is I just try and avoid Twitter until i've watched the event.
They are a couple of things I'd love to see to improve my Twitter experience, but i'm really interested to hear what Twitter fans here on DownloadSquad would change about the service.
Feel free to share in the comments, and don't forget you can follow us on Twitter via @DownloadSquad.
