The part about using "Accept" headers instead of "/v1/" links really threw me for a loop. The APIs I've come across from major applications (e.g. Twitter, Foursquare, Instagram) all have versioning in the link structure, not in the "Accept" headers. I understand that this post is supposed to highlight what REST APIs should do, not what everyone should do, but the author's emphatic insistence that "THIS IS BAD!!!!!1" leaves me confused as to what the proper method is.
If they increase the volume of the audio signal, would that do much to increase the range? It would be awesome if someone could use this technology at a range beyond NFC... for example, using it to hack together a pseudo-mesh network inside a subway car.
Am I the only one bugged by the quote "This legislation is a serious threat both to Facebook’s business in California"? A serious threat both to Facebook's business in California and... what?
For those of you that have Firefox 4, it might be fun to play around with the new "-moz-element()" function that allows you to embed one (or more!) html elements as a background image, using this to create a series of prime-spaced overlapping colors.
This is awesome. You know what would make this super-awesome? Being able to filter by keyword. Though they're probably already filtering down the tweets or else the map would be a complete mess.