Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat]  Dave Täht quoted in the ACLU blog
Date: Tue, 24 Jun 2014 13:08:23 -0700	[thread overview]
Message-ID: <CAA93jw4mvCad6SbGcUKB_XbrXUjSivuWL5o15coMKKT9JeYiTw@mail.gmail.com> (raw)
In-Reply-To: <53A9D92B.7010603@hp.com>

On Tue, Jun 24, 2014 at 1:01 PM, Rick Jones <rick.jones2@hp.com> wrote:
> On 06/24/2014 12:45 PM, Dave Taht wrote:
>>
>> In an age where you have, say, gbit fiber to your business, it makes quite
>> a lot of sense from a security and maintenence perspective
>> to be hosting your own data and servers on your own darn premise, not
>> elsewhere.
>
>
> Perhaps, but where does having gigabit fibre to a business imply the
> business has the space, power, and cooling to host all the servers it might
> need/wish to have?

I didn't say there aren't compelling reasons also to co-locate in a data center,
but for many uses today, being able to host a basic website, some service,
email, etc at your own location, is perfectly doable, and possibly
preferable to co-locating places where things like this are happening:

http://fish2.com/ipmi/

or this:

http://en.wikipedia.org/wiki/Room_641A

>
>
>> I am glad gfiber exists to put a scare into certain monopolists, but
>> even then I'd be tons happier if municipalities treated basic wired
>> connectivity as we do roads. One of the great "Secrets" of silicon
>> valley is it got wired for fiber early, through the vision and
>> foresight of people like Brian Reid and everybody got easy access.
>
>
> That must be a really well-kept secret as I am aware of no fibre running to
> my house in Sunnyvale :)

The fiber loop around palo alto has quite the inspiring story behind
it. Maybe brian will
write it down one day, or already has.

http://en.wikipedia.org/wiki/Brian_Reid_(computer_scientist)


> rick jones
> speaking for myself alone



-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

  reply	other threads:[~2014-06-24 20:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 18:51 [Cerowrt-devel] " Rich Brown
2014-06-24 19:29 ` Dave Taht
2014-06-24 19:36   ` [Cerowrt-devel] [Bloat] " Steinar H. Gunderson
2014-06-24 19:45   ` [Cerowrt-devel] " Dave Taht
2014-06-24 20:01     ` [Cerowrt-devel] [Bloat] " Rick Jones
2014-06-24 20:08       ` Dave Taht [this message]
2014-06-24 21:48         ` Dave Taht
2014-06-24 21:38       ` Michael Richardson
2014-06-28  1:10         ` David Lang
2014-06-28  4:06           ` David P. Reed
2014-06-28  4:28             ` Dave Taht
2014-06-28 16:16               ` [Cerowrt-devel] Low Power UPSes (Was: Re: [Bloat] Dave Täht quoted in the ACLU blog) Joseph Swick
2014-06-30  3:45                 ` David Lang
2014-06-30 12:00                   ` dpreed
2014-06-28 16:49               ` [Cerowrt-devel] [Bloat] Dave Täht quoted in the ACLU blog Theodore Ts'o

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw4mvCad6SbGcUKB_XbrXUjSivuWL5o15coMKKT9JeYiTw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=rick.jones2@hp.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