Skip to content
This repository has been archived by the owner on Jun 24, 2022. It is now read-only.

📝 Correction | invidio.us #2113

Open
1 task
foxscore opened this issue Nov 3, 2020 · 5 comments
Open
1 task

📝 Correction | invidio.us #2113

foxscore opened this issue Nov 3, 2020 · 5 comments
Labels
approved approved, waiting for a PR 📝 correction Correction of content on the website todo

Comments

@foxscore
Copy link

foxscore commented Nov 3, 2020

Description

invidio.us is no longer running, and only lists alternative instances.
My suggestion would be to either redirect to another instance by default, or tell the user uppon viewing the /providers/video/ page that the original service is no longer online.

Why I am making the suggestion

See description

My connection with the software

None - Was just looking for YT alternatives.

  • I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.
@foxscore foxscore added the 📝 correction Correction of content on the website label Nov 3, 2020
@oXyiGYJ
Copy link
Contributor

oXyiGYJ commented Nov 7, 2020

Not sure if directing to an instance would be the best bet, but as far as I understand the code base is still being maintained, could just direct them to that to pick an instance, or add another section of curated/trusted instances?

@Mikaela
Copy link
Contributor

Mikaela commented Nov 8, 2020

If PrivacyTools is linking to specific invidious instances, my solution would be making the actual instance a variable in _config.yml and using it instead of the domain whenever linking to Invidious and in case the instance goes down or there is other cause for replacing it, it would just need one change to get fixed everywhere.

Isn't PrivacyTools hosting a PeerTube instance? Would it be an option to ask for author of linked videos for a permission to reupload them on PrivacyTools PeerTube if they aren't already on PeerTube?

If PeerTube videos are also reachable from other instances (like YouTube/Individious/Nitter/etc. by changing their hostname, I would make PeerTube a variable too.

Example: in _config.yml have invidiousInstance: https://invidious.snopyta.org/ and on pages refer to {{site.invidiousInstance}}/watch?v=dQw4w9WgXcQ"

@thansk
Copy link

thansk commented Nov 10, 2020

It's good as it is now. Linking to a single instance will over flood it.

@freddy-m freddy-m added the approved approved, waiting for a PR label Nov 18, 2020
@rusty-snake
Copy link

https://invidious.snopyta.org/ shows already a banner:

Please try to use different invidious instances to better the distribute load between them

https://instances.invidio.us/ lists additional information.

@gary-host-laptop
Copy link

I can make a PR for this, although it doesn't seem to be a resolution on what should be done.

In my opinion we should redirect to https://instances.invidio.us/ and add a warning about using always the same instance to avoid overtrafficking it.
Also another good option would be to list FreeTube and drop Invidious, since it has been out of beta for some months now, it works a lot better and it is still being updated.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved approved, waiting for a PR 📝 correction Correction of content on the website todo
Projects
None yet
Development

No branches or pull requests

7 participants