All Google has to do is ban scalping of the tickets. You buy a ticket, YOU get in, not the holder of the ticket.
How would one implement that while maintaining the ability for a business to decouple purchasing a ticket from the decision of which member of a development team gets to go?
Under which section(s) of the Sherman act?
For anyone wondering what postbigbang is referring to by "reduces yourself to their level":
That's why you need multiple layers in your transmission. The obvious signal should be a long, slow count of all of the prime numbers up to some arbitrary cut-off, like 9973. Then the transmission should repeat. This will give the aliens a strong clue that you're operating in base-10. Then, layered in your transmission - perhaps in a side channel, or by having different signals in amplitude modulation, frequency modulation, and polarization modulation, you can give multilayered information.
The next-most-obvious signal in your "palimpsest" should be a primer of some sort. This is where you can build basic mathematic, chemistry, etc. — ultimately building up to the detailed instructions for building a device the aliens can build that will transport one of them through a wormhole to talk to her dead father.
That should do it.
...the absence of Flash.
That would be true if we were to use this display for the uncreative purpose of displaying whatever threat-level the DHS is currently at.
I would pay for a display like this. Back in 2004 I had to resort to using the various colors of the dry-erase-marker rainbow to create a threat-level display on the whiteboard in my office. Back then my team's product had a memory leak somewhere in it, and nobody believed me. The servers would be up for a handful of days, and then just when everybody was lulled into a false sense of security we would get a flurry of random OutOfMemoryExceptions as the whole thing would sieze up and become unresponsive - pulling system administrators out of their scheduled meetings to conduct emergency rolls in a panic. And then, back to business as usual.
At first I was alone in suspecting a leak. Back then we didn't have any memory monitoring in place so it was all thruthiness from my gut. But worse than being alone in my suspicions was the sinking feeling that the leak was proportional to user load, which was on a steady incline with no sine of abating. So over the course of a few months - while everybody went about their business of making sure to only work on things that could be billed to client project numbers - the frequency of emergency rolls steadily increased, and I kept elevating my threat level in response.
"What's that on your whiteboard," some would ask. I would explain that a shitstorm was on the horizon and that we had better take some time to find and fix the memory leak even if it meant taking a hit to billable hours. "Leak? What leak?"
By doing this I got a partner onboard who put some hand-rolled memory monitoring in place using JFreeChart to plot the decline. "See...a memory leak!," we would insist. "No, no," said the best and brightest of our software engineers. "It'll pick up," he continued, suggesting that maybe I didn't really understand how the garbage collector worked and that maybe it merely needed to fall below some threshold before it kicked in.
And with that, I once again elevated the threat level, and kept elevating it until it hit the top. Eventually we got to the point where one out of four nodes in our cluster was always in the process of being rolled, with users spilling over to the remaining 3, and one of them would crumble just as the 4th node was coming back up.
We eventually discovered a dubious use of ThreadLocal in the old version of Xalan (the pre-xsltc version), and fixed the problem by upgrading the library. But without the threat-level indicator in my office, I might never have gotten attention to the problem before it was too late.
I'll pay $200 for one of these boards. And I want all of the colors, damn it.
How is it not the 4th model of the iPhone? There was the original, which spoke the 2.5G Edge protocol, then there was the 2nd one which spoke a 3G protocol, then there was the 3rd phone - the 3GS - which added a faster processor and video recording, and now there is the 4th phone, dubbed the iPhone 4.
...half a billion priapic pop-ups in China.
So diamond is no longer the hardest [material] known to man?
It hasn't been for quite some time now, but the myth lives on. It was the hardest "naturally occurring" material until this discovery, apparently.
Reading sometimes helps.
There's an app for that.
Entropy requires no maintenance. -- Markoff Chaney