But it is literally unreadable to me. I couldn't finish reading the thread and had to find an alternative way out of twitter.
Fist trial, using my android phone with fennec fox. There is a modal that hides the content asking me to "log in"; if I close the modal I go back to the twitter homepage. Thus unreadable because I don't have a twitter account. Sometimes I have managed to read a few tweets by a "smart" combination of closing the successive modals and reloading the page, but not this time.
Second trial, using my laptop with firefox browser and heavy adblocking. I can read only the first three tweets, the rest do not load due to some third-party javascript.
No big deal. Third trial, now I open a "clean" firefox browser session with just ublock origin, and I manage to read about 30 tweets, until it starts talking about hyperbolic rotations. The thread obviously continues, but the sole link below it "show replies" does not work. When I click on it it says "Whoops! Something went wrong. Please try again!".
Typically I wouldn't bother and stop reading. Fuck twitter. But today I really wanted to read this thread because I teach these things. Thus I learned to use nitter, which gives an interface of twitter that, even if it's equally ugly, it sort of works (in that you can actually manage to read the text).
In retrospect, this is an extremely sad state of affairs. We have an excellent article which is made of a short text, a few simple formulas, and a few simple images. This could be a static html page of a handful of Kb with img tags. But it is a slow and humongous javascript monstrosity that does not even work, and may disappear at any time if twitter "bans" this user for reasons unrelated to this text.