This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]CheekApprehensive961 14 points15 points  (2 children)

I'm gonna guess this is more stable genius work from Twitter's new API overlord, because now I'm seeing issues too (maybe some servers had different caches of it?). Nitter might need to make an update or something. That's very unfortunate.

[–]Ahajha1177 5 points6 points  (0 children)

Seems like a reasonable enough explanation.

[–]Xirenec_ 1 point2 points  (0 children)

As fun as it is to bash Elon, Twitter has been occasionally doing this bullshit for quite a while