Freakoverse

Concord 1: Concord Concord 2: Highgaurd Concord 3: Marathon Concord 4: Horizons Hunters Gathering

Don't think I shared, visually, the NIP-SHORT I thought of. Also, after demoing the simulation of it, got feedback to realize I can make it even shorter. With that said, what the updated NIP-SHORT brings to the table is... Turning (swapped 1 with 2 so it stays as text here): naddr2qvzqqqrkcgpzquuz5nxzzap2c034s8cuv5ayr7gjaxz7d22pgwfh0qpmsesy9eflqp4nxvp5xqer5den8qexzdrrvverzde5xfskxvm9xv6nsvtxx93nvdfnvy6rze3exyex2wfcx4jnvcfexscngveexvmnwwpsxd3rsd3kxq6ryef4xdnr5cek8pnrwc34xgknyv33xqkngc34xyknscfjxsknzvp38quxgc33vejnqvqhqecq8 Into: e-npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r-3qzq-5d3d0 Or into (if you have a DNN ID): e-nabceabsurd-3qzq-5d3d0 Didn't implement it in a client yet, probably not anytime soon, but hopefully soon enough, and I (and I imagine most nostr devs with their clients) will see a significant decrease in the number of their users giving them critisism about a post's address being stupid long (scary, inconvenient, etc) x3

I can't be there, so I'm hoping I can "finish" DNN and release what I have, horribly coded I'd imagine as it was vibed (and probably also not structured well as I'm no expert in the field), and hope a few start exploring it, implement it in their nostr clients, see if this fits with their ideas/projects in terms of being rid of ICANN-DNS (and a path to be rid of ICANN-IANA), and start a continous back and forth to make it better =3 What I mean by "finish", is to release the code for: - DNN node and a guide to have it up on a server (not sure if with or without the updated awareness system, to deliver a similar value like what 1.1.1.2 and 1.1.1.3 does, if not then 'planned updates' it goes in x3) - An updated PWANS signer app, that fixes the currently broken NIP-46 (that i thought I fixed =/) - The Daemon, to handle resolving DNN address and manage SSL/TLS certs for it (at least the Windows version with hopes for the linux version too) - The Demin browser, which is a fork of the Min browser that has DNN resolving and ssl/tls handling for it, hopefully with an overview guide on implementing DNN support for it on browsers (don't think so, but will see, perhaps just a basic general one) - JumbleDNN, which is a fork of Jumble that adds DNN support as well as NIP-UPV2 (traditional username and password, evolved, on nostr), hopefully with an overview guide on implementing DNN support on nostr clients I'd probably also make a rough overview video for the whole project, and try to present the high value offering this project brings to the nostr and dns worlds, and aiming to help people make it 'click' for them. (Side note: I still giggle every now and then because got this slave domain:

DNN

)View quoted note →