-
-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nitter is Dead. Should it be removed from the extension? #898
Comments
It should be removed and added to #892. |
Nitter is still perfectly usable on local or private instances and a couple of public instances like https://nitter.poast.org |
You can submit Redirector Rules. And I'll add them to the website #892 |
Removing "dead" projects and forcing people to use a second extension feels against the spirit and goals of the project. None of the maintainers or what not clearly understand how open source software works. Please reconsider and do better. |
One instance of nitter is down, there are many others, there is even a redirector that automagically redirects to a host that is less loaded and not out of API tokens. just cutting away the entire redirection option for twitter without letting the user choose the redirection target on their local browser is kinda harsh. |
Why would you remove this??? If you're not able to use Nitter, simply uncheck Twitter. Is that so hard? If you're worried about a negative reflection on this browser extension's reputation, just add a little disclaimer:
|
This reverts commit b6c9802.
Please add back Nitter, it was working fine for me on multiple instances and I do agree upon the fact that it's the users decision to supply working instances within the redirector; I could always make a PR of some updated working instances pre-configured but stuff like this becomes cumbersome updating with the newest alive instances... @Seby458 Do you think you could make a PR of your fork to speed up process? Unless a maintainer can revert 👍 |
Looking at the history of Instagram redirections, it seems when Bibliogram shut down that the extension pivoted to using a different frontend. I don't believe any alternate Twitter frontends exists besides Nitter, and it doesn't sound like any should be popping up anytime soon.
Should Twitter redirects be retired then? Or at least disabled by default until further notice?
The text was updated successfully, but these errors were encountered: