-
-
Notifications
You must be signed in to change notification settings - Fork 384
📝 Correction | invidio.us #2113
Comments
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? |
If PrivacyTools is linking to specific invidious instances, my solution would be making the actual instance a variable in 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 |
It's good as it is now. Linking to a single instance will over flood it. |
https://invidious.snopyta.org/ shows already a banner:
https://instances.invidio.us/ lists additional information. |
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. |
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.
The text was updated successfully, but these errors were encountered: