Yes I'm fine with that. It doesn't make much difference in the end.
Posts
-
Yes, a Delete activity is sent to all instances with actors that follow the category/community. -
Yes, a Delete activity is sent to all instances with actors that follow the category/community.Try doing a bare delete (no announce wrapper), with the actor being the moderator who deleted the post.
https://join-lemmy.org/docs/contributors/05-federation.html#delete-post-or-comment
-
Yes, a Delete activity is sent to all instances with actors that follow the category/community.We only federate the deletion if it is in one of our local communities.
The activity is signed by the person who did it, so if Mastodon detects that the person deleting is not the author and doesn't know how to find out if someone is a moderator or not, that's their problem.
Mastodon has been dropping the ball on groups support for years so I didn't even bother to find out if they handle it well - I bet they don't.
-
Yes, a Delete activity is sent to all instances with actors that follow the category/community.Looks like for Mastodon we just do a bare
Delete. -
Yes, a Delete activity is sent to all instances with actors that follow the category/community.only understood by Piefed? Not Lemmy
No, that's a Lemmy thing too.
-
Yes, a Delete activity is sent to all instances with actors that follow the category/community.Possibly although the differences of federation between the threadiverse and the rest of the fediverse go way beyond deletes. FEP 1b12 is a whole thing, chipping away at it piece by piece would be slow going.
-
Yes, a Delete activity is sent to all instances with actors that follow the category/community.There are lots of other uses for
Move. A community whole could move instances, a user could move instances, etc. -
Yes, a Delete activity is sent to all instances with actors that follow the category/community.Yes, a Delete activity is sent to all instances with actors that follow the category/community. Those instances then delete their local copy. In Lemmy/PieFed there is no distinction between deletion and removal.
The deletes are soft so it is possible to un-delete by sending an Undo activity. PieFed keeps soft-deleted posts (topics, in NodeBB language) for a few days then after a week deletes the content from the database.
All of these activities are enclosed in an
Announceand the http POST is signed using the community key. So in a way the content 'belongs' to the community, not to the original author. With that model of ownership the idea of removal redundant - a post without a community is not a post.Tangentially - it would be good to come up with a way to move a topic to another category and federate that so the move can happen on other instances, too. We could go off-piste and create a
Moveactivity, or useRemove(from old topic/comm) followed byAdd(to new topic/comm) to do the same thing. I feel more inclined to go withMoveas it's a single atomic operation that either succeeds or fails, despite it not being in the spec.The AP spec is so badly stretched by various implementation-specific differences that I don't think it's worth being ideological about adherence to it it anymore.