Well, sure. It's your private data so it's behind a login. You can get a free application key which you allow you to programmatically download your information, eg graph.facebook.com/me/events /photos, etc. Every bit of data has its own URL, contrary to TBL's claims in the article. Authentication and authorization are orthogonal to the URI scheme.
Comments
I don't get the criticism "each piece of information does not have a URI". Has TBL not seen http://graph.facebook.com ?
I can't view that link because I'm not logged in to Facebook.
Well, sure. It's your private data so it's behind a login. You can get a free application key which you allow you to programmatically download your information, eg graph.facebook.com/me/events /photos, etc. Every bit of data has its own URL, contrary to TBL's claims in the article. Authentication and authorization are orthogonal to the URI scheme.
Is Apache hurting the way because you can password-protect URIs? Is "403: Forbidden" the 'evil' part of the HTTP spec?
I somehow don't think that, "this information requires a login," is the death of the web.