Burrow is being updated to match the new functionality. Burrow had some version of mentions already. It will use the default way now.

Also adding a couple of more Burrow specific customizations like being able to pin a thread so that you can find and update it easily

Okay so mentions are finally here in Studio. Other full-featured clients should plan to support this.

Built against RFC-1/TN-6 and incorporating a suggestion from @Aneesh Sathe about found mentions (since mentions don’t send notifications they have to be discovered in inbound feed items on the receiving side)

What a mention is

Type @ada while writing. When you publish, it becomes a link to Ada, under the name you gave.

That's most of it. The handle ada is your own shorthand and stays private to you. Readers see "@Ada Ruiz", linked to wherever you said Ada can be found.

A mention notifies nobody. It's closer to writing someone's name with a link than to tagging them on a social network. Nothing is sent to Ada, and no count of mentions exists anywhere.

from Blygger ↗ · excerpt of v1

And re found mentions

Finding out when someone mentions you

Since a mention notifies nobody, how would you ever know? Your own reader can look.

from Blygger ↗ · excerpt of v1

Also since mentions now means people, quotes and stubs are now called responses even though they use the webmention protocol.

Mentions are ordinary links but carry rel=me/h-card data invisibly with other socials for clients that understand that convention.

Quick background on the two conventions, since mentions lean on both.

rel=me is a microformat for saying "this other page is also me." You add rel="me" to a link pointing at one of your profiles elsewhere, such as a Mastodon account or a GitHub page. It becomes verifiable when the link goes both ways: if that profile links back to your page with rel="me" too, a client can be fairly confident the same person controls both. It's the same mechanism Mastodon uses for its green checkmark on profile links, and IndieAuth uses it for sign-in.

h-card is a microformats2 vocabulary for describing a person or organization in ordinary HTML. Class names mark up the pieces: h-card on the container, p-name for the display name, u-url for the main link, u-photo for an avatar, and so on. A parser reads those classes and gets structured profile data, with no separate API or JSON needed.

Together, a mention can be a plain link to a human and still say who that person is and where else they live online.

Thanks to Aneesh for helping think this through.

from Venkatesh Rao's Blyg ↗ · snapshot of v1