Found this:
https://en.m.wikipedia.org/wik...
Looks like you need to use water droplets in motion to harvest the energy. I wonder if you could work out a way to do it with just moving air?
The way to do this is to start inside the existing namespace: get yourself a short 2nd-level domain and start signing people up underneath it. Decide on your own policies for who gets what sub-domains and delegate them out. I'd suggest making WHOIS privacy the default policy, but be sure to keep a chain of accountability so that you aren't providing a spam haven.
The fun starts when the Man comes to confiscate your 2nd-level domain. At that point, if you're big enough and enough people depend on the services resolvable under your domain, you need to do a PR campaign appealing directly to the resolver community and ask them to configure a special exception for your 2nd-level, pointing directly at your nameservers. Gets even more interesting with DNSSEC as they will need to add a DS record as well. You will need an alternative means to publish your KSK to the world. There are some interesting enhancements being proposed for the RPKI to allow this kind of sub-domain exception policy, but we need a few additions to DNS and DNSSEC to make it work smoothly.
I'm all for a new set of policies, but you've got to give props to the current root.
Slashdot Mirror
Found this: https://en.m.wikipedia.org/wik... Looks like you need to use water droplets in motion to harvest the energy. I wonder if you could work out a way to do it with just moving air?
Can you reverse the principle to make a solid state windmill that generates power with no moving parts?
And listen to Riker this time around.
Don't forget, they issued an advisory about Independence Day: http://www.netfunny.com/rhf/jokes/96/Jul/id42.html -Pete
The way to do this is to start inside the existing namespace: get yourself a short 2nd-level domain and start signing people up underneath it. Decide on your own policies for who gets what sub-domains and delegate them out. I'd suggest making WHOIS privacy the default policy, but be sure to keep a chain of accountability so that you aren't providing a spam haven.
The fun starts when the Man comes to confiscate your 2nd-level domain. At that point, if you're big enough and enough people depend on the services resolvable under your domain, you need to do a PR campaign appealing directly to the resolver community and ask them to configure a special exception for your 2nd-level, pointing directly at your nameservers. Gets even more interesting with DNSSEC as they will need to add a DS record as well. You will need an alternative means to publish your KSK to the world. There are some interesting enhancements being proposed for the RPKI to allow this kind of sub-domain exception policy, but we need a few additions to DNS and DNSSEC to make it work smoothly.
I'm all for a new set of policies, but you've got to give props to the current root.