pull down to refresh
17 sats \ 3 replies \ @deSign_r OP 19 Sep \ parent \ on: What creative ideas have you been rambling on? Design
That's great! Nice to hear that SN will be integrating CLINK.
The centralized naming issue is a big deal. Have not been following but keep hearing a lot about it, mesh-things happening and also something happening with nostr, not sure is or is related with the one you mentioned. But not sure how to technically resolve it with the decentralization ingredient.
Was not what synonym is trying to do with... pubky or something else? Or what @ca98am79's spacesprotocol is doing? Keet from pears is also doing something similar I guess, but related with the IP.
Not too familiar with synonyms effort, afaik they went all in on some dht data scheme which sounds to me like a dead end.
Glancing at spaces and it's more like my past attempts, using the chain for authority and persistence. This new non-authoritative model would be the opposite, what I've learned looking at all other attempts and my own is that persistence and authority are the opposite of what's needed since they're common to every failed attempt.
reply
Does this
.nostr maybe similar to what you were planning on your previous comment #462059?reply
In my example .nostr would be context disambiguation, not a dns suffix for resolution.
This demo is everything that's wrong with most decentralized naming efforts in my view and per my post, its no different than manually adding a dns host record on your local system which is useless for making such a system reachable more broadly
Also whats also not shown here must be a custom CA or cert import to make the browser work with it, which can't be easily distributed across all devices, and for it's own sake is pointless since the idea of communicating with a nostr identity would be to use it's keypair for comms not an SSL cert.
Everyone is basically just reinventing "unstoppable domains" which itself has been around in various forms for decades
reply