WordPress Federation: Recap of 2025
Fediverso
12
Posts
5
Posters
42
Views
-
In June, we published our 2025 roadmap: Building the Future of WordPress Federation, outlining the areas we wanted to focus on for the rest of the year.
As we step into 2026, it’s time to look back at how the roadmap held up and what we shipped in 2025.
2025 at a Glance
2025 turned out to be an ambitious and, at times, challenging timeline. Even so, we were able to make meaningful progress across most of the areas we set out to work on.
Over the course of the year, we introduced the Following feature, significantly expanded moderation tooling, refined actor handling, and improved the reliability and performance of core federation workflows. Along the way, we also shipped a first experimental draft of the Reader, offering an early look at what reading the Fediverse inside WordPress could become.
Not everything on the roadmap was completed, but we’re happy with how much we were able to achieve and with the foundations that are now in place for what comes next.
Roadmap
Below is a review of the roadmap topics we outlined for 2025, what we worked on, and what remains open.
Followers / Following ✅
Work in 2025 expanded ActivityPub beyond followers by introducing the Following feature, allowing WordPress sites and users to actively follow accounts on the Fediverse.
Alongside this, we improved the reliability and performance of both follower and following lists, including better synchronization across instances and faster resolution and display of large collections.
This work also laid the foundation for later features, such as the experimental Reader.
Related release posts:
Actors ✅
We continued refining how local and remote actors are represented and resolved. Internal refactors reduced special-case handling and improved consistency and performance across actor resolution, including follower, following, and block lists.
This work primarily affected internal behavior rather than user-facing UI.
Related release posts:
Moderation ✅
In 2025, ActivityPub-specific moderation was significantly expanded. Site-wide and personal blocking now cover domains, keywords, and individual actors, with consistent checks applied to incoming activities.
We added blocklist subscriptions with scheduled syncing and bulk domain imports, including support for community-maintained lists such as the IFTAS DNI list. Moderation handling was also refined with improved reject behavior for quote interactions.
Related release posts:
Reader 🧪
An experimental Reader UI was introduced behind a feature flag. When enabled, it adds a “Social Web” area to the dashboard where posts and shares from followed accounts can be read inside WordPress.
The feature is disabled by default and explicitly marked as experimental.
Related release posts:
Direct Messages ⏸️
Direct Messages were not implemented in 2025. This remains an open roadmap topic for future consideration once related foundations mature further.
Fully Delete Profiles ✅
Deletion semantics were improved to better support explicit federated cleanup. Delete activities are now sent when WordPress users are removed, and deletion-related handling was aligned across activity processing.
A CLI-based self-destruct command was introduced to allow site owners to explicitly remove their site’s federated presence.
Related release posts:
Client-to-Server API ⏸️
Client-to-Server API support was not implemented in 2025. No user-facing features shipped under this topic.
Beyond the Roadmap
While the roadmap helped guide our focus in 2025, not everything that shipped was planned from the start. Some features emerged from day-to-day usage, feedback, and practical needs that became clearer over time.
A few of those are worth highlighting.
Quotes
Support for quote interactions improved significantly over the year. We refined detection and handling of quoted replies and links, added proper handling for quote comments, and improved how quote permissions are revoked when quoted content is deleted. This made quoted interactions more reliable and consistent across instances.
Related release posts:
Onboarding
We also improved onboarding for new users by adding clearer guidance and better defaults after plugin activation. This helped reduce friction for sites federating for the first time and made initial setup more approachable.
Related release posts:
Extra Fields UI
While not originally planned as a roadmap item, work on Extra Fields resulted in a more flexible and user-friendly UI. New blocks and layout options made it easier to display federated profile data in different formats, allowing themes to choose how much structured information to surface.
Related release posts:
Wrapping up
Looking back, 2025 was a year of steady progress. We focused on the foundations we set out to improve, shipped meaningful features along the way, and left room for unplanned work that addressed real needs as they came up.
Now we’d love to hear from you: What was your favorite feature this year? What are you most excited about and what do you still miss or hope to see next?
Your feedback has shaped this project throughout 2025, and it continues to guide where we go from here. We’re already working on our 2026 timeline, and your ideas, experiences, and questions are an important part of that process.
Thanks for being part of the journey and see you on the Fediverse.
-
undefined pfefferle@mastodon.social shared this topic on
-
In June, we published our 2025 roadmap: Building the Future of WordPress Federation, outlining the areas we wanted to focus on for the rest of the year.
As we step into 2026, it’s time to look back at how the roadmap held up and what we shipped in 2025.
2025 at a Glance
2025 turned out to be an ambitious and, at times, challenging timeline. Even so, we were able to make meaningful progress across most of the areas we set out to work on.
Over the course of the year, we introduced the Following feature, significantly expanded moderation tooling, refined actor handling, and improved the reliability and performance of core federation workflows. Along the way, we also shipped a first experimental draft of the Reader, offering an early look at what reading the Fediverse inside WordPress could become.
Not everything on the roadmap was completed, but we’re happy with how much we were able to achieve and with the foundations that are now in place for what comes next.
Roadmap
Below is a review of the roadmap topics we outlined for 2025, what we worked on, and what remains open.
Followers / Following ✅
Work in 2025 expanded ActivityPub beyond followers by introducing the Following feature, allowing WordPress sites and users to actively follow accounts on the Fediverse.
Alongside this, we improved the reliability and performance of both follower and following lists, including better synchronization across instances and faster resolution and display of large collections.
This work also laid the foundation for later features, such as the experimental Reader.
Related release posts:
Actors ✅
We continued refining how local and remote actors are represented and resolved. Internal refactors reduced special-case handling and improved consistency and performance across actor resolution, including follower, following, and block lists.
This work primarily affected internal behavior rather than user-facing UI.
Related release posts:
Moderation ✅
In 2025, ActivityPub-specific moderation was significantly expanded. Site-wide and personal blocking now cover domains, keywords, and individual actors, with consistent checks applied to incoming activities.
We added blocklist subscriptions with scheduled syncing and bulk domain imports, including support for community-maintained lists such as the IFTAS DNI list. Moderation handling was also refined with improved reject behavior for quote interactions.
Related release posts:
Reader 🧪
An experimental Reader UI was introduced behind a feature flag. When enabled, it adds a “Social Web” area to the dashboard where posts and shares from followed accounts can be read inside WordPress.
The feature is disabled by default and explicitly marked as experimental.
Related release posts:
Direct Messages ⏸️
Direct Messages were not implemented in 2025. This remains an open roadmap topic for future consideration once related foundations mature further.
Fully Delete Profiles ✅
Deletion semantics were improved to better support explicit federated cleanup. Delete activities are now sent when WordPress users are removed, and deletion-related handling was aligned across activity processing.
A CLI-based self-destruct command was introduced to allow site owners to explicitly remove their site’s federated presence.
Related release posts:
Client-to-Server API ⏸️
Client-to-Server API support was not implemented in 2025. No user-facing features shipped under this topic.
Beyond the Roadmap
While the roadmap helped guide our focus in 2025, not everything that shipped was planned from the start. Some features emerged from day-to-day usage, feedback, and practical needs that became clearer over time.
A few of those are worth highlighting.
Quotes
Support for quote interactions improved significantly over the year. We refined detection and handling of quoted replies and links, added proper handling for quote comments, and improved how quote permissions are revoked when quoted content is deleted. This made quoted interactions more reliable and consistent across instances.
Related release posts:
Onboarding
We also improved onboarding for new users by adding clearer guidance and better defaults after plugin activation. This helped reduce friction for sites federating for the first time and made initial setup more approachable.
Related release posts:
Extra Fields UI
While not originally planned as a roadmap item, work on Extra Fields resulted in a more flexible and user-friendly UI. New blocks and layout options made it easier to display federated profile data in different formats, allowing themes to choose how much structured information to surface.
Related release posts:
Wrapping up
Looking back, 2025 was a year of steady progress. We focused on the foundations we set out to improve, shipped meaningful features along the way, and left room for unplanned work that addressed real needs as they came up.
Now we’d love to hear from you: What was your favorite feature this year? What are you most excited about and what do you still miss or hope to see next?
Your feedback has shaped this project throughout 2025, and it continues to guide where we go from here. We’re already working on our 2026 timeline, and your ideas, experiences, and questions are an important part of that process.
Thanks for being part of the journey and see you on the Fediverse.
@activitypub.blog wonderful...
-
In June, we published our 2025 roadmap: Building the Future of WordPress Federation, outlining the areas we wanted to focus on for the rest of the year.
As we step into 2026, it’s time to look back at how the roadmap held up and what we shipped in 2025.
2025 at a Glance
2025 turned out to be an ambitious and, at times, challenging timeline. Even so, we were able to make meaningful progress across most of the areas we set out to work on.
Over the course of the year, we introduced the Following feature, significantly expanded moderation tooling, refined actor handling, and improved the reliability and performance of core federation workflows. Along the way, we also shipped a first experimental draft of the Reader, offering an early look at what reading the Fediverse inside WordPress could become.
Not everything on the roadmap was completed, but we’re happy with how much we were able to achieve and with the foundations that are now in place for what comes next.
Roadmap
Below is a review of the roadmap topics we outlined for 2025, what we worked on, and what remains open.
Followers / Following ✅
Work in 2025 expanded ActivityPub beyond followers by introducing the Following feature, allowing WordPress sites and users to actively follow accounts on the Fediverse.
Alongside this, we improved the reliability and performance of both follower and following lists, including better synchronization across instances and faster resolution and display of large collections.
This work also laid the foundation for later features, such as the experimental Reader.
Related release posts:
Actors ✅
We continued refining how local and remote actors are represented and resolved. Internal refactors reduced special-case handling and improved consistency and performance across actor resolution, including follower, following, and block lists.
This work primarily affected internal behavior rather than user-facing UI.
Related release posts:
Moderation ✅
In 2025, ActivityPub-specific moderation was significantly expanded. Site-wide and personal blocking now cover domains, keywords, and individual actors, with consistent checks applied to incoming activities.
We added blocklist subscriptions with scheduled syncing and bulk domain imports, including support for community-maintained lists such as the IFTAS DNI list. Moderation handling was also refined with improved reject behavior for quote interactions.
Related release posts:
Reader 🧪
An experimental Reader UI was introduced behind a feature flag. When enabled, it adds a “Social Web” area to the dashboard where posts and shares from followed accounts can be read inside WordPress.
The feature is disabled by default and explicitly marked as experimental.
Related release posts:
Direct Messages ⏸️
Direct Messages were not implemented in 2025. This remains an open roadmap topic for future consideration once related foundations mature further.
Fully Delete Profiles ✅
Deletion semantics were improved to better support explicit federated cleanup. Delete activities are now sent when WordPress users are removed, and deletion-related handling was aligned across activity processing.
A CLI-based self-destruct command was introduced to allow site owners to explicitly remove their site’s federated presence.
Related release posts:
Client-to-Server API ⏸️
Client-to-Server API support was not implemented in 2025. No user-facing features shipped under this topic.
Beyond the Roadmap
While the roadmap helped guide our focus in 2025, not everything that shipped was planned from the start. Some features emerged from day-to-day usage, feedback, and practical needs that became clearer over time.
A few of those are worth highlighting.
Quotes
Support for quote interactions improved significantly over the year. We refined detection and handling of quoted replies and links, added proper handling for quote comments, and improved how quote permissions are revoked when quoted content is deleted. This made quoted interactions more reliable and consistent across instances.
Related release posts:
Onboarding
We also improved onboarding for new users by adding clearer guidance and better defaults after plugin activation. This helped reduce friction for sites federating for the first time and made initial setup more approachable.
Related release posts:
Extra Fields UI
While not originally planned as a roadmap item, work on Extra Fields resulted in a more flexible and user-friendly UI. New blocks and layout options made it easier to display federated profile data in different formats, allowing themes to choose how much structured information to surface.
Related release posts:
Wrapping up
Looking back, 2025 was a year of steady progress. We focused on the foundations we set out to improve, shipped meaningful features along the way, and left room for unplanned work that addressed real needs as they came up.
Now we’d love to hear from you: What was your favorite feature this year? What are you most excited about and what do you still miss or hope to see next?
Your feedback has shaped this project throughout 2025, and it continues to guide where we go from here. We’re already working on our 2026 timeline, and your ideas, experiences, and questions are an important part of that process.
Thanks for being part of the journey and see you on the Fediverse.
@activitypub.blog Thinking of 2026 now; I have a particular feedback, the possibility to interact from Mastodon directly, as the plugin "enable mastodon apps" from Alex Kirk doesn't work with all clients.
-
In June, we published our 2025 roadmap: Building the Future of WordPress Federation, outlining the areas we wanted to focus on for the rest of the year.
As we step into 2026, it’s time to look back at how the roadmap held up and what we shipped in 2025.
2025 at a Glance
2025 turned out to be an ambitious and, at times, challenging timeline. Even so, we were able to make meaningful progress across most of the areas we set out to work on.
Over the course of the year, we introduced the Following feature, significantly expanded moderation tooling, refined actor handling, and improved the reliability and performance of core federation workflows. Along the way, we also shipped a first experimental draft of the Reader, offering an early look at what reading the Fediverse inside WordPress could become.
Not everything on the roadmap was completed, but we’re happy with how much we were able to achieve and with the foundations that are now in place for what comes next.
Roadmap
Below is a review of the roadmap topics we outlined for 2025, what we worked on, and what remains open.
Followers / Following ✅
Work in 2025 expanded ActivityPub beyond followers by introducing the Following feature, allowing WordPress sites and users to actively follow accounts on the Fediverse.
Alongside this, we improved the reliability and performance of both follower and following lists, including better synchronization across instances and faster resolution and display of large collections.
This work also laid the foundation for later features, such as the experimental Reader.
Related release posts:
Actors ✅
We continued refining how local and remote actors are represented and resolved. Internal refactors reduced special-case handling and improved consistency and performance across actor resolution, including follower, following, and block lists.
This work primarily affected internal behavior rather than user-facing UI.
Related release posts:
Moderation ✅
In 2025, ActivityPub-specific moderation was significantly expanded. Site-wide and personal blocking now cover domains, keywords, and individual actors, with consistent checks applied to incoming activities.
We added blocklist subscriptions with scheduled syncing and bulk domain imports, including support for community-maintained lists such as the IFTAS DNI list. Moderation handling was also refined with improved reject behavior for quote interactions.
Related release posts:
Reader 🧪
An experimental Reader UI was introduced behind a feature flag. When enabled, it adds a “Social Web” area to the dashboard where posts and shares from followed accounts can be read inside WordPress.
The feature is disabled by default and explicitly marked as experimental.
Related release posts:
Direct Messages ⏸️
Direct Messages were not implemented in 2025. This remains an open roadmap topic for future consideration once related foundations mature further.
Fully Delete Profiles ✅
Deletion semantics were improved to better support explicit federated cleanup. Delete activities are now sent when WordPress users are removed, and deletion-related handling was aligned across activity processing.
A CLI-based self-destruct command was introduced to allow site owners to explicitly remove their site’s federated presence.
Related release posts:
Client-to-Server API ⏸️
Client-to-Server API support was not implemented in 2025. No user-facing features shipped under this topic.
Beyond the Roadmap
While the roadmap helped guide our focus in 2025, not everything that shipped was planned from the start. Some features emerged from day-to-day usage, feedback, and practical needs that became clearer over time.
A few of those are worth highlighting.
Quotes
Support for quote interactions improved significantly over the year. We refined detection and handling of quoted replies and links, added proper handling for quote comments, and improved how quote permissions are revoked when quoted content is deleted. This made quoted interactions more reliable and consistent across instances.
Related release posts:
Onboarding
We also improved onboarding for new users by adding clearer guidance and better defaults after plugin activation. This helped reduce friction for sites federating for the first time and made initial setup more approachable.
Related release posts:
Extra Fields UI
While not originally planned as a roadmap item, work on Extra Fields resulted in a more flexible and user-friendly UI. New blocks and layout options made it easier to display federated profile data in different formats, allowing themes to choose how much structured information to surface.
Related release posts:
Wrapping up
Looking back, 2025 was a year of steady progress. We focused on the foundations we set out to improve, shipped meaningful features along the way, and left room for unplanned work that addressed real needs as they came up.
Now we’d love to hear from you: What was your favorite feature this year? What are you most excited about and what do you still miss or hope to see next?
Your feedback has shaped this project throughout 2025, and it continues to guide where we go from here. We’re already working on our 2026 timeline, and your ideas, experiences, and questions are an important part of that process.
Thanks for being part of the journey and see you on the Fediverse.
@activitypub.blog hope federation with Lemmy and Piefed gets on this years list, as better integration with threadiverse could really move things forward 🖤
-
@activitypub.blog hope federation with Lemmy and Piefed gets on this years list, as better integration with threadiverse could really move things forward 🖤
@harce @activitypub.blog what problems do you have with lemmy?
-
@harce @activitypub.blog what problems do you have with lemmy?
@pfefferle @activitypub.blog havent done checks with other sites, but asumed it would be the case for all:
An AP + event federation enabled wordpress we have doesnt update on a Lemmy instance when used as a multiuser/community;https://adapulawska.org
https://szmer.info/c/kolektyw@adapulawska.orgLast time I checked manually searching an URL would fetch it and update the community post list. My understanding was its some interoperability issues to be resolved.
-
@pfefferle @activitypub.blog havent done checks with other sites, but asumed it would be the case for all:
An AP + event federation enabled wordpress we have doesnt update on a Lemmy instance when used as a multiuser/community;https://adapulawska.org
https://szmer.info/c/kolektyw@adapulawska.orgLast time I checked manually searching an URL would fetch it and update the community post list. My understanding was its some interoperability issues to be resolved.
@harce @activitypub.blog you can check @notiz.blog on piefed and lemmy. It should work on both sites!
On lemmy you should be able to even look up posts through a search. I have not much experience with piefed though.
-
@pfefferle @activitypub.blog havent done checks with other sites, but asumed it would be the case for all:
An AP + event federation enabled wordpress we have doesnt update on a Lemmy instance when used as a multiuser/community;https://adapulawska.org
https://szmer.info/c/kolektyw@adapulawska.orgLast time I checked manually searching an URL would fetch it and update the community post list. My understanding was its some interoperability issues to be resolved.
@harce @activitypub.blog here are some screenshots
-
@harce @activitypub.blog here are some screenshots
@pfefferle @activitypub.blog yes, i can see that working in this case. Ill do some tests and come back, as its clearly not working as expected on our site.
-
@pfefferle @activitypub.blog yes, i can see that working in this case. Ill do some tests and come back, as its clearly not working as expected on our site.
@harce @activitypub.blog you have to use the combined actor mode (users and blog-user). This way, the blog-user acts as the community and the users are publishing into the community.
maybe I should write a blog post about that!
-
@harce @activitypub.blog you have to use the combined actor mode (users and blog-user). This way, the blog-user acts as the community and the users are publishing into the community.
maybe I should write a blog post about that!
@pfefferle @activitypub.blog thats what https://szmer.info/c/kolektyw@adapulawska.org is (should be)
@kolektyw is the handle of the collective account
-
@activitypub.blog Thinking of 2026 now; I have a particular feedback, the possibility to interact from Mastodon directly, as the plugin "enable mastodon apps" from Alex Kirk doesn't work with all clients.
@elettrona @activitypub.blog I hope 2026 will be the year, to boost ActivityPub also as Client2Server API!
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Week in Fediverse 2026-02-27
Servers
- Bookwyrm v0.8.5
- Gush! v0.0.31
- Hollo v0.7.4
- flohmarkt v0.16.0
- Mastodon v4.5.7
- Wafrn v2026.02.02
- GoToSocial v0.21.0
- Loops v1.0.0-beta.10
- Ktistec v3.3.1
- Mitra v4.19.0
- Stegodon v1.8.0
- Hometown v1.2.0
- gathio v1.6.1
- Castopod v1.15.5
- NodeBB v4.9.0
- PieFed v1.6.7Clients
- Pachli v3.4.0
- tooi v0.22.0
- Summit v1.78.1
- Photon v2.3.0
- Blorp v1.10.3
- Phanpy changelogTools and Plugins
- Poduptime v6.2.1
- Fediverse invitationFor developers
Protocol
- FEP-a427: Server Domain Migration
- FEP-fc48: Generic ActivityPub serverArticles
- Self-Hosting Pixelfed: Federated Instagram Without the Algorithm
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019c7c6f-742a-7930-2413-73b1d9611c99
-
How many is your backlog for follow request approvals?
#Polls #AskFedi #Mastodon #Fediverse #Followers #Survey #FollowRequest #Poll
-
Is there a place in the #Fediverse where groups can meet? 🤔
#random question
-
@info@social.fedimtl.ca can we make sure to invite this Emilio person every time? 🤣
What's his handle I wonder...
-
@n00q I can't wait!
-
Tonight at @foulab is this month's #Fediverse Night. 7pm onwards.
I'll be trying to work on upgrading a Hometown instance with the newly released massive upgrade!
-
@Neko0001 Ah beh! Merci.
-
@nitchevo
☺️
