revolutions per minute - a new metric for measuring responsiveness
 help / color / mirror / Atom feed
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: Rpm <rpm@lists.bufferbloat.net>,
	libreqos <libreqos@lists.bufferbloat.net>,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Rpm] [Bloat] [Starlink] [LibreQoS] net neutrality back in the news
Date: Fri, 29 Sep 2023 15:19:58 +0000	[thread overview]
Message-ID: <D87F70A3-76D7-4D7B-B22B-6911411A7BB9@cable.comcast.com> (raw)

On 9/29/23, 09:29, "Rich Brown" <richb.hanover@gmail.com <mailto:richb.hanover@gmail.com>> wrote:
> Thank you Jonathan for this clear description of the issues and their history. I wonder if there's a fourth one - privacy. 
> Rosenworcel's talk also points out that ISPs might want to monetize our traffic patterns and location data. (This is less of an issue in the EU, but the US remains a Wild West in this regard.) 

That reference is to mobile networks in the US - but the US-EU contrast you make is a good one! The EU IMO does privacy right - it is not sector-specific regulation but is general privacy protecting law that protects user data no matter the entity collecting/aggregating/sharing. In the US we seem to pursue sector-specific privacy law - like specific to credit cards. What we end up with is a real mess and I would love to see comprehensive national data privacy legislation - but our legislative body can’t even agree right now to keep our government funded past this coming Sunday. ;-)

IANAL but it seems like if the US wanted to provide comprehensive location data privacy then it would have a uniform law that applied not just to a MNO with towers that can locate a handset, but also what the apps loaded on that handset with access to GPS can do with the data as well - and any other party that might be able to collect data.

JL 



             reply	other threads:[~2023-09-29 15:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 15:19 Livingood, Jason [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-29 13:16 Livingood, Jason
2023-09-27 18:21 [Rpm] " Dave Taht
2023-09-28  6:25 ` Sebastian Moeller
2023-09-28 16:38   ` Dave Taht
2023-09-28 19:31     ` Sebastian Moeller
2023-09-28 19:39       ` Dave Taht
2023-09-28 20:08         ` [Rpm] [LibreQoS] " dan
2023-09-28 20:48           ` [Rpm] [Starlink] " Livingood, Jason
2023-09-28 22:19             ` [Rpm] [Bloat] " David Lang
2023-09-29  4:54               ` Jonathan Morton
2023-09-29 12:28                 ` Rich Brown
2023-09-29 16:15                   ` dan
2023-09-30 12:00                     ` Frantisek Borsik
2023-09-30 12:19                       ` Sebastian Moeller
     [not found]                         ` <CAMo6_mstw1tKjZfonQ=3Zc5TNqrffkEiUEXzCxLUf85o3kJs9A@mail.gmail.com>
2023-09-30 15:20                           ` Sebastian Moeller
2023-10-04 22:19                           ` Michael Richardson
2023-09-29  6:24               ` Sebastian Moeller

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

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

  git send-email \
    --in-reply-to=D87F70A3-76D7-4D7B-B22B-6911411A7BB9@cable.comcast.com \
    --to=jason_livingood@comcast.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=libreqos@lists.bufferbloat.net \
    --cc=richb.hanover@gmail.com \
    --cc=rpm@lists.bufferbloat.net \
    --cc=starlink@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