nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn have you looked to see if this could be used in a Nostr client? It’s backed by Matrix and Mozilla

Reply to this note

Please Login to reply.

Discussion

Read through the spec yesterday. It's sort of abstract and more complex than nostr needs, aince it deals with binding names to multiple keypairs. There is also some reliance on a consistent application policy. Some good ideas, but I (and others) think not the right fit.

Thanks for the summary 🤙🫂