-
Website
http://staynalive.com/ -
Original page
http://staynalive.com/articles/2008/05/03/why-i-hate-the-twitter-syntax/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
Jesse Stay
566 comments · 71 points
-
MariSmith
5 comments · 20 points
-
brianjesse
6 comments · 4 points
-
Benjamin Golub
5 comments · 30 points
-
partywedo
11 comments · 3 points
-
-
Popular Threads
-
FriendFeed Turns the Twitter Firehose Back On
2 days ago · 5 comments
-
A Christmas Story: OpenID, OAuth, My Home, and Your Privacy
1 day ago · 2 comments
-
FriendFeed Launches Status Update Sync to Auto-update Facebook
1 week ago · 7 comments
-
Cinch Enables On-Site Recording of Audio for the Stream
2 days ago · 2 comments
-
Just in Time for the Holidays, FriendFeed Becomes First OAuth Wrap Provider
1 week ago · 6 comments
-
FriendFeed Turns the Twitter Firehose Back On
I remember reading about this elsewhere and I believe the answer that somebody else came up with was that the @reply
symbol came into common usage on the Gawker networks with the commenting system. (I could be wrong)
The non-standard practice may have originated elsewhere but I saw several mentions from longtime gawker commenters
that after a short incubation period of using the @reply visual function (as this is a visual function
created only by the human brain and not translated by software by any means), the community started to develop
grease monkey scripts to ease the use and readability of the commenting system and thus including the @reply format
as code that could be parsed by the script. I could be making wild speculations here, but it may give you
some insight and a lead into the information that you were looking for.
Second answer - IRC vs txt.
I am making another speculation here based less on fact and more on just what I know of certain services. I think
that your second query revolves around terms such as SMS and '140 character limit' and Service Providers and
not needing to install any software on the client side mobile device. I believe (speculation again) that the
developers of this particular social app may have asked themselves questions about how to integrate mobile devices
into the loop of communication without installing any client side software. What would be the most universal?
I think that asking these questions may lead us into the information that helps clarify your confusion as to why
-- as to why twitter had come to evolve as it had -- Instead of IRC evolving in its place.
(sorry for the disjointed post, I can never see what I am typing once my characters reach your "recent
visitors window on your sight, and the text never autowraps while I am commenting)
turning certain statements made back upon themselves thus either slighty damaging your credibility or ego, or both
I have, of course, chosen *not* to take advantage of this. However, if there is somebody following your blog that does not like you, they may jump on the opportunity you left open with this post. See @vaspersthegrate for more info about blogosphere warfare. ;)
If you would like to know more about the vulnerabilities that I noticed, feel free to contact me and I would be happy to let you know in private so as not to call them out in public.
In Twitter, where your potential pool of pingers is the whole site, you could very easily get spammed up and miss replies you really should have seen, if someone's plain username were enough to ping them, especially for a username that's a common word. I do think it wise to make attempting to get someone's attention a deliberate action.
From that standpoint, switching usernames with trivial commands makes no sense, and '/msg username message' is, if anything, considerably worse than simply 'd username message'.
Twitter's command structure is simple and focussed. That's all it needs to do. Expecting it to be a clone of IRC simply because some people are using like like they used to use IRC is just foolish. I would be surprised if the majority of Twitter's userbase has ever used IRC, and if Twitter had, for some reason, chosen to use IRC-like commands it would be just as much a learning experience for them as the current set.
This is somewhat like complaining that a random text editor doesn't support EMACS commands, because you're used to using EMACS. The world does not pick conventions simply to suit your personal needs.
But why shouldn't a different type of service choose their own conventions? That's what happened with the '@user' convention, which coded support was added for only after people started using it themselves.
Twitter is not IRC, 2.0 or otherwise, and its command syntax fits better than using an odd subset of IRC's would.
I was an avid IRCer on undernet back in '94 - '95 and met a lot of great people in Utah that are still RL friends. Now in 2008 I'm finally getting back into social networking on the internet.
I'm glad Twitter is not just another IRC platform. I like that it's archived so doesn't have to be realtime, that it has basic threading, and you choose who you listen to. I can't really see myself spending a lot of time on IRC again, but for some weird reason I don't mind using twitter.
I still don't like the @ style messaging though.
Here's the url: http://projects.friocorte.com/twitter-irssi/
Cheers,
Clint
You can only see it at night, but you can have a msg posted there by 'd xmlabs '.
Have fun with it (and be good ;)
-mp
-mp