The Twitter account for this site was locked. I logged in and got this cheerful message:
We’ve temporarily limited some of your account features.
What happened? In order to make sure Twitter is as safe as possible, sometimes — like now — you may be asked to confirm you’re not a robot. Easy, right? Just complete the following to get back to the Tweets.
What next? For full access, please: [p]ass a Google ReCAPTCHA challenge.
There are a couple of funny things here. I’m sure you picked up that em dashes aren’t supposed to be padded with spaces! This is an affront to typographic style, convention, and taste. What’s next, people using three full stops instead of an ellipsis? Rarely do I ask here for people to think of the children, but I’ve even slipped into passive voice here given how overwhelmed I am at this dashed misapplication. This cannot—and must not—stand. Hey look, em dashes used correctly!
But also, this Twitter profile is fed from an RSS feed, so it isn’t human. Having a human manually tweet each time I write a post would negate the point. I know, they want to know a human owns it and it wasn’t just randomly generated. Still, the fact it’s been around since 2008 and had a human post to it a bunch of times should have demonstrated that.
Thanks to everyone who emailed and tweeted me about this, it should all be good now.
I also need to figure out how to get IFTTT working with Mastodon. I set up a pipeline but I don’t think it’s ever worked.