Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "tapper" <j.lancett@ntlworld.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Random thought - reactions?
Date: Fri, 15 Dec 2017 16:11:24 -0500 (EST)	[thread overview]
Message-ID: <1513372284.081220590@apps.rackspace.com> (raw)
In-Reply-To: <72295b28-0574-40fc-fbe8-97881e2a362a@ntlworld.com>

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]


Thanks for this. I hadn't seen it yet.
 
On Friday, December 15, 2017 2:32pm, "tapper" <j.lancett@ntlworld.com> said:



> Motherboard & VICE Are Building a Community Internet Network
> https://motherboard.vice.com/en_us/article/j5djd7/motherboard-and-vice-are-building-a-community-internet-network-to-protect-net-neutrality
> It seems that people are all thinking the same thing, but coming up with
> different things!


I'm all for what Motherboard and VICE are contemplating. It's a great option, and may create an interesting opportunity for wireless mobile, too. But that's far more complex to fund and maintain than constructing an overlay over an already subscribable infrastructure. I wish them well, and I hope that the key idea of maximizing interoperability of all functions (including paying for upstream capacity) will be front and center in their minds. Balkanization of the subnets of the public Internet is a big worry - boundaries will destroy the Internet as effectively as content selectivity and content-based rate limiting will.

[-- Attachment #2: Type: text/html, Size: 1758 bytes --]

  reply	other threads:[~2017-12-15 21:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15 17:18 dpreed
2017-12-15 19:32 ` tapper
2017-12-15 21:11   ` dpreed [this message]
2017-12-15 22:45     ` Joel Wirāmu Pauling
2017-12-15 23:14       ` David Lang
2017-12-18  2:26         ` dpreed

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=1513372284.081220590@apps.rackspace.com \
    --to=dpreed@reed.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=j.lancett@ntlworld.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