The Twitter API still works, with some serious limits. Not easily incorporated into products, but useful for individuals with developer accounts. Not an insurmountable hurdle, it seems, though I was a developer from before. A few bullet points.#
I was confused about the status of the Twitter API, but it turns out it's still there, and there is a package that connects to it for Node apps. #
It took me a few hours to add support for Twitter in my textcasting server app which is how my software connects to all the various services. #
I should probably add a plugin abilitiy for textcasting so that other services could easily be added, without modifying the core app. Totally doable. It's already factored that way internally.#
I should probably write some docs for it too. 😄#
Anyway, the deal with Twitter is that it's free for up to 1500 posts per month, as I read it, which seems manageable for one person (me), but no way is it enough for a community of users. #
Why connect to Twitter? People are there. Until they aren't we're going to need a way to push stuff to Twitter.#
You know those obnoxious sites that pop up dialogs when they think you're about to leave, asking you to subscribe to their email newsletter? Well that won't do for Scripting News readers who are a discerning lot, very loyal, but that wouldn't last long if I did rude stuff like that. So here I am at the bottom of the page quietly encouraging you to sign up for the nightly email. It's got everything from the previous day on Scripting, plus the contents of the linkblog and who knows what else we'll get in there. People really love it. I wish I had done it sooner. And every email has an unsub link so if you want to get out, you can, easily -- no questions asked, and no follow-ups. Go ahead and do it, you won't be sorry! :-)