Decentralizing Microcredentials with ActivityPub + OpenBadges (BadgeFed)
/2025-06/session/3-k/
Note: two sessions on the same subject, with the same convener, merged into one set of notes.
Convener: Maho Pacheco (@mapache@hachyderm.io)
Participants who chose to record their names here:
- Luis Quintanilla (https://www.lqdev.me, @lqdev@toot.lqdev.tech)
- Evan Prodromou (@evan@cosocial.ca>)
- Ian Forrester (@cubicgarden@mas.to)
- Paul Fuxjaeger (@cypherhippie@chaos.social)
- Aaron Klemm
- Jayne Samuel-Walker (@tcmuffin@toot.wales)
Notes
Website: https://badges.vocalcat.com/
Blog account: @badgefed@vocalcat.com
BadgeFed:
- BadgeFed is a decentralized implementation of ActivityPub for issuance
- Badges can be verified independently.
- Accepts comments and ActivityPub interactions (Like, Comment, etc)
- Fully OpenBadges 2.0 compliant
Maho providing badges to attendees using BadgeFed. For badges provided in this unconference follow: @badgefed@badges.vocalcat.com
Open badges 3.0 spec: https://www.imsglobal.org/spec/ob/v3p0
Project Repo: https://github.com/tryvocalcat/badgefed
Inspired by: https://activitybadges.org/
The badge is an attachment in an ActivityPub note, see https://github.com/tryvocalcat/badgefed/blob/main/USAGE.md for details of implementation.
BadgeFed instances:
- http://verifiedby.maho.dev/ - Personal one (maho)
- http://badges.vocalcat.com/ - Main one (for badgefed)
- https://verifiedby.baddie.tech/ - Podcast
There was questions if you could retrack/remove a badge? (maybe soon)
There might be a API to allow access without setting up a docker instance? (planned)
Next Steps:
- Set up own instance to make it accessible to non-technical audiences
- Documentation
- Technical Documentation
- API for gamifying
- Moodle plugin