the thing about me boosting those posts is that well uh
those posts no longer exist on that instance
...mastodon is definitely going to have to work on the whole deletion thing
basically, i bet if anyone can't see those posts i just boosted, if they check @luna, they'll see that there's more than 0 followers
@boots ...
(is a large rock)
@boots ...ooh, uhm. I hate to bust open that theory, but... https://tootplanet.space/media/PJZKkb7kTb6PuIHYHCI
@InspectorCaracal new theory! everyone who saw the boosts federated the user who boosted them originally, getting them cached, but they don't follow the actual moon
@InspectorCaracal okay nevermind i just checked on someone else on ephemeral that's wrong too
hmmmmmm
@bea @boots @InspectorCaracal I think when boosting a toot we gotta be prepared to (re) broadcast a delete to all the nodes where that toot went
can make a lot of redundant traffic though so I'm not in love with the idea yet. needs work
@boots also even if mastodon support deletes right, it doesn't mean any server will respect it. Anyone is free to build an alternative backend or just a feed reader that does not support deletions.
@href yeah, i just want the ability to do that to require an active effort on the part of whoever wants to do it
honestly i don't care if it's possible to do on something other than vanilla mastodon, i just want it to be harder than "it's possible to do on accident on a vanilla instance"
i think what's happening is mastodon isnt propagating the deletion event beyond instances where the user is actually federated, making it so that boosted posts are cached