Doing caching correctly is tricky. Some kind of cache hinting might be needed. As a default though having it cache with a 5 minute interval would blunt the hit of a popular page very significantly. It would also allow for the use of a CDN like Fastly, Akamai, CloudFront, or CloudFlare in front if things get very hot.
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 ;)
Well, I'm not really against corporations per se. I work for one I quite enjoy and whose aims I think are good and in the general interest.
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.
NXDOMAIN hijhacking is really frustrating. I remember Verisign doing that back in the early 2000s to drive domain registrations into their hands. It was quickly fixed, but shows one of the major gaps in DNS.
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 :)
Indeed. This is the essential difference between capitalism and corporatism (sometimes called crony capitalism). Corporatism is insidious. It enables established players to control markets by manipulating regulations through political favors and disabling competitors through predatory positioning or pricing. It's very unfortunate that many people (including myself in the past) throw out the entire history of prosperity building that capitalism has enabled by conflating it with corporatism. Much of the sentiment driving the distaste for disruptive innovation thinking it will cause a race to the bottom directly supports incumbent large corporations and corporatism. It's easy to fall prey to this, because the narrative can easily have compelling stories of the human harm caused by technical innovation.
This is a compelling demonstration of Keybase.io's file system.
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.
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 ;)