jrollans.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
I was on a #mastodon instance for a while, hosted by a tech Youtuber. When that instance shut down, I moved to another independently hosted mastodon instance, then decided to self-host a Pleroma (alternative to mastodon) server and have been on that ever since (a couple years).
The call for proposals is open for the COSCUP Fediverse track in Taipei, Taiwan. ActivityPub-related software, including server and client implementations, are great topics for the event.
COSCUP (“Conference for Open Source Coders, Users, and Promoters”) is the FOSDEM of East Asia. Run by the Open Source community in Taiwan, it brings together people excited about FOSS across the region.
For the first time, this year, members of the Korean ActivityPub developer community FediDev KR are joining up with FediLUG of Japan to program and run a Fediverse track at COSCUP. This has the potential to be a huge step forward for the Fediverse developer community. Although many major projects, like Fedify and Misskey, are created and promoted in East Asia, distance and language barriers make it hard for East Asian devs to participate in European and North American in-person events.
The Fediverse track is open to proposals about ActivityPub implementations, clients for ActivityPub platforms, ancillary services, libraries and toolkits. But also, as at FOSDEM, talks about the human aspects of Fediverse technology, like moderation, policy and governance, are welcome and encouraged. This event looks like it will cover as much interesting conceptual space as its twin at FOSDEM.
Hong Minhee, hongminhee@hollo.social, was one of the main speakers at FOSDEM’s Social Web devroom this year. Their talk about Fedify was important, but even more important was their effort to bridge the gap between Asia’s and Europe’s Fediverse development communities.
I (Evan) hope that COSCUP brings together many Asian developers, but I also hope that North American and European individuals and teams put in proposals as well. Knitting together these two important communities on the Fediverse requires effort from both sides. That’s why I’m applying to speak (about ActivityPub 1.1), and why I hope to see many familiar faces among the new ones in Taiwan.
RE: https://mastodon.social/@bagder/116359048796181736
Could be potentially nice for fediverse server testing, as more implementations make the jump to final RFC 9421 HTTP signatures.
On the flip side, ever more complex curl invocations (here: Accept header plus signature fields plus key file, presumably) suggest use of more specialized CLI tools, such as provided by @fedify, or at least scripts/aliases.
Speaking of RFC 9421, which notable fediverse implementations can't handle it yet? Anyone keeping track?
When someone asks me what the #Fediverse, #Mastodon or #ActivityPub is I'll use this illustration from UNIX Review, April 1985.
When I interviewed @Gargron he said that education was key to @Mastodon and the fediverse growing. That, along with the algorithm-free approach of most ActivityPub-supporting platforms, inspired me to create https://algo.free
It covers the benefits of going algo-free, provides ActivityPub-powered alternatives to centralized, algo-driven platforms, and offers tips for getting started.
C’è una sorpresa per voi nell’uovo di Pasqua! 🐣
Per tutti coloro che vogliono capire come funziona il fediverso grazie al protocollo ActivityPub ed iniziare a muovere i primi passi nei social network decentralizzati:
The #SEO community is now turning against #ownedmedia in favor of "being part of the conversation".
In other words, "go spam #reddit with your crap self-promotional content" so the LLMs will (hypothetically - not theoretically) include your brand in their citations.
I'm much more fond of the idea of taking advantage of federation on "owned media". It's still in its infancy but it's improving.
And anyone who operates a #wordpress blog is only an #activitypub plugin away from federating their content.
As always, we are looking for people to help test, this time single-user instance self-hosting. If you are interested in a activitypub-enabled self-host linktree alternative check https://github.com/tryvocalcat/fediprofile now with SingleUser mode enabled!
I've been working on a highly customizable multiplatform fediverse client, similar to bridging technologies that exist currently but a bit more seamless and robust, and focused on the indieweb vibe and personal customization overall. Excited to get it out there for testing, but I am really enjoying what I have so far. #interop #atproto #activitypub #retro #indieweb
#ActivityPub developers: which of these HTTP caching headers does your software publish or consume?
| Last-Modified: | 5 |
| ETag: | 6 |
| If-Modified-Since: | 3 |
| If-None-Match: | 3 |
Week in Fediverse 2026-04-03
Servers
- TinyAP v0.1.7
- Iceshrimp v2026.4.1
- Gush! v0.0.34
- Ktistec v3.3.5
- Socialhome v0.23.0
- PeerTube v8.1.4
- Misskey v2026.3.2
- NeoDB v0.13.0
- PieFed v1.6.14
- Wafrn v2026.03.03
Clients
- nicolium v0.1.2
- Voyager v2.45.1
- Blorp v1.12.0
- Mitra Mini: A headless ActivityPub client that implements FEP-ae97 specification
Tools and Plugins
- Friends v4.0 (WordPress plugin)
For developers
Protocol
- FEP-1a11: Send Announces Containing Many Activities
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019d30f2-2656-7043-04d6-328ad9750e23
Do you have a basic shared hosting plan? You can now host a #Fediverse instance on that plan. Check out #Starling: https://github.com/dfaria-eu/Starling
Idea for experiment: mail to fediverse?
My ambition: having people writing to "username @ domain dot ext" and mail content goes into public, or private, on fediverse "handle @ domain . ext".
Someone already did it? Pros and cons? Disadvantages are more than benefits?
I heard about a trick called "mail2mastodon" but before doing deeper research I first wanted to understand how the effort is, and if it's worth.
A full fediverse instance running on a simple shared host, in pure PHP, with no external dependencies. That is the idea behind Starling:
https://github.com/dfaria-eu/Starling/
#opensource #office #sovereignty #europe #microsoft (bye bye) #privacy #fediverse #activitypub
Please share this. I hope it's the start of something big.
Again looking at running my own #Mastodon instance and seeing a ton of abandoned projects for lightweight, single-user #ActivityPub servers. Are there options that are actively maintained and ready for use? I've run #Pleroma before but don't actually need a web frontend. Happy to @phanpy and that's it. Suggestions, anyone?
Here’s an interesting thought experiment.
Way back in the 1980s and 90s, Usenet was a sorta-federated discussion forum (using the NNTP protocol) that was very popular. It still exists and is distributing 400 million messages each day (mostly spam and trash as far as I can tell). Hard numbers are difficult to come by but it seems like Usenet is capable of significantly higher throughput. Why is that?
The big thing holding ActivityPub back is the fan-out. You know the story - someone with 50,000 followers causes their instance to send up to 50,000 HTTP POSTs every time they click the little spinny star or reply to something.
It’s basically a hub-and-spoke network topology. Except everyone takes turns being the hub, ideally, but not much in practice. And in this topology, the hubs are where the strain and bottlenecks are.
Back in the 1980s they had computers literally 1000 times slower than ours and network links to match. So how did they do this? With a peer to peer network topology! When a new post is made, they don’t send it to everyone they just send it to a handful of other servers. Those servers in turn forward the post on to a handful of other peers, and so on, until the whole network receives the post. No individual server is a single point of failure and none has to bear the full brunt of orchestrating it all.
Let’s do a picture. A creates a post and sends it to B and D.
A ─ B ─ C
\ /
─ D ─
B sends it on to C.
Meanwhile D sends it on the C also but C already has it so does nothing more. IRL this would be a much larger mesh. Who peers with who can be a mixture of manual selection and random spiciness.
Posts can arrive out of order so each server would need to wait until the dependencies between posts are resolved before making them available to clients. That’s a bit tricky.
In the ActivityPub-over-NNTP idea, each NNTP post would be a thin wrapper around a data structure containing the HTTP headers (with signature and digest) and JSON that a normal HTTP POSTed Activity would have. Servers would use NNTP to distribute the activities and upon receiving one they’d POST it to their own /inbox to run the usual ActivityPub processing that their AP instance does.
{
"headers": {
"Signature": "...",
"Digest": "...",
"Date": "..."
},
"activity": { ... normal ActivityPub JSON ... }
}
In this way there is no need to rewrite ActivityPub semantics as only the transport layer changes. Our existing inbox logic remains intact.
NNTP comes with a lot of historical baggage so we’d probably need to evolve the protocol a bit. Maybe use HTTP requests (even http2 streams?) instead of the original line-oriented text protocol using raw TCP sockets. But you get the idea.
Thoughts?
Yes, #HolosSocial is far from perfect, but everything is being done to improve the UX. I still believe in this project because it offers a lot of perspectives, and bad behavior can be fixed.
Thank you to all the people trusting this project. Even if it fails, I am pretty sure it will help push #ActivityPub further.
| yes, for myself and other people: | 12 |
| yes, just for myself: | 32 |
| no, but maybe in the future: | 38 |
| no: | 38 |
Closed
Turns out making an #activityPub server is not the work of a few hours. I may have over-promised.
I know some ActivityPub devs feel jealous of AtProto’s success.
I’ve felt it too.
But really, we shouldn’t.
Every serious step toward decentralization is a win for the open social web.
With tools like Bridgy from @anewsocial, we can stay connected across protocols and keep building a more open future together.
If you really believe in empowering humanity, then this isn’t competition, it’s momentum.
Announcing Mitra Mini v0.1.0
Mitra Mini is an ActivityPub client that implements nomadic identity. It has become stable enough that I decided to cut the first release.
The basic features have been implemented: posts, reposts, likes. For more information, check the project's readme:
https://codeberg.org/silverpill/minimitra
It all started nearly four years ago with a vague idea that linking cryptographic keys to #ActivityPub actors could unlock decentralized identity in Fediverse. Eventually, the solution was discovered, and implemented by several projects, but these implementations were servers, not clients. Now there is finally a client, and the design has been proven to work well.
Friends, if you haven't already, it would be a big favour to me if you could enable tags.pub to boost your public tagged posts.
Just search for @_followback in your Mastodon UI. Click the follow button there. (Don't try to follow from the profile page; it doesn't work yet.)
It will follow you back, and when you make a post with a hashtag in it, the server will boost your post from the appropriate hashtag.
#Holos started at the end of 2025. A full #ActivityPub server now runs on your phone, with the ability to use your own domain as your identity, #E2EE DMs via Signal Protocol, zero-knowledge encrypted backup, #ActivityPub media served from your own cloud, a tailored timeline based on your interests thanks to #HolosDiscover, and the ability to switch views depending on your mood or the content you want to browse. Thank you for your feedback and support that helped to go through these steps.
RE: https://mastodon.social/@HolosSocial/116302845964923188
With #Holos, you can have your identity on your own domain. No server? A simple CNAME record is enough. Already have a server? Point a subdomain to handle #ActivityPub traffic and serve a static JSON file on your root domain.
This is a step toward the same sovereignty #Nostr offers with cryptographic identities, but staying in the #ActivityPub ecosystem you already know.
fedicat boosted#Holos will support custom root domains tomorrow. You'll be able to use @you@yourdomain.com as your identity while #ActivityPub traffic is routed through a subdomain.
With a single user, a simple static json file will be enough on your root domain.PS: if you already use a subdomain, it will work without extra work.
Week in Fediverse 2026-03-27
Servers
- Vernissage Server v1.32.0
- snac v2.91
- Lemmy v0.19.17
- Mitra v5.0.0
- Gush! v0.0.33
- Mastodon v4.5.8
- Hubzilla v11.2.0
- Mobilizon v5.2.3
- NodeBB v4.10.1
- appy v0.5.0
- Madblog v1.3.0
- A Redesign for Profiles (Mastodon)
- TinyAP: Tiny ActivityPub Micro-blogging
- oeee-cafe: The federated and networked oekaki board
- ActivityPub bots: ActivityPub / Mastodon compatible instance to quickly create and deploy multiple bots
- ProFed: Federated professional network
Clients
- Holos v1.1.0
- Fedilab v3.37.2
- Pachli v3.5.0
- Mastodon for iOS v2026.02
- Summit v1.80.0
- Blorp v1.11.0
- Aria v1.4.8
- Announcing Nicolium v0.1.0
- Hackers' Pub Android
Tools and Plugins
- Poduptime v6.3.1
- Enable Mastodon Apps v1.5.0 (WordPress plugin)
For developers
- Fedify v2.1.0
- APx v0.22.0
- Federails v0.8.0
Articles
- Dipping a Toe into the Fediverse (Again)
- Can we have a more “social” media?
- Mastodon (Bluesky/X/Instagram) is not the right platform for posting long-form content (a blog is)
- FediMod FIRES on building better and decentralised social media applications
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019d0d0a-2958-a430-8db0-95350f8495e5
#Holos will support custom root domains tomorrow. You'll be able to use @you@yourdomain.com as your identity while #ActivityPub traffic is routed through a subdomain.
With a single user, a simple static json file will be enough on your root domain.
PS: if you already use a subdomain, it will work without extra work.
My ongoing #ActivityPub projects in order of priority, for anyone waiting for something:
– Interaction policy / reply controls FEP: highest priority, stalled for the past few weeks due to other responsibilities
– @encyclia: probably migrating from Deno+Fresh to Node+Hono for @fedify 2.0, boring infra work
– Updating @fedidevs starter packs for compatibility with @loops and @Mastodon packs: on warm hold, will get to it, but vainly hoping someone will write a Python lib for it before I have to 🙃
Would you like to run your own Mastodon (ActivityPub) bot and don't know how?
Try my tool: https://github.com/nekromoff/mastodon-bots
Easy to install, easy to deploy a bot. And then your bot can do whatever you want - create posts, communicate with people, post images or just sit there doing nothing and being a bot.
@delta might like to have a word with you. 😅
I did not try to make the literal comparison between a person who emails or creates email-related software with #fediverse AP solution development.
What I did want to point out was how blurred the lines are in the #ActivityPub fediverse between stuff that is the protocol, and stuff that is solution development i.e. app-specific / domain-specific.
The anti-patterns I listed are encountered by any newcomer dev who takes an interest in creating fedi apps & services, and is faced with much more than they bargained for when reading the AS/AP specs.
It forms a barrier to entry, decrease in attractiveness to create fedi apps, and devs leaving the space for greener pastures (e.g. to #ATProto or various still-less-mature-than-fedi #P2P protocols)
There are a couple of #ActivityPub projects that focus on providing the good tools that abstract away the complexities of wire-level network comms, and help free the hands of a solution developer to focus more directly on what people need, instead of on plumbing and Babylonian speech confusion of how things fit together. I try to emphasize these projects, e.g. @fedify by listing them higher in the https://delightful.coding.social curated lists.
But their challenge is to offer a kind of reverse to browser quirks mode. Web browsers can handle about any malformed HTML a person throws at it, and still manage to turn that into machine processable form, and make the most of it.
As a fedi toolkit builder you almost need to do the opposite. Focus on offering comprehensive and intuitive API's and functionality to solution developers, and translate it into wire chaos that constitutes the fediverse-protocol-of-the-day.
Thanks
updated attribute must be set to the latest modification date, and an Update activity to the modified Note object be sent out there. There are no provisions for a history of changes or a modification reason that I know of.Say, how are edits to posts managed? Is there any indication an edit happened, a way to see the original\previous versions or to add an explanation for the changes that's not just a "Edit: x-y-z" line?
I suppose this might more a question for the #ActivityPub tag tho'.
With the news of the secret $100 million investment in Bluesky by Bain, I keep thinking about protocols.
Maybe the perceived "drawbacks" of #ActivityPub are ultimately strengths?
#ATproto handles identity in a way that allows a single sign-in across apps. But wouldn't this make it easier to profile you? Is this why crypto VCs are so attracted to it?
And ATproto has funding in the 100s of millions by VCs but at some point they'll want to turn a profit. There is ZERO pressure here to ensh*tt*fy
Thanks to oxzi, matoken, Louis Merlin, dandelions, Bruno Cesar Rocha and any other contributors I may have missed as well!
I submitted a Pull Request to update MacPorts' snac to 2.91 here:
https://github.com/macports/macports-ports/pull/31777
GitHub Continuous Integration checks are running, hopefully they will complete without issues?
Regardless, it's up to someone else with commit access to merge it!
#snac #MacPorts #OpenSource #ActivityPub #Mastodon #NoDatabaseNeeded
#NoJavaScript #NoCookiesEither #NotMuchBullShit #snacAnnounces
Fixed some local posts not being shown if the replied post is deleted.
Fixed web UI incorrect links to public posts for some configurations.
Fixed encoding bug in Mastodon-style share links.
Fixed an error that made imposible to leave empty the following hashtags or blocked hashtags from the web UI.
Include post attachments in the RSS feed entries.
Added some OpenBSD-specific documentation (contributed by oxzi).
Fixed some timezones (contributed by matoken).
Fixed some crashes (special thanks to Louis Merlin for helping me with this).
Updated Docker scripts to avoid generating a useless log file.
Fixed several memory leaks, key generation errors and HTML inconsistencies (contributed by dandelions).
Added ostatus.org and FEP-3b86 data to Webfinger objects.
Added a new CONTRIBUTING.md file. Among other guidelines, I explicitly say there that AI contributions are NOT accepted.
snac is now available as a Yunohost app. Thank you very much to Bruno Cesar Rocha for this.
If you find #snac useful, please consider buying grunfink a coffee or contributing via LiberaPay.
Hashtag following also allow URLs to RSS feeds of ActivityPub objects (like e.g. https://mastodon.social/tags/ThankYouTuesday).
Users can now configure a webhook to receive an HTTP POST for every notification. This can be useful for implementing bots that react to activities, like autorepliers, chatbots or interactive textual games (see snac(1) for more information).
The number of pending follow confirmations is shown next to the "people" link.
Faster performance metrics (contributed by dandelions).
Improved lowercasing in hashtags (contributed by postscriptum).
A search-by-url tweak for implementations that return 200 for invalid webfinger queries (e.g. piefed).
Mastodon API: added follow confirmation endpoints, fixed collisions in attachment file names.
Fixed potential crashes in attachment uploads.
If you find #snac useful, please consider buying grunfink a coffee or contributing via LiberaPay.
Notifications are now shown in a more compact way (i.e. all reactions are shown just above your post, instead of repeating the post ad nauseam for every reaction).
New command-line option unmute to, well, no-longer-mute an actor.
The private timeline now includes an approximate mark between new posts and "already seen" ones.
Fixed a spurious 404 error in the instance root URL for some configurations.
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
This release has been inspired by the song The Answers to the Questions by #Christabell and #DavidLynch.