You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can we have a new option to manipulate timeline visibility, which is "I have seen this post too many times"
Motivation
Sometimes we don't want to block or hide any other users.
It is just something hot or some viral content.
It is OK to see it one time or two times when scrolling the timeline.
But when it gets too hot and appears on our timelines too frequently, it is very annoying.
And since none did anything wrong, it is just a result of the accumulation of personal interests, in my opinion, we should not apply 'hide' or 'block' on users posting it, but apply something similar on the too hot 'toots' themselves.
Thank you.
The text was updated successfully, but these errors were encountered:
I understand this is not exactly what you are asking for (manual hiding of a post as opposed to automatically preventing a post from coming back in the timeline after a threshold), but would #18945 solve your issue?
This sounds like it might be related to #18693 ? If users could be given the option to set how long it is between boosts being visible again (including never seeing boosts again) this would also help with individual posts appearing too often?
Pitch
Can we have a new option to manipulate timeline visibility, which is "I have seen this post too many times"
Motivation
Sometimes we don't want to block or hide any other users.
It is just something hot or some viral content.
It is OK to see it one time or two times when scrolling the timeline.
But when it gets too hot and appears on our timelines too frequently, it is very annoying.
And since none did anything wrong, it is just a result of the accumulation of personal interests, in my opinion, we should not apply 'hide' or 'block' on users posting it, but apply something similar on the too hot 'toots' themselves.
Thank you.
The text was updated successfully, but these errors were encountered: