DIP-225 Social Graph / DIP-227 User Data Operations #231
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
DSNP needs a way of specifying various user-related data that allows an implementation flexibility in storing social graph data while standardizing data formats and application layer data interaction semantics. GitHub issues: #225 #227
Solution
The proposed user data spec strikes a compromise between the need for blockchains to segment data in optimal ways and the desire, from an application developer's point of view, to have data in an easy to work with format, whilst specifying details of schema, compression and encryption to ensure interoperability.
The user data types for the social graph that follow this approach are public follows, private follows, private connections, and private connection PRIds, and the spec describes how each is generated and interpreted.
Change summary:
Steps to Verify:
npm run build
npm run lint