From: Kenneth Porter <shiva@sewingwitch.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Meeting software continues to ignore the bloat issue
Date: Wed, 10 Mar 2021 20:52:49 -0800 [thread overview]
Message-ID: <61D93E89625B74F2A5ED5CFE@[172.27.17.193]> (raw)
No mention of bloat here!
<https://www.zdnet.com/article/microsoft-tackles-the-bandwidth-problem-for-remote-workers-using-teams/>
Perhaps we can nudge this author to learn more?
next reply other threads:[~2021-03-11 4:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 4:52 Kenneth Porter [this message]
2021-03-11 15:18 ` Jonathan Foulkes
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='61D93E89625B74F2A5ED5CFE@[172.27.17.193]' \
--to=shiva@sewingwitch.com \
--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