From: David Collier-Brown <davec-b@rogers.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] I just heard a "buffering" commercial on local radio, from CDN77
Date: Fri, 3 Mar 2023 07:33:15 -0500 [thread overview]
Message-ID: <5976c14b-f0b8-c28a-1899-2929ebe99d88@rogers.com> (raw)
In-Reply-To: <5976c14b-f0b8-c28a-1899-2929ebe99d88.ref@rogers.com>
They talked about buffering in the conferencing sense, and did some
typical distortions of the announcer's voice to illustrate it. Then they
went on talk about latency. This was on the "low cost" local radio in
Toronto, Ontario, 680 News, where I don't usually hear ads for content
delivery networks.
Their site, https://www.cdn77.com, talks about video a lot, and says
they use open source technologies.
--dave
parent reply other threads:[~2023-03-03 12:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5976c14b-f0b8-c28a-1899-2929ebe99d88.ref@rogers.com>]
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=5976c14b-f0b8-c28a-1899-2929ebe99d88@rogers.com \
--to=davec-b@rogers.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