-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Problem ======= DSNP should provide affordances for finding content that do not rely on a single DNS-based point of failure for content hosting. More in the original discussion: #273 Solution ======== Enhance the specification to treat URLs in Announcements as suggestions rather than canonical locations for content. Provide a simple and well-specified set of hashes and encodings that can be used consistently throughout the protocol. Use IPFS CIDv1 specifically for locating profiles. Change summary: --------------- * Broaden ProfileResource definition so that different types of profile resources can use different, possibly distributed, file systems via a generic `contentAddress` field * Simplify multihashes to use base32 encoding only and sha2-256 or blake3 as the hashing algorithm * Update various example hashes in line with this * Update to pre-1.3.0 versioning and sync prerelease changelogs for other recent additions to the spec * Change spec language to expand on how to treat content hash + URL pairs. * Announcements use the same base32 encoded multihash for the `contentHash` and `targetContentHash` fields. --------- Co-authored-by: Wes Biggs <wes.biggs@amplica.io>
- Loading branch information
Showing
16 changed files
with
104 additions
and
110 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.