From: James Forster <jim@connectivitycap.com>
To: Frantisek Borsik <frantisek.borsik@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>,
codel@lists.bufferbloat.net,
Jeremy Austin via Rpm <rpm@lists.bufferbloat.net>,
libreqos <libreqos@lists.bufferbloat.net>
Subject: [Codel] Re: [LibreQoS] Re: [Starlink] Keynote: QoE/QoS - Bandwidth Is A Lie! at WISPAPALOOZA 2025 (October 16)
Date: Tue, 30 Sep 2025 14:24:49 -0600 [thread overview]
Message-ID: <9390D9DA-3C77-429F-A41D-E0FECD52FF06@connectivitycap.com> (raw)
Wow, that’s fantastic, Frantisek! Great work making this happen.
These sort of titles aren’t my favorite. I think I understand the sentiment but find the issues more nuanced than that. :-)
If you can get clear audio, not much quality is needed for panels and talking beads. Best would be a feed right into an iPhone/android.
Jim
next reply other threads:[~2025-09-30 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 20:24 James Forster [this message]
2025-09-30 20:48 ` Frantisek Borsik
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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9390D9DA-3C77-429F-A41D-E0FECD52FF06@connectivitycap.com \
--to=jim@connectivitycap.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=frantisek.borsik@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
--cc=rpm@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