So someone deleted their Mastodon account and now my instance is receiving an Undo(Announce) for everything they've ever done.This ... is ... concerning, considering one should assume a single Delete(Actor) should automatically handle all of the side e...
-
So someone deleted their Mastodon account and now my instance is receiving an Undo(Announce) for everything they've ever done.
This ... is ... concerning, considering one should assume a single Delete(Actor) should automatically handle all of the side effects?
I'm not particularly worried about the noise, bandwidth, or cycles, it's mostly just out of principle that I think this is weird.
I think @hrefna tooted about this awhile back too.
-
@devnull Yep. Under the ActivityPub there's no inferences that deleting the actor deletes things downstream from the actor, despite this being a sensible position.
So you get variable implementations that either:
1. Assume that deleting the actor is sufficient.
2. Undo everything, which is also not in accordance with the spec but fits with how AS frames things.
3. Delete literally everything (technically twice), which fits with how AP is written.
4. Just not propagate account deletions -
@hrefna time for a SWICG account deletion task force
-