Twitter updateTue, Mar 27, 2012 at 10:04PM
For the past hour, I’ve been looking at the page source for composing tweets. What Twitter has set in place means I won’t be able to pursue this route any longer: Twitter’s JS checks if the page is served from their servers. I it’s not, then it won’t let updates through. Unless I use userscripts (which is hack-y, and the page takes just as long to load) I can’t privately do anything, so the API is going to get used.