Caught this is on one of the piped instance. Every video on this instance has the same warning. Piped is an opensource privacy frontend for YouTube, which uses NewPipe’s youtube extractor.
You must log in or register to comment.
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn’t great, if contents of the website are behind a paywall maybe copy them into the post
- Don’t promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
- 0 users online
- 57 users / day
- 383 users / week
- 1.5K users / month
- 5.7K users / 6 months
- 1 subscriber
- 2.44K Posts
- 57.6K Comments
- Modlog
Seems like the issue is widespread and while some instances are affected, some not.
Github Issue on Piped: https://github.com/TeamPiped/Piped/issues/2487
This simply means that the instance is not up to date.
As I understand it; NewPipe Extractor is supposed to load the YT webpage in it’s entirety; execute it’s code and parse out the relevant video bits. Old extractor versions will be broken as YouTube regularly updates it’s webpage(s) with new data and behaviors the extractor needs to account for.
you’re right. It was fixed in newpipe. https://github.com/TeamNewPipe/NewPipe/issues/8713
The instance(piped.palveluntarjoaja.eu) shows it’s up to date, it probably got rate limited.
Which videos? On newpipe 0.25.1 I’m having no issues, but it might be due to the videos, who knows… On freetube I’m not having issues either BTW (though not related to newpipe AFAIK)…
All videos on this insance seems that way. https://piped.palveluntarjoaja.eu.
I dug deeper and it seems like an outdated instance issue (probably using an older newpipe extractor). this was fixed in newpipe in late 2022. https://github.com/TeamNewPipe/NewPipe/issues/8713
It seems that long videos like this: https://piped.mha.fi/watch?v=m3att9ydcxc
No issues in newpipe, though piped.mha.fi is not a valid URL on newpipe, still searching for the video
m3att9ydcxcdoes it. No issues on freetube either, neither with invidio instances, like:https://yt.funami.tech/watch?v=m3att9ydcxc