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
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
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, 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.
granary: the social web translator
Fetches and converts data between social networks, HTML and JSON with microformats2, ActivityStreams 1 and 2 (including ActivityPub), Atom, RSS, JSON Feed, and more.
neodb-social/neodb
🧩 a self-hosted server tracking what you read/watch/listen/play, powering a global distributed community federating via ActivityPub and ATProto.
OAuth Client Implementation | Bluesky
This is a guide to implementing atproto OAuth clients "The Hard Way." Optimistically, most developers will have an SDK available for their programming language which supports OAuth, and they can simply refer to SDK documentation. This guide is intended for early adopters, SDK maintainers, or developers with more sophisticated OAuth needs. It is agnostic to whether developers are building clients to work the the app.bsky microblogging Lexicons, or implementing novel application Lexicons.
I'm certainly not against saying what I think AT Protocol has wrong. github.com/swicg/activitypub-api/issues/…
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.socialAtmosphere social client apps should make it easier to broadcast beyond the protocol. Ex. In-app mirroring tools for Threads, X, and other microblogging platforms. As well as having post scheduling. Let people share across the social internet, but make sure ATproto feels like home base.
