
⁂ Article
Seeking interop testing for geosocial ActivityPub client
Hey, all! I’m seeking some help testing an application I whipped up for the Geosocial task force of the W3C Social Web Community Group. It’s called https://checkin.swf.pub/ , and it’s a barebones checkin service, similar to Swarm, but implemented as a pure Web client. You can watch the application in action.
It logs into your account on an ActivityPub server using OAuth 2.0. It […]
Please don’t mind me, I’m just testing if I broke the ActivityPub federation of this site (or not). If you’re reading this and didn’t get my previous post from today, it’s here:
My adventures in self-hosting: day 210 (viva FOSS!)
cheers!

⁂ Article
7.0.0 – I will follow you!
Just when you thought things were settling down… boom 💥 — the ActivityPub plugin gets another big upgrade. Say hello to version 7.0.0, a release packed with new features, polish, and under-the-hood improvements to help your WordPress site federate smoother, smarter, and more securely than ever.
Let’s dive into what’s new.
Following the Fediverse
We’ve added the initial building blocks for Following support — both sending and managing follow requests for remote actors. […]

wanderer: Decentralized trail database: #wanderer by @flomp is a new, #opensource, #decentralized #trail database where you can upload tracks (or import them from #STRAVA or #Komoot), create or share routes, and connect with communities through #ActivityPub-powered #federation.
https://spatialists.ch/posts/2025/07/09-wanderer-decentralized-trail-database/ #GIS #GISchat #geospatial#SwissGIS

Hello Fedi friends!
I’m currently experimenting with the POSSE method of publishing (“Publish [on your] Own Site, Syndicate Elsewhere”) on my federated WordPress site (this one) so that I can more easily organize posts and retrieve them in the future. This is the first of such posts.
I have created a “micro” post category and edited the functions.php file of my WordPress blog to exclude such posts from the main blog.
Here is the code I’m using:
function exclude_category( $query ) {
if ( $query->is_home() && $query->is_main_query() ) {
$query->set( ‘cat’, ‘-2132’ );
}
}
add_action( ‘pre_get_posts’, ‘exclude_category’ );
Where -2132 is the number assigned to the category “micro”.
You can find the category number by hovering over it in the Categories menu.
I also plan to tweak my site’s navigation menu to make “micro” appear under the blog category.
At some point in the future that will replace the “blog”… otherwise it’s too confusing to follow how many blogs I actually have.
I am also debating whether to migrate my GoToSocial account to WordPress using the MOVE function. What’s holding me back for now? I will need to be able to implement Serdy’s blocklists here before I do that. I experienced some terrible trolling and abusive messages when I didn’t have blocklists in place on my GoToSocial account last month, so I learned my lesson.
And I’d like to see how “social” the Friends for WordPress plugin by Alex Kirk is, before I consolidate my two accounts.
Anyway, this is all really exciting, made possible by the magic of #ActivityPub and the ActivityPub for WordPress plugin by @pfefferle. Thank you Matthias!
Onwards and upwards!

This is an interesting observation: I responded to someone's public post on a Mastodon (glitch) server as a private message (I have a toggle in my Compose interface that allows me to control that). That message went out fine and they received it, although I'm not sure what the UI looked like.
Their response #ActivityPub message from Mastodon however was unusable. I found it in my database, but the to
and cc
fields were empty.
{
"cc": [],
"to": [],
"type": "Create",
...
}
I suppose I could still pull these up for the UI using the inReplyTo
field. But blanking out the address fields seems like a weird choice for #Mastodon.