Google I/O announced for June 25-26
plus.google.com
plus.google.com
Still can't say I'm surprised about either point. They were clearly stuck for material for that third day and I heard definite noises about them sharing the concerns some of us voiced about the attendee demographics!
Frankly the 2013 keynote was a tad embarrassing too (without the giveaway the mood in there would've been a lot more skeptical - my row were amazed by how bad a lot of the demos were), so I wonder if they're going to tone that down.
And... I wonder if such a lottery system would help take on general ticket scalping. (I could see a lottery mechanism doing some kind of 'real person' verification.)
1) No feeling of "I missed the 2 minute window"
2) No feeling of "I couldn't buy it because your system was down"
I mean it still sucks for people that can't make it, but want to go, but at least everyone at least gets a chance this way.
Actually, last year they implemented some kind of IP-based persistence for each potential attendee: you could try to get on queue for a ticket on your smartphone or laptop and every time you access the timer did a reset.
There were not as many talks on the third day, and they were the less-interesting ones. The demo pit had been completely dismantled and removed overnight after the second day's program had ended. There was a box lunch instead of a hot lunch like the first two days.
I wound up leaving halfway through day 3, instead spending the afternoon looking to explore SF a little and get a couple beers.
I'm surprised this hasn't been mentioned yet, especially for the HN crowd, but it's relatively easy for any developer to write a bot to auto-register them-self. One could even use Selenium.
There is a very popular Google Developer's MeetUp and space for 200+ runs out in less than 5 minutes of unannounced meetings opening up for registration. I am 100% sure that a lot of bots can and do register for these events.
Well, I'm not completely sure if it is that easy. Last year they had a first queue to get a ticket which did reset every time you opened a tab in your browser or entering via another device. After that, you had another queue to access your personal data, and finally you needed to use Checkout for buying the ticket. Not sure if they're going to do the same, but I'd love to hear some kind of programming challenges to get yours.
While the sessions are available as video streams, the sessions and discussions in between the sessions are not. I was at I/O last year and I not only had a good time, I also learned a lot during the three days.