Wednesday, October 27, 2010
Free Speech Costs Exactly $105
This is just so unbelievably broken. Why is there a requirement to register anything in the first place? Apparently, this was done so that the rights holder can find the contact information of the person who handles DMCA requests without too much work. This could have been satisfied a far simpler solution: require that the contact information to be available on a well know URL (e.g. /dmca-contact) for the site to be compliant. But of course, the lawyers making the laws would have no idea that would even be technically possible.
This kind of stupidity just increases my belief that copyright is hopelessly broken and cannot be fixed.
Tuesday, October 26, 2010
More Twitter OAuth Stupidity
Twitter uses the OAuth consumer key to identify client applications. Now they've gone a step further, and are revoking the consumer keys of open source clients that fail to adequately obfuscate the key in the source code. Twidge was disabled yesterday. It was fixed a day later after the developer modified the source to comply with Twitter's requirements. So far, I haven't heard of any other open source clients having problems.
I don't know what Twitter hopes to accomplish with this ridiculous obfuscation requirement. Even if the key is hidden in the source code, it's still available to any one who examines the code. Does the requirement apply to closed source clients? In the above article, the author extracted the consumer key from the binary of the official Twitter Android client. Anyone want to bet it hasn't been fixed?
Wednesday, September 8, 2010
Book Burning
It bugs me how everyone is focusing on the fact that it's a Qur'an that these ignoramuses are planning to burn. Burning any book is just wrong. It doesn't matter whether it is a Qur'an, a Bible, a science text, or Anne of Green Gables. And yes, I'm sure there is a nutter somewhere in the world that might find Anne of Green Gables offensive.
Makes one glad to be human doesn't it? (/_;)
Thursday, September 2, 2010
How Not To Use OAuth
The OAuth protocol avoids the problem of giving your credentials to third party client applications and web sites when you want them to access your data on another site. Twitter is an example of how not to use OAuth.
It seems the genii who run Twitter require client software identify themselves with a consumer secret and key, which has to be embedded in the application somehow. Obviously, this is huge problem for open source applications, since it is impossible to obfuscate anything when people can see the source code.
As the article points out, the OAuth RFC actually recommends against using the consumer key protocol to identify application as Twitter is doing. Isn't it great when companies ignore standards for the sake of their own business goals? ^_^
Wednesday, August 4, 2010
Another Useless Poll
Saturday, April 10, 2010
Links? We Don't Need No Stinking Links!
I wonder how long before they notice the traffic to their site has plummeted. I googled for "japan nikkei newspaper" and didn't get a single result going directly to the newspaper's web site. Makes sense, otherwise Google would have to get permission for any links before it could show them to me.
I'd provide a link to Nikkei newspaper, but... ^_^
