Switch Tombstones from targeting signatures (going away in DIP-#145) to targeting contentHash.
Motivation
Signatures do not provide great targets, whereas hashes are part of the DSNP Content URI and are considered unique on a per-user basis thanks to #158.
See #145 for additional details about why signatures are going away.
Specification Pull Request
Current change pull request: #181
Rationale
We realized there are two types of announcements: ones that are additive (Broadcast, Reply, etc...) and ones that are "state changes" (Graph Change, Reaction, etc...). Tombstones (and Updates DIP-#174) are for altering the state of these additive announcements. This means that we should target these announcements more specifically and with an easier path.
Alternatively we could target the DSNP Content URI. This is a more flexible setup. However it would allow for targeting content from other DSNP Ids or other arbitrary data that might slip through validation.
Backwards Compatibility
Breaking Change
This is a breaking change and should be included in DSNP v1.1.
Security Considerations
This should improve security.
Dependencies
DIP-#149
References
DIP-#145 has much of the discussion around this topic
Abstract
Switch Tombstones from targeting signatures (going away in DIP-#145) to targeting
contentHash.Motivation
Signatures do not provide great targets, whereas hashes are part of the DSNP Content URI and are considered unique on a per-user basis thanks to #158.
See #145 for additional details about why signatures are going away.
Specification Pull Request
Current change pull request: #181
Rationale
We realized there are two types of announcements: ones that are additive (Broadcast, Reply, etc...) and ones that are "state changes" (Graph Change, Reaction, etc...). Tombstones (and Updates DIP-#174) are for altering the state of these additive announcements. This means that we should target these announcements more specifically and with an easier path.
Alternatively we could target the DSNP Content URI. This is a more flexible setup. However it would allow for targeting content from other DSNP Ids or other arbitrary data that might slip through validation.
Backwards Compatibility
Breaking Change
This is a breaking change and should be included in DSNP v1.1.
Security Considerations
This should improve security.
Dependencies
References
Copyright
Copyright and related rights waived via CC0.