4 ms·

So much complexity to get an HTML page on the internet. IMO the future of data ownership is self hosting from devices like raspberry pi's and upcycled Android p

So much complexity to get an HTML page on the internet. IMO the future of data ownership is self hosting from devices like raspberry pi's and upcycled Android phones. What works now: * Tunnel proxies[0] like ngrok. You can get an HTML page on the internet in 2 minutes with ngrok. * Software like Caddy which simplifies certificate management. What's needed: * IPv6 and ISPs to drop NAT so we don't need proxies. Good luck. * More upload throughput. Good luck. * Services that make it much easier to register a domain name and manage DNS. Should be easier than buying and setting up a phone. This is ripe for the picking. * Software designed with federated self hosting in mind. Like Inrupt Solid and similar projects. OT: Text-to-speech has gotten really impressive these days. Took me a solid minute to figure it out. [0]: https://github.com/anderspitman/awesome-tunneling https://github.com/anderspitman/awesome-tunneling

Uehreka 6y ago
If every link in the chain supports IPv6, can you connect directly to a computer behind a NAT by using IPv6? Or are IPv6 connections NATed too and we’re likely stuck with this for the foreseeable future?
tweetle_beetle 6y ago
On the domain/DNS side, how do you see things being simplified? Services like GoDaddy already try to do this, but in hiding functionality or renaming key terms to dumb them down, they confuse things further for anyone using mainstream materials to reference or learn from. TTL is often dumbed down to an "auto" setting - fair enough, but beyond that how much more can you simplify within the existing technology frameworks? (Admittedly all the verification and security records are getting a bit out of hand, but they aren't compulsory.) Anecdata: I had a colleague think they were helping with something because they saw "domain forwarding" turned off for a domain that was used as a secondary domain for an existing site. It was all working absolutely fine, using server config and DNS. They turned it on and behind the scenes the "friendly", "easy to use" provider removed the custom nameservers and cleared the DNS records. When I initially turned the forwarding off again, it added some records to forward to its domain parking service. All of this was obscured and presumably done in the name of helping users.
- anderspitman 6y ago
  I see it being simplified the same way phones and cars have been simplified. These are very complex systems with simple interfaces and well understood failure modes. If your call doesn't go through you check how many "bars" you have. If you have enough reboot. If it still doesn't work take it to a store. If your car fails it displays a light. Check the manual or take it/have it towed to a shop. There are annoyances but we know what to do. The problem is that DNS was designed for developers. That's fine but we need an interface for the average Joe to own a domain name. Yes there will be challenges and tradeoffs, but we can sure do a lot better than where we are.

Uehreka 6y ago

If every link in the chain supports IPv6, can you connect directly to a computer behind a NAT by using IPv6? Or are IPv6 connections NATed too and we’re likely stuck with this for the foreseeable future?

tweetle_beetle 6y ago

On the domain/DNS side, how do you see things being simplified? Services like GoDaddy already try to do this, but in hiding functionality or renaming key terms to dumb them down, they confuse things further for anyone using mainstream materials to reference or learn from. TTL is often dumbed down to an "auto" setting - fair enough, but beyond that how much more can you simplify within the existing technology frameworks? (Admittedly all the verification and security records are getting a bit out of hand, but they aren't compulsory.) Anecdata: I had a colleague think they were helping with something because they saw "domain forwarding" turned off for a domain that was used as a secondary domain for an existing site. It was all working absolutely fine, using server config and DNS. They turned it on and behind the scenes the "friendly", "easy to use" provider removed the custom nameservers and cleared the DNS records. When I initially turned the forwarding off again, it added some records to forward to its domain parking service. All of this was obscured and presumably done in the name of helping users.

anderspitman 6y ago
I see it being simplified the same way phones and cars have been simplified. These are very complex systems with simple interfaces and well understood failure modes. If your call doesn't go through you check how many "bars" you have. If you have enough reboot. If it still doesn't work take it to a store. If your car fails it displays a light. Check the manual or take it/have it towed to a shop. There are annoyances but we know what to do. The problem is that DNS was designed for developers. That's fine but we need an interface for the average Joe to own a domain name. Yes there will be challenges and tradeoffs, but we can sure do a lot better than where we are.