I still live on Twitter, even if they occasionally go and break their API without warning. Which is kind of what happened yesterday. Users of a few different clients ran into an issue where they could receive tweets, mentions and DM’s all the day long. Posting? Different story. Twitter threw back a 411 error–which, just for the record, does not mean what Twitter would like to think it means. I’ll let you know what that is when Twitter lets me know. No one has any idea just yet how to fix it. But like that’s stopped me. So late-ish last night, I put together a vaguely quick attempt at fixing the issue. It involves an entirely different–and yes, supremely simple to use–program and, for those who need it, support files for the screenreader I use. You can download the zip archive of both the program and the scripts for JAWS for Windows from over here. Instructions on how to use the program from the perspective of a visually impaired person are right this way. If there’s a question that isn’t answered here, feel free to come find me, and I’ll see what I can do. In the meantime, happy breaky day!
The basics of what Twitter ate, and how to work around it.
- China says it’s a lie. that’s all the evidence I need.
- If you own an M1 Mac, I’m a little jealous and a lot sorry.
- I would absolutely love a self-driving car. It won’t happen in my lifetime.
- Ontario votes Not The Liberals, again.
- Ontario doesn’t do accessibility. Also water is wet.