From: dan <dandenson@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Rpm <rpm@lists.bufferbloat.net>, libreqos@lists.bufferbloat.net
Subject: Re: [Rpm] [LibreQoS] benton's consumer broadband label prototype
Date: Wed, 26 Oct 2022 09:09:50 -0600 [thread overview]
Message-ID: <CAA_JP8WeDT9sAgm2PByn_eePFk-mJxxK6m5eR9Y6WV7pb7nCGw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6rbuMj0EVHokfgW80M5vj_UZeiVeO+0xya0OX3Tjed1A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]
Complete fail on a marketing perspective though, this would have to be
legislated and then handled by a third party. No one is going to put out
essentially a warning label that says 'poor' or 'marginal' in any category
for a product they sell. I wouldn't, and we have LTE services to get to
people with no other option and they are quite happy, it would be
detrimental to hand them a sheet that says that the service is actually
'poor'.
Also, my trust in the government to decide what's good or bad...
laughable. You'd get things like on the example page. 903.5Mbps Median
download speed, 811.8 Median upload speed, gaming rating poor and video
conferencing marginal, on Fios service. I know that's an example, but it's
so spot on what the government might do...
As an operator, I will not implement this unless forced to and then I'll
support lobby efforts to get it removed.
On Tue, Oct 25, 2022 at 8:30 PM Dave Taht via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:
> is actually... not bad.
>
> https://www.benton.org/blog/consumer-driven-broadband-label-design
>
> --
> This song goes out to all the folk that thought Stadia would work:
>
> https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>
[-- Attachment #2: Type: text/html, Size: 2295 bytes --]
next prev parent reply other threads:[~2022-10-26 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 2:30 [Rpm] " Dave Taht
2022-10-26 15:09 ` dan [this message]
2022-10-26 15:27 ` [Rpm] [LibreQoS] " Sebastian Moeller
2022-10-26 15:42 ` dan
2022-10-26 15:57 ` Dave Taht
2022-10-26 20:08 ` Sebastian Moeller
2022-10-26 21:50 ` dan
2022-10-26 16:10 ` Jonathan Morton
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=CAA_JP8WeDT9sAgm2PByn_eePFk-mJxxK6m5eR9Y6WV7pb7nCGw@mail.gmail.com \
--to=dandenson@gmail.com \
--cc=dave.taht@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
--cc=rpm@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