Why Facebook's 'Frictionless Sharing' violates HTTP
Sorry, but this really feels like hyperbole to me. For two reasons:<p>1) Before any action is shared back from the site to Facebook, the user has agreed to authorize that site (application) and add it to their timeline. Part of that dialog shows what's going to happen (<a href="https://developers.facebook.com/docs/beta/authentication/" rel="nofollow">https://developers.facebook.com/docs/beta/authentication/</a>).<p>2) There are plenty of other examples around the web where submitting a HTTP GET request results in an action. For example, clicking an up arrow on Hacker News submits a GET request which increases the karma score on another author. What becomes more important is how you protect against XSRF and crawlers not accidentally changing state within your app.