#Tag
Some thoughtful stuff about passkeys and the identity system, includes a few angles I hadn’t thought of: https://lucumr.pocoo.org/2025/9/2/passkeys/
Some thoughtful stuff about passkeys and the identity system, includes a few angles I hadn’t thought of: https://lucumr.pocoo.org/2025/9/2/passkeys/
The act of entering the temple through spatial and psychic layers moves the compass of identity from Australian-ness to Chinese-ness. It is a subtle movement of layers and reveals that identity is not monolithic but is a function of its environment. In this case the built environment of the temple. Although the temple is a physical, tangible part of the urban street, its influence on the visitor is more than that, the journey into its heart pulls at all our human senses.
More writing today #AsianDiaspora #architecture #identity
(2/2)
My understanding is that work done in FEPs informs the SocialCG task forces working on various aspects of social web applications. I imagine they're also watching Nostr architecture and NIPs for ideas, as well and ATProto and wherever their protocol experimentation happens.
Then the work done at SocialCG will feed into getting a charter for an updated version of ActivityPub itself. Locking in a bunch of experience from practice, and moving experimentation to new frontiers.
"That's the irony of what Blaine did when he created WebFinger. It was supposed to support multiple! It wasn't supposed to just be this is your fediverse address, it was supposed to be, here's how you find all the different account of information about me, and different things."
@rabble, 2025
https://wedistribute.org/podcast/s2e3-rabble-from-nos-social/
So ... WF is meant to facilitate something like Libravatar, where all roads lead back to a canonical profile? Hmm ...
Does anyone have experience with Key Event Receipt Infrastructure (KERI)?
> “Could there possibly be a unifying #DID method that covers the use cases of all others?” This is precisely what #KERI attempts to be. What makes KERI special is also the fact that it is not just another DID method. The KERI protocol has a grander vision of being the #identity overlay for the internet.
In the quest for #NomadicIdentity and #ActivityPub fediverse KERI may be worth looking into.
https://socialhub.activitypub.rocks/t/nomadic-identity-for-the-fediverse/2101/75
⁂ Article
Digital Identities that Benefit Humans
Today I’ll be traveling to Geneva to attend the Global Digital Collaboration Conference which seeks to “foster wallets, credentials and trusted infrastructure for the benefit of all humans.” I want to make sure that whatever comes out of this discussion really does benefit humans, and is therefore rooted in human rights. I have spoken publicly about how we incorporate ethics into our standards and specifications in order to make sure we ground them in human rights and “avoid dystopia.” The notion of storing a government-supplied digital credential on your personal device has great potential, but could also lead to harm through increased surveillance, centralisation of trust, and widening of the digital divide. We need to design these systems carefully in order to prevent misuse and overreach and to protect privacy and dignity.
⁂ Article
Digital Identities that Benefit Humans
Today I’ll be traveling to Geneva to attend the Global Digital Collaboration Conference which seeks to “foster wallets, credentials and trusted infrastructure for the benefit of all humans.” I want to make sure that whatever comes out of this discussion really does benefit humans, and is therefore rooted in human rights. I have spoken publicly about how we incorporate ethics into our standards and specifications in order to make sure we ground them in human rights and “avoid dystopia.” The notion of storing a government-supplied digital credential on your personal device has great potential, but could also lead to harm through increased surveillance, centralisation of trust, and widening of the digital divide. We need to design these systems carefully in order to prevent misuse and overreach and to protect privacy and dignity.
Hey Fediverse! 👋
We just wrapped up an amazing FediForum June 2025 a week ago, and BadgeFed was right in the thick of it! Here’s a recap of what we did, what we learned, and what’s next for decentralized badges.
BadgeFed had the honor of presenting and hosting two unconference sessions and showing off our work in one speed demo slots (watch the demo). The energy was fantastic; lots of curiosity, sharp questions, and a real hunger for open standards in the credentialing space.
A big theme at FediForum was specs and open standards. We’re right there with you! That’s why we’ve enhanced our technical documentation to explain exactly how BadgeFed uses ActivityPub and OpenBadges together:
Read more in our DETAILS.md.
We heard you: people want to try BadgeFed! Right now, it’s a solo setup (one admin, one Docker container), but we’re working hard to make it easier for others to deploy, configure, and even federate their own instances. Stay tuned for updates on multi-admin support and streamlined onboarding.
One of the most important pieces of feedback we received was about badge discoverability vs. timeline spam (see the issue). We want badges to be easy to find and share, but we also don’t want to flood the Fediverse with unwanted posts. This is now our top priority, we’re rethinking how verbose BadgeFed should be, and exploring opt-in/opt-out models for badge visibility and hashtag use.
We’re also working on ways to let you embed badges in your blog or add them to your Mastodon profile. More news on that soon!
FediForum was a fantastic experience, huge thanks to everyone who attended, gave feedback, and showed interest in decentralized credentials. Let’s keep building a more open, verifiable, and user-empowered Fediverse!
Badge up, and see you in the timeline! 🏅
You can read the article "BadgeFed @ FediForum June 2025: Unconferences, Demos, and Community Feedback" by @mapachehere as well.
#activitypub #badgefed #fediverse #dotnet #decentralization #open-source #openbadges #identity #fediforum #recapHey Fediverse! 👋
We just wrapped up an amazing FediForum June 2025 a week ago, and BadgeFed was right in the thick of it! Here’s a recap of what we did, what we learned, and what’s next for decentralized badges.
BadgeFed had the honor of presenting and hosting two unconference sessions and showing off our work in one speed demo slots (watch the demo). The energy was fantastic; lots of curiosity, sharp questions, and a real hunger for open standards in the credentialing space.
A big theme at FediForum was specs and open standards. We’re right there with you! That’s why we’ve enhanced our technical documentation to explain exactly how BadgeFed uses ActivityPub and OpenBadges together:
Read more in our DETAILS.md.
We heard you: people want to try BadgeFed! Right now, it’s a solo setup (one admin, one Docker container), but we’re working hard to make it easier for others to deploy, configure, and even federate their own instances. Stay tuned for updates on multi-admin support and streamlined onboarding.
One of the most important pieces of feedback we received was about badge discoverability vs. timeline spam (see the issue). We want badges to be easy to find and share, but we also don’t want to flood the Fediverse with unwanted posts. This is now our top priority, we’re rethinking how verbose BadgeFed should be, and exploring opt-in/opt-out models for badge visibility and hashtag use.
We’re also working on ways to let you embed badges in your blog or add them to your Mastodon profile. More news on that soon!
FediForum was a fantastic experience, huge thanks to everyone who attended, gave feedback, and showed interest in decentralized credentials. Let’s keep building a more open, verifiable, and user-empowered Fediverse!
Badge up, and see you in the timeline! 🏅
You can read the article "BadgeFed @ FediForum June 2025: Unconferences, Demos, and Community Feedback" by @mapachehere as well.
#activitypub #badgefed #fediverse #dotnet #decentralization #open-source #openbadges #identity #fediforum #recapHey Fediverse, we’ve got some exciting news—BadgeFed is moving out of the prototype phase! That’s right, what started as a scrappy proof-of-concept is now becoming a real, structured, and (dare we say) polished federated badge system.
And since we believe in working out in the open, we want to share our roadmap with you.
We’re focusing on three major areas to take BadgeFed from “hey, this kinda works” to “oh wow, this is actually usable.”
Right now, logging in is a bit of a mess. So we’re tackling authentication properly, integrating OAuth so you can log in using your Mastodon (or other Fediverse) account.
We’re building this with .NET and Blazor because performance and scalability matter. Plus, no one wants to manage yet another username/password combo.
We’re making sure BadgeFed speaks ActivityPub fluently. Right now, federation kinda-sorta works, but we need to define a proper spec that makes badge issuing,
earning, and verification seamless across different platforms. Whether you’re on Mastodon, Pleroma, or something else entirely, BadgeFed should just work.
We’re ironing out the kinks so badges travel as smoothly as your cat pictures. Also we want to support export and import from OpenBadges spec, and we need to do some experimentation on how this could travel on the fediverse.
What’s cooler than a decentralized badge system? A decentralized badge system that’s easy to set up.
We’re working on clear documentation, making installation painless, and putting together a Docker container so you don’t have to wrestle with dependencies or even dotnet.
One command, and boom—you’re federating badges like a pro.
Once the big three are solid, we’re setting our sights on some much-needed improvements:
We’re heads-down working on these priorities, but as always, feedback, ideas, and contributions are welcome.
This is an open-source project, and the best way to make sure it fits the needs of the Fediverse is to have the community involved.
If you want to help, hop into our discussions, check out the repo at https://github.com/tryvocalcat/badgefed, or just share your thoughts. Let’s make federated badges a thing! 🏅
You can read the article "BadgeFed: From Prototype to Reality" by @mapachehere as well.
#activitypub #badgefed #fediverse #dotnet #decentralization #open-source #identity #roadmapA space for Bonfire maintainers and contributors to communicate