I thought I had done a good job of explaining here: Google Wave API Google Group: Got To Undo The Ban On Me. But I never thought I was indispensable to the group. Although vision is a specialty all its own. And just like every Tom, Dick and Harry feels like he is an expert on politics, people think great coders are by extension also great visionaries. Not true. Some are, but it is not by extension.
I think I have come to my conclusion: I Did My Part. I will have to do in the blogosphere what I was hoping to do through this Google Group.
I have a feeling a lot of glass is going to be broken in the fight on the 3.0 definition down the line. Google Wave is not my baby. But the 3.0 fight will be my own.
I protested. I did my part. If the protests are not going to work, and the ban on me at the Google Wave API Google Group is not going to be lifted, I move on. I guess I will have to find out other ways to spot trends in Google Wave development. I am sure there will be several good blog options. We are at the early stages of seeing blogs dedicated completely to Google Wave. Maybe some of those bloggers will do the reading for me in those Google Groups.
A great way to follow an open source project is in the very open perhaps.
Einstein was attacked by some with anti-Jewish leanings. When a pamphlet was published entitled 100 Authors Against Einstein, Einstein retorted "If I were wrong, one would be enough."
The name is clear enough: Google Wave API. It is a group about Google Wave API. So if
you are going to post messages about viagra ads and Nigerian dictators who need help with money transfer, then you don't belong in the group. So I am not trying to argue it is my human right to belong to the group.
The initial protest was that it was a group for hard core code talk. I respect the sentiment. But there were numerous threads about spam, t-shirts and invitations to Wave. Noone seemed to have been bothered, bothered enough to protest and ban people.
The third thing I established was that code and community/culture are both on par, they are both important. You can not expect to have strictly technical conversations and still exp
ect to create waves with Google Wave. And then I offered to stick my vision, culture and community talk to one out of the 300 plus threads in the group.
Then they said, it is not what you are saying, it is how you are saying it. Why do you post links to your blog posts in this group? People who don't "get" links and blogs should voluntarily walk away from a group about Google Wave development.
The slam dunk was I said but my primary interest is in code talk. That is why I joined the group in the first place. I wish to follow all the code related conversations so I can spot trends in Wave development over the coming months as we prepare to unleash Wave upon the world.
Google has had a blog search for a while now. But it has stayed away from Twitter search for too long. I am glad finally they are doing it, because nobody else is.
Google to Launch a Microblogging Search Engine Google prepares to launch a service that indexes and ranks content from microblogging services like Twitter. ...... Twitter's search enginehas two important drawbacks: it's limited to Twitter and it sorts the results by date. While there are other search engines like Tweefind that try to sort Twitter posts by relevancy and search engines like Twingly that index multiple microblogging sites, none of them does a great job. ...... will sort the results by relevancy
About time this happened.
My expectations have been low. I want to be able to find everything I ever tweeted. Is that too much to ask? Has been for the native Twitter search engine.