Sporkmonger

purveyor of fabulously ambiguous eating utensils

Web 2.0 Invitations

Posted by sporkmonger
Written October 27th, 2005

<rant>

Sir,

Because of your web interests and particularly the subjects you deal with in your web site, we would like to inform you about the launch of #####. ##### is a free downloadable application which includes for the first time search, management and sharing of information. Based on a pooling of user knowledge, ##### is in the tradition of collaborative services which have started to develop on the web, as shown by the recent launch of Yahoo's MyWeb 2.0. But contrary to tagging systems developped in its time by del.icio.us, ##### offers indexing of web users' bookmarks to overcome problems of language, synonyms and other syntaq quirks.

As an internet expert, we would be delighted if you could give us your advice on our service. As far as it's possible this will allow us to take account of any coments you may have for the launching of a definitive version. You are able to download ##### from http://www.#####.com.

Enjoy your visit and hopefully talk to you soon,

--
####### ######
CTO #####
http://www.#####.com

Alright, since this is no longer just an isolated occurance, I’m going to complain. Look, this whole Web 2.0 thing has gotten out of control. Totally. So I’m going to add my complaints to Joel’s.

There’s several problems here. Firstly, please don’t call me “Sir.” I just don’t dig it. I mean, really, I’m 23. In 23 more years, I still probably won’t dig it, but at least it’ll be more plausibly complimentary or respectful or some such.

Secondly, people are spamming me with invitations to test out faux-web-2.0 services under the mistaken impression that I will give them useful feedback that will help them to be better. Problematic. Definately. Well, in this case, the best feedback I can give is: “Please innovate. Social bookmarking has been done. More importantly, it’s been done well. Making a social bookmarking clone that runs through a toolbar and is more friendly to Spanish-speaking folk is not innovation.” But unless he’s down with scrapping the whole thing and starting to work on something else instead - a painful fact of life that sometimes we just have to face - well, somehow I don’t think he’ll appreciate that feedback.

Thirdly, the (badly implemented) clones are going to hit the point (probably very soon, if this one is any indication) where their sole competitive advantage is language. In other words, some random startup comes along and creates the newest “Web 2.0” (I already hate this term after having used it once or twice now) whiz-bang. But because they failed to make it easy to use in whatever language the reader happens to use, some other company gets a chance to rip off their whiz-bang, but with a Portugese version instead. And with the current climate, that could very well be fatal. I mean, it’s not hard to get volunteers to translate your interface for you. You just need users who are passionate. Heck, that’s what Google does in order to get their huge list of supported interface languages.

So, quick recap:

  1. I’m not an “Internet Expert.” I’m not even an “Internet Insider.” I like it that way. Theoretically, fewer distractions.
  2. If you’re going to send me an unsolicited email, please be reasonably sure ahead of time that I’m going to be interested in the conversation, because you’re interupting me. It’s just common net courtesy.
  3. And if you’re actually using this to generate your business plan, I am the wrong person to be talking to. Really.
  4. If you’re working for an actually innovative startup, please consider thinking about i18n, unicode, and all that jazz. Actually, do more than consider it. Just do it. Not everyone speaks English, and there’s no reason to restrict “Web 2.0” (there’s that involuntary shudder again) to English speakers. At the very least, don’t hardcode your interface strings. Leave room for i18n for later if you can’t fit it into version 1.0.

Thank you, now returning you to your regularly scheduled unrantiness.

</rant>

FeedTools 0.2.17 Real Soon Now™.

Tags: ,
  1. Written October 29th, 2005 at 12:21 AM
    ...please consider thinking about i18n, unicode, and all that jazz. Actually, do more than consider it. Just do it.

    Amen to that! I couldn’t agree more. The first thing I do when trying out a new web app is to submit (in a textare a or as a user name or whatever) some sample text in from the What is Unicode? page translations on the Unicode site.

    If it ends up converted into html escapes, for instance, I consider that a very bad sign about the coding behind the app.

    Not using Unicode these days seems just about indefensible to me.

  2. Written October 30th, 2005 at 07:38 PM

    I wonder if they weren’t trying to game you for a link…

    Also, love FeedTools and have a suggestion: what do you think of the idea of decomposing the content of the ‘Feeds’ table into two tables: ‘Feeds’ and ‘Entries’?

  3. Written October 31st, 2005 at 11:26 AM

    I’m sure they were trying to get a link, because, as far as I can tell, they already have a released product downloadable and useable by anyone (for sufficiently small values of “useable”). That’s partly why I removed all mention of their name. That and to keep them from getting too terribly annoyed if they saw this entry.

  4. Written October 31st, 2005 at 11:58 AM

    Oh, and on the feeds/entries thing, something akin to that will show up in version 0.3.0. Actually 0.1.0 did that, and there are some major problems with that, but 0.3.0 will move to a three table model. Instead of just feeds/entries, it will be feeds/feed_entries/feed_caches or something to that effect. The basic idea is to provide the tools for subscription management instead of just a caching mechanism.

  5. Written November 4th, 2005 at 07:40 PM

    Excellent news. Thanks for the clarifying that.

Leave a Response

NOTE: I'm afraid Javascript needs to be on in order to comment.

Comments should be formatted using Textile.

Ruby code should be enclosed within a <macro:code lang="ruby"> element. Other languages are supported. For output you can simply omit the lang attribute.