AlainODea
An even more impressive trick might be a TLS server with SNI running vhosts which could check that the content was signed by a keybase user with a DNS proof for controlling that same domain. That would allow custom domains based on DNS CNAMEs. Now I'm getting carried away though ;)
The challenge, as I see it, is to have governments with a spine, but governments not so big that they stifle freedom or crowd out opportunities. Governments need to be powerful enough to overrule the biggest corporations so that corporations can exist without the cronyism. Power alone is insufficient though because even a powerful government is peopled by individuals who can sometimes be bought cheaply.
The East India Company is a somewhat terrifying example of what is possible with unbound power for corporations. It's an equally bad and unsubtle endpoint as an all government central economy. Diversity of thought and composition, as in many places, yields better results than homogeneity.
I think corporations are necessary for large-scale, long-term commercial endeavours. Certain classes of services to both individuals and businesses need continuity and corporations are well-suited to providing that kind of continuity.
Where we are today forgives incumbent large corporations too much and (certainly in Canada) makes it far too difficult for entrepreneurs to start small businesses.
I run my own DHCP and DNS at home mainly for performance reasons: https://github.com/AlainODea/home_network
Prior to doing that I had serious issues with buffering on iTunes and Netflix. That was probably mostly a DHCP problem, but I figured getting names for local systems (getting numerous at that point) was worthwhile.
Fitting all of this into a Raspberry Pi as you have done is really compelling. I'm currently using a Dell Precision T3500 and it's not exactly light on power consumption. I'll have to give this a shot. Maybe I can convince my son to try it on his Kano :)
This idea could be taken further to get past the past the ugliness complaint. Imagine something takes Markdown from these and renders it only if verified. Someone could stand up a TLS-protected site (possibly protected with a letsencrypt.com cert to reduce cost) that conditionally renders (based on keybase verify) and potentially caches renders for performance.
Either way, this is neat and I'm excited to see what other ideas our creative crowd come up with in using Keybase.io's new file system feature.