Hmm, to be honest, I did expect a little bit more after waiting for three(!) months now …
The hype seems to have settled. Now I hope that Google can come up with some more details to their API soon, so developers can start building interesting tools for this new ecosystem. If they wait another three months, I guess it will be too late.
There is also an early API written for Node.js providing profile information and a user's posts as rss/atom/json (also available as npm package): https://github.com/fhemberger/googleplus-scraper
It's still read only, though – haven't seen anything writing back to G+ yet. All approaches to share/crosspost rely either on monitoring your public posts or sharing posts with a special bot user, which is linked to other services like twitter via oauth.
So for the German data protection authority it's fine that all european flight passenger records and all direct debit transactions are transferred to the US because of the "international war on terror", but Facebook's "like" button is a severe privacy issue?
I think it's an important point to keep in mind, and honestly I don't understand why Google "by design" refuses to perform at least an automated test for extensions.
BTW: Awesome Screenshot has already disabled this behavior with the latest update.
Looks interesting, but after activating Native Client, I just see a black box in Chrome 15.0.849.1 dev on OS X 10.6.8 – anybody else has that issue? Or do the games only work on Windows?
Hmm, why aren't they joining forces with identi.ca and pushing an already existing service (with a small but existing user base)? There would have been so much room for improvement, instead, they create YATC (yet another twitter clone) from scratch, without any backup from an existing community …
I really don't think that they can compete with twitter this way. Let's see how this will evolve.
Still seems to be a bit much code to write for a single test compared to other testing frameworks (e.g. nodeunit on the server side or QUnit for client scripts).
The code coverage check is a nice feature - are there any other testing frameworks around supporting this?
Why build a clone instead of creating something original?
Oh, it's a “social media advertising startup” ... $$$
Now the Grupon hype is over, people start copying other things. I think it's time for some more original concepts than just clones, copies and meetoos.
Of cause, most Google+ tools will become obsolete by the time Google releases the official API. On the other hand, getting into it is a typical nerdy approach, that I love: Play around with the newest toys, see what can be done with them.
Personally, that's what drives me in this case: Learn something new, do some creative coding (without having to invest too much time like working on a 'real' project), provide something useful for those, who also already tamper with it, have fun. And maybe we stumble upon a useful idea, which can be extended, once the official API is out.
As you already have the link to one site spreading your pirated app, I'd contact them and ask them to remove the link. Sure, this won't stop the pirates (or other folks sharing the file on other platforms), but it's worth a try.
Of cause, it would be interesting to see how many people are using the pirated version of your app, if it can be achieved with little effort.
The hype seems to have settled. Now I hope that Google can come up with some more details to their API soon, so developers can start building interesting tools for this new ecosystem. If they wait another three months, I guess it will be too late.