Got my ICANN-DNS alt working, and aside from improving it and hitting up internet browser teams, I (and all who would use it) now have an option to tell my users to visit a freedom domain rather than a traditional one, if things go wrong and they take my traditional domain away, where nobody can take that domain away or ask me for any information or require permission from someone, and it's human-readable/memorable too. It's nostr+bitcoin based (without adding anything to bitcoin). Hit me up you're interested to learn more / happy to talk about it and/or help =3

Realistically? To be part of a set of relays (in partnership with other clients that do this as well) where members only can write into it and the public can read from it.

neat. would be pretty neat as well if there was a service out there that either allows users to check if their nsec has been leaked somehow, or even the service DM affected users about the leak with partial proof to alert them.

Golf is fun again =3 https://store.steampowered.com/app/4069520/Super_Battle_Golf/

Sounds good. Applied 🤘

kind of understand it, but i don't kind of care for it x3 Let's go with "the sweat is real!" x3

1. sorry that happened 2. now i'm thinking of a comic "i'm a human rights activist, and here's a taste of the first rule of human rights *punch*, which is that you don't have rights" 3. i'm sorry x3

Just a quickie

Had a similar thought a few days ago. Gist: Don't put much energy into convincing sheep/slaves to become aware/free, but rather make stuff for them to take advantage of them to benefit those who want to be aware/free, or are aware/free. This would result in an all around benefit for all (to the best that one can do. You can't 'force' someone to be aware/free, so that is the limit of what one can and should do.) (typo at the end, meant to say: "solutions for the sheep *where we'd* utilize")

- Brought back 'username and password' on nostr, evolved. - PC nostr signer (remote and local), lookin good, because screw makin on on mobile those are caged machines x3 - No need for any setup after keypair generation, start receiving eCash/Lightning, native bitcoin, and (soon) native other cryptos (secp256k1 based only), and no-scanning bitcoin (and other) silent payments, social native bitcoin (and other) sending, and easy multisig flow. - encoded an npub (63 chars of gibberish) to something human-readable/memorable/usable/locally-meaningful (8-16 chars), which also acts as a TLD, and also helps solves day-0 WoT problem, relay discovery and centralization problem too, as well as no need for a CA, and more. - Shortened event addresses (from 150-260 chars to 18-26 chars)

DNN node code up: https://github.com/Freakoverse/dnn-node (check the DEPLOYMENT.md for installation on a linux server) Here's a quick video guide to installing one on a linux server: It's probably rough af and messy, but it's better to put something out there to play around with and improve as time goes on. (I'd honestly want to refactoring everything from the start, but that'd waste a lot of time and not having something out there for others to check isn't a good thing imo) You can read about the DNN project (read me and node-policy) and its NIPs (specifically NIP-DN) here: https://git.nostrdev.com/freakoverse/DNN Couldn't be at #soveng unfortunately for SEC-06 (Identity) and SEC-07 (Network, ICANN DNS/IANA), this project pretty much fits for both cohorts. Identity & Signers (SEC-06): I made a desktop signer, DENOS, that's basically the user's nostr identity manager, that's also a wallet manager (eCash, focusing on nutzap management, and native bitcoin with both native segwit and taproot for two different purposes, DNN ID/TLD acquisition & management, local signing flow and a username/password sign-in flow, and later down the line I'd add what I'm calling Nostr Silent Payments (multi-currency, Bitcoin multisig but with good/clear UX, and a merchant e-commerce POS system (that includes traditional fiat payments). When a new user comes and generates a nostr keypair, they don't have to do anything else aside from that and you can immediatly send them eCash (nutzap focused, so no heavy token management), native bitcoin, or (later) other crypto and their tokens. And if they grab a DNN ID, aside from turning their npub (63 chars of gibberish) into a human-readable/memorable/usable/locally-meaningful ID (8-16 chars), it would also decently add to their WoT score from day 0. The Network Stack (SEC-07): There's a lot here, but focused on the ICANN-DNS problem as well as the Certificate Authority problem. With DNN, you can now have https://example.nabandonaread or https://example.naboutzook , where you acquire a Top-Level Domain (TLD) by sending yourself bitcoin from your bitcoin address that was derived from your npub and publishing a few events (DENOS has this function / as easy as it can be), and after acquring a TLD, you can have many domains at no extra cost. Forever yours, no requiring payments, no auctions, no fomo, and no trading, as simple and as fast and as cost-effect as it can be, and scales well (and it doesn't add anything to Bitcoin). SSL/TLS doesn't require CA as well, the cert would be self-signed (still secure) and you can put a thousand year validity if you want (set and forget). It should also be prepped (i hope, didn't do much testing on this part) for a Tollgate and FIPS future. Other: DNN solves other problems as well, secondary-effect benefits: - Nostr relay discovery problem (solves missing posts/messages, etc) - Relay centralization (no need to post or read from popular relays) - Impersonations (easily identify the correct person to follow) - Long event addresses (shorten event post from 150-260 chars to 18-26 chars) - Unfamiliar login flow (bringing back traditional username/password login flow, but evovled) - More Hit me up with any questions/feedback/topics, publically or privately, text or call (or in VRC, that would be fun y not x3) about any of this, especially if you want to implement DNN support in your nostr client (I forked Jumble and added support for it there, including some of the other benefits/NIPs like username/password login, local signer login, ID resolution, event addressing shortening, but forgot to add node query for user relay to be utilized so perhaps later), check it out: https://jdnn.top/ #nostr #DNS #ICANN

Another "free speech" platform with invite codes x3

What's good about new stuff is that it's varying degrees of being magical, but what I'm hoping for, that we won't repeat the same mistake again from the past, is to make the infra not-centralized, at least not completely, so that we'd start to work unbelievably hard again to decentralize it.