This commit is contained in:
Jay Graber
2020-06-16 17:58:11 -07:00
parent 30338f4e39
commit ce0a2dde64
7 changed files with 78 additions and 60 deletions

View File

@@ -12,7 +12,7 @@ Account credentials are managed by the users 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.
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
@@ -22,7 +22,7 @@ Each instance sets its own moderation policies, either through the unilateral de
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.
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.
@@ -40,22 +40,24 @@ 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.
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?)
Requirements for interop: implement the ActivityPub protocol (are there different requirements for 3rd party receivers?)
### Scalability
### Metrics
### In the wild
### Implementations & Applications
[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)
List of ActivityPub projects: https://github.com/BasixKOR/awesome-activitypub
[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.
[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/)
[https://www.w3.org/TR/activitypub/](https://www.w3.org/TR/activitypub/)