The ActivityPub protocol is a decentralized social networking protocol based upon the [ActivityStreams] 2.0 data format. It provides a client to server API for creating, updating and deleting content, as well as a federated server to server API for delivering notifications and content.
ActivityPub
ActivityPub is a protocol and open standard for decentralized social networking. It provides a client-to-server (C2S) API for creating and modifying content, as well as a federated server-to-server (S2S) protocol for delivering notifications and content to other servers. ActivityPub is the defining standard of the Fediverse, a decentralised social network of various social interaction models, and content types, which consists of independently managed instances of software such as Mastodon, Pixelfed and PeerTube, among others.
ActivityPub Client API: A Way Forward | Steve Bate
The ActivityPub Client-to-Server (C2S) protocol was envisioned as a cornerstone of the decentralized social web, along with the Server-to-Server (S2S) protocol. Standardized by the W3C in 2018, C2S defines how user-facing applications, such as mobile apps or web clients, and bots should interact with social servers using Activity Streams 2.0 and JSON-LD. In theory, it ... Read more
ActivityPub, AT Protocol, and more!
Talking about this article and how ActivityPub and AT Protocol are maybe not as different as people might think. We covered some slides to an unrecorded talk of mine, which explores a lot of things...
FediForum Talk: How To Bullshit Your Way Through a Conversation about ActivityPub
By Evan Prodromou, Social Web Foundation and editor of the ActivityPub standard. One of the best bluffers in the field of distributed social networks gives you just enough knowledge about ActivityP...
ActivityPub
Connect your site to the Open Social Web and let millions of users follow, share, and interact with your content from Mastodon, Pixelfed, and more.
Developer Documentation for ActivityPub & Fediverse | SocialDocs
The comprehensive developer resource for building with ActivityPub, Mastodon, and the Fediverse. Guides, specs, API reference, and tools.
ActivityPub, AT Protocol, and more!
A conceptual model of ATProto and ActivityPub
If you were to design an open social networking protocol, what would that look like? Which metaphors and comparisons would you use to get a general idea of how the network functions? And what would you answer if people ask if your network is decentralised and federated?
ActivityPods - Personal data spaces powered with ActivityPub
Brings together ActivityPub and Solid Pods and empowers developers to create truly decentralized applications.
neodb-social/neodb
๐งฉ a self-hosted server tracking what you read/watch/listen/play, powering a global distributed community federating via ActivityPub and ATProto.
Many people are talking about decentralized social media protocols like #ActivityPub and #ATProto and all the amazing things one can do with them. But do you actually know how they work? We thought we'd do something about this. Come to #FediForum next week if you are curious and like to find [โฆ]
Original post on mastodon.social
mastodon.socialThere are a lot of architectural bits, but if I had to pick one design feature it's Lexicons. Lexicons allow for new shared data types and structures in a way that are immediately available on network for any other service provider to adopt. Getting shared agreement in ActivityPub is hard.
Pedro Vezza
Why did you decide to bet on atproto over Mastodon or similar?
I'm certainly not against saying what I think AT Protocol has wrong. github.com/swicg/activitypub-api/issues/โฆ
