Today's Most popular News

Source:CenterNetworks

Video messageboard application Seesmic appears to be entering the video blog comments game today. I suggested that Seesmic should get into this game last month (Loic, for the check, please spell my name Allen). Video host Viddler seems to be leading the video comments charge and currently their plugin works with Wordpress.

The new Seesmic video commenting system is live on Techcrunch (one of Seesmic’s investors). Here is a screenshot from a post on Techcrunch:

Unfortunately my video camera isn’t unpacked yet so I can’t test it. Michael Arrington from Techcrunch commented last week that he has a lot of trolls and losers who comment on TC and that he spends an hour every day removing comments. What will it be like now that there will be video?

I am guessing that if you post a video comment using the Seesmic plugin, it will create a thread in the Seesmic application. Will video comments help save Seesmic? Perhaps it will help as I’ve suggested before that I like the idea of being able to contribute in the fashion you prefer on a blog (audio, video, text). With Loic’s smile and charm, I am sure that many blogs will install the plugin which will lead to greater visibility for Seesmic. As for the Seesmic app itself, I still struggle as to why video is a better medium for a messageboard than text is.

Partner Links
– Web Jobs
– NY Tech Directory
– CenterNetworks LinkedIn Business Group
– CenterNetworks Facebook Fan Page
– Purchase an Apple iPhone

Source:CenterNetworks

Early this morning Orli Yakuel who runs the Go2Web20 startup directory had all of her direct messages (aka private messages) on Twitter exposed to her 600+ followers. Michael Arrington has a good recap of the issue on Techcrunch. The instant that I read about this trouble I thought it could be one of the large number of third-party apps built on Twitter’s API. Arrington has since updated his recap to note that it looks like it was a third-party app, GroupTweet that caused the direct messages to be shown to the public.

In this case, everyone seemed to immediately blame Twitter for the issue. As more platforms (Twitter is a platform) launch and more applications are built on top (e.g. Twhirl, FriendFeed, GroupTweet, etc.), we will need to determine methods and techniques to determine when the issues are with the platform and when they are with the application. By default, that isn’t an easy proposition.

Furthering the issue and making it more complex is the issue of installation and updates. For example, you install x app to work with Twitter today. You read the terms and are satisfied so you install. A couple of weeks go by and you are bored with it so you leave and move on to the next one. When the first app updates, you may get hit with the updates and not even remember that you installed the first app and blame the issue on the second app or the platform. See how complicated this can get? Where’s Columbo when you need him!

Here’s a startup idea: a tracker for Web apps that you’ve installed and their current status (installed, active, not active, deleted, etc.)

Of course with all of the issues Twitter has faced, I can see why the immediate blame went to them.

This entry was posted on Wednesday, April 23rd, 2008 at 8:00 am and is filed under TechCrunch, twitter, Insights, API. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.