







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...
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
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.
How to implement a basic ActivityPub server
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.
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...
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...
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

Introducing the ASML ActivityPub Fuzzer: Improving Testing in the Fediverse - Applied Social Media Lab at Harvard University
The ActivityPub Fuzzer is a small program to help developers build social media software on the Fediverse by emulating known Fediverse software.

The Magic of Federation | An interview with Matthias Pfefferle
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.

Welcome | Takahē
Takahē is an ActivityPub server designed for efficient use on small- to medium-size installations, and which allows you to host multiple domains on the same infrastructure. It’s currently in an beta state, meaning most things work and it can talk to most of the Fediverse, but there’s still some polish and features left to add. The flagship instance can be found at takahe.social, and if you’re interested, you can also learn more in our documentation, browse the code on our GitHub repository, come and chat to us on Discord, or read some of Andrew’s blogs about building it.
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.

ActivityPub, AT Protocol, and more!
Alright @jay.bsky.team @pfrazee.com @dholms.xyz @why.bsky.team @emily.bsky.team ..restofbskyteam hear me out network of ActivityPub servers = "fediverse" so federated AT Protocol / BlueSky = "ATmosphere" ;) okay sorry for pinging you all have a nice day
Alright @jay.bsky.team @pfrazee.com @dholms.xyz @why.bsky.team @emily.bsky.team ..restofbskyteam hear me out network of ActivityPub servers = "fediverse" so federated AT Protocol / BlueSky = "ATmosphere" ;) okay sorry for pinging you all have a nice day