BT blocking DNS
2016-01-03 14:37:58.824359+01 by Dan Lyke 2 comments
Wow, fuck you BT
This is all the more reason we need to move away from DNS to key-based identity systems.
2016-01-03 14:37:58.824359+01 by Dan Lyke 2 comments
Wow, fuck you BT
This is all the more reason we need to move away from DNS to key-based identity systems.
[ related topics: Photography Databases ]
comments in descending chronological order (reverse):
#Comment Re: BT blocking DNS made: 2016-01-04 01:17:13.937904+01 by: Dan Lyke
All document references can be done through a combination of hashes and public keys, those can be resolved to current ip addresses via something like tagged Bit Torrent hash chain, and names can either be local our shared (like we resolve names to phone numbers now).
#Comment Re: BT blocking DNS made: 2016-01-03 20:42:54.324944+01 by: Jack William Bell
Not sure what you mean by 'key-based identity system'. Can you elaborate?
I've given a lot of thought to the possibility of people hosting their own DNS servers, using some kind of shared naming system that can be updated from particular hosts. These DNS servers would still forward requests to the regular DNS servers, but only after looking at the shared name lists first.
The problem with that, from a social-good aspect, is that we end up with a 'balkanized' Internet where groups of people congregate around their preferred sites. Not that having an open DNS stops echo chambers from forming . . .
In any case this would do two things:
So, how is your concept different from this? How would it be implemented?