For a lot of things in ActivityPub, there are almost direct parallels in NodeBB. An as:Note object pairs well with a NodeBB post, an as:Person is a NodeBB user, etc.

One thing that didn't map 1:1 was the Delete activity, which at surface level, seems rather straightforward — just delete the object! However, once you dig in, there are some additional considerations:

• in NodeBB, we have two separate states for content removal.
  • A delete, where the post is still present (but its content unavailable to non-privileged users), and a
  • A purge, where the post is scrubbed from the database entirely, and all references to it, removed
• in ActivityPub, there is a single activity, as:Delete
• Implementors may opt to replace the object representation with an as:Tombstone (how quaint!), but they may also just opt to use a 404

So there are some nuances that are left intentionally vague.

Kaniini on SocialHub makes the argument that a Delete should be treated like a cache invalidation, which has its own merits.

This is how NodeBB will interpret the protocol specification, and how we will align it with our own dual-state post deletion mechanic (delete & purge):

1. When a local post is deleted, we will federate out an Update(Tombstone) referencing the id
2. Afterwards, if the content is retrieved, an as:Tombstone will be served.
   • Deleted posts in NodeBB still maintain their place in the topic, so when the context is retrieved, the note will still be present in the collection.
3. If we receive an Update(Tombstone), we will delete the local representation of the post
4. When a local post is purged, we will federate out a Delete(Note)
5. Afterwards, if the content is retrieved, we will serve a 404
   • The note will no longer exist in the context collection
6. If we receive a Delete(Note) (or Article, or Question, etc.) we will not delete it immediately. Instead, as kaniini advises, we will attempt to retrieve the object from the origin:
   • If we see an as:Tombstone, we will delete the post (soft delete)
   • If we encounter a 404 or 410, we will purge the post (hard delete)

I'm writing this out less as a guideline for myself, but to solicit opinions and to give others a chance to point out if I've interpreted the spec incorrectly.

For a lot of things in ActivityPub, there are almost direct parallels in NodeBB. An as:Note object pairs well with a NodeBB post, an as:Person is a NodeBB user, etc.

One thing that didn't map 1:1 was the Delete activity, which at surface level, seems rather straightforward — just delete the object! However, once you dig in, there are some additional considerations:

• in NodeBB, we have two separate states for content removal.
  • A delete, where the post is still present (but its content unavailable to non-privileged users), and a
  • A purge, where the post is scrubbed from the database entirely, and all references to it, removed
• in ActivityPub, there is a single activity, as:Delete
• Implementors may opt to replace the object representation with an as:Tombstone (how quaint!), but they may also just opt to use a 404

So there are some nuances that are left intentionally vague.

Kaniini on SocialHub makes the argument that a Delete should be treated like a cache invalidation, which has its own merits.

This is how NodeBB will interpret the protocol specification, and how we will align it with our own dual-state post deletion mechanic (delete & purge):

1. When a local post is deleted, we will federate out an Update(Tombstone) referencing the id
2. Afterwards, if the content is retrieved, an as:Tombstone will be served.
   • Deleted posts in NodeBB still maintain their place in the topic, so when the context is retrieved, the note will still be present in the collection.
3. If we receive an Update(Tombstone), we will delete the local representation of the post
4. When a local post is purged, we will federate out a Delete(Note)
5. Afterwards, if the content is retrieved, we will serve a 404
   • The note will no longer exist in the context collection
6. If we receive a Delete(Note) (or Article, or Question, etc.) we will not delete it immediately. Instead, as kaniini advises, we will attempt to retrieve the object from the origin:
   • If we see an as:Tombstone, we will delete the post (soft delete)
   • If we encounter a 404 or 410, we will purge the post (hard delete)

I'm writing this out less as a guideline for myself, but to solicit opinions and to give others a chance to point out if I've interpreted the spec incorrectly.

@julian i still say delete only makes sense as a cache invalidation when it comes to remote content. that hasn’t changed

@julian I'm focusing on Deletion (both Notes and Actors) in Discourse at the moment and I'm thinking of essentially adopting the approach you've outlined here. Have there been any updates to your approach since you wrote this?

Thanks for clarifying.

1. I am reasonably sure that nobody else besides NodeBB (and now Discourse) knows what to do with an Update(Tombstone), so nothing happens. It means soft deleted posts on our end are essentially ignored and still visible.

The latter may actually be a concern and warrant an admin-side option to explicitly federate out a Delete.

Yeah, I'm currently weighing this one. I'm wondering whether Update(Tombstone) really makes sense. I can see why you took that approach. I'm just mulling the implications, particularly

It means soft deleted posts on our end are essentially ignored and still visible.

I'm currently thinking users may find this surprising and it may interfere with things like moderation. But I'm still mulling it.

tbh the more I think about this, the more it feels like federating Update(Tombstone) is never going to work very well.

We'd first have to win the argument that federating Tombstones make sense at all. I found the arguments to the contrary relatively persuasive on that front (I know you're aware of this, but just giving context for other folks reading this):

The Delete Activity And It's Misconceptions

Instead of using my personal blog, I’m going to just start writing about ActivityPub here instead, as I think it is more useful to have a central repository of all knowledge relating to ActivityPub that is easily searcha…

SocialHub (socialhub.activitypub.rocks)

I wonder if we can't just do point 6 on your list:

If we receive a Delete(Note) (or Article, or Question, etc.) we will not delete it immediately. Instead, as kaniini advises, we will attempt to retrieve the object from the origin:

• If we see an as:Tombstone, we will delete the post (soft delete)
• If we encounter a 404 or 410, we will purge the post (hard delete)

So to play that out:

PublisherPost is deleted

1. On soft delete:
   • Convert (Note|Article) to Tombstone
   • Federate Delete(Note|Article)
2. On hard delete:
   • Delete (Note|Article)
   • Federate Delete(Note|Article)

ReceiverReceives Delete(Note|Article)

1. Remote (Note|Article) returns Tombstone
   • Convert (Note|Article) to Tombstone
   • Soft-delete associated post.
2. Remote (Note|Article) returns 404 (or 410)
   • Delete (Note|Article)
   • Hard-delete associated post.

I recognize that this makes the Delete activity work differently for S2S than it does C2S, which is to say that a user or client cannot distinguish between "soft delete" and "hard delete" this way. Otherwise, the "cache invalidation" idea is a sensible one.