This DNS over HTTP thing

Thu Oct 3 04:34:18 UTC 2019

On Wed, Oct 2, 2019 at 9:13 AM Livingood, Jason <Jason_Livingood at comcast.com>
wrote:

> The challenge of course is that in the absence of a silver bullet
> solution, that people working to combat all forms of child exploitation are
> simultaneously trying several things, ranging from going to the source as
> you suggest and arresting people, to trying to interrupt the online tools
> that they may use or that might fund/support them, etc.  So they don’t
> approach it as a binary choice between trying these ecosystem measures vs
> going to the source – they are working all the levers.
>

Yes, obviously they are trying multiple levers--but who gets to draw the
line, where are they going to draw it, and why do they get to decide for me?
What prevents an absurd 'solution' like "We can not only stop child
molestation, but rape in general if we just castrate everyone" from being
one of the levers, but intentionally breaking tools like DNS is acceptible?

People who are determined enough will find ways to circumvent the
system--something along the lines of "the internet treats policy blocks as
damage and routes around it".

How many times has The Pirate Bay been blocked only to pop up under a
similar domain name hosted out of a new country?

> It is unfortunately a very difficult problem. FWIW, a recent NYT article
> on this was interesting – see
> https://www.nytimes.com/interactive/2019/09/28/us/child-sex-abuse.html
> Headline is “The Internet Is Overrun With Images of Child Sexual Abuse.
> What Went Wrong? Online predators create and share the illegal material,
> which is increasingly cloaked by technology. Tech companies, the government
> and the authorities are no match.”
>

I completely agree--it's a difficult problem, and I wish I had a solution.
That article turns my stomach.  I have kids, and I worry about it every day.

-A
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20191002/6c7b41b6/attachment.html>