Tomorrow is Global Accessibility Awareness Day. So far, 68 people are pledging 258.5 hours toward improving #accessibility in #WordPress. 🙌 This is our second year hosting a virtual contributor day, and we need you! 🫵

My goal is to provide feedback to the 108 themes on WordPress .org with the accessibility-ready tag. You don't need #a11y testing experience to do this. More info in the 🧵 #GAAD

Global Accessibility Awareness Day (GAAD), on Thursday, May 21, 2026, is a great opportunity to learn, listen, and improve the digital experiences we create together.

We encourage everyone to check out and support one of the many events being hosted by accessibility advocates, educators, and organizations around the world.

Drop an event you’ll be attending in the comments so others can discover and support it too.

accessibility.day/

#GAAD #WordPress #Accessibility #A11y #InclusiveWeb

At WordCamp Canada 2025, Matt Mullenweg shared a bold vision for the future of WordPress! 🚀 From the Day One app & AI-driven development to navigating legal/technical shifts in content, the platform is evolving.

Check out the highlights and stay tuned for this year’s line up! ✌️ 🇨🇦 #WordPress #WCEH2026

In the video in the post I just boosted, @anildash says #Substack is now boiling the frog in a slow move from email towards lock-in. And of course they work with Nazis etc.

What we need is an effort between newsletter publishers like #Ghost #WordPress etc and reader apps like @wallabag to build an ecosystem like podcasting. To make it smooth while remaining totally open. I'd argue for using #ActivityPub in addition to RSS to support boosts. Then we need decentralized money.

#APnative

Hmm, this is interesting... Someone apparently bought some (legit) Wordpress plugins, solely to put malware backdoors in those plugins!

(Having run a bunch of Wordpress sites in the past, I have zero trust in the software not being compromised, in general, somehow... so many times -- no plugins, all security patches installed -- those blogs all turned into pharmaceutical spamming websites overnight. 🤷 )

techcrunch.com/2026/04/14/some…

#cybersecurity #wordpress

One of the best things about the Fediverse is that conversations happen everywhere, across Mastodon, WordPress, Pixelfed, and dozens of other platforms. One of the trickiest things about the Fediverse is finding those conversations in the first place.

Hashtags have always been the Fediverse’s answer to discovery. But because the network is decentralized, the posts you see for any given hashtag depend on which servers yours already knows about. If nobody on your server follows someone who posted about #[url=https://activitypub.blog/tag/wordpress/]WordPress[/url]Federation, you’ll never see that post, even though it’s public and out there.

tags.pub changes that.

What Is tags.pub?

tags.pub is a global hashtag server built by the Social Web Foundation, a nonprofit dedicated to growing the open social web, and an organization Automattic is proud to partner with.

The idea is simple: tags.pub collects publicly posted content from across the Fediverse and redistributes it based on hashtags. When you follow a hashtag account like @[url=https://tags.pub/user/photography]photography@tags.pub[/url], you’ll see posts tagged #photography from servers your instance might never have heard of. It fills in the gaps that decentralization naturally creates.

The project is open source (AGPL-3.0), privacy-conscious, it doesn’t store post content, images, or media, and respects user controls like #NoTagsPub and #NoBots opt-outs.

How It Works on WordPress.com

If you’re running a WordPress.com site with the ActivityPub plugin, there’s nothing to configure. tags.pub already works out of the box. Your public posts and their hashtags are discoverable across the Fediverse through tags.pub, and you can follow hashtag accounts from your Following page.

Connecting a Self-Hosted WordPress Site

For self-hosted WordPress sites, head to Settings → ActivityPub → Settings and scroll to the Relay section. Add one of these URLs:

• Inbox: https://tags.pub/user/_____relay_____/inbox
• Shared Inbox: https://tags.pub/shared/inbox

This creates a one-way connection where your server sends public posts to tags.pub for hashtag distribution, and your posts become part of the global hashtag network.

Following Hashtags

Once connected, you can also follow specific hashtags by searching for them as accounts. For example, to follow #[url=https://activitypub.blog/tag/wordpress/]WordPress[/url] posts from across the entire Fediverse, follow:

<div>@[url=https://tags.pub/user/wordpress]wordpress@tags.pub[/url]</div>

Any publicly tagged post that reaches tags.pub will be boosted by that account into your timeline. When posts are edited or deleted, tags.pub updates accordingly.

Privacy and Control

tags.pub is designed with user agency in mind:

• Opt out anytime by adding #NoTagsPub or #NoBots to your bio, your posts won’t be boosted.
• Block the domain entirely if you prefer not to interact with the service at all.
• No content storage, tags.pub doesn’t archive your posts, images, or media. It only maintains boost records.
• Respects blocks, if someone blocks tags.pub, their content stays out.

A Step Toward Better Discovery

Discoverability is one of the areas we’ve identified on our 2026 roadmap as a key challenge, and services like tags.pub are exactly the kind of infrastructure that helps solve it. By connecting WordPress sites to a global hashtag network, your posts can reach people who care about the same topics, even if they’ve never heard of your blog before.

If you’re already using ActivityPub for WordPress, connecting to tags.pub takes less than a minute. Give it a try and let us know how it works for you. Have you noticed more engagement from the wider Fediverse? We’d love to hear about your experience.

Yesterday I shared Discover more of the Fediverse with tags.pub in my Pook-Emu Bee links for the day. The post introduces a new feature for the ActivityPub for WordPress plugin: Subscribing a site to the tags.pub relay for hashtag boosting. It provides the following instructions for self-hosted WordPress sites such as this one:

For self-hosted WordPress sites, head to Settings → ActivityPub → Settings and scroll to the Relay section. Add one of these URLs:

• Inbox: tags.pub/user/_____relay_____/…
• Shared Inbox: tags.pub/shared/inbox

The instructions offer two URLs and say “[a]dd one.” I added the second because it is more aesthetic. But I did wonder what the difference was between the two URLs. So too did commenter bocops:

Could you explain the difference between the “Inbox” and the “Shared Inbox” relay URLs?

Post author and ActivityPub for WordPress developer Matthias Pfefferle answered the question:

from a user perspective there is none. you can use either one of them!

While the instructions do say “[a]dd one of these URLs” and I interpreted the instructions correctly in the first instance, I will offer my two-cent take that it does raise a question why there are two URLs and how they may differ. I dealt (and will deal again) with this issue regarding site feeds. On NLJ, I make a point of promoting various feed formats, namely RSS, ATOM, RDF, and JSON. However, I am sensitive to the fact that many readers may not be familiar with feeds, much less different formats. Thus, I explain that RSS (our default) and ATOM should work in all feed readers, so most people should use one of those formats (usually RSS since that is the WordPress default at /feed/) unless they have a specific reason to use JSON (which I use to subscribe to NLJ in Miniflux) or RDF (that seems less likely but maybe there are some RDF fans out there). Regarding the tags.pub post, I would recommend offering one link as a sort of “default” while adding a note (or footnote) on the distinction (if any) for people who may be interested.

All that aside, tags.pub works for me and is a very nice feature for WordPress sites (both .com and .org) taking advantage of new Fediverse features. I tip my hat to Mr. Pfefferle and everyone who is working on it.