General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] new bufferbloat video from Battle(non)sense
Date: Mon, 29 Jul 2019 07:47:59 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1907290745370.19225@uplift.swm.pp.se> (raw)

[-- Attachment #1: Type: text/plain, Size: 441 bytes --]


Hi,

Battle(non)sense has released a new video on bufferbloat.

https://www.youtube.com/watch?v=LjJW_s5gQ9Y

At the end of the video he mentions that Dave Taht and Sebastian Möller 
had helped him with the video. Great! I really like that these kinds of 
videos are done to help a wider audience understand the problem with 
bufferbloat to create market demand for the solutions available.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

             reply	other threads:[~2019-07-29  5:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-29  5:47 Mikael Abrahamsson [this message]
2019-07-29 15:18 ` Dave Taht
2019-07-29 15:31   ` Dave Taht

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=alpine.DEB.2.20.1907290745370.19225@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=bloat@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