Post #649584

2026-03-15 02:49 UTC

ActivityPub is also used for federation. Badge issuers (ActivityPub actors) can follow other issuers. When a badge is issued, a Create activity is federated. Other servers receive that activity and can store a local copy of the badge. This works very similarly to how Mastodon servers cache posts. Because of that, badges can also be: • revoked using the Delete activity • updated using the Update activity Again, this reuses existing ActivityPub verbs instead of inventing a new protocol or new spec. Simple primitives, (I love how simple it is), powerful results.

Replies (1)

@mapache@hachyderm.io 2026-03-15 02:52

Now let’s talk about @fediprofile@social.vocalcat.com @badgefed@mastodon.social issues recognition to recipients identified by a profile URL. It intentionally does not allow email addresses (even hashed ones). This avoids security issues and allows recipients to be identified using public profiles. Privacy at it's best. Any URL can be used as a profile: • LinkedIn • Mastodon • GitHub • personal websites • Instagram (ugh, eww) • etc... If that URL also happens to be an ActivityPub actor (for example a Mastodon or PixelFed profile), the user will also receive a mention or notification when a badge is issued. -- Many people already receive badges across different identities. For example, I personally have badges tied to: • my LinkedIn • my personal website • gaming profiles This is where the concept of a badge wallet or badge backpack becomes useful. A place to collect them all. (POKEMON!)

Open ##2661029