TIL that you can self-boost a toot, which shoves it to the front of everyone's timeline (boo, rude).
... but I also learned that you can make a filter on one or more toots and select them individually to add to the filter (awesome, yay). So now I have a "squelched" filter to kill self-boosted toots.
I like how so far, every problem I have with this protocol already has a solution.
(... now to see how much work it would be to add "is self-boosted toot" as a criteria in the filter)
p.s. I'd say something like "Stop self-boosting your toots," but it's your service too and I ain't gonna tell you how to live your life. Just know when you're repetitive my squelch is judging you silently. ;)
One thing that people do sometimes is that they self-boost toots that were unlisted (e.g. because they were deep in a reply chain under something unlisted), so that they appear once in the public timeline (and/or on their "toots" list instead of only "toots and replies").
("Unlisted" means technically that as:Public is not in the `to` field, but in the `cc` field.)
@robryk Oh yeah, but the context I was seeing is the same toot coming over and over to the top of my timeline after I'd already read it because it was important to the writer. It doesn't impress itself in my brain more on the fifth viewing; I've already read it.