# backup deployed app...
# deploy app...
# return whatever
What "value" did Jar Jar add?
APK: the application sounds like it does a great job of fetching the data, but it seems much more useful to stick that data inside a DNS proxy or recursive resolver. Even if the resources required to run it are prohibitive for a crappy wifi router, it could be run on a box on the local network, and the crappy router uses it as its DNS resolver.
Then when I manage my home network of varying devices (tablets, phones, mixed OS laptops & desktops, even visitors) they will all get the benefit of DNS-level filtering.
I would manage a corporate network in a similar way. During DHCP when they get some local DNS resolvers, or hard-coded, the 1-3 local resolvers do all the DNS filtering for the entire network. A unified web UI on the master DNS resolver could micro-manage the rules if necessary (unblock something, add a manual block, local dns resolution, etc).
Only 3 letter strings and longer were allowed.
The problems with
Technically it was the US Dept of Commerce that didn't want
Signing doesn't affect the distributed problem. If you want
I suppose if you get your key signed by 1000 of your friends, and mine is only signed by 5, then yours becomes more popular. Until your 999th friend sends spam from your domain, and now everyone starts signing my key and it becomes more authoritative.
Even in a block chain type system, domains or TLDs would be awarded first come, first served (like today with the hierarchical system) and then transferred from one party to another (like today).
The only difference would be the cost. Should it be inverted? The first TLD on the DNS block chain would be very, very expensive, but the last million would be inconsequential.