From: Jack Haverty <jack@3kitty.org>
To: nnagain@lists.bufferbloat.net
Subject: Re: [NNagain] NTIA: national spectrum strategy
Date: Thu, 14 Mar 2024 09:47:26 -0700 [thread overview]
Message-ID: <38bd1996-e38c-4a7f-bcad-cc8888d2ee26@3kitty.org> (raw)
In-Reply-To: <CAA93jw7iP6z1f48AVk9bdiUK3CwikrGpBSLTP7OAmruGq5HkFA@mail.gmail.com>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 1573 bytes --]
On 3/14/24 05:16, Dave Taht via Nnagain wrote:
> In other news, the House voted to ban tiktok yesterday. I do not
> understand how simultaneously,
> we can accept security cameras (largely built around Linux and
> violating the GPL) also built elsewhere,
> or IoT, or home routers rife with CVEs...
My naive explanation---
Policy-makers seem to focus on how technology is used. To
policy-makers, "The Internet" is a poorly understood technology with
many possible uses. Whoever and wherever "we" are, our policy-makers
create laws and regulations to constrain those uses. For every "we"
there is likely a number of "them".
Security cameras allow "them" to spy on us. That's generally considered
bad, but apparently not as bad as Social Media, which allows "them" to
control us, by flooding us with misinformation, disinformation, and what
we curiously call "spam". When advertisers or even our government does
it, it's OK. When "they" do it, it's bad.
Spying of course also allows "us" to spy on "us" as well. That's
apparently not as bad as allowing "them" to control "us", especially if
we can create policy that retains the ability for "us" to exert control
on "us" while preventing "them" from communicating with "us". Those
techies simply have to figure out how to make it happen.
I personally do not understand how "network neutrality" relates to other
policies. Perhaps it conflicts with other policies such as one that
outlaws communications based on ownership of a company?
Jack Haverty
[-- Attachment #1.1.1.2: Type: text/html, Size: 2017 bytes --]
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2469 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]
prev parent reply other threads:[~2024-03-14 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 12:16 Dave Taht
2024-03-14 16:47 ` Jack Haverty [this message]
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=38bd1996-e38c-4a7f-bcad-cc8888d2ee26@3kitty.org \
--to=jack@3kitty.org \
--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