From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] bufferbloat still misunderstood & ignored
Date: Wed, 28 Mar 2018 17:53:01 +0200 [thread overview]
Message-ID: <87k1twgpsy.fsf@toke.dk> (raw)
In-Reply-To: <mailman.172.1522252010.3573.cake@lists.bufferbloat.net>
Kevin Darbyshire-Bryant via Cake <cake@lists.bufferbloat.net> writes:
> From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
> Subject: bufferbloat still misunderstood & ignored
> To: Cake List <cake@lists.bufferbloat.net>
> Date: Wed, 28 Mar 2018 15:46:47 +0000
>
> http://forums.thinkbroadband.com/talktalk/t/4587923-sensible-discussion-with-talktalk-about-bufferbloat.html
>
> The thing that bothers me more than anything….. the first reply comes
> from a staff member of ‘thinkbroadband’.
"Solution is two get two lines, so if a big download is using up one
they can do latency sensitive stuff on the other."
Lovely; an ISP that found a way to monetise bufferbloat... :/
-Toke
next parent reply other threads:[~2018-03-28 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.172.1522252010.3573.cake@lists.bufferbloat.net>
2018-03-28 15:53 ` Toke Høiland-Jørgensen [this message]
2018-03-28 19:32 ` Dave Taht
2018-03-29 0:04 ` Jonathan Morton
2018-03-29 0:26 ` Dave Taht
2018-03-29 0:53 ` Jonathan Morton
2018-03-29 1:07 ` Dave Taht
2018-03-29 9:07 ` Andy Furniss
2018-03-30 8:05 ` Pete Heist
2018-03-30 15:29 ` Jonathan Morton
2018-03-31 10:55 ` Toke Høiland-Jørgensen
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k1twgpsy.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cake@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.uk \
/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