Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: "David Bray, PhD via Nnagain" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] Internet Education for Non-technorati?
Date: Wed, 11 Oct 2023 12:23:25 -0700 (PDT)	[thread overview]
Message-ID: <ponn8079-832r-7po3-0sr0-s6408022prp0@ynat.uz> (raw)
In-Reply-To: <CA+aeVP8yWO=UVQ90Ueaz9L7ybVeuU0XggecF6jGz=_fu7-XRxQ@mail.gmail.com>

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

On Wed, 11 Oct 2023, David Bray, PhD via Nnagain wrote:

> There's also the concern about how do startups roll-out such a label for
> their tech in the early iteration phase? How do they afford to do the extra
> work for the label vs. a big company (does this become a regulatory moat?)
>
> And let's say we have these labels. Will only consumers with the money to
> purchase the more expensive equipment that has more privacy and security
> features buy that one - leaving those who cannot afford privacy and
> security bad alternatives?

As far as security goes, I would argue that the easy answer is to ship a current 
version of openwrt instead of a forked, ancient version, and get their changes 
submitted upstream (or at least maintained against upstream). It's a different 
paradigm than they are used to, and right now the suppliers tend to also work 
with ancient versions of openwrt, but in all the companies that I have worked 
at, it's proven to be less ongoing work (and far less risk) to keep up with 
current versions than it is to stick with old versions and then do periodic 'big 
jump' upgrades.

it's like car maintinance, it seems easier to ignore your tires, brakes, and oil 
changes, but the minimal cost of maintaining those systems pays off in a big way 
over time

David Lang

[-- Attachment #2: Type: text/plain, Size: 146 bytes --]

_______________________________________________
Nnagain mailing list
Nnagain@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/nnagain

  parent reply	other threads:[~2023-10-11 19:23 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11 17:31 Jack Haverty
2023-10-11 17:38 ` David Bray, PhD
2023-10-11 18:06   ` Dave Taht
2023-10-11 18:18     ` rjmcmahon
2023-10-11 18:35       ` Dick Roy
2023-10-11 18:49         ` rjmcmahon
2023-10-11 20:42           ` Dick Roy
2023-10-11 20:59           ` Sebastian Moeller
2023-10-11 18:19     ` David Bray, PhD
2023-10-11 18:23       ` David Bray, PhD
2023-10-11 20:49     ` Sebastian Moeller
2023-10-11 19:23   ` David Lang [this message]
2023-10-11 20:06     ` rjmcmahon
2023-10-11 22:58       ` David Lang
2023-10-12 15:55         ` Robert McMahon
2023-10-12 16:04           ` rjmcmahon
2023-10-12 16:49             ` David Lang
2023-10-12 17:30             ` Dave Taht
2023-10-12 18:17               ` rjmcmahon
2023-10-12 20:14                 ` David Lang
2023-10-13  4:31                   ` rjmcmahon
2023-10-13  8:34                     ` David Lang
2023-10-13 15:55                       ` Robert McMahon
2023-10-13  8:38                     ` Sebastian Moeller
2023-10-13 17:35                       ` rjmcmahon
2023-10-13  6:35           ` Sebastian Moeller
2023-10-13 17:20             ` rjmcmahon
2023-10-14 10:41               ` Sebastian Moeller
2023-10-14 19:59                 ` rjmcmahon
2023-10-19  0:40                   ` David Lang
2023-10-19  2:02                     ` Robert McMahon
2023-10-19  2:05                       ` David Lang
2023-10-19  2:12                         ` Robert McMahon
2023-10-19  2:25                           ` David Lang
2023-10-19  3:13                             ` rjmcmahon
2023-10-11 20:42 ` Sebastian Moeller
2023-10-12 19:52 ` Hal Murray
2023-10-13 18:47   ` Jack Haverty
2023-10-13 20:50     ` rjmcmahon

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

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

  git send-email \
    --in-reply-to=ponn8079-832r-7po3-0sr0-s6408022prp0@ynat.uz \
    --to=david@lang.hm \
    --cc=nnagain@lists.bufferbloat.net \
    /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