I think it's a good idea of a put a comparison table between DNN and all other past attempts that tried to bring about change to dns, and put that table in the readme of the project, which will help people understand the difference and potentially help with developer adoption. DNN vs: Nomen, Spaces, ENS (Ethereum Name Service), BNS (Bitcoin Name Service), Name Coin, Unstoppable Domains, Handshake, Starname, etc (anything else?) I think I can also just bundle a lot of them that depend on another blockchain other than bitcoin. (side note: What's interesting about DNN, is that it can be chain agnostic, and anchor to however many blockchains it wants, but i don't care about any of them and i'm just focusing on bitcoin at the moment, and others can add support for other chains if they want, as i don't see a need to waste time on any of them since bitcoin is the most secure and the most decentralized).

With DNN, the ICANN-DNS problem is solved, and I thought "someone else can handle the ICANN-IANA problem", and someone conceptually did, but I thought today "why wait for the implementation to then have DNN support it later?" I'll just go ahead and support it now and build/playtest with it as soon as possible. DNN will actually be a non-hostile full ICANN (DNS and IANA) alt. With adoption, the internet will be half fully decentralized/permissionless/censorship-resistant. What's left is the ISP problem, and I'm hoping, with time, Tollgate will be that solution. Once it reaches 50%+ adoption, the internet will fully be properly decentralized/permissionless/censorship-resistant. The other issues (CDN, ads, etc) are a breeze in comparison / would be fixed later.

I know I said I wanted to relax today, but an idea struck me and I think I'm close to figuring out a scheme to shorten nostr event/post address down to 30% (or 5% depending on the address), from their original size. Meaning no more stupid long addresses of nostr posts when sharing them. This is for those with a DNN ID to get the smallest possible share link/address. No more scaring people with huge nostr links. Hopefully I'll figure it out x3

Still need to do a bunch more work on this, but I said I'd show magic by today, showcasing the latest state of DNN, and here it is: What was done: - Massive visual and UX overhaul. - Updated the name/ID encoder (now shows fewer words most of the time, so even more human readable/memorable). - Grabbing relevant events from other relays. - Implemented the Awareness system (if there's a domain that's problematic, the node can mark it and not server it. Others can choose to do it). - Updated the 6200 connection event to include a more complex support of connecting to servers (including delegating connection data to a server without risking your nostr nsec). - Remove signer nostr connect. - Optimization (the dashboard isn't slow/sluggish anymore) - Fixed a bunch of bugs. What was done (extra): - Tested support of DNN on a nostr client and worked (on jumble.social fork). - Tested support of DNN on a browser (lightweight one for now) to not only retrieve a website, but also verifying SSL/TLS certificate that's self-signed (no need to co-sign with the Certificate Authority). To do: - Double-check on re-org scenario. - Node peer discovery, connectivity, auto self-discovery, and management as well as handling edge cases of conflicting data. - Double-checking on TLS functionality working on the browser to the intended server. - Detailed documentation of the project (a lot more than currently available, and on the node itself, including documentation on implementation on nostr clients and browsers, and down the line Operating Systems / specifically Linux distros). - Set up pages for n0.0/n0 and b1m.0/b1m/b1000000.0/b1000000 to be nostr pages showcasing posts by different maintainers of different versions of DNN nodes and Bitcoin nodes (to solve the issue bitcoin has with which to best promote and use the market-decided node version. I don't want to have that mess with DNN, and on the way giving that solution to Bitcoin as well). - Implementing the second part of DNN ID registration in PWANS (At which point this would be the tool to use to get IDs easily and manage them). - Plan and develop and implement what I'm calling "username and email version 2" and implement it in PWANS alongside the jumble.social fork. - Update the jumble.social fork to auto-discover a user's (with a DNN ID) relay list to have users finally establish proper connection with each other and significantly decrease the chance of missing communications (solves that problem on nostr). - keep testing, improving, and fixing, until I'm satisfied with everything and have the DNN repo public for use and/or review the code and push PRs to fix it / contributors come and see the mess to fix and improve things bit by bit x3 (if that doesn't happen, I'll just hire one or two people to review the code and see where issues are and improve things, when funds become available), so that people can start running their own DNN nodes and expand the network / its decentralization. I hope I didn't forget anything else to mention. Now that my self-imposed obligation of sharing this today is done, and even though I want to continue, I want to relax and so I'll spend just one day, tomorrow, not working on any of my projects or others' (aside from normal work), because it's needed x3

"The node should be significantly faster now. Want me to also optimize the dashboard's block/anchor loading, or should we stop here for tonight?" Fuck you AI, I'm not going to sleep xD

