Everything relevant to the reader is captured by the twitter post of the developer. What does macrumours, or the verge from an earlier post, add?

Twitter recently completely blocked js-free viewing, it's never ideal.

I just read the tweet with a text-only browser that does not process javascript, using an "approved" User-Agent string.

Really? Until a few months ago I used to visit twitter links in FF w/noscript blocking js, it would just divert me to "classic" mode.

This is what happens currently in FF:

https://pengaru.com/~vc/tmp/twitter.png

Maybe they've stopped supporting my version of FireFox on Linux, and I've wrongly assumed it's strictly the lack of js? I'm not sure if that's any better... since this browser is perfectly capable of everything needed to view tweets.

I never used a popular browser to read tweets in the past. I was using mobile.twitter.com leading up to this change; this is no longer possible. AFAICT what has changed is that they are requiring an "approved" user-agent string. Someone here on HN tried Googlebot and it worked. I just tested it and it is still working. There are other strings that work. You definitely do not need javascript to read Twitter.

> Someone here on HN tried Googlebot and it worked. I just tested it and it is still working

Was there an HN thread regarding this change that I missed?

Thanks