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
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.
wilwade
changed the title
Update requirement for publish date (required=true)
DIP-158 Make published required in Activity Content Type Note
Mar 31, 2022
Abstract
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
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
Profile
type 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.
The text was updated successfully, but these errors were encountered: