From: Dave Taht <dave.taht@gmail.com>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] viability of the data center in the internet of the future
Date: Tue, 1 Jul 2014 02:06:12 -0700 [thread overview]
Message-ID: <CAA93jw5gFa2DijQTaf8qp5CwoUFkN4+YtSW5kOtN=p8p-eGkyQ@mail.gmail.com> (raw)
In-Reply-To: <20140701084001.GA27192@sesse.net>
On Tue, Jul 1, 2014 at 1:40 AM, Steinar H. Gunderson
<sgunderson@bigfoot.com> wrote:
> On Tue, Jul 01, 2014 at 01:37:23AM -0700, Dave Taht wrote:
>> I
>> liked web proxies, they were often capable of reducing traffic by 10s
>> of percentage points, reduce latency enormously for lossy or satellite
>> links, and were frequently used by large organizations (like schools)
>> to manage content.
>
> By “manage” I assume you mean “censor”, right?
I do (sometimes) strive to be politically correct.
Have you done a google search with "safesearch" off lately? Try it for
a day. At work.
Frankly safesearch and adblockplus are the only two things keeping the
web tolerable for me, and I used to use privoxy and various other
services in conjunction with squid to keep javacript out, and banner
ads under control for all users on sites located far away from the
"normal" internet with limited bandwidth.
Places like, um, New Zealand.
So, I mostly meant 'manage'. I am certainly well aware that web
proxies are frequently used to enforce various forms of censorship.
Quite a few are transparent proxies, which I think is wrong. Having an
explicit proxy assignment (as supported in the protocol), makes for
effective use of split tcp, and you can turn it off if you don't like
it.
What I wish to 'censor' on my own networks is offensive content, which
mostly includes intrusive advertising! - the savings in bandwidth and
on load time are enormous on killing that alone. Certainly I'd like a
world where users had that blocked by default on clients, but we'd
have to get bitcoin deployed first...
I can't defend 'censorship' as in blocking access to certain words,
and I do worry about the fact we've outsourced even as much as
safesearch to the Ministry of Information.
But I can certainly defend 'the local network owner''s ability to
manage their bandwidth more appropriately, and regret that that world
is going away. polipo, for example, generally does a great job of
speeding up web access over wifi - eliminating the dns lookups and
utilizing http 1.1 pipeline and having a short local rtt can make a
real difference.
>
> (I find it questionable that we are teaching our children from the very
> beginning of their education that it is OK to censor the Internet arbitrarily.)
Got any kids?
> /* Steinar */
> --
> Homepage: http://www.sesse.net/
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Dave Täht
NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
next prev parent reply other threads:[~2014-07-01 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 4:58 Dave Taht
2014-06-28 12:31 ` David P. Reed
2014-06-29 0:50 ` Fred Baker (fred)
2014-07-01 8:37 ` Dave Taht
2014-07-01 8:40 ` Steinar H. Gunderson
2014-07-01 9:06 ` Dave Taht [this message]
2014-07-01 9:27 ` Steinar H. Gunderson
2014-07-01 16:38 ` Fred Baker (fred)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw5gFa2DijQTaf8qp5CwoUFkN4+YtSW5kOtN=p8p-eGkyQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=sgunderson@bigfoot.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox