Simon

Simon

See my reply to Doug's comment, but here is my thoughts on search and
hash tags.

I think they are great but still largely misunderstood as a search
tool when really they are better for sending tweets. For example, if I
send a tweet “vSphere rocks!” And you reply “@rbrambley bang your
head, dude!” I did not need to use vSphere as a hash tag to find it
later, but you did and did not use it because it was awkward. This is
common. So if we want to search “vSphere” my tweet is discovered but
the replies are not.

So, I agree with using a common hash tag for the event. That not only
makes it easier to track the entire conversation, but it also
registers, tallies, and trends our event tweets globally under a
single tag. VSphere is the best obvious tag, but personally I like 3
to 4 letter hash tags (makes 5 characters with the #) to allow for
larger tweets and RTs.

I've suggested #421 and #VMW yesterday on Twitter. Maybe we should use
#v12n? In fact that ties the virtualization community better for now
and all future tweets about anything or any event.

Maybe I'm over analyzing it? What do you think?

I am betting that all non VMware announcements will still contain
vSphere as a keyword, so my plan of using it as a common denominator
should pull a lot in from Google/Twitter searches.

For the Twitter side of things you could try and setup a keywork (hashtag) and spread the word so whenever anyone mentions the new release they put it in it? That way you could then use something like twitterfall.com or search.twitter.com etc to follow everyones tweets? Maybe something like #vsphere, that way you'll also get tweets that ppl mention it in but dont know about the hashtag.

Did that make sence?

Simon