reposted
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
View note →
