.

My original article “Why Twitter is the Backbone of Web 3.0” was too long. Lemme simplify.

Round 1: Make a Twitter client that duplicates the functionality of Facebook, but in a massively-distributed way. ie. Make the Twitpics and YouTubes and Audio Streams all show up in the interface right in the feed. This is easy to do, and with competition should provide lots of reasons for Facers to move on over. Make it work with ONE LOGIN.

Once you solve that….

Round 2: Change the Way the Web Works.

• I wanna log into my computer once a day. I don’t ever wanna log into yours.
• This means no joining “networks”. This isn’t 1984 — We have an “Internet” now.
• When I send a message, I want it to be instantly available to all my friends in its original form.
• I don’t wanna type in a URL or paste an embed code ever again. Grab and send, receive and forward, NO CODE. Icons OK.
• I don’t wanna visit your static web page. TMI. Waste of bandwidth.
• I’d rather depend on my web client and my network of friends to filter your tweets.
• I wanna be able to quickly clip and re-assemble a media presentation from streamed web content right in the client/browser and “tweet” it.
• My client should automatically unpack my friends’ tweeted multimedia presentations, filtered how I desire.
• A “tweet” is the atom of Web 3.0. It consists essentially of 1) a link to a presentation file, 2) a text annotation, and 3) links to security keys at both the source and the forwarding “tweet provider”.
• A “presentation” is analogous to a “web page” of the next generation. It’s a loose container of web clippings, all pointing to the original source files, with instructions for clipping and (optionally) reassembling them.
• On the receiving side, I want the option initially just to see tweeted content elements in my browser, sorted how I like. (ex. only photos and annotations arranged in a Facebook-Feed-style layout.)
• But if I’m intrigued I could gesture to see more of the presentation. It may resemble an adhoc “web page” presentation, but it could also show up in my client simply as media elements separated how I like too see them.
• There are no “play/pause/stop buttons” to fuss with in the presentation. Redundant. Just use the keyboard or operating system controls.
• In general, interacting with web pages is old news. Rather than managing back-and-forth and URLs, browsers will become more about tagging/filtering, presenting/tweeting, and just socializing.

Comments? Questions?