While updating #145 and then #148 we realized that content hashes should be "required" to be unique, achievable via making the published field required.
Motivation
We want users to still be able to publish the same content more than once, but have replies, reactions, and other references be separated. (For example, "Good morning!")
Specification Pull Request
Current change pull request: TODO
Additional Actions
[ ] Create story in activity-content to update requirement
[ ] Create story in activity-content-java to update requirement
[ ] Create story in activity-content-swift to update requirement
Rationale
The other alternatives required more on chain data. This reduces the on chain data while still maintaining the same level of trust.
Requiring published on the Profile type does not appear to be necessary as it already uses a last profile wins resolution algorithm.
Backwards Compatibility
While this is a breaking change, as of this publishing no content exists without said value. It is already the effective default
Security Considerations
While users could lie about the date, as duplicate Announcements are ignored, the purpose of generating unique hashes is as secure as it was before.
Abstract
While updating #145 and then #148 we realized that content hashes should be "required" to be unique, achievable via making the
publishedfield required.Motivation
Specification Pull Request
Current change pull request: TODO
Additional Actions
Rationale
The other alternatives required more on chain data. This reduces the on chain data while still maintaining the same level of trust.
Requiring published on the
Profiletype does not appear to be necessary as it already uses a last profile wins resolution algorithm.Backwards Compatibility
Security Considerations
While users could lie about the date, as duplicate Announcements are ignored, the purpose of generating unique hashes is as secure as it was before.
Dependencies
None
References
Copyright
Copyright and related rights waived via CC0.