The important part is the linked GitHub comment from the primary maintainer (and owner) of the Nitter project. To save readers a click
Guest accounts have been removed, they weren't just led to believe that. With real accounts getting rate limited immediately and likely banned, I don't see any path forward for Nitter.
I would say that Nitter as a whole is not owned by anyone, that person is the owner of one of the Nitter instances, in addition to being the primary maintainer of the project as you correctly stated.
I agree with the second part of your comment about all instances being in danger. It is unfortunately a common problem faced by many privacy-respecting frontends (Nitter, Libreddit, Proxigram, Piped etc)
This is one of the long time running instances shutting down, linking to the primary nitter author saying it's the end for all instances eventually. And providing insights from the status page.
If they don't get new guest accounts, they're all going to shut down withing 30 days. It's just left over accounts and caches giving you the impression everything is fine.
Don't forget the rolling DoS herds of scrapers having no more ways to do stuff on their own, which are now trying to use the remaining instances - killing even more.
I shouldn't have to paste this here, but: "If nothing changes, all remaining instances will go down eventually: Instances rely on guest accounts, which are valid for a certain time and of which you need a ton to run a public instance. The API for this got taken down and it doesn't look like a fluke this time."
It's unfortunate that this mistaken comment is top voted.
"If nothing changes, all remaining instances will go down eventually: Instances rely on guest accounts, which are valid for a certain time and of which you need a ton to run a public instance. The API for this got taken down and it doesn't look like a fluke this time."
I don't know for sure, I've been watching a couple accounts that have been dormant for a while, but several instances have broken search, so maybe the account pages are cached.
Edit: I just checked an instance and it seems to have tweets from the past minute or two, but if the backend accounts that drive them are getting banned, it's probably gonna tank in the upcoming weeks.
The submitted title was "Nitter Is Dead". We changed it to the article title overnight, but I've since changed it to a representative sentence from the text.
The important part is the linked GitHub comment from the primary maintainer (and owner) of the Nitter project. To save readers a click
Source: https://github.com/zedeus/nitter/issues/983#issuecomment-191...
The way I interpret this comment is that all public Nitter instances are at risk of becoming inoperable (at their current scale).
> (and owner) of Nitter.
I would say that Nitter as a whole is not owned by anyone, that person is the owner of one of the Nitter instances, in addition to being the primary maintainer of the project as you correctly stated.
I agree with the second part of your comment about all instances being in danger. It is unfortunately a common problem faced by many privacy-respecting frontends (Nitter, Libreddit, Proxigram, Piped etc)
I really meant to say "owner of the Nitter project", but you are nonetheless correct about ownership of Nitter instances. I have edited my post.
5 replies →
I counted 10 instances recently going down on the status page. There is at least a correlation, probably a cause.
This is one of the long time running instances shutting down, linking to the primary nitter author saying it's the end for all instances eventually. And providing insights from the status page.
If they don't get new guest accounts, they're all going to shut down withing 30 days. It's just left over accounts and caches giving you the impression everything is fine.
Don't forget the rolling DoS herds of scrapers having no more ways to do stuff on their own, which are now trying to use the remaining instances - killing even more.
I shouldn't have to paste this here, but: "If nothing changes, all remaining instances will go down eventually: Instances rely on guest accounts, which are valid for a certain time and of which you need a ton to run a public instance. The API for this got taken down and it doesn't look like a fluke this time."
It's unfortunate that this mistaken comment is top voted.
"If nothing changes, all remaining instances will go down eventually: Instances rely on guest accounts, which are valid for a certain time and of which you need a ton to run a public instance. The API for this got taken down and it doesn't look like a fluke this time."
Except half of the instances are rate limited, so unless you know the username or tweet you are looking for, good luck searching for anything.
Oh, does it mostly affect searching?
99% of the time I touch twitter, it's to go to a specific tweet or timeline.
I don't know for sure, I've been watching a couple accounts that have been dormant for a while, but several instances have broken search, so maybe the account pages are cached.
Edit: I just checked an instance and it seems to have tweets from the past minute or two, but if the backend accounts that drive them are getting banned, it's probably gonna tank in the upcoming weeks.
[dead]
Good to hear. I only follow specific users via nitter (via Feedbro extension)
The submitted title was "Nitter Is Dead". We changed it to the article title overnight, but I've since changed it to a representative sentence from the text.
nitter.cz and nitter.net are having issues and being rate limited.