UK-style headaches coming for everyone now on discord. Seems like I actually need to start making that discord alt, even if barebones/rough, shit is getting worse and worse faster than expected.

I've figured out, with the help of another bouncing the idea with, an improvement to NIP-17 / Giftwraps where it protects even the receiver of a message + prevents spam attacks that burns processing power. This is with the assumption you want a whitelisted-only DM experience.

Not sure if I should change the DNN ID encoding to something else than how it's currently done. Right now we get something like 'nABCeAbsurd' (n-abc-e-absurd), where after ~1.5 years we'd start getting results like 'nABCe1Absurd' (n-abc-e-1-absurd), and the number always increases every ~1.5 years. Also, depending on demand, people might get two words at the end like 'nABCe1AbsurdAbility' (uncommon/rare, but it could happen). The best alt i can think of, with human readability/memorability in mind, is a result of something like 'nAbilityStealKD' (n-ability-steal-kd), where after around ~80 years we'd start getting results like 'nabilitysteal1kd' (n-ability-steal-1-kdz), the number increases around every 80 years. nABCeAbsurd (after ~1.5 years a number appears, and increase) vs nAbilityStealKD (after ~80 years a number appears, and increase) (side note: most people would get get 1 or 2 letters at the end most of the time, so nAbilityStealK or nAbilityStealKD, but on high demand it would be nAbilityStealKDO) (nothing is case-sensitive btw) After asking two famility members (normies) on which would they most likely remember, easily read and share, write, out of the two following options: nABCeAbsurd nAbilityStealKD They chose the second option. So I'll most likely change it to that. Keep in mind that this is an ID, a TLD (google.nabilitystealkdo), and part of a short link of posts with nip-short (.com/post/e-nabilitystealkdo-3qgx-f515d). Asking here a well, which type would you prefer and remember? nABCeAbsurd (worst result within 200 years: nABCe123AbsurdAbility) nAbilityStealKD (worst result within 200 years: nAbilitySteal2KDO)

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 →

For any who wants to get a monitor, don't get an MSI one. 3 months later and it borked sadly. Got another monitor, let's see how Lenovo goes.

I know people do posts where they'd ask "reply with mentions of hidden gem projects" or "reply with mentions of talented individuals", etc, but what I want for people to do is something with the following template: "Reply with mentions of people who usually talk about <interest>" that's not nostr/bitcoin related. So that you can find, follow, interact with people of your other interests and have a diverse feed =3 Here's mine: Reply with mentions of people who usually talk about games and anime #nostr #gaming #anime #asknostr

Writing up Q&As, which includes a "Why DNN and not XYZ?" Also made a comparison table (probably need to update it more) And considering what I wrote before in terms of new benefits I realized, and the below text you might read, I'll also add another doc mentioning use-cases/applications (since there's a lot). Side note: I also just realized (so I need to update the doc with this) that assuming DNN becomes mainstream, a search engine based on it is possible, without needing websites to put special code in their website to be indexed by a system, resulting in the ability for anyone to create a competing search engine without relying on historical indexing of a single entity. What this means: Let's assume DNN was there from the start, and Google did it's thing and became the best search engine, though they started censoring their search results and modifying it to fit their and others' needs, corruption, etc (all of which happened), another search engine would appear, have almost all the same data, and doesn't do BS actions/behaviour like we see with Google, and people start using it without any friction, resulting in an immediate competitive strike, which ultimately results in a healthier system and everyone benefits. Side note, the second coming: sudo pacman -S vlc? sudo yay -S vlc? nah, let's go with sudo nabtaAbove -S vlc sudo nabobZoo -S vlc etc Gist: nostr based, user based, creation of list of repos to install shit on your linux) That's be great to have one day =3

I decided to look into Handshake (for comparison purposes with DNN). After looking into it: Weeks to get a TLD? Seperate chain / not bitcoin? Auction processes that might skyrocket what I want (and dealing with said auction process)? Recuring payments where i'd lose it if I forget? Sell domains to others as you bought a rented TLD? Not interested / similar to others. The more DNS protocols I compare DNN to, the rate of my belief in its success increases exponentially.

Wait a minute... I just realized... DNN provides an human-readable/memorable receive address to a bitcoin address without needing a nostr address. Just do a self transfer from your bluewallet for example, and there we go, now you have something like nabobAbove where people can send sats to, instead of a long address string. This just added a big value point for Bitcoin users without needing to interact with nostr. --- I'm also thinking if I can derive shitcoin addresses from an npub (don't think i'll do it, but just document it for other apps if they're interested in doing so... or maybe I will for marketing purposes? Will see).

I really love Boji If I were to serve a king in a fantasy world, it would be Boji x3