Subnostr

I wrote another thing (it seems like this became a series x3).

The ICANN Problem, Solved with #Bitcoin and #Nostr via #Nomen

https://yakihonne.com/article/naddr1qqxnzd3exy6rsvfjxc6ngwpsqgsre6jgq6c7r2vzn5cdtju20qq36sn3cer5avc4x8kfru5pzrlr7sqrqsqqqa28wj860q

Reply to this note

Please Login to reply.

Discussion

Water Blower 2y ago

We should encourage people to share just the nostr event id instead of the url of the specific client. I still like to read articles on Habla.

Water Blower 2y ago

Of course, some client developers will intentionally not do that or don't event expose the artcle's event id in their UI to increase their centralization of users.

Freakoverse 2y ago

I don't mind. There I'd imagine there'd be some backend magic complications to deal with (that I'm no expert at).

For now, though, I'll hopefully keep in mind to post the client link + nostr id.

With that said:

nostr:naddr1qqxnzd3exy6rsvfjxc6ngwpsqgsre6jgq6c7r2vzn5cdtju20qq36sn3cer5avc4x8kfru5pzrlr7sqrqsqqqa28wj860q