Nitter.net rate limited
ParamoreFan opened this issue · 24 comments
When I try to see replies or search that's when it happens
Same here. I don't know what the real problem is either. Either way, there are other instances of Nitter that still work and you can find them here: https://status.d420.de/ . If I had to take a guess, I thought Nitter was supposed to switch instances when one got limited, so maybe something broke there.
Every instance I've tried so far returns the "rate-limited" error when trying to load individual tweets. Only profile feeds work.
EDIT: found some that work
Even if I use the instances at https://farside.link/, they are all rate limited.
So this is why when I visit user profiles on nitter, it only shows 1 tweet? nitter.poast.org looks to be fully working.
The guest account creation method stopped working yesterday at 6:00 UTC as well...
Not sure if it's the same for everyone, but my instance got DDOSed starting this night. I don't know if it was a bad actor or just some researchers trying to scrap Twitter. I has to apply a ratelimit to stop them.
Uh oh:
https://www.eff.org/deeplinks/2024/01/save-your-twitter-account
https://www.vanityfair.com/news/2023/07/elon-musk-latest-twitter-meltdown
That second link is from 6 months ago. The first link, while containing important opinions, doesn't seem relevant to the current problems that Nitter is having.
Uh oh:
https://www.eff.org/deeplinks/2024/01/save-your-twitter-account
https://www.vanityfair.com/news/2023/07/elon-musk-latest-twitter-meltdownThat second link is from 6 months ago. The first link, while containing important opinions, doesn't seem relevant to the current problems that Nitter is having.
oops.
Same here. Even in a working instances like https://nitter.soopy.moe/ only the tweets work. When clicking on tweets and replies, it says rate limited. I can still view media and tweets though.
So far, i've just been using https://nitter.woodland.cafe/ and it's been working just fine. If it gives you a rate limited message just refresh the page 1-2 times and it goes away. https://nitter.catsarch.com/ , https://nitter.privacydev.net/ , and https://nitter.moomoo.me/ have been working for me, but privacydev and moomoo are kinda slow.
have been working on scripts using nitter instances and fxtwitter; can't test properly. was wondering why someone would DDoS the services, came to amusing theory: the Taylor Swift AI gens. Time lines up, I think. Oh, well; hope things get better soon!
aside from the DDoS, Is the server overload mostly caused by people using the wayback machine saving nitter pages? Saving twitter pages directly have issues, mainly that the playback (viewing the WBM version) often fails to save the content (you get the "something went wrong" instead of the actual tweet content), and also that it takes forever to save a single tweet.
aside from the DDoS, Is the server overload mostly caused by people using the wayback machine saving nitter pages? Saving twitter pages directly have issues, mainly that the playback (viewing the WBM version) often fails to save the content (you get the "something went wrong" instead of the actual tweet content), and also that it takes forever to save a single tweet.
I don't think it's DDoS, If just refreshing the page solves in many cases the problem, it means it is something to do with the Nitter software.
Some newbies were scraping nitter heavily (I run an instance behind cloudflare https://nitter.freedit.eu/). Not too many ips. So, literally, it's not ddos but dos.
aside from the DDoS, Is the server overload mostly caused by people using the wayback machine saving nitter pages? Saving twitter pages directly have issues, mainly that the playback (viewing the WBM version) often fails to save the content (you get the "something went wrong" instead of the actual tweet content), and also that it takes forever to save a single tweet.
I do not think that saving nitter.net with the Wayback Machine worked. Last time I tried, I got 403 errors:
"Sorry
The capture failed because Save Page Now does not have access rights for https://nitter.net/<twitter_username>/status/<tweet_id>
(HTTP status=403)."
Also, saving using archive.today (archive.ph) did not worked due to "infinite loop" (capture starts and never finishes until timeout).
Yes, there was a massive amount of DOS'ing, or at least flooding of some kind to public instances around the same time guest accounts were disabled. Most instances should never have seen rate-limiting based on the accounts they had.
I run private instances with "quite a few" accounts and not one experienced anything out of the ordinary, so it wasn't Twitter expiring accounts. I can't put my finger on as to why... But all accounts 30-days after they were retrieved before Jan 24 should work until they expire upstream. We grabbed enough accounts on that day to at least have the ability to operate until the 24th.
This just started happening on my instance. It seems like the guest accounts are getting ratelimited way faster than usual. I was getting dozens of accounts ratelimited per minute, with not that many requests. Could be a case of Twitter clamping down on their usefulness?
EDIT: For some reason my instance started working just fine and I haven't gotten a ratelimit in hours yet it says all 20,000 accounts are limited 🤔
EDIT 2: Now my instance is completely rate limited. That's it. It's over 😞
same for me on serveral instances
Same for me, on most instances.
Furthermore, I don't know if this has anything to do with it, but I have several times been wrongly detected as "bots" by certain instances.
@zedeus Please restrict this and related issues to collaborators only, or people will keep leaving pointless "me too" comments.