-
Notifications
You must be signed in to change notification settings - Fork 877
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: NSFW content unplayable when Family Friendly toggle turned off #5579
Comments
Okay so just to be clear you turned on the |
yes I turned it on, and if I turn it off, Freetube still refuses to play them, saying Error: this helps our community, learn more. It's inconsistent, sometimes it says Error: this video may be inappropriate for some users. |
by Warning ahead of time (in expected behavior), I mean we should have a disclaimer with the options to either skip video or continue. |
Those error messages sound like they are coming from the Invidious API, but you said you were using the local API. Without further information e.g. links to the videos or screenshots of the error messages I can't say exactly what is going on but the second error message likely means that the uploader disabled embedding, so the age-restriction cannot be bypassed and the only way to watch it is with an official YouTube app while logged in with an age-verified YouTube account. |
This one is unrelated, see #5489
Nothing we can do about this and these errors are unrelated to that setting. |
Guidelines
Describe the bug
NSFW videos don't play when Family Friendly content is turned off
Expected Behavior
NSFW videos play as usual (possibly with a warning ahead of time), if Family Friendly content is turned off
Issue Labels
accessibility issue, API issue, content not loading, feature stopped working, usability issue
FreeTube Version
v0.21.3 Beta
Operating System Version
Windows 11
Installation Method
.exe
Primary API used
Invidious API
Last Known Working FreeTube Version (If Any)
No response
Additional Information
No response
Nightly Build
The text was updated successfully, but these errors were encountered: