One thing people have asked me over the last month is whether #SWF will be organising the Social Web Devroom at #FOSDEM2027 . The answer is: fingers crossed! We submitted the application to manage the devroom ahead of the October 4 deadline. We haven’t heard back yet; the announcements are scheduled for October 20, about a week from this writing. If the dev room is accepted, we will put out the call for proposals soon after that — it has to be published by October 27. We have been really lucky to have broad participation from volunteers and partner orgs in doing the organization for the last 2 events. It encompasses everything from soliciting applications, judging the entries, and building the schedule to MCing the event, helping people at the door, and watching the time for speakers. If you want to be part of that work, please let us know! It is much easier work if we spread it around. SWF is also _not_ organising BOFs at FOSDEM. So, if you have something to discuss, please plan a BOF! I really recommend coming to @fosdem if it’s affordable and convenient for you. It’s a great event.

A few months back, we posted about the new Fediverse instance called “the Forkiverse“. This is a Mastodon instance started by the hosts of the Search Engine podcast and the Hard Fork podcast. The site has picked up tens of thousands of users, with a distinctive local culture, and is a nice part of the Fediverse. The hosts are planning to shut down the server on Dec 31, 2026. They go over the reasons in an episode of the Search Engine podcast, Vladimir Putin’s Forkiverse. The reasons are pretty understandable — the cost of the hosting and the effort needed to moderate and manage the Forkiverse instance isn’t offset by their own enjoyment of the platform or a sense of mission. I (Evan) am interviewed as part of this episode. It was a tough interview to do — I never want to talk about servers shutting down. But it’s part of the work that we are concentrating on here at the Social Web Foundation — in particular, the study of Fediverse server sustainability that is partly funded by our grant from the Interledger Foundation. Understanding what it means when instances shut down is important. The interview was one of several that I’ve done with the Search Engine folks. We talked for several hours back in 2024, when my ActivityPub book had just come out, and when the SWF was just starting. We had follow up interviews in the intervening years. It’s been a good relationship, actually. Search Engine has a new episode that includes excerpts from those interviews on its premium feed today. The episode is available on a few platforms — I found it on Spotify at Thirty-three minutes of hopefulness for a better internet . I was worried that it was going to be kind of saccharine — here’s this idealist, fighting for hopeless cause — but I think it actually is a pretty good listen. I got to be human, instead of a caricature, which was nice. It’s been nice to stay connected to the Search Engine team, including PJ Vogt, during this time. I’m glad that he and the other people involved in the Forkiverse are giving the site a long enough time to wind down that the users there can move to other instances. And I’m glad that they’re going to stay connected to the Fediverse from their accounts on Threads, Bluesky, or elsewhere. I remain hopeful for the Fediverse, and I hope you are, too. We’re doing something important together.

Today, with the help of our partner the Interledger Foundation, we are announcing a new program of grants for multimedia software and creators. In this program, we are asking software developers and publishers to partner to make new and better content on the Fediverse. Multimedia, such as audio, video, and images, provides an engaging experience for Fediverse users. It can give a more visceral social and media experience than text alone. Multimedia software, however, can be difficult to develop, host, and use, and integrating it with other ActivityPub services takes time. It’s also challenging to produce engaging media on the Fediverse. It can be hard to develop an audience, work with unfamiliar tools, and understand the different dynamics of a federated architecture. Our intent with the Fediverse Multimedia Grants program is to bring more, and newer, rich content to the Fediverse for people to enjoy. We want to give creators a chance to get their feet under them, develop an audience, and make a permanent home on the Fediverse. We also want this program to help developers concentrate on creators’ needs — authoring, editing, organizing and publishing rich, engaging content. For this program, we are offering grants of up to US$20,000 to developer/creator teams to start new publications on the Fediverse. We expect the teams to work in close cooperation, providing mutual support and feedback. Our expected outcome is ActivityPub-enabled software that’s better fitted to the needs of creators, and new publications with a foothold in the Fediverse. Applications are open today at the Fediverse Multimedia Grants round of our grants portal. Applications are only for developer/creator teams. For publishers who aren’t familiar with Fediverse software, or developers who don’t have a good idea for a publisher to work with, please feel free to contact us and we’ll try to point you in the right direction to make a match. Important dates for the program: * Applications open: 7 Oct 2026 (today) * Applications due: 4 Nov 2026 * Decisions announced: 18 Nov 2026 * Projects start: 1 Dec 2026 Please ask questions in the comments and replies for this post, or contact us privately. I (Evan) will also be organizing a session on the grant program at Fediforum today, 7 Oct 2026. Thanks so much to the Interledger Foundation who generously funded this and other programs at the Social Web Foundation and who have been excellent creative partners in crafting this program.

ActivityPub software usually (but not always!) uses a handle format defined by RFC 7033, Webfinger, which looks like _username@domain.example_. There’s a ActivityPub and Webfinger report from the Social Web Community Group that details how this interaction works. All parts of this handle format can include non-ASCII Unicode characters, like accented Latin, Chinese, Arabic, or Hindi scripts. But it takes extra work, so users can’t count on non-ASCII characters being supported in their own or others’ software. This is a problem for the Fediverse. Of the most-spoken human languages, only three primarily use only ASCII characters (English, Malaysian, Indonesian), for a total of about 500 million people. That means about 90% of humans use languages with non-Latin, or accented, character sets. We are missing an opportunity to include more people worldwide with internationalized handles with names, words and domains in their native languages. Jim DeLaHunt @jdlh has been doggedly pursuing better support for internationalized Webfinger handles in ActivityPub. To this end, the Social Web Community Group started tracking Internationalized Webfinger Handle Adoption. Covering dozens of servers, clients, and libraries that implement ActivityPub, the tracker helps to discovery which software can interoperate with inclusive handles. If you know of ActivityPub software that isn’t on this list, or that doesn’t have its adoption tracked (question mark in the matrix), please add an issue or open a PR in the ActivityPub Webfinger task force repository.

About 14 years ago, I created a webfinger package for NodeJS. At the time, NodeJS was only a few years old. I had created pump.io as a new social networking engine and the successor to StatusNet. I needed a client for webfinger lookup — the process of converting a _user@domain.tld_ handle to a API endpoint for processing messages — and there wasn’t one for NodeJS, so I made it. It is kind of an antique — very old callback-style code that has its own HTTP processing system. It supported the older version of Webfinger, RFC 6415, using XML for the data format. It also supported the (at that time) new Webfinger specification, RFC 7033. Since its last release in 2013, version 0.4.2, I hadn’t touched the project. It’s just been languishing in the npm repository, squatting on the “webfinger” package name, and collecting dust. The Webfinger RFC was published, ActivityPub was standardized, and the Fediverse grew and grew, without a single change to the package. I realized I was sitting on this package a couple of years, ago, and I’ve been wanting to get a new version out. This week, I just did it. I ripped out all the legacy support for RFC 6415, upgraded the tests to use the Node test runner, switched from callback style to async/await, changed to ESM modules, and changed the format to StandardJS. I also added a little utility method, so it’s easier to look up links in the JRD file that is returned. Now, to get an ActivityPub actor, you just do this: const types = [ 'application/activity+json', 'application/ld+json; profile="https://www.w3.org/ns/activitystreams"' ] const actorId = (await webfinger('user1@foo.example')).link('self', types)?.href I think the dependencies are low enough that you can use this version of the library from browser apps, although I haven’t tried it yet. Anyway, I published version 0.5.1 today. I hope it provides some value to other people working on Fediverse software.

One of the requests I (Evan) have heard often over the years about ActivityPub is to make publishing on the Fediverse as easy as publishing with RSS. To make an RSS feed for a person or a site, a publish provides, dynamically or even statically, a single file, with a simple format, and makes it available over the Web. Other people’s feed reader software can download the feed and show the user either the full content of the site, or enough of a summary to get the user to click a link and read in your browser. So… why can’t ActivityPub be like that? Make a feed, and let others read it if they want to? The good news is, _it can._ ActivityPub defines an entire read-only structure for actors, content, and activities. Pushing content to other servers is _entirely optional_ — you can just tell other servers that you don’t accept remote content, and they won’t push it. The read-only interface to ActivityPub is rich and extensible — it covers content like text, images, video and audio, but also activities like liking, sharing, and replying. It’s not quite as simple as RSS — it requires a lot more, smaller files — but it’s pretty straightforward. The bad news is that most widely-used ActivityPub software doesn’t recognize read-only ActivityPub feeds. Most ActivityPub servers expect to send messages to every actor, and to receive messages in reply. They don’t have internal facilities to check ActivityPub feeds regularly for new content and activities. This isn’t just a technical issue; it’s also an adoption issue. If implementing ActivityPub requires all the infrastructure of our message-passing services — queues, signatures, filtering, fanout — it inhibits software developers and publishers from experimenting with the protocol. Implementing RSS can take a day or maybe a week of developer work. Implementing ActivityPub’s federation protocol can take months. Which one is going to be done in a hackday or a medium T-shirt-size sprint task, and which one is going on the back-back-back-backlog? To make it easier to understand and support this proper subset of ActivityPub, I published FEP-b06c: ActivityPoll last summer. (“Poll” is in contrast to “publish” — emphasizing the read-only structure.) It’s a profile of ActivityPub, identifying parts of the ActivityPub spec that will work, or not, with a static, read-only ActivityPub publisher. It also includes new terms to easily identify a read-only ActivityPub actor, as well as a way to declare how often a feed is updated (very useful for limiting the load on both the reader and the server sides). In order to test the profile, and identify shortfalls, I implemented a plugin for the static site generator (SSG) software, Jekyll. Using a static site generator keeps this process honest — there’s no temptation to add just a teensy bit of dynamic content generation; it has to be entirely static. If we can show interoperability with actors implemented with an SSG, we’ve shown that static ActivityPub publishing is truly possible. The plugin is called jekyll-activitypub-static (there’s already a jekyll-activity-pub plugin, which uses off-site dynamic endpoints to implement the federation protocol, so this one emphasizes that it’s static). It’s in the rubygems.org repository, so you can just add the gem name to your Gemfile for your Jekyll site, and it should install correctly. The configuration is pretty straightforward, and has pretty reasonable fallbacks, but you can tweak it to get more specific features. I’ve got an example actor on GitHub Pages at @evanp . You can search for it in Mastodon, and view the profile, but you can’t follow it directly. Other front ends can view it more directly — please tell me if yours can! If you’ve got a Jekyll site, please try out jekyll-activitypub-static and let me know what you think. Fair warning — the Webfinger support depends on having your site deployed at the root of the domain. There are probably some ways to work around that — let me know if you find one! If you have changes or enhancements you think can be made, let me know. And if you’ve got a full-featured implementation of the ActivityPub federation protocol, please consider implementing a polling structure for static actors. FEP-b06c covers most of the caveats, but please feel free to leave a comment if you find another gotcha. I’ll be right in there with you — I’m going to implement it in onepage.pub and activitypub.bot. Thanks to everyone who has commented on FEP-b06c, and to people who’ve tried and contributed to jekyll-activitypub-static. I look forward to more implementations!

Mallory and I (Evan) will both be at HOPE in New York tomorrow. Mallory is giving a talk on I-Stars: Protocols and Power on the main stage which looks _awesome_. I’ll be holding a workshop to help people Get on the Fediverse Already – setting up their Fediverse accounts for the first time. Since we’re both there, we want to have a meetup with the wider Fediverse community in New York! So, we’re organizing a Fediverse Meetup at the Irish Exit inside the Moynihan Train Hall at Penn Station at 7PM. HOPE is just a block away at the New Yorker Hotel, so we think this is a good location. And who doesn’t love Penn Station? We’ll grab a biggish table and put up a sign — you should be able to find us pretty easily. All Fediverse denizens and lovers of the Open Social Web are welcome. We will be around for a couple of hours at least — if you have a favourite evening talk at HOPE you don’t want to miss, please feel free to stop by. And watch the #fediversemeetupnyc hashtag for news and pics.

This is a quick reminder that I (Evan) will be speaking about 10 Ways to Grow the Fediverse at Fedicon 2026. Fedicon is a fantastic event in Vancouver, colocated with FOSSY, that brings together some of the most interesting people working on the Fediverse today. I’m excited about talking about Fediverse growth, but I’m equally excited to see the other speakers on the agenda. If you’re going to FOSSY and/or Fedicon, please come say hello!

On Friday, August 14, 2026 at the HOPE conference in New York City, we’ll be running a workshop to help new people join the Fediverse. This is an exciting first for us, and we’d love your help making it a great experience. Here’s what we need: * **Open-registration Fediverse servers that are welcoming the HOPE audience.** The HOPE conference welcomes people involved in information security, digital rights, as well as experimentation with radio, electronics, and other tech. It also usually has people from New York, New Jersey, and elsewhere in the Atlantic seaboard. If you know of servers that would welcome this kind of new member, please let us know! Even if the server isn’t open registration, but can accommodate new users on the day of the workshop, we’d love to coordinate. * **First-timer Collections.** Do you know of a good starter follow pack that new users might enjoy? Especially if their interests overlap with the HOPE audience. Just some names to follow is a big help, too. * **New user tips**. What helps people get started on the Fediverse? What helps them stay engaged? * **Volunteers**. Will you be at HOPE? Want to meet interesting people and help them get started with the Fediverse? It should be fun and easy. Please reply to this post with ideas or contact info. This is going to be fun!

