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.
Learning vibe-coding by writing a fb-group clone for #ActivityPub, able to federate with Lemmy and Mastodon, in #Rust. Let's see what comes out of it...
We just rebuilt vir.group from the ground up. This is not a minor update. This is a fundamental rewrite of the product DNA.
https://vir.group
What changed:
ActivityPub integration is now fully native. Your posts reach the entire fediverse. Hundreds of millions of users across Mastodon, Bluesky, Threads, and dozens of other compatible platforms. No duplicate content. No managing multiple accounts. Post once. Reach the world.
Matrix protocol with E2EE encryption is now the default. Even we cannot read your messages. Session keys are yours alone. Recovery key gives you full control. Encrypted reactions, replies, edits, deletions. Works on mobile and web simultaneously.
Audio and video calls are built directly into the app. WebRTC with our own TURN relay in Europe. HD video. Noise suppression. CallKit on iOS. Push notifications on locked screen. No external links. No "let's switch to Zoom."
Projects hub is now a full marketplace. Publish your project with description, media, links, tags, and investor pitch. Categories for technology, art, education, manufacturing, services. Global reach via ActivityPub. Premium placement with 48-hour moderation. SEO optimization with short links and canonical URLs. Click analytics. Direct encrypted chat with interested parties.
Full feed control. Filter by words, topics, languages, domains. Mute, block, hide. Choose global, local, followed, trending, or your own custom lists. No algorithmic recommendations. You decide what you see.
Web version now matches mobile. Three columns. Composer. Side navigation. Same E2EE. Same calls coming soon. Responsive design that works on ultra-wide monitors without stretching one column across the screen.
This is not a social network. Not a messenger. Not a project marketplace. It is all three. Built for builders, creators, investors, and analysts.
Register in one minute. Publish your first project today.
#virgroup #ActivityPub #Fediverse #Matrix #E2EE #DecentralizedWeb #OpenWeb #PrivacyMatters #SecureMessaging #Startups #Entrepreneurs #Investors #ProjectShowcase #CreatorEconomy #SocialNetwork #Bluesky #Mastodon
So #Vine is coming back, this time as #DiVine!
Does anyone know anyone who can get me an invite code? I want in!
The App is coming back with no #AI allowed, and will allow people to own their own content.
For the geeks: it's built on the #OpenSocial protocol #Nostr, and apparently they're experimenting with integrating the #ATProtocol, future integration with #ActivityPub, the protocol behind #Mastodon and #Flipboard.
https://www.youtube.com/watch?v=zUGnNIh60-0
#Holos is a new social network working with #ActivityPub. This is not an app where you can connect your Mastodon, Pixelfed or PeerTube account.
There is no web version and no API because the ActivityPub server runs on the device itself. That's the whole challenge behind this project.
If there is more engagement, I plan to build a desktop version and even sync between different devices.
The official account for all announcements is @HolosSocial
There are a LOT of Fediverse projects out there!
If you're a techy person interested in self-hosting Fediverse platforms, you might like to check out the "Delightful Fediverse" list which tries to feature every Fediverse project available:
🌱 https://codeberg.org/fediverse/delightful-fediverse-experience
(It's worth noting the meaning of the emoji next to project names, as the status of different projects varies.)
Fedilabs announces: Fedilab 3.40.0 is available. https://toot.fedilab.app/@apps/116562487875307972 #fediverse #FediLab #ActivityPub
> Any implementation of a music collection on top of #ActivityPub would still have to implement the collection itself, and maintain standards for how backfilling works and how the collection is shaped, so why not start with a clean implementation that only provides the parts that are important to a music collection to begin with?
Yet I do wonder about https://xkcd.com/927
We often think about ActivityPub by how we experience it on the fediverse. But the fediverse rn is only a very particular implementation of AP, specialized to support microblogging and traditional social media use cases.
AP offers "a social graph of addressible actors to exchange activities with an object payload". Actors, activities, and objects are all fully customizable linked data, they can be anything, modeled to represent any domain.
With an ActivityPub API client you maintain your music collection locally, then publish and interact to a static site, or other interested actors.
Changed default: for newly created instances, disable_inbox_collection is set to true (see snac(8) for more information). The reason is because it seems to be used for harrasing people.
Changed default: for newly created instances, disable_history is set to true (see snac(8) for more information). The reason is because archived history files don't reflect reality after posts are deleted or modified (they always have been an ugly kludge).
Changed default: in previous versions, posts with a scope of unlisted were shown in public pages and RSS feeds. Now, they are no longer shown. If you want to get back to previous behaviour, use a new toggle in the User Settings section (see snac(1) for more information).
New admin configuration option: if the purge_static value is set to true in server.json, each user's static directory is explored and those files there that are no longer attached to any post or referenced anywhere are deleted. See snac(8) for more information about those cases where you may not want to enable this option.
Allow serving files from subdirectories of the static/ subdirectory (contributed by la_ninpre).
Minor tweak to webfinger code to handle Hubzilla's peculiarities.
Fixed a search case where URLs to GotoSocial statuses were misidentified as accounts.
Accounts that follow you are now marked with a thumb-up emoji, because followers are adorable people.
Fixed some account export errors.
Fixed an incorrect hash in post links.
Show an account's location link in the people page, if they have one.
Mastodon API: Fixed hashtags loosing the link after editing a post, minor tweak in access token processing (contributed by trondd555).
Drop usage of PATH_MAX (contributed by sergiodj).
New Polish translation (contributed by kpm).
Updated German and Czech translations (contributed by zen and pmjv).
If you find #snac useful, please consider buying grunfink a coffee or contributing via LiberaPay.
@fluffy I mean, for the most part this sounds like a mininalist #ActivityPub Server (or Client, setup as a middleware that uses an existing account)…
- I'm pretty shure extensive Clients/Middleware like #FediSuite (made by @christin) already implement like 75-90% of that.
The most needed missing functionality is propably some sort of "Library" that retains links to said content to make said posts uniform and avoid having to manually copy & paste them everytime…
- A bit like my #NowPlaying posts.
As for the #Streaming aspect: #DLNA is designed to work on #LAN and given the"legal spicyness" of #FileSharing in many juristictions, I'm shure anything beyond linking #YouTube / #Peertube, #SoundCloud / #BandCamp, etc. is gonna be problematic…
- I mean, if I were to run an #InternetRadio I'd propably only broadcast @creativecommons - licensed #music and having a "Now Playing" - #Bot would certainly be something I'd want…

This post is about work happening on WordPress.com, specifically the Reader, the long-running subscription-and-reading surface that’s been part of WordPress.com since 2008. It’s a sibling effort to the ActivityPub plugin, not a feature of it. We think it matters to plugin readers anyway, because the two pieces are converging, and the converging point is what we’ll be working on next.
Two weeks ago, Automattic kicked off something internally called Radical Speed Month, a four-week sprint where small teams ship fast on focused projects. We (@jeremy and @pfefferle) took the chance to spend it on something that’s been sitting at the edge of the Fediverse-and-WordPress conversation for a while: making the WordPress.com Reader speak Fediverse.
Today is roughly the halfway mark, and the picture is clearer than we expected. Here’s what shipped, what’s in flight, and what’s still ahead.
The Reader on WordPress.com has held a single, useful role for over a decade: it’s where your subscriptions live. Blogs, podcasts, RSS feeds. What it hasn’t done, yet, is read the open social web. Your Mastodon timeline lives in another app. Your Bluesky timeline lives in a third. The Fediverse is out there, and the Reader stays over here.
The Radical Speed Month bet: ship three protocol adapters in four weeks, and prove the Reader can become a universal aggregator. RSS / Google Reader API (so any reader app can use WordPress.com as a sync backend), ActivityPub (so Mastodon, Pixelfed, and friends show up natively), and ATProto / Bluesky (because that’s where a real chunk of the social-web conversation has gone). One Reader, every protocol you care about.
If you’ve been following the ActivityPub plugin for a while, you already know one half of this story, your blog speaking out to the Fediverse. The other half is reading in, and that’s where this month’s work concentrates.
Any Google Reader-compatible app can now point at WordPress.com and use it as a sync backend. That includes Reeder, NetNewsWire, ReadKit, lire, Unread, Fiery Feeds, Feed Me, and Read You. The auth onboarding is short, and your subscriptions, read state, and stars sync across whichever app you actually like. We’re working on a setup guide that walks through the steps for the most common apps; it should land soon.
This wasn’t directly Fediverse work, but it’s part of the same idea: the Reader as a backend, not a destination. If your reading habit lives in a different app, that’s fine. Your subscriptions still live on WordPress.com.
The Bluesky / ATProto adapter has moved further than the original plan suggested.

You can:
The remaining piece on the Bluesky side is quote-posting and deleting your own posts, which we’re shipping together. After that, Bluesky is a complete first-class tab in the Reader.
Mastodon followed the same pattern: connect, verify, then a steady cadence of small additions like timeline, in-app threads, author profile and feed (with Posts / Replies / Media filter tabs), and tag and hashtag feeds. All of those are live for Mastodon today.

What’s still coming on the Mastodon side is the equivalent of the Bluesky interaction work (favourite, boost, reply, quote) built on the same shape that worked for Bluesky. Expect those to land in the second half of this month.
If you read 8.1.0 — By the Numbers, you’ll have noticed a small line in the announcement: the plugin now exposes an ActivityPub API. It’s experimental, behind a feature flag, and lets third-party apps create, edit, and delete posts on your blog the way they would post to a Mastodon account.
That work isn’t an accident. It’s one half of a bridge, and Radical Speed Month is the other half.
The Mastodon-in-Reader work that shipped this month is user-level: you connect your Mastodon account once, and the Reader can sync your Mastodon timeline regardless of where your blog lives. That’s a useful starting point, but it’s not the only path forward. The model we’ve been working toward for a year is blog-level: each ActivityPub-enabled WordPress blog as its own social identity inside the Reader, with the plugin providing the actor and the ActivityPub API providing the connection.
That work is on the schedule for the second half of the month. The radical-speed pace gave us proof first: timelines, threads, profiles, and interactions can all run through one shared pattern, with two networks already validating it. With the pattern in place and the plugin’s ActivityPub API ready to talk to, the blog-level path slots into the same architecture, letting your plugin-enabled blog appear as an ActivityPub identity in the Reader sidebar, with its inbox, its outbox, and its real ActivityPub follow graph. And because the API is part of the ActivityPub standard, the same path works for any Reader or client that speaks it, not just WordPress.com.
A short list of what we’re chasing for the second half of the month and just past it:
A month feels short to ship three protocols’ worth of reading, profiles, and interactions. It’s worth saying out loud: this didn’t happen because we worked unsustainable hours. It happened because we sat with the design for months, picked a shape that lets each protocol reuse the same plumbing, and broke the work into pieces small enough that any one was reviewable in a day or two. “Radical speed” turned out to mean: a backlog of careful design, drained quickly.
If you run an ActivityPub-enabled WordPress blog, whether on WordPress.com or self-hosted, the practical takeaway is small for now and meaningful soon. The plugin’s ActivityPub API in 8.1.0 is the foundation for your blog showing up as a real social identity inside any Reader or app that speaks the same protocol. The WordPress.com Reader is the first concrete target, but the universality matters: any client that implements the standard can talk to your plugin-enabled blog the same way.
Already, the work this month means there’s now a Reader on WordPress.com that knows how to read the Fediverse alongside RSS and Bluesky. That’s a meaningful thing to have built, and the bridge from your plugin-enabled blog to that Reader is what the second half of the month is about.
We’ll keep posting updates as the month closes out. If you have thoughts on what blog-level ActivityPub in the Reader should look like, what protocols you’d want next, or how the plugin’s ActivityPub API should evolve to make this seamless, leave a comment on the plugin’s GitHub repository or reply on the Fediverse. We read every message.
Following the recommendations I got, I set up a #NodeBB forum to discuss the projects #Fedilab, #Holos, #CastLab and #Fedle.
Each category federates over #ActivityPub, so you can follow it directly from your Fediverse account: @fedilab, @holos, @castlab, @fedle.
More details: https://forum.fedilab.app/post/2
Week in Fediverse 2026-05-08
Servers
- Vernissage v1.35.0
- Pleroma v2.10.2
- Funkwhale v2.0.2
- Betula v1.7.0
- Hollo v0.8.2
- Akkoma v2026.05
- Ktistec v3.3.7
- NodeBB v4.11.0
- Misskey v2026.5.1
- Ties v0.2.1
- PieFed v1.6.21
- Lemmy Development Update April 2026
Clients
- Nicolium v0.2.1
- Fedilab v3.39.0
- Pachli v3.6.1
- Mastodon for Android v2.12.0
- Coho v1.0
- PixelDroid v1.0.beta42
- Blorp v1.13.0
- Mitra Mini v0.4.0
- Holos v1.5.5
Tools and Plugins
For developers
Articles
- Join the fediverse! zine
- A Bridge to Somewhere: How to Link Your Mastodon, Bluesky, or Other Federated Accounts
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019de52a-a351-7ee2-a48b-7306090edfe6
I'm curious whether anyone on #Mastodon can explain why this post https://mstd.seungjin.net/@theguardian/116535352864096634 is appearing in my feed many times over? I follow several Maths/education related #hashtags (via #relays ), and thought at first I was getting one through each #hashtag #relay (1 post each), but when it exceeded that I looked and in fact it only contains one hashtag I follow, so it's the same post over and over again, maybe a dozen times so far. Why is that happenning? #askFedi #federation #activityPub
Have you ever wondered how #ActivityPub actually works?
This presentation by Evan Prodromou from #FediForum should answer your questions in 30 minutes.
https://spectra.video/w/s8DKnnaPFw2b1JS8zD5VE8
/cc @evanprodromou
Wanted to check out #Smithereen? Well, now you can! I've just set up a demo server that lets you sign up for a temporary account to play around:
Week in Fediverse 2026-05-01
Servers
- Hollo v0.8.0
- ActivityPub for WordPress v8.2.0
- NodeBB v4.11.0
- PieFed v1.6.20
- TinyAP v0.1.8
Clients
- Pachli v3.6.0
- tooi v0.24.0
- Tusker v2026.1
- Nicolium v0.2.0
- Jerboa v0.0.87
- PeerTube Mobile v2.1.2
- Mitra Mini v0.3.0
- Holos v1.5.2
For developers
Articles
- The Seven Deadly Fediverse UX Sins: A Redemption Report Card
- The Architecture of Autonomy and Freedom
- What would a LinkedIn alternative look like on the open web?
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019dc0ea-e585-7be3-8174-327c55ab28d5
New from me: Federation Has a European Legal Problem
on what the recent Russmedia ruling means for open social protocols like #ActivityPub and #atproto
warning: do not read if you value your sanity
https://connectedplaces.online/federation-has-a-european-legal-problem/
I (Evan) will be at the Wikimedia Hackathon 2026 in Milan, Italy this weekend (May 1-4). I’m especially interested in how we can connect Wikimedia projects and content to the Social Web using ActivityPub. I’ll be holding a session on the topic on Sunday May 3 at 9AM, but I’ll also be available for discussions throughout the weekend.
My hacking project plan is to make an ActivityPub object server for films. There are about 343,000 films in Wikidata, which compares pretty favourably with the 740,000 films in IMDB. There is a JSON-LD interface to Wikidata, but the types used don’t match up with ActivityPub types like Video. So, like places.pub, I’ll set up movies.pub to share an ActivityPub object for every Q-item for a movie, as well as a search endpoint to find films by name.
If I get ahead of the project and I’m not too jet-lagged, I’d like to add an ActivityPub API app to “check in” to a movie that you’re watching (and maybe give a little review). Similar to checkin.swf.pub with places!
If you’re at #wmhack this weekend, please come say hi. I love talking about Wikimedia projects and the open social web.
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.