A stupidly round-about way to get Twitter client data

Back in July, Twitter took away the ability to see what client was used to post a message from the tweets they displayed on their web client. This was widely assumed to be part of their plan to suck all the oxygen out of the 3rd party client developer ecosystem (but to be honest, I think it’s probably just a sensible U/X decision.)

I didn’t know this, because I mostly use a 3rd party client. So this is the crappy workaround I just came up with.

Of course, if you’re the kind of person who cares about the originating client, you’ll be using a 3rd party client. Twitter’s own Tweetdeck still displays client data.

Blog comments powered by Disqus