A _relay server_ is a server that collects public content from many Fediverse servers and distributes it to the other servers. tags.pub , the global hashtag server run by the Social Web Foundation, can follow relay servers and boost any tagged content coming from the connected servers. Especially for relay servers that gather together content from lots of small servers, this can help connect people with others who share their interests on the Fediverse. However, some people have said they were surprised by the boosts, since they hadn’t directly connected their server to tags.pub. To avoid this, tags.pub is now unsubscribed from the open registration relay servers it was previously using. If your content is no longer being boosted, you can still connect your account or your server directly to tags.pub. tags.pub may subscribe to relay servers in the future, but we’ll coordinate with the relay server admins first to make sure there are fewer surprises.

I (Evan) will be at DWeb Camp Berlin this year. DWeb camp is a 5-day camping event in a forest near Berlin, where decentralized web hackers and advocates from around the world convene to discuss the state of the Web. I’ll be there hacking on ActivityPub implementations and meeting interesting people. If you’re coming to DWeb camp, please let me know — it’d be great to connect.

I am OVER THE MOON excited to see that #Mastodon now has a filtering option for notifications from bots. It’s working spotlessly from a build of Mastodon 4.6 from today. This means that people using servers with #tags.pub as a relay can opt out of getting boost notifications from tagbots but still keep sharing their content and still keep getting boost notifications from people. Thanks 🙏🏼 to the @Mastodon team for including this feature; it goes a long way to making tags.pub work for everyone.

We’re proud to have been involved in organizing and supporting the european.social effort to promote European social sovereignty. Digital independence is an important topic for policymakers worldwide; local control of social network platforms needs as much if not more attention. Working with our fellow signatories, we think the European Social Stack declaration provides a framework for giving Europeans control over their social networks while staying fully connected to the rest of the world. Federation and bridging let people on different networks, with different ownership and business models, share their lives on the Internet, inside and outside Europe. SWF thinks this common-sense approach to social sovereignty is a good template for others outside Europe to borrow. Thanks to all our fellow signatories; we’re looking forward to building the sovereign social web with you.

Just a note — we are finishing up our analysis of the data from the Social Web Sustainability Survey that we announced recently. If you run a Fediverse server — a Mastodon or Pixelfed site, a Lemmy site or a NodeBB forum, or an ActivityPub-enabled WordPress blog or Ghost.org newsletter, or even if you run Threads.com — we want to hear from you. What’s difficult about operating a service? What’s useful? How do we keep you on the Social Web? Please take this chance to respond to the survey — it’s the best way to let SWF and others know your priorities for sustainability and support.

A quick reminder that NLnet has an Open Social Fund specifically for projects that implement ActivityPub. They make grants of 5000 to 50000 euros. Their next proposal deadline is June 1, 2026. The proposal process requires just a few hours of work. It’s definitely worth the time to get into this important program!

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.

I (Evan) will be giving talk at Fediforum 26-04 next week, April 28, 2026, on the exciting topic of faking your way through ActivityPub conversations. Here’s the description: > “One of the best bluffers in the field of distributed social networks gives you just enough knowledge about ActivityPub to sound smarter than everyone around you. In this talk, Evan will cover the essential architecture of ActivityPub, what works and what doesn’t, and what is coming up next for the standard. You’ll walk out of this talk with just enough knowledge to speak with confidence about _anything_ at Fediforum.” > > If you’ve ever wanted to know what ActivityPub is and how it works, please come along. I hope the event is fun and interesting. Bring questions! > >

As part of the work on Fediverse sustainability announced earlier this year, the Social Web Foundation is running our first Fediverse Sustainability Survey . We’re seeking operators, moderators and administrators of Fediverse sites, from the smallest to the largest, to fill out the anonymous survey and share information about how their instances work. If you help run an instance, please take the 10-15 minutes needed to fill out the survey. We need a _lot_ of responses (hundreds!) to get statistically relevant data, so please feel free to share the link. We’re also on the lookout for operators of instances that are no longer running; there is a lot to learn about sustainability from servers that closed down, for whatever reason. We’ll publish findings here as part of our sustainability report, supplemented by interviews with selected respondents. Thanks!

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.