Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DIP-227 User Data Operations #227

Closed
p5150j opened this issue Jan 30, 2023 · 0 comments
Closed

DIP-227 User Data Operations #227

p5150j opened this issue Jan 30, 2023 · 0 comments
Assignees
@wesbiggs
Labels
blocked Blocked by another issue documentation Improvements or additions to documentation DSNP enhancement New feature or request

Comments

@p5150j
Copy link

p5150j commented Jan 30, 2023

Create a DIP that describes the new Replace User Data and Get User Data operations, their parameters, and outputs, as well as the User Data Changed Record.
@p5150j p5150j added documentation Improvements or additions to documentation enhancement New feature or request blocked Blocked by another issue labels Jan 30, 2023
@p5150j p5150j added the DSNP label Jan 31, 2023
@wesbiggs wesbiggs mentioned this issue Feb 7, 2023
Closed
3 tasks
@wesbiggs wesbiggs changed the title DIP: User Data Operations DIP-227 User Data Operations Feb 10, 2023
@wesbiggs wesbiggs mentioned this issue Feb 12, 2023
Merged
3 tasks
@wilwade wilwade mentioned this issue Feb 17, 2023
Closed
wesbiggs added a commit that referenced this issue Mar 10, 2023
@wesbiggs @wilwade
DIP-225/DIP-227 Graph and User Data Operations (#233)
e59cb82 
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:
---------------
- [ ] Added new page on User Data and included in navigation links
- [ ] Added items to Operations and Records tables
- [ ] Rewrote Graph page to define relevant user data types and the PRId
algorithm

Steps to Verify:
----------------
1. Generate HTML with `npm run build`
2. Review spec site for content and formatting
1. Check for errors with `npm run lint`

---------

Co-authored-by: Wil Wade <wil.wade@unfinished.com>
@p5150j p5150j closed this as completed Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wesbiggs wesbiggs

Labels
blocked Blocked by another issue documentation Improvements or additions to documentation DSNP enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@p5150j @wesbiggs