"nitter.net was hit by a large bot attack which has caused weird rate limiting. Please use another instance." [1]
[1]: https://github.com/zedeus/nitter/issues/740#issuecomment-132...
Though the problem with these national instances may be distinct, the main Nitter.net instance hasn't been working since October 25th apparently. This same issue (no tweets show up) remains today; I've experienced this bug for the past few weeks.
https://github.com/zedeus/nitter/issues/707
Musk announced his intent to deprecate the old Twitter API, which Nitter relies on, but it's unknown whether it's been done, or if it has anything to do with this (Nitter issues predate both the deprecation announcement, and, actually, Musk's takeover, though Nitter.it is only offline since recently).
I like that it is just an nginx response. As if the web server is the lawyer.
Could someone explain what nitter is?
Nitter.ca is also down. I wonder if Twitter is bent out of shape.
You can connect to nitter.net but all account tweets seem gone.
Another backup solution is https://rss-bridge.github.io/rss-bridge/ which can allow you to bring RSS feeds and a ton of other sources into your RSS reader. Couple this with libredirect add-on in your browser whenever you want to see more info.
I've got my own instance, and since the code is open-source everybody can run their own. Who has interest in keep playing this stupid whack-a-mole game with open-source software that anyone can run?
Everyone needs to run their own instance. It isn't hard.
nitter.kavin.rocks worked for me
Must be that freedom I was missing.
undefined
undefined
Instance status aggregator:
https://xnaas.github.io/nitter-instances/