ok, DNN IDs/TLDs are now: n{Word}{Word}{n}{Letter(s)} > example: nAbilityZooKD instead of n{3Letters}{Letter}{n}{Word(s)} > example: nABCeAbsurd Updated the forked browser to be able to parse this new encoding. Also updated/expanded the Awarenes DB to be more rebust for moderation marking (of a domain or a whole TLD is spam/scam/malware or adult, so OSs and/or browsers can optionally filter them out. (Untested). I've also impleneted NIP-SHORT i shared some time back, to shorten nostr event addresses, on the fork of jumble, check out this example short link: https://jdnn.top/notes/enAbandonAreaD2qgv59a9a I've posted an initial draft of NIP-NSP (Nostr Silent Payments) to be implemented at a later date (this is just the first draft, and it'll most likely be heavily modified):

Gitea

DNN/docs/NIPS/NIP-NSP.md at main

DNN - A decentralized, Bitcoin-anchored naming system for nostr and the web.

Now I need to fix the my signer's nip-46, and give more attention to the discord alt soltuion.

Considering how I figured out how to improve NIP17's privacy, as well as reduce the number of events for it, both at the cost of removing cold-DMs, I'm wondering if we can still have cold-DMs with current nip17 spec, but decrease the spam attack surface. Adding a POW score threshold info in my kind:0 (for me to even fetch your DM from relays, it must pass this difficult level) DNN ID could also be a thing (for me to even fetch your DM, you must have a DNN ID), an indication that you spent some money Both could be used at the same time as well. I'm also thinking, considering my previous posts about receiving money to a npub = (you must send me X amount of money before I can add you to my contact list so we can start DMing each other privately) Dunno, but POW score is a good start i'd say =3

Is DEG Mods the only nostr client that handles media like text posts in regards to censorship-resistance? In DEG Mods, it has a system/flow set in place where when an image (or any file) gets uploaded, it tries to upload said image/file to multiple blossom servers, and logs the sources, then does a hash check on fetch/download to verify authenticity. Meaning: If a source/host deletes an image/file, the system would try to find the image/file on other blossom servers and fetches it when found, then hashes what it found and match-check it with the hash address in the link. From what I can see, most nostr clients upload an image once and there is know scan/search function or hash check? If no or few clients do this, then this is something that must be changed. When I have time (and when i remember x3) i'll add tickets to nostr client repos to add suchs systems/flows to acheive media censorship/failure/maliciousness resistance (or at least try to), or hopefully others publish those tickets instead.

I figured out how to improve Silent Payments on Bitcoin (the huge processing that needs to be done to know if you received funds or not). Also figured out a Silent Payment style method but for your npub, also without that huge processing problem, and for multiple cryptos / not just bitcoin (only chains with secp256k1, so sadly monero can't be part of this, unless i or someone else can figure out a way to make it work). Assuming I didn't miss anything or misunderstood something, i figured out: A multi-chain, low-overhead, Nostr-native stealth payment protocol. One nPub = private receive address for multiple currencies. Won't work on it now, later, since I gotta do other stuff.

Want xD

コトブキヤコレクション 2026｜KOTOBUKIYA COLLECTION 2026

遊☆戯☆王デュエルモンスターズ ARTFX J 城之内克也 -熱き決闘者たち- ｜ コトブキヤコレクション 2026｜KOTOBUKIYA COLLECTION 2026

遊☆戯☆王デュエルモンスターズ ARTFX J 城之内克也 -熱き決闘者たち-