📝 Correction | invidio.us #2113
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#2113
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
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
_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
haveinvidiousInstance: https://invidious.snopyta.org/
and on pages refer to{{site.invidiousInstance}}/watch?v=dQw4w9WgXcQ"
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.
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.