General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: David Collier-Brown <davecb.42@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] slashdotted
Date: Wed, 8 Dec 2021 12:05:05 -0500	[thread overview]
Message-ID: <7613f474-d913-9a67-f405-09732852765e@rogers.com> (raw)
In-Reply-To: <CAA93jw4_J14T01X2mDY4dZ0jVG3zX2L8g4yGU1Nw9DXDg5M1Bw@mail.gmail.com>

Slashdot has a rating system, voted upon by engaged authors. The real 
trash is voted down to 0 or -1, and the dumb stuff floats around 1 or 2.

My CTO reads at level 4 or 5 (;-))

--dave

On 12/7/21 09:40, Dave Taht wrote:
> slashdot is a language understood by mgmt?
>
> One poster went and checked his service (got an A on a bufferbloat
> report and gave a kudos), another asked a good question about applying
> sqm on top of that, the vast majority found something else to complain
> about, and several (one especially) put the whole bufferbloat problem
> down as a conspiracy by the ISPs to gauge and throttle users, even
> when I presented the best data we had (on how much we improved wifi)
> about it having been a theory failure.
>
> Well, maybe it is a language understood by mgmt. You have to really
> sort through this sort of chaff to find the wheat, This new tool holds
> some promise: https://github.com/sylvia-ou/netcheck/issues/1
>
> I hope those that deploy this stuff at scale look at macro-metrics,
> like reduced support calls, more than user feedback.
>
> The reddit conversation fared better:
> https://www.reddit.com/r/HomeNetworking/comments/r7cfvg/comcast_delivers_90_working_latency_reductions_by/
> as did linked in.
>
> As it is, I put in a christmas wish for santa for a flame retardant suit.
>
> On Mon, Dec 6, 2021 at 10:44 PM Taraldsen Erik
> <erik.taraldsen@telenor.no> wrote:
>> Thanks for that link! Written in a language an by a source (Comcast) which my company can relate to.  Posted it to our internal "facebook" main page.  Hope some in the management actually picks up on this now.
>>
>>
>> -Erik
>>
>> ________________________________
>> Fra: Bloat <bloat-bounces@lists.bufferbloat.net> på vegne av Dave Taht <dave.taht@gmail.com>
>> Sendt: søndag 5. desember 2021 19.12.52
>> Til: bloat
>> Emne: [Bloat] slashdotted
>>
>> I went to bed early yesterday, and woke up to slashdot.
>>
>> https://tech.slashdot.org/story/21/12/05/0225227/comcast-reduced-working-latency-by-90-with-aqm-is-this-the-future
>>
>> --
>> I tried to build a better future, a few times:
>> https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
>>
>> Dave Täht CEO, TekLibre, LLC
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>
>
-- 
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net           |                      -- Mark Twain


      reply	other threads:[~2021-12-08 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-05 18:12 Dave Taht
2021-12-07  6:43 ` Taraldsen Erik
2021-12-07 14:40   ` Dave Taht
2021-12-08 17:05     ` David Collier-Brown [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/bloat.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=7613f474-d913-9a67-f405-09732852765e@rogers.com \
    --to=davecb.42@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=davecb@spamcop.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