To (Web2.0) Developers: I Want Control of My Data, I Want to Write My Own Rules I sure am with Doc Searls and Dave Winer on this one. I want control of my own data. And I want to write my own rules on how others may and may not use my data. First because if you tell me I have no friends simply because my data is not on your […] Operators of Nitter instances are sometimes faced with the issue of bots using their instances to scrape a large number of tweets in a short period of time, and they often respond to this issue by introducing rate limiting, which has the unfortunate effect of making it harder for legitimate visitors to access Nitter. Dutch Provinces Looking for Open Data Inspiration Last week ten of the twelve Dutch Provinces met at the South-Holland Provincial government to discuss open data, and exchange experiences, seeking to inspire each other to do more on open government data. I participated as part of my roles as open data project lead for both the Province of Overijssel, and the Province Fryslân. […] It was created by a developer known as Zedeus and the Nitter GitHub repository was created in June 2019. As of the 10th of November 2022, 39 people have contributed to it on GitHub, over 6,000 people have starred it, and it has been forked 275 times.

The nicest feature of Fairside it that you can call it to have it redirect you to a working instance. In my experience Nitter instances encounter less issues than other alternative services’ instances such as Invidious for YouTube, nevertheless I agree this may occur occasionally. Personally I’ve set a dedicated bookmarklet sub-folder in Firefox’s Bookmarks Toolbar to which I’ve added 5 simple scripts to handle 5 Nitter instances, allowing to switch easily from one to another :

Comments

For instance, [https://farside.link/nitter] will open a working instance of Nitter. reliable in my experience.

Doctrow, Cory (10 April 2020). "Pluralistic: 10 Apr 2020 – Pluralistic: Daily links from Cory Doctorow". Pluralistic . Retrieved 10 November 2021. Edit: nitter.net uses more graphql endpoints than most instances because it's running a dev version A way to deal with this issue is by using a Nitter redirector, such as Farside. Farside has a list of working Nitter instances, which is updated every 5 minutes to remove instances which are slow to respond or which output error codes. Customization: Nitter offers customization options, allowing users to tailor their experience based on their preferences.Yandex is the only search engine that displays Nitter results from time to time, but you know, you hope the instance they gave you is not the one that is broken.