-
-
Notifications
You must be signed in to change notification settings - Fork 322
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(YouTube - Hide layout components): Hide community posts does not work for new type of community post #4340
bug(YouTube - Hide layout components): Hide community posts does not work for new type of community post #4340
Comments
Someone who is savvy with logcat needs to identify a custom filter that hides these. |
attaching my logcat below, which i generated right after starting youtube and this new community post showed up |
There are no ReVanced debug statements in that log. |
Log protocol buffer should only be used for local debugging. Don't submit logs with that on unless you've manually inspected every line for any private information and redacted anything questionable. Protocol buffer will include device IP and other potential personal information. |
and the regular logcat? |
The regular debugging switch should be on. It logs no private data. |
Update: I decompiled the youtube app and tried to exclude some moe elements to no avail.
|
Confirm with filter |
This fixed it! May I ask how did you find that this was the element? |
|
I got it from the linked PR. You can find it by filtering the logs. |
I see. @Bceez thank you! |
Bug description
Youtube rolled out a new type of community post in which creators can link their old videos. It looks exactly like a regular community post but with a video attached to the post at the bottom. This new type of community post is not being hidden despite the "turn community posts off" toggle.
example (this is in subscription subscribption feed)
my settings:
Error logs
to reproduce, simply sub to a channel that has done this and go to subscribtions.
Solution
No response
Additional context
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: