-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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] "This helps protect our community." #4908
Comments
same here :( |
A/B test so not all instances are affected yet, but yes, unfortunately there's another block. With that said, this is a duplicate issue. |
Duplicate issue of issue that has last comment stating the solution was released and any more comments disallowed from anyone except for collaborators (and yeah that solution worked for weeks). I think its completely fine to report that this happens again since this is basically new issue with the same symptoms. Just because YT returns the same error string doesn't mean its the same reason. |
I'm seeing the same thing but it's instead saying "This video may be inappropriate for some users." |
That is fair, but it's nearly identical, the only difference being that the patch previously made no longer works. Not to mention, creating new issues only increases bloat, and the devs are already aware of the block. Making a "master" issue per se to track blocks would honestly work best - all that's needed is to update the OP and have the comments act as a changelog. Much better than having a ton of separate issues all for the same thing, which is just another attempt by Google to block Invidious.
Also helps to prevent comments like this. This is completely separate and not related to the block, see #2189. |
Describe the bug
This #4734 is happening again on nearly all instances.
FUCK GOOGLE
Steps to Reproduce
Logs
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: