If you're wondering how to stop seeing the same boosts again and again, there is a feature built into Mastodon called "Group Boosts" which prevents you seeing the same boost twice. This is switched on automatically for everyone, you do not need to do anything to switch it on.
Unfortunately, it is also set to allow boosts to repeat after 40 other posts, and this number cannot be adjusted by users or admins.
If you're comfortable using github, vote for this to be fixed at https://github.com/mastodon/mastodon/issues/18693
Unfortunately it is not that simple.
The server could do it based upon age of when the user last saw the boost. The problem is that this adds more complexity to the server to manage. And, there is no guarantee that the user actually saw (eyeball read) the boost in the first place.
I think this is best managed client-side, and that requires the client to track which post was boosted, and then would likely not be over 24 hours before it is aged out of a cache. Though, if you have the ram, you could make the expiry time longer.
Needs to be client side, but continue to waste bandwidth as happens now.
It is important that the original post creation timestamp is NOT a factor.
I'm not sure what you mean, as the feature exists already?
This is about being able to adjust the number "40", not about creating the feature?
Guess there's possibly a resource issue with higher numbers, but shouldn't that be up to the instance owner to decide?
Approximately 60% of my timeline is boosts, mostly redundant. I have disabled seeing boosts for this reason.
The boosts are still wasting bandwidth, but it at least makes my timeline more readable.
I still miss posts (not boosts) every day because they are buried too deep and too old.
If I miss something, I just hope that it will get mentioned again when I am reading. I do sleep sometimes.
If it is important and newsworthy, it will come up again.
`