SAPPHIRE08: some stats

by admin on May 23, 2008

in Asides,General

Summize: 240 Tweets with #sapphire08 tag (less than I would have thought)

Technorati: 18 blog posts (way off the mark)

Eventtrack: 4,484 items including photos (but that includes duplicated items coming via places like FriendFeed)

Flickr: 176 (way off as well)

Picasa: 279 (all Gregor by the looks of things)

All of which goes to show that tagging and search are still nascent arts.

Comments have been disabled for this post.
Sort: Newest | Oldest

Dupes definitely annoy me. :(

@Dennis :-) so you think the "dupes" are that major of a turn off? I saw them as annoying but not a major joykill - now has my top priority.

@craig- you already know that I believe Eventtrack rocks. The point is that most trackers don't get the dup stuff and are failing to filter so that enterprise peeps see true value.

SDN posts are actually in the Eventtrack stream, I used the bookmarklet and AIR app to add them directly.

Eventtrack is also working to deal with the duplicates from Friendfeed, Hashtags, Twitter and Tweetchannel - this event has 859 items in this category so rough analysis you could say just divide by 4 and it still looks like Eventtrack is the most extensive in terms of aggregating the social objects around a given tag.

SDN posts are actually in the Eventtrack stream, I used the bookmarklet and AIR app to add them directly.

Eventtrack is also working to deal with the duplicates from Friendfeed, Hashtags, Twitter and Tweetchannel

You can be sure someone at SAP is doing the analysis. <lol></lol>

I have about 5 posts sitting in live writer waiting for some polish. It has been pretty busy since returning from the event.

I also suspect that posts on SDN don't show up on that list.

It would be interesting to compare those statistics to another event with a web20 focus just as a comparison.

regards,
Nigel

Hi Dennis,
more pictures to come. Have to find out how I can tag them all with SAPPHIRE08 at once like Flickr allows to do.

Regards
Gregor

Previous post:

Next post: