Our great sponsors
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
ens
Discontinued Implementations for ENS core functionality: The registry, registrars, and public resolvers.
Domain names as handles are a cool idea, and you can already do a variant of them in the "fediverse" either by hosting your own instance of a service or by configuring a WebFinger alias (which is what I do).
I'm less convinced by DIDs[1], which is what Bluesky seems to run on: I've yet to see an explanation for why the DID standard exists, given that it effectively punts all semantics (including basic things like cryptographic verification) onto unstandardized "methods" in an uncontrolled global namespace.
[1]: https://www.w3.org/TR/did-core/
Yeah. I've used that enough to learn how it works. I think the biggest issue is that it's not the default and most people take the easiest path which is using GitHub, etc.. There's a neat project that can help generate some of the web resources needed to use vanity imports:
https://github.com/leighmcculloch/vangen
Similar to how the nostr protocol does it: https://github.com/nostr-protocol/nips/blob/master/05.md
> I hope this idea catches on
This already exists with Ethereum Name Service (ENS) https://ens.domains and Sign-in With Ethereum.