mirror of
https://gitlab.com/bluesky-community1/decentralized-ecosystem.git
synced 2025-01-24 16:00:39 +01:00
Restructure topics, add network structure doc
This commit is contained in:
parent
bc53d7da10
commit
c60bcd2e06
@ -19,7 +19,9 @@ Overviews of decentralized social networks
|
||||
|
||||
## Topics:
|
||||
|
||||
This is a suggested list of how we could organize by topic. Under each topic, we can address how existing protocols and projects have addressed it.
|
||||
This is a suggested list of how we could organize by topic in the `topics` directory.
|
||||
|
||||
This section will be structured as comparisons between how protocols handle these core topics. Under each topic, we can address how existing protocols and projects have addressed it. Can evaluate pros and cons, as well as include concepts from projects not covered more in depth elsewhere.
|
||||
|
||||
#### Network structure
|
||||
|
||||
@ -32,8 +34,9 @@ This is a suggested list of how we could organize by topic. Under each topic, we
|
||||
#### Identity
|
||||
|
||||
- Decentralized identity
|
||||
- Key verification
|
||||
- Key backup
|
||||
- Key management
|
||||
- Key verification
|
||||
- Key backup
|
||||
- Reputation, Trust
|
||||
- Account recovery
|
||||
- Privacy
|
||||
|
43
topics.md
43
topics.md
@ -1,43 +0,0 @@
|
||||
# Topics
|
||||
|
||||
This section will be structured as comparisons between how protocols handle these core topics. Can evaluate pros and cons, as well as include concepts from projects not covered more in depth elsewhere. If this section expands a lot, it can also be organized into separate files in a directory.
|
||||
|
||||
#### Network structure
|
||||
|
||||
- Federation
|
||||
- P2p
|
||||
|
||||
#### Identity
|
||||
|
||||
- Decentralized identity
|
||||
- Key management
|
||||
- Reputation, Trust
|
||||
- Account recovery
|
||||
- Privacy
|
||||
|
||||
#### Data
|
||||
|
||||
- Data models
|
||||
- Data availability
|
||||
|
||||
#### Money
|
||||
|
||||
- Business models
|
||||
- Payment
|
||||
|
||||
#### Filtering
|
||||
|
||||
- Queries
|
||||
- Curation
|
||||
|
||||
#### Moderation
|
||||
|
||||
- Protocol level
|
||||
- Server level
|
||||
- User level
|
||||
- Content level
|
||||
|
||||
#### Governance
|
||||
|
||||
- Upgrading protocols
|
||||
- Organizational structure
|
12
topics/network-structure.md
Normal file
12
topics/network-structure.md
Normal file
@ -0,0 +1,12 @@
|
||||
# Network Structure
|
||||
|
||||
Federated approach to decentralized network architectures can be categorized as federation where you pass messages between systems (SMTP, XMPP, ActivityPub), and federation where you replicate data between systems (Git, Matrix, NNTP).
|
||||
|
||||
P2p networks can be analyzed on a spectrum of fully distributed and p2p, to partially distributed. Supernode architectures, and points of logical centralization in p2p systems, should be addressed.
|
||||
|
||||
- i.e. Textile cafes peers as p2p network infrastructure (https://docs.textile.io/concepts/cafes/)
|
||||
|
||||
Hybrid federated/p2p approaches should be considered - i.e. a client-server architecture, where you can optionally run the server client-side.
|
||||
|
||||
- i.e. Matrix's new P2P work
|
||||
- categorization of blockchain light clients?
|
Loading…
Reference in New Issue
Block a user