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

Add the possibility to configure custom Nitter and Invidious instances. #2

Closed
PoorPocketsMcNewHold opened this issue Sep 28, 2019 · 8 comments

Comments

@PoorPocketsMcNewHold
Copy link

Making the extension redirect to other instances of Nitter and Invidious should be pretty easy to do, as you only really need to replace the nitter and invidious instance name by the one chosen by the user.
However, a setting extension page for it still need to be done.

@SimonBrazell
Copy link
Owner

This is a great idea, I'll look into adding it.

@SimonBrazell
Copy link
Owner

Was actually thinking of adding a menu to allow the user to disable the redirects if they like too.

@SimonBrazell
Copy link
Owner

Do you think this should be a list of predefined instances or a text field for entering whatever instance they want?

@PoorPocketsMcNewHold
Copy link
Author

Well, I think predefined Instances should be better. It may cause some issues when some instances dissapears or when the list isn´t updated, but it shouldn´t change that heavily to be honest.

@SimonBrazell
Copy link
Owner

I'll make it a text field for now that way the user can add whichever instance they like and we don't have to a maintain a list in the extension.

@SimonBrazell
Copy link
Owner

SimonBrazell commented Oct 7, 2019

Finally got around to doing this, pushed up to the stores, let me know what you think.

Also added the ability to disable redirects too.

@moppman
Copy link

moppman commented Oct 7, 2019

Great work!
Unfortunately, the twitter redirection doesn't work at all for me in Firefox 69.0.1
edit: works Chrome, though. Strange.
edit2: I deleted all twitter cookies and cache data, now it's working in Firefox, too :)

@SimonBrazell
Copy link
Owner

@moppman, that's strange, wonder if there is anything I can do to stop this behavior in the future, might need to read up on the Firefox API a bit more. Thanks for the update and workaround!

SimonBrazell pushed a commit that referenced this issue Oct 26, 2020
mittermichal pushed a commit to mittermichal/privacy-redirect that referenced this issue Jul 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants