Add edits
This commit is contained in:
parent
2522ef21e1
commit
989b4035d2
|
@ -1,26 +1,25 @@
|
|||
# Data & Discovery
|
||||
# Data
|
||||
|
||||
Data structures, data availability, persistence, and mutability in decentralized applications.
|
||||
Data portability
|
||||
### Data Models
|
||||
|
||||
Decentralized systems do not have a single central system to coordinate updates.
|
||||
Shared data models enable interoperability.
|
||||
|
||||
### Data availability
|
||||
Solid - Solid's data model is RDF. [RDF](https://www.w3.org/RDF/) uses URIs to name the relationship between things, allowing structured data to be shared across different applications. RDF could potentially [be a barrier to adoption](https://hal.inria.fr/hal-01966561/document), due to its complexity.
|
||||
|
||||
No server has a unified global view of a decentralized network.
|
||||
Matrix - Matrix transports messages using JSON, and tracks conversation history through DAGs.
|
||||
|
||||
Data is only available along user connections or the follow graph, whether that is determined by node or by server.
|
||||
Mastodon - ActivityPub uses streams of JSON-LD. Mastodon was formerly compatible with OStatus, which used RSS.
|
||||
|
||||
Mastodon - No global search functionality
|
||||
IPFS - IPFS uses a custom data model, [IPLD](https://ipld.io/), designed to treat hash-linked data structures as subsets of a unified information space.
|
||||
|
||||
Ssb - Ssb uses append-only logs of signed JSON.
|
||||
|
||||
### Mutability
|
||||
|
||||
Federated applications allow users to edit and delete content, handled at the server level. Content may not be guaranteed to be deleted across the entire network in some cases - protocols should require applications to honor delete messages.
|
||||
|
||||
P2p applications have more variance around mutability.
|
||||
|
||||
Ssb & Hypercore - Messages added to the append-only log are immutable. Applications can choose not to display messages indicated as deleted, but the data cannot be overwritten.
|
||||
|
||||
IPFS - Once added to a network, content is discoverable by its hash. If a copy remains stored on the network, it is re-discoverable by this reference.
|
||||
|
||||
### Data structures
|
||||
|
||||
JSON-LD
|
||||
|
||||
RDF
|
||||
|
|
|
@ -5,3 +5,11 @@ In decentralized networks, whether federated or p2p, there is often no global se
|
|||
This issue being discussed in Mastodon: https://github.com/tootsuite/mastodon/issues/9529
|
||||
|
||||
Hashtags are used to filter and discover content in ssb, diaspora, mastodon
|
||||
|
||||
### Data availability
|
||||
|
||||
No server has a unified global view of a decentralized network.
|
||||
|
||||
Data is only available along user connections or the follow graph, whether that is determined by node or by server.
|
||||
|
||||
Mastodon - No global search functionality
|
||||
|
|
|
@ -18,7 +18,7 @@ Desirable qualities for decentralized identities:
|
|||
|
||||
## Decentralized Identity
|
||||
|
||||
OAuth is currently the most successful identity standard. OAuth was created to securely transfer user credentials from one site to another. OAuth identity providers became centralized because users could not run or choose their own identity providers.
|
||||
OAuth is currently the most successful identity standard. OAuth was created to securely transfer user credentials from one site to another. OAuth identity providers became centralized because users could not run or choose their own identity providers. (See decentralized identity protocol comparisons in [Decentralizing the Social Web](https://hal.inria.fr/hal-01966561/document))
|
||||
|
||||
### Identity in federated applications:
|
||||
|
||||
|
@ -41,18 +41,20 @@ P2p systems key management, key verification, key backup. Account recovery.
|
|||
- Aether
|
||||
- Iris
|
||||
|
||||
### Blockchain identity
|
||||
### Blockchain Identity
|
||||
|
||||
In 2001, Zooko Wilcox-O'Hearn named three desirable properties of decentralized network identifiers: human-meaningful (memorable), decentralized (global), and secure (unique). This became known as [Zooko's triangle](https://en.wikipedia.org/wiki/Zooko%27s_triangle). Prior to the invention of cryptocurrency blockchains, which enabled decentralized global consensus, it was thought that only two of these three properties could be achieved at one time. Now, many projects have created protocols for naming systems that fulfill all three properties.
|
||||
|
||||
- Namecoin
|
||||
- Blockstack
|
||||
- Handshake
|
||||
|
||||
Lots of them.
|
||||
Microsoft
|
||||
IBM
|
||||
- Microsoft
|
||||
- [IBM](https://www.ibm.com/blockchain/solutions/identity/networks) - IBM is helping to create, operate and maintain permissioned decentralized identity networks built using Hyperledger
|
||||
|
||||
### Decentralized Identifiers (DIDs)
|
||||
|
||||
[DIDs](https://w3c-ccg.github.io/did-primer/) are a new type of globally unique identifier that do not require a centralized registration authority, and can serve as a decentralized public key infrastructure. DIDs are a [W3C standard](https://www.w3.org/TR/did-core/).
|
||||
The [DID W3C standard](https://www.w3.org/TR/did-core/) is an emerging standard around decentralized identifiers. [DIDs](https://w3c-ccg.github.io/did-primer/) are a new type of globally unique identifier that do not require a centralized registration authority, and can serve as a decentralized public key infrastructure.
|
||||
|
||||
The format of a DID is: a scheme identifier, followed by the DID method, followed by a method-specific identifier. A simple example: `did:example:123456789abcdefghi`
|
||||
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
# Moderation
|
||||
|
||||
One of the most acute problems with centralized platforms is the need to develop one-size-fits-all moderation policies for billions of users. Decentralizing social platforms places the power to determine moderation policies in the hands of users or communities.
|
||||
One of the most acute problems with centralized platforms is the need to develop one-size-fits-all moderation policies for billions of users. Decentralizing moderation puts decisions about what content to block or allow in the hands of users and communities.
|
||||
|
||||
## Moderation in federated systems
|
||||
## Community moderation
|
||||
|
||||
### Matrix
|
||||
|
||||
|
@ -10,10 +10,18 @@ Servers in Matrix have terms of use that users agree to when they join. Rooms ma
|
|||
|
||||
### Mastodon
|
||||
|
||||
Each server admin can create their own moderation rules as well as a theme for their server. Their TOS may include rules about whether data can leave the server, etc. Users choose which server to join, opting into the moderation policy, theme, and TOS they prefer.
|
||||
Each server admin can create their own moderation rules as well as a theme for their server. Their TOS may include rules about whether data can leave the server, etc.
|
||||
|
||||
## Moderation in p2p systems
|
||||
### Reddit
|
||||
|
||||
## Experiments
|
||||
### Aether
|
||||
|
||||
Curation and moderation markets
|
||||
Users elect and impeach topic moderators.
|
||||
|
||||
## User moderation
|
||||
|
||||
User level moderation allows users to opt into different content preferences, for example subscribing to shared blocklists, or enabling certain filters.
|
||||
|
||||
# Mastodon
|
||||
|
||||
Users choose which server to join, opting into the moderation policy, theme, and TOS they prefer.
|
||||
|
|
|
@ -9,6 +9,6 @@ Some e2e messaging encryption options:
|
|||
|
||||
### Access Control
|
||||
|
||||
There may be a need for different levels of access to user data - for example, to create read-only applications, paywall, or private sharing.
|
||||
Different levels of access to user data can be controlled through server permissions on federated systems. In p2p systems, access control must be implemented through cryptographic permissions, or access control lists.
|
||||
|
||||
Object capability security authorization system
|
||||
|
|
Loading…
Reference in New Issue