Embed Notice

@ryo @PhenomX6 @charliebrownau Last time I peeked into the OpenNIC community (probably 7+ years ago) I remember the situation being where everyone except like one or two TLD operators all using a very outdated, broken, and unsupported PHP application (I’m talking like “register_globals”-era tier) that was written for OpenNIC use by someone that had since moved on. There was periodic interest in someone to come along and do a full rewrite of it, usually never reaching any fruition, meanwhile one of the lead people having a total and absolute deathgrip that any rewrite absolutely just HAD to target PowerDNS (I believe) as a backend authoritative DNS server, all because PowerDNS had the feature of querying a MySQL server behind it for any DNS records… ‘therefore clearly the most superior option’ since you could just set DNS records in a MySQL database instead of having to ‘deal’ with zone files… Meanwhile BIND has had the capacity of dynamically creating and updating new DNS zones in a running server since ~”9.7.2-P2” released (around late 2010?), without having to reload all zone files, but nope, that’s not good enough, it “HAS TO be PowerDNS!” Either way, I’m sure someone else could come along and do better. The other fun thing with DNS is that there’s other serializations now, like DNS-over-HTTPS (JSON), where you could even have a braindead web developer be able to write some unusual alternative DNS network (versus just a typical alt-root DNS network using standard conventional DNS), and also not have to deal with any public DNS servers being weaponized for reflected DoS attacks per the inherent issue of DNS, UDP, and the source IP in a IPv4/IPv6 being forgeable for any networks that don’t conform to BCP 38.

I agree on commending I2P, and I do also commend Tor as an option, but would weigh I2P over Tor.

And yes, I agree on the prediction of the future outlook of the internet being a scatter of separate invite-only overlay networks, using the internet merely as a transport.