@jec @DawnPaladin You bring up a very important point: DNS is a big problem. Domain names are inherently scarce and therefore expensive. This adds to the already large burden of self-hosting.

It's a big reason why people end up with big-social-site.com/@my-username: because it's free.

We should ask ourselves how this can be addressed (heh). How important is it to have a globally unique human-readable name online? Pretty much none of us have unique given name + family name, yet we manage fine.

@binarycat Minimalism theater

@floppy
Not sure I see the problem with automated updates for a personal home server?
@alcinnz @wire

@alcinnz
Static only is too limited IMO. Dynamic routes are required for creating interactive tools/experiences. You're right of course that it increases the attack surface substantially. That's why on my project (https://Dropserver.org) each app runs in a sandbox, with strictly limited access to some read-only dirs, write access to only one app dir, and no network listeners.
I know sandboxes can never be perfect, but they significantly raise the bar for a breach.
@floppy

@jgoerzen @aral @cjd Yggdrasil looks interesting, but they politely ask not to use a crawler on the network. That doesn't sound so good? What happens if it gets popular and you can't count on people's general good behavior to keep the network from clogging up.

In this era I would think protocol designers would assume bad intentions all around and design for that?