devol
/
ecosistema-social-decentralizzato
mirror of https://gitlab.com/bluesky-community1/decentralized-ecosystem.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update activitypub.md

This commit is contained in:
Golda Velez 2020-05-18 00:17:43 +00:00
parent e97b25c503
commit 03757ad728
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
protocols/activitypub.md
View File

@ -12,12 +12,22 @@ Account credentials are managed by the user’s instance, so if users forget the
### Data Storage/Message Persistance
As a federated system, ActivityPub is not opinionated about how messages are persisted as long as each server follows the protocol requirements. Each server is expected to maintain an inbox and outbox for each of its users.
### Moderation/Reputation
Each instance sets its own moderation policies, either through the unilateral decisions of an admin, or through some sort of collective vote. Admins can ban entire instances, cutting off their visibility. If an instance gets banned by many others, its users can still talk with each other, but they will be isolated from the rest of the Fediverse. This happened to Gab.com, which set up an instance.
### Social/Discovery
Messages are addressed to a user at a specific server, and normal DNS and ip address routing are used to find the server addressed.
Users can push messages to the special 'public' group which makes them available to all interested users. "Like"s and "Follow"s may be used by servers to determine which public messages to accept/retrieve. For example, the followers of a user who Likes a post may receive the post in their feed.
Instances may accept delivery of messages addressed as 'public' to a shared inbox on the instance but are not required to.
Not clear if there is a global search capability.
### Privacy and Access Control
### Monetization
@ -26,12 +36,22 @@ Federated social networks require both hosting and development costs to maintain
### Interop with other systems
The spec mentions delivery to third-party apps but unsure how/how much this happens in the wild.
Requirements for interop: implement the ActivityPub protocol (are there different requirements for 3rd party receivers?)
### Scalability
### Metrics
### In the wild
[Mastodon](https://mastodon.social/about) (the largest federated network built on ActivityPub) has 2699 nodes and 2.6M users as of 5/2020 (Mastodon home page asserts 4.4M, a bit more than what the-federation.info stats provide; maybe some servers are not counted)
[Pleroma](https://pleroma.social/) is compatible but running different software, also talking the ActivityPub protocol. According to stats at [the-federation.info](the-federation.info), Pleroma has 620 nodes with 35K users as of 5/2020 Users on Mastodon and Pleroma can communicate.
Gab is running a fork of the Mastodon software but has been banned; technically users there could communicate with the others if they were not explicitly banned.
### Links
[https://www.w3.org/TR/activitypub/](https://www.w3.org/TR/activitypub/)