Skip to content
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

Closed
MintMain21 opened this issue Mar 8, 2024 · 7 comments
Closed

Nitter is Dead. Should it be removed from the extension? #898

MintMain21 opened this issue Mar 8, 2024 · 7 comments

Comments

@MintMain21
Copy link

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?

@ManeraKai
Copy link
Member

It should be removed and added to #892.

ManeraKai added a commit that referenced this issue Mar 10, 2024
@polak14
Copy link

polak14 commented Mar 11, 2024

Nitter is still perfectly usable on local or private instances and a couple of public instances like https://nitter.poast.org

@ManeraKai
Copy link
Member

You can submit Redirector Rules. And I'll add them to the website #892

@Cynosphere
Copy link

Cynosphere commented Mar 12, 2024

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.

@seefood
Copy link

seefood commented Mar 20, 2024

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.

@6Fv
Copy link

6Fv commented Mar 30, 2024

Why would you remove this???
Nitter is not "dead".

If you're not able to use Nitter, simply uncheck Twitter. Is that so hard?
Don't disable it for everyone that still uses it...

If you're worried about a negative reflection on this browser extension's reputation, just add a little disclaimer:

Hey, in order to get this to work, you'll have to put in a tiny amount of effort

Seby458 added a commit to Seby458/LibRedirect that referenced this issue Apr 29, 2024
@obfuscated-loop
Copy link

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 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

7 participants