-
Website
http://www.scripting.com/ -
Original page
http://www.scripting.com/stories/2009/06/25/theMythOfPerfection.html -
Subscribe
All Comments -
Community
-
Top Commenters
-
eas
55 comments · 4 points
-
AndrewBurton
134 comments · 10 points
-
Michael Markman (Mickeleh)
154 comments · 16 points
-
Rex Hammock
52 comments · 9 points
-
malatmals
81 comments · 3 points
-
-
Popular Threads
-
How I develop formats and protocols. (Scripting News)
1 day ago · 11 comments
-
Open is in the eye of the beholder. (Scripting News)
3 days ago · 13 comments
-
Store Twitter URLs in earth's oceans? (Scripting News)
5 days ago · 16 comments
-
Why today's Twitter is like Napster in Y2K. (Scripting News)
5 days ago · 15 comments
-
If you wrote the words you own the copyright. (Scripting News)
5 days ago · 7 comments
-
How I develop formats and protocols. (Scripting News)
Hope this has piqued your interest a little. My Identica user name is jakec94 (same as my Twitter one, but lower case).
:) nmw
1. high length-limit (48k? :)
2. make replies, links, etc. part of the metadata and not part of the data
3. Ability to follow a thread easily (a-la what tweetdeck does now in 0.26)
4. Groups
5. being able to see all messages from person A, including replies, via API, even if they a twit starting with a "@B" (i.e. replies)
1. "in-reply-to-status-id" is already in the tweet metadata, and that's how Tweetie and other apps reconstruct the reply chains. (Of course, that reply metadata is often absent now that power users have stopped using the reply button in reaction to Twitter's #fixreplies screwup: always hiding replies from other followers who don't follow the replied-to account.) The whole "@business" is no longer refered to as "replies", it's called "mentions". (Though I think Twitter Inc is still inconsistent on this-- starting with @ still hides the tweet from others, like a reply.)
2. Links are not typically "metadata" per-se. Often they are the main content of a Tweet. But a case for links in metadata would be a field like "with-regard-to-url". That might be cool. Very similar to "in-reply-to-status-id".
My wish for a new feature would be the ability to add tags to the people that I follow and follow me. And then be able to view the stream of a certian tag, groups basicly.
Originofspecious.blogspot.com
Perhaps if Twitter (the co.) implement groups that problem would be solved, perhaps not. Has anyone worked on a nice little open format to describe these things called 'groups' ?
1. Extensible metadata on posts
2. People represented by OpenIDs or INames, instead of Twitter, Inc. names
3. Digital signatures on posts
4. Decentralized architecture for pub/sub and mirroring
Isn't Twitter.com too entrenched in its namespace and the web2.0 strategy of "owning the data" to serve as the pub/sub system we deserve? RSS/ATOM was a much better direction, in my book. Regarding 140 characters, it's maybe the main thing Twitter got right! RSS/ATOM post titles should similarly have a max recommended length, for the sake of client apps.
Keep up the great posts!
Current limit is 10
I achieve this now but its frustrating. I've found this a quick way to find people who write about stuff I care about.
Groups of people too is essential
Right now, Twitter is a noise machine, a radio signal broadcasting mess of 'hello', 'hello', me-me-me... there is no way of organizing the stream in real-time to extract the signal from the noise, 'yet'. Hashtags, Groups, verified accounts and future algorithms will help. But for now: follow the link and read the blog or website and the comments add to what Twitter is not allowing at the moment.
@buckybit
interesting. Of course you can delete it and repost, which might actually make more sense since the newly edited tweet would again enter followers streams & search results as fresh content whereas an older tweet that is edited may not be seen again by some/most.
For the most part, I think corrections can be made by just posting them and noting a previous post that was inaccurate. For the embarrassing spelling error or a wrong or missing hyperlink, for example, or just a poorly written tweet... delete and re-tweet because most will have already received it in their app/device (similar to some cases of RSS and blog post edits).
So their is only partial value in editing a tweet... usually a case of perfectionism (to the point of dave's post) and content aesthetics.
For journalists using twitter, I suggest using a private back channel twitter account as a repository for tweet drafts... Follow this account with your live public-facing account and re-tweet accordingly. You can use this private stream for notes, quotes, url references and your final approved micro-message which you can distribute to your followers by copy/pasting or if you use a nice desktop app like tweetie, just "repost" and remove any additional RT/via/@username stuff.
As for government officials, I don't like the idea of editing tweets and the aforementioned technical realities will make an edit moot regardless.
At the end of the day, "be careful what you tweet" or maybe rather... "you are what you tweet". sorry, could not resist.
Btw, to answer Dave's question of my most desired feature... Yes I look forward to Groups (I like that tweetie/apebits has decided to also wait on twitter instead of bloating their software with group functionality). Beyond Groups, I have concluded that their could be great value in evolving the Twitter Profile to become an actual micro-site of sorts... aggregating in various content (FriendFeed-like) and possibly even allowing for new longer form text and media publishing. Twitter could evolve opposite of FaceBook.... starting with the real-time micro-text-messaging and then user profile pages whereas FB started with the profile pages and added in the micro-message 'status' streams etc.
The last feature that will be interesting and I think we might see one day is 'Pay With Twitter'. That could be very very powerful and if I were Paypal, I'd be trying to be a deep partner now before Twitter implements their own micro-payment system. Twitter may not initially have it's own marketplace but it would be inevitable.
@sull
(this post has been edited ;)
This is a problem, cause most of my followers who speak in english don't understand portuguese. And I may lose followers for this reason.
I would like to let my followers choose if they want to receive my english, portuguese or both tweets.
Secondly, (as a developer) better API's for getting older messages (i.e. more than 200 at a time), and higher/no API limits for users.
Given I live in two different places my other wish would be allowing us to define a timezone override for individual tweets when we're outside our defined timezone in our profile.
There are fortunately glimmers of Steve Gillmor's long missed "track" functionality returning, which thrills me to no end though Dustin's version of Twitterspy has held me in excellent stead in the intervening months amidst the broader availability of search related tools for real time conversation. These days it would be great to have some of the not-so-old features like "search" to work properly (that is give results from more than just the last 8-15 days). Hard to think that the $15 million shelled out for Summize was really just worth this after all the intervening time!? I recall not so long ago that Twitter might even be a so-called "Google-Killer" when it came to search, but if they can only manage to search two weeks worth of tweets in real time, they've got some serious work to do. Perhaps before we go looking for more functionality, we should hope for the functions they've currently got to actually work properly in the first place.
Honestly, I'm just thrilled that they've managed to scale as well as they have in the last 9 months. I remember when failwhales were an hourly sight almost a year ago. Things still manage to get hairy in this regard if you just look at the backlog and some of the downtime experienced today with the millions posting nebulousness about Michael Jackson.
If I could, I would hope for some better version of Social Media Signal Processing so we might increase the signal above the noise caused by the influx of the millions who joined the service since December 08.
In short, let ME define my communities of interest and don't assume (quite wrongly) that I want everyone lumped into one, big pile.
As an example, if I have 100 followers and 30 of them are common for the @usertest, when i RT a tweet of his, just the other 70 people of my list will see the RT. Is that clear?
I believe that that could make sharing of thoughts, opinions, links etc more useful and less repetitive -- although I don't know if RT is exactly a core function for the most of people.