Avatar
Melvin Carvalho
de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645
Mathematician and Web Developer

I helped design DID (well, a bit). It's perfectly possible for different systems to have different URI schemes, in fact, it's encouraged at internet scale, which is the path to interoperability

nostr already has decentralized identifiers. In fact they are more decentralized than DIDs because the canonicalization does not depend on an http context, or on external vocabs and schemas, including xml schemas

It would not be hard to give nostr a URI scheme, and I think it can be done by cherry picking the best parts of DID, and throwing out the bloat, the technical debt, external centralized dependencies and stuff that doesnt work, such as range of the did resolution function

nostr URI schemes can be simple, self-contained and truly decentralized, allowing internet scale interop

So far people are coalescing around nostr:npub.. type things, which I wasnt fond of at first, but is growing on me

What's your lichess puzzle rating? 2563 here.

Want a correspondence game?

It could also be the solution. Checkpoints on #nostr would prevent large 51% attacks

Is grapheneOS any good?

It could be yes. Is the value of the social sybil resistance greater than the cost of storage. The answer is maybe, but probably yes, imho. It is to a degree mitigated by the fee market.

An accurate realtime checkpoint server would be better than a mining network

If only we had the technology to make one...

The more you drink, the more you like it

Amazing, thanks. Can we copy the design and give them to friends?

It's just liking a project. The BEST way to help #[3] is to star projects that developers are working on, especially the small ones. It encourages developers to spend time working on nostr

https://github.com/topics/nostr

3999 stars. Who wants to be #[0]? They can be only ONE!

https://github.com/nostr-protocol/nostr

He could be trying to gas light a change in the #[2] protocol, to spark a civil war