







Today we’ll be looking at how to connect the protocols powering Mastodon in the simplest way possible to enter the federated network. We will use static files, standard command-line tools, and some simple Ruby scripting, although the functionality should be easily adaptable to other programming languages. First, what’s the end goal of this exercise? We want to send a Mastodon user a message from our own, non-Mastodon server. So what are the ingredients required? The message itself will be formatted with ActivityPub, and it must be attributed to an ActivityPub actor. The actor must be discoverable via Webfinger, and the delivery itself must be cryptographically signed by the actor.
FediGames
I’ve started this project to learn about the ActivityPub protocol. FediGames is a small ActivityPub server which provides games as services to the fediverse. The games are played by mentioning the game service and your opponent(s). I’ve many tested this with Mastodon and Firefish, hopefully other applications also work. If you are looking for an opponent feel free to challenge me for a round of bunkers 🙂 @bunkers@games.rerere.org @h4kor@chaos.social Server: https://games.rer...

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, Lemmy, and PeerTube, among others.
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
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
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 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

FEP-1042: Peer to Peer Fediverse Identities
Hey folks, we at [Distributed Press](https://distributed.press) have been working on making a bridge between peer to peer or "dweb" protocols and ActivityPub implementations over the past year and wanted to solidify our approach so that others can interoperate. Here's is an initial draft expla...
How to Create Your Own Decentralized Messenger Protocol - Build it yourself
Ever wondered how to build a decentralized messenger without any central servers? It's all about federation - just like email! In this post, I'll show you how to design a simple protocol from scratch, from server discovery using .well-known files to handling end-to-end encryption.

Why ActivityPub is the future
We often tout things like “Mastodon is based on open web protocols” as one of its advantages. I want to elaborate why exactly that’s a good thing.

One Login: Towards a Single Fediverse Identity on ActivityPub
On fediverse apps like Mastodon, Pixelfed and (soon) Threads, content is federated — but identity isn’t. We look at potential solutions.

Integrating ActivityPub within Solid specs
I’ve been spending a bit of time catching up on this discussion and experimenting. I have successfully subscribed to remote ActivityPub actors and processed inbox activities. (My write-up: JG10 Solid devlog ) I ended up using an architecture not yet mentioned here, in which the inbox and outbox are public append LDP containers that receive activities. Solid notifications are used to notify an external agent that reads the new activity and processes it. This works because Solid already supports...

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.

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...
Cross-server Interactions in ActivityPub
So, Richard McManus asked me about how ActivityPub supports cross-server usage. As an example use case, let’s say a user with the account eric@social.example wants to comment on a photo by di…

I'm certainly not against saying what I think AT Protocol has wrong. github.com/swicg/activitypub-api/issues/…