felixfoertsch/decentralized-ecosystem
1
0
Fork 0
mirror of https://gitlab.com/bluesky-community1/decentralized-ecosystem.git synced 2026-04-17 23:08:34 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update AP, p2p img, moderation, privacy

Browse Source
This commit is contained in:
Jay Graber
2020-07-12 13:36:55 -07:00
parent 2515123c76
commit 263a42f650
5 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
protocols/activitypub.md
View File

@@ -54,7 +54,7 @@ Mastodon is currently [adding e2e encryption to ActivityPub](https://github.com/
Any service that implements the ActivityPub server-to-server protocol can interoperate with the ecosystem. A service like Twitter would need to add Webfinger and JSON-LD representations of users and tweets.
The client-to-server protocol is rarely used in practice, but defines a standard way for user client software to connect to ActivityPub servers, creating a universal client ecosystem. If it were widely used, a user application could mix and match different servers like Mastodon, Pleroma, PixelFed, and any new service that implemented the client-to-server protocol.
The client-to-server protocol defines a standard way for user client software to connect to ActivityPub servers. In practice, it is rarely used. None of the major Fediverse services implement it. The vision of how it would work if it were widely used is that a user application could mix and match different servers like Mastodon, Pleroma, PixelFed, and any new service that implemented it.
Diaspora, another federated social network, chose not to adopt ActivityPub.