You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When remote objects are received, they are parsed and a local representation is saved to the database.
Occasionally, we may want to delete these notes (e.g. pruning, received deletion, etc.)
Existing NodeBB logic should be updated so that if an existing remote post is passed in, all additional references added by src/activitypub/notes.js are handled.
When fetched via S2S, a Tombstone object should be served for deleted posts
When local posts are deleted, an Update(Tombstone) should be federated out
Likewise for post restoration
Upon receipt of an Update(Tombstone), the local representation of the Note should be soft deleted
When posts are purged, a Delete(Note) should be federated out
Upon receipt of a Delete(Note), the Note should be re-retrieved. If 404/410, purge. If Tombstone, delete.
The text was updated successfully, but these errors were encountered:
When remote objects are received, they are parsed and a local representation is saved to the database.
Occasionally, we may want to delete these notes (e.g. pruning, received deletion, etc.)
Existing NodeBB logic should be updated so that if an existing remote post is passed in, all additional references added by
src/activitypub/notes.js
are handled.Update(Tombstone)
should be federated outUpdate(Tombstone)
, the local representation of the Note should be soft deletedDelete(Note)
should be federated outDelete(Note)
, the Note should be re-retrieved. If 404/410, purge. If Tombstone, delete.The text was updated successfully, but these errors were encountered: