Flutterby™! : BT blocking DNS

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

BT blocking DNS

2016-01-03 13:37:58.824359+00 by Dan Lyke 2 comments

RT Hash Tag ‏@stwange:

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 ascending chronological order (reverse):

#Comment Re: BT blocking DNS made: 2016-01-03 19:42:54.324944+00 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:

  1. Break the monopoly on domain names and make it possible to have any domain you like (inside your shared name group)
  2. Allow for a new kind of ShadowNet (not quite dark enough to be a DarkNet) of aligned users, similar to Gibson's Walled Cities

So, how is your concept different from this? How would it be implemented?

#Comment Re: BT blocking DNS made: 2016-01-04 00:17:13.937904+00 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).

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)

Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.