Apparently, Twitter requires RFC 3986-encoded URL params on their API. Didn’t know that and that’s probably why it was failing! https://tools.ietf.org/html/rfc3986
Just checking if posting this causes a deadlock!
Actually it didn’t because it didn’t POSSE correctly to Twitter. There seem to be some beautiful things about the Twitter API that make this fail once in a while and I haven’t yet discovered why.