I’ve been on a bit of a development hiatus the last couple of months, but I’m starting to work on the project again. One thing I’ve been wanting to address is the broken support for Invidious/Piped.
With Youtube seemingly hellbent on making sure those no longer work, should I remove support for them in Tesseract or give those projects a while longer to find a workaround? I don’t closely follow development of either of those, but last I checked, it seemed pretty much dead because of YouTube’s shenanigans.
The code could be a lot cleaner if I removed that support, but if there’s a chance of either of them coming back, I’d be willing to leave it in.
Questions for the Community
- Is it just public Invidious/Piped instances that are broken?
- Do private instances still work?
- Do you think either project will come up with a medium to long term workaround?
I’m thinking if private instances still work, I may just remove the public list and only enable the option if the user specifies a custom instance in the app settings. For historic posts, I’ll just have it rewrite any Invidious/Piped links to canonical YouTube links or the user-defined custom Inv/Piped instance if defined. If not, then I may just remove that support entirely and only rewrite old links to go through YouTube directly so they still work.
Thoughts?