Comments on: No additional Twitter meta tags, please!

By: Hugo Reyes

Hugo Reyes — Mon, 14 Dec 2009 16:36:08 +0000

FAIL

There is only one path this concept will take. Next year we will see it

By: Die nächste Evolutionsstufe von Twitter: Twitterformats?

Die nächste Evolutionsstufe von Twitter: Twitterformats? — Mon, 14 Dec 2009 15:34:24 +0000

[...] habe damals für The Next Web International meine Meinung ziemlich eindeutig formuliert und stehe seit dem in einem kreativen Dialog mit [...]

By: Stowe Boyd launches Microsyntax.org « LocalLab : Foire aux Infos

Stowe Boyd launches Microsyntax.org « LocalLab : Foire aux Infos — Mon, 08 Jun 2009 19:21:53 +0000

[...] I’m sympathetic to arguments (and pleas!) against adding additional structure or formatting to tweets, I think that the bigger opportunity here extends beyond Twitter (which is primarily a public [...]

By: Nick Valuy

Nick Valuy — Mon, 01 Jun 2009 04:50:15 +0000

“Twitter” is an idiotic name. “Tweet” simply makes me puke.

Real time messaging platform is a great idea. But the name ruins it all.

By: @24z replaces @ralfrottmann — THE NEW 24100.NET

@24z replaces @ralfrottmann — THE NEW 24100.NET — Fri, 29 May 2009 07:18:18 +0000

[...] an attempt to further optimize the ration between meta information and content in my tweets, I’m migrating my Twitter account from @ralfrottmann to @24z, thus [...]

By: Microsyntax « (flotter Blogname wird nachgereicht)

Microsyntax « (flotter Blogname wird nachgereicht) — Thu, 28 May 2009 08:47:30 +0000

[...] mit Microsyntax verbundene Spezialsprache unschön und ausgrenzend zu sein (vgl. auch The Next Webs Post dazu) – mir fiel das kürzlich auf, als ich von einem generell SEHR online-affinen Kollegen [...]

By: nanoformats are dead, long live the microsyntax at notizBlog - a private weblog written by Matthias Pfefferle

Wed, 27 May 2009 18:51:02 +0000

[...] Prinzipiell finde ich die Idee ganz spannend und freue mich auf die erste Ergebnisse… und hoffen wir mal dass die zukünftigen Tweets nicht ausschließlich aus Meta-Informationen bestehen: [...]

By: Sure, let’s stuff more crap in Twitter messages — Shooting at Bubbles

Sure, let’s stuff more crap in Twitter messages — Shooting at Bubbles — Wed, 27 May 2009 07:24:53 +0000

[...] into something it was never intended to be – an Instant Messenger. I also have to side with Ralf Rottman from TheNextWeb.com when he says Don’t make me [...]

By: Ralf Rottmann

Ralf Rottmann — Tue, 26 May 2009 20:12:51 +0000

As Stowe pointed out in his reaction to our article (http://www.stoweboyd.com/message/2009/05/no-additional-twitter-meta-tags-please—the-next-web.html) he kind of untied his ideas away from Twitter.

Separating Twitter usability issues away from his (now) more general claim for an embedded microsyntax makes sense.

Adding a second field to any Twitter UI would IMHO kill what makes Twitter successful: It’s overall simplicity. 140 characters. That’s all you get.

For Twitter I’d still advocate to enhance the API and provide much more meta information per tweet. They should make those features publicly available for their dev community.

However, as I’ve outlined in the article I strongly believe they will keep this added value for themselves in order to evolve a rich tooling business model around those kind of capabilities – and finally start making some money.

In essence Twitter has become sort of a Network Operator. And like the Telco’s protected their walled gardens for so long, Twitter will do the same. The API limit is just the start.

We should start to thing about a truly open alternative. I’m open for suggestions and would definitely be able to contribute. DM me at Twitter. (http://twitter.com/ralfrottmann)

By: riffic

riffic — Tue, 26 May 2009 19:27:32 +0000

how about getting metadata OUT of the message, and into a separate field for that particular set of data? I’d love to be able to use descriptive urls again