Maybe you don't use it very often? For months before the recent chaos it was very reliable. The fact that it's working today is only because I fixed it, Twitter didn't change anything.

It works great. Don't pay attention to the philosophers.

I quit twitter when I discovered it. Thank you.

To be clear, this is not intended to be a dig at the nitter team, I always assumed the software was more their focus than nitter.net

Timelines are usually blank, to the point that I have removed it from the rotation of instances in my browser redirector extension. I assumed this was a result of being rate limited by Twitter.

I will admit that since I did remove it from the rotation, I don't see it that often these days, mostly when others link to it and then I navigate to a timeline.

I’ve had timelines/tweets fail to load, but a refresh fixed it quickly. If this was a consistent problem did you consider opening an issue to see if they could improve the website?

Any chance you can re-enable rss?

It's disabled on nitter.net to reduce load while this new solution is being tested. Check the instance list for updated instances, most of them have RSS enabled: https://github.com/zedeus/nitter/wiki/Instances

Thanks for your work on this.

Search, which is required for the multi-timeline feature, isn't implemented right now. I have a fix in the works using a legacy endpoint.

Broken link?

Apparently. The correct URL is here: https://news.feinberg.northwestern.edu/2022/02/investigators...

ETA: The study was done in mice, so maybe the title should reflect that?

Any rate limit errors are false flags caused by bugs, they aren't related to load or real rate limits

I'm not sure why this is down-voted despite it being posted by what looks like the original developer according to their username: https://github.com/zedeus/nitter

I have no idea, maybe "false flag" was too incorrect? You're right, I am.

"False flag" is pretty close to loaded language these days.

"Spurious error" would probably be a better term.

Thanks, BTW, amazing tool.

This isn't actually true, the "Instance has been rate limited" error was a false flag. It turned out to be a bug in the API token parser, found and fixed by a contributor. Nitter instances have yet to run into a real rate limit.

The old rate limit errors were false flags caused by a bug in the API token parser. Nitter instances have yet to run into a real rate limit.

I see. Thanks for the information.

Nitter supports lists the same way Twitter does. Example: https://nitter.net/NASA/lists/Astronauts

You can sort of create your own too (currently limited to ~25 profiles due to Twitter limitations), like this: https://nitter.net/SpaceX,elonmusk,ID_AA_Carmack

Inspired by Twint I created an alternative web client that relies almost entirely on web scraping. The parser is more complete than Twint's due to the different goals, supporting things like polls and videos properly. It's still work in progress but very usable with features like RSS and convenient profile search. https://github.com/zedeus/nitter

I don't use twitter android application and the browser version on mobile is extremely slow. This made twitter usable on my browser again. Thanks! PS: It would be even more useful if someone hosts it in a domain like <someshortcode>twitter.com, then I can just add shortcode to the url and escape from the slow, official one.

Use a PWA instead. Go to Twitter on Chrome and do "Add to Home Screen". Really fast.

Thank you! I love it! It's so much better than the official front-end and works fine without JS.

No content gets edited by Nitter except links being expanded and twitter/youtube links getting replaced (unless the user disables that)