I had, apparently, blocked from my memory the fact that Twitter, Facebook, and probably every other place in the world requires OAuth these days. OAuth requires, unless I'm missing something, two things: the user to sign in via the service's website (inconvenient but not impossible), and place for the service to send the oauth_token and oauth_verifier. And there it gets awkward. Pumpkin Spice isn't supposed to be dependent on anything the user isn't a customer for (other than the already-existing networks). So who manages that token and verifier? OAuth2 gets past this but Twitter, at least, doesn't allow user-level posting from OAuth2. Maybe screen-scraping would be more effective. Page created: 08 November 2014 |