fediverse

<p>Hey, all! I’m seeking some help testing an application I whipped up for the <a href="https://github.com/swicg/geosocial" rel="nofollow">Geosocial task force of the W3C Social Web Community Group</a>. It’s called <a href="https://checkin.swf.pub/ " rel="nofollow"><span class="invisible">https://</span>checkin.swf.pub/</a>, and it’s a barebones checkin service, similar to Swarm, but implemented as a pure Web client. You can watch the application in action.</p><p>It logs into your account on an ActivityPub server using OAuth 2.0. It then reads your inbox, filtering the activities there to only show geosocial ones. You can use the geolocation services in the browser, and the <a href="https://socialwebfoundation.org/2025/04/29/places-pub/" rel="nofollow">places.pub</a> service for a place vocabulary, to find nearby places. You can then “check in” to one of the places, with a note, and control of the privacy of the activity.</p><p><a href="https://www.w3.org/TR/activitystreams-vocabulary/#h-motivations-geo" rel="nofollow">Geosocial activities</a> are part of the core <a href="https://www.w3.org/TR/activitystreams-vocabulary/" rel="nofollow">Activity Vocabulary</a> that underlies ActivityPub. But, they’re not as widely implemented as other activities in the vocabulary. This app is trying to change that, by making them available on the network, and making it easy to create them.</p><p>To test the client, your service will need to support:</p><p><a href="https://www.w3.org/community/reports/socialcg/CG-FINAL-apwf-20240608/" rel="nofollow">Webfinger</a> (for login)<br><a href="https://www.w3.org/TR/activitypub/#client-to-server-interactions" rel="nofollow">ActivityPub API</a> (“client-to-server”, “C2S”)<br><a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/d8c2/fep-d8c2.md" rel="nofollow">FEP-d8c2</a> (OAuth 2.0 profile for ActivityPub API)<br><a href="https://www.w3.org/TR/activitypub/#proxyUrl" rel="nofollow">proxyUrl</a> (for fetching data from remote servers)</p><p>To test federation, your service will need to support:</p><p>Receiving <a href="https://www.w3.org/TR/activitystreams-vocabulary/#dfn-arrive" rel="nofollow">Arrive</a>, <a href="https://www.w3.org/TR/activitystreams-vocabulary/#dfn-leave" rel="nofollow">Leave</a>, and <a href="https://www.w3.org/TR/activitystreams-vocabulary/#dfn-travel" rel="nofollow">Travel</a> activities<br>Showing those activities to users</p><p>As of this writing, Mastodon does not work for either of these. If you want to test receiving federated messages, follow me on evan@onepage.pub . I’ve been using it a lot!</p><p>Code for the checkin application is here: <a href="https://github.com/social-web-foundation/checkin" rel="nofollow" class="ellipsis" title="github.com/social-web-foundation/checkin"><span class="invisible">https://</span><span class="ellipsis">github.com/social-web-foundati</span><span class="invisible">on/checkin</span></a></p><p>This is my second ActivityPub API client (<a href="https://github.com/evanp/ap" rel="nofollow">ap</a>, the command-line client, was my first), and my first one for the Web. I found this process really fun and invigorating. I was able to create a new kind of social networking application (well, new on the Fediverse…) purely from the client side. The app saves no data to the server; everything is done in the browser.</p><p>Please reach out on GitHub or comment here if you want to work on interoperability. I’m happy to help debug connections if needed.</p> <small class="notice" x-post-type-data="type=&#x27;Article&#x27; attributed_to=None"> Takahe has limited support for this type: <a href="https://socialwebfoundation.org/2025/07/14/seeking-interop-testing-for-geosocial-activitypub-client/">See Original Article</a> </small>

<p><a href="https://activitypub.blog/2025/06/11/our-2025-roadmap-building-the-future-of-wordpress-federation/" rel="nofollow">Alongside our upcoming plans</a>, we’ve already shipped several important features in recent releases. Here are some highlights of what’s now available in the ActivityPub plugin.</p><p>Onboarding</p><p>We’ve added an onboarding flow after plugin activation to help guide new users through key decisions — such as selecting the Actor Mode.</p><p>It’s also a great opportunity to explain Fediverse concepts for users who are new to them.</p><p>More details:</p><p>👉 <a href="https://activitypub.blog/2025/05/14/5-9-0-easier-onboarding-for-your-fediverse-experience/" rel="nofollow">5.9.0 — Easier onboarding for your Fediverse experience</a></p><p>Move</p><p>The Move Activity is used by Mastodon to migrate accounts to different servers — and can also be used for domain or username changes.</p><p>In the WordPress ecosystem, one of the main motivations for implementing Move was to support changing the domain of a WordPress blog — a common scenario for WordPress site owners.</p><p>We’ve built a solid foundation in the plugin to both send and receive Move Activities. However, because Move is not yet widely adopted across the Fediverse, we’ve decided to pause further work on this feature until there is broader ecosystem support.</p><p>Account migration remains a crucial capability for a healthier, more portable social web. If you’re interested in the broader context and challenges around this, we recommend watching <a href="https://fediforum.org/2025-06/" rel="nofollow">Cory Doctorow’s keynote from the June FediForum</a>:</p><p><a href="https://www.youtube.com/watch?v=7_Gs1t0qe78" rel="nofollow" class="ellipsis" title="www.youtube.com/watch?v=7_Gs1t0qe78"><span class="invisible">https://</span><span class="ellipsis">www.youtube.com/watch?v=7_Gs1t</span><span class="invisible">0qe78</span></a></p><p>We’ll revisit this as the standard matures and more servers implement consistent handling of Move.</p><p>More details:</p><p>👉 <a href="https://github.com/Automattic/wordpress-activitypub/milestone/5" rel="nofollow">GitHub — Move Milestone</a></p><p>Outbox</p><p>Earlier versions of the plugin supported only the federation of custom post types, sending all messages in one bulk.</p><p>That approach works up to about 1000 followers, but does not support retries, logging, or error handling.</p><p>To support larger blogs or news sites — we needed a more robust system.</p><p>We now have mechanisms to:</p><p>Federate activities to more than 1000 followers.<br>Use a staggered delivery system that prioritizes servers.<br>Provide a stable and scalable architecture.<br>Support retries and error reporting.</p><p>This improved Outbox system also makes it easier for third-party plugin developers to federate their own content types in a reliable and scalable way.</p><p>More details:</p><p>👉 <a href="https://github.com/Automattic/wordpress-activitypub/milestone/4" rel="nofollow">GitHub — Outbox Milestone</a></p><p>Changelogs</p><p>These are just the major milestones. If you’re interested in everything we ship, be sure to subscribe or follow the blog — we publish detailed <a href="https://activitypub.blog/category/changelog/" rel="nofollow">changelog posts</a> with every new plugin release, listing all new features and improvements.</p><p>As always, we welcome your feedback and ideas — they help shape the future of the ActivityPub plugin and the growing WordPress Fediverse community! 🚀</p> <small class="notice" x-post-type-data="type=&#x27;Article&#x27; attributed_to=None"> Takahe has limited support for this type: <a href="https://activitypub.blog/2025/06/24/what-we-shipped-so-far-in-2025/">See Original Article</a> </small>