It stops working once the actual X accounts used to harvest the data hit their weekly limits.
The real X accounts used to be a fallback for when guest API access wasn't working but now they're the only reason these instances work at all. The reason why Nitter is dead is guest API access was shut down.
Once those actual X accounts have their limits restored, the instances will start working again until they hit the limit once again.
Try this. This nitter instance worked for awhile, stopped working and now works again - until it gets clobbered by tptb again.
https://nitter.poast.org/a_newsman/status/1762910441976549449
It stops working once the actual X accounts used to harvest the data hit their weekly limits.
The real X accounts used to be a fallback for when guest API access wasn't working but now they're the only reason these instances work at all. The reason why Nitter is dead is guest API access was shut down.
Once those actual X accounts have their limits restored, the instances will start working again until they hit the limit once again.
Thank you for that explanation. I had no idea of the mechanism behind this on-off-on behavior. Makes sense.