The UX of links on the Fediverse

User-centric thinking about links.

TLDR; A proposal for loading AP status links internally by default

Not to pick on Mastodon, but I’ll use it as an example because some Mobile apps have started to implement the experience I want to discuss.

Default situation
When using Mastodon the Web app, it is not uncommon to reference another post by pasting a link, whether to our own, or to another users post perhaps on another instance, or even from a different software.

Users on the Web app wishing to consult the link will usually click the link opening a new window or tab (where interaction on a remote instance is limited). A motivated user can copy the link, paste it into the search bar and load the status internally.

Wouldn’t it be simpler if the default interaction would load the link internally? And if users want to consult a remote status in context they can open the link in a new window or tab as they would elsewhere on the web.

Existing fragmented alternatives
Some apps (Toot!, Metatext) have implemented this behaviour by default for links to Mastodon status.

Standardizing for interoperability
We’re talking about the fediverse though, so interoperability is by necessity a given.

So how could we craft a link and signal to any other ActivityPub client that the link can be loaded as application/activity+json?

Data attributes. What if clients, when crafting a link would provide a hint using data attributes.
An example:

<a href="" data-activitypub-link="activity+json">A poll about interacting with remote status</a>

A number of server implementations are already fetching links for oEmbed, this addition seems somewhat trivial, but with a big improvement for end users!

Thought, comments?

Crossposted to Socialhub


Social icons

Social media interaction buttons have become ubiquitous.

While siloed social media can compete against each other for pixel space, what about federated social media?

We could attempt to compete in this arena, indeed AddToAny now includes a Mastodon button, and this is great. But what about those who are using Pixelfed, Friendica or Zap? Sure Pull requests can be made.

But, what about existing web software that is joining the Fediverse, such as WordPress, and Drupal. Would placing their logos beside other share buttons even make sense to anyone?

How can federated social media, with its plethora of domains and dozen or so software implementations (and counting), leverage this now standard user expectation?

What if we unified our branding / marketing, wouldn’t this collaboration elevate the whole Fediverse?

This unified branding for the Fediverse is something currently being worked out, with Designers adding new graphics for consideration, check out the proposals and feel free to suggest your own over at

Though once a common logo is decided, there will still be the issue of how to represent a user’s url… where a domain must also be included.

Which do you prefer?

URL form of identifying an actor (user) with Fediverse logo
WebFinger form of identifying an actor (user) with ActivityPub logo


March 10-11, a free virtual conference on accessibility axe-con

WordPress ActivityPub

http signatures update

Confirming that the Fix for required digest headers in mastodon now works

WordPress ActivityPub

Add support for latest HTTP Signatures spec draft

In response to feedback from the httpwg regarding their http signatures spec draft

Mastodon 3.2.1, now requires a Digest header in their POST requests.

Here is a Pull request for the wordpress plugin

WordPress ActivityPub


Just another attempt at federating posts.

It works!

Though as suspected, only on mastodon 3.2.0 (will add PR for digest headers)
WordPress ActivityPub


Really excited with the WordPress ActivityPub plugin!

Back in june I started a Pull Request to add Private Messages to the plugin.

As I was hacking at it, I realized that Comments were only being received, and that federated replies to the fediverse had yet to be implemented!

So, for reasons, I decided to push out the bulk my work. The PR is a culmination of the many features and approaches I have been testing.

The most important piece, which I look forward to cleaning up is threaded and federated comments!

In the coming days I look forward to dogfooding the features on this site.