I see some videos about how AI, if used by a new company/startup that's fully vibe-code focused, is good for prototyping stuff but when it comes to production things go to shit real fast. Generally speaking i think it's true, but also not at the same time. How I generally do it at the moment: Prototype for fun. Document. Once you had your fun, research, document, then build (from scratch again) the product assuming production-ready use immediately, and constantly test and edge-case test, and load test. That "document > research > document" part is basically heavy research and understanding the logic/system flows to keep the AI in the right track, and always test for production-level use. And after a while, I'd have expert/talented human code-reviewers on it. That's how I'm doing things anyway. AI won't be magical for those aren't knowledgeable about the thing they want to make. AI programmed DNN for me, but it didn't think of that solution for the ICANN-DNS problem, it didn't solve Zooko's triangle, it didn't think of the naming encoder system that's scalable, it didn't think of the adoption strategy, it didn't think of collision-avoidance with legacy DNS, it didn't create the UX flow of PWANS and think of the edge-cases of the eCash flow, had DEG Mods been made with AI it wouldn't have known or pushed for various UX enhancements and censorship-resistant systems. AI is great with coding, it's saving me tens of thousands of dollars, but it's no where near the mastermind.

Records of Ragnarok Season 3 6 episodes in IM NOT CRYING! YOU'RE CRYING! Side note: Progress is going well with DNN. Pwans is part of the ecosystem of DNN, so consider that also progress for DNN. I want to see I want to show stuff by Monday at the latest, but we'll see (to basically show "oh... it works. Like in an end-user kind of works. Fuckin cool!").

There's one issue with DEG Mods that needs fixing, and it will be fixed sometime next year (hopefully early next year but I'm not sure). It's not something any user would notice, it's just a simple kind swap to something custom, as right now, since launch, it's been using a kind standard that's definetly not fit for it. It was set that way because of, initially, a lack of proper understanding of nostr, specifically relays. And while yes it's a simple kind swap, I don't want to break compatibility with the mods that were published so far, as well as not wanting to be attacked (spam) via a loophole because of this backward compatibility, and it'll probably take a week or so of planning/adjusting the code to finish this (with human hands for this, not AI x3). This new custom kind will basically be the 'game mods' kind, and would be used for DEGA of course. Considering all the new custom kinds there'd be for DEGA, there'll probably be a NIP for it, similar to have theres a NIP for DNN, so I guess a... NIP-GEMS (Games E-Commerce, Management & Social).

The more time I spend planning, designing, developing on/for/with nostr, the more my brain gets rewired to think differently than with traditional systems. It basically boils down to "think with events" like "think with portals" x3

Post-nut clarity? Try post-noticing clarity. Oi. Why are you noticing? Stop noticing.

Pwans updated. Adding eCash/Cashu/NutZap, how I wanted it, was a big headache testing things out and solve all the edge cases x3 But ya, it's in, and... don't forget this whole thing vibe coded and is a pwa so be careful x3

PWANS

(auto update wasn't robust enough, so if you don't see the thing to refresh the app, then you have to first backup your seeds and/or keys, then basically delete the cache of Pwans from the browser you installed it on)

I wanted to push an updated to Pwans with the thing that got announced for DEGA yesterday, but nutzaping has a lot of edge cases that needs work. Not sure if I'll be able to finish it today even but fingers crossed

This wasn't planned, but it happened. First look at DEGA (heavily stripped down, this is basically a static page). Social post: https://xcancel.com/DEGAStoreX/status/1998802728328606026 Page:

DEGA

Once the site actually goes live (still far away since i'm still designing), and the link will change because of nostr addresses, I'll do a redirect (so the devs won't have broken links on their hands)

I think we need a new "we" Theres the normal we as I've just used it. Theres the royal we. How a freedom lovers we? We, the collective of freedom lovers, have spoken x3

Something neat will be announced tomorrow. (and, on a different note, maybe an update to Pwans. Still tinkering)

I just realized I can try to implement the "perfect" eCash/CashU UX, that's geared towards nostr, in my head, at least one flow of it, in PWANS. Dunno when tho.

There's catbox.moe for uploading files with direct download links (click a link, it downloads right away), with an upper limit of 200mb. There's pomf.lain.la (discovered this today) with an upper limit of 1gb. Anyone know another such service? (direct link + upper limit of 1gb + that version is free like the above).

PWANS changelog Main points: - Offline signing with fun animated qr codes = Super cool x3 - Manual reconnect = a quick "have you tried turning it off and on again?" - Post whatever kind of nostr event directly (this is more for technical nostr users) - You can find this changelog in tapping the logo on the top left then scroll down What I couldn't do: - Push notifications (would've been cool, but ya it's ass to add =/) What I didn't do yet: - Remote offline signing for bitcoin transactions - DNN name/ID implementation Also, here's the repo:

Gitea

PWANS

Progressive Web App Nostr Signer