From: Hal Murray <halmurray@sonic.net>
To: nnagain@lists.bufferbloat.net
Cc: Hal Murray <halmurray@sonic.net>
Subject: Re: [NNagain] Internet Education for Non-technorati?
Date: Thu, 12 Oct 2023 12:52:44 -0700 [thread overview]
Message-ID: <20231012195244.33D5228C241@107-137-68-211.lightspeed.sntcca.sbcglobal.net> (raw)
In-Reply-To: Message from Jack Haverty via Nnagain <nnagain@lists.bufferbloat.net> of "Wed, 11 Oct 2023 10:31:03 -0700." <cabb8f4c-c397-4853-b949-31c1b2800be6@3kitty.org>
Jack Haverty said:
> A few days ago I made some comments about the idea of "educating" the
> lawyers, politicians, and other smart, but not necessarily technically
> adept, decision makers.
That process might work.
Stanford has run programs on cyber security for congressional staffers.
From 2015:
Congressional Staffers Headed to Stanford for Cybersecurity Training
https://cisac.fsi.stanford.edu/news/congressional-staffers-headed-stanford-cybe
rsecurity-training
> Today I saw a news story about a recent FCC action, to mandate "nutrition
> labels" on Internet services offered by ISPs:
Is there a chicken-egg problem in this area?
Suppose I had a nutrition-label sort of spec for a retail ISP offering. How
would I know if an installation was meeting the specs? That seems to need a
way to collect data -- either stand alone programs or patches to existing
programs like web browsers.
Would it make sense to work on those programs now? How much could we learn if
volunteers ran those programs and contributed data to a public data base? How
many volunteers would we need to get off the ground?
Could servers collect useful data? Consider Zoom, YouTube, gmail, downloads
for software updates...
--
These are my opinions. I hate spam.
next prev parent reply other threads:[~2023-10-12 19:52 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
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 [this message]
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=20231012195244.33D5228C241@107-137-68-211.lightspeed.sntcca.sbcglobal.net \
--to=halmurray@sonic.net \
--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