Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: dan <dandenson@gmail.com>
Cc: James Forster <jim@connectivitycap.com>,
	Jason Livingood <jason_livingood@comcast.com>,
	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: [Cake] Re: [LibreQoS] Re: [Starlink] Keynote: QoE/QoS - Bandwidth Is A Lie! at WISPAPALOOZA 2025 (October 16)
Date: Wed, 1 Oct 2025 23:32:57 +0200	[thread overview]
Message-ID: <CAJUtOOhiu8CVLARsiMKUkN4s87_VUr17su1Nr_4aManrwkCQAg@mail.gmail.com> (raw)
In-Reply-To: <CAA_JP8XOeSOqbZJPH=1_oWMD055vOUxHipxJMs8sbsHLu5MHCA@mail.gmail.com>

Let's say that I love it, channeling my inner Dave Taht. But there were a
couple of voices asking if I won't consider to change it a bit, to be "less
hostile" to our "bandwidth is king!" friends...and I was trying, but this
was really sticky and I'm happy that it stayed this way.


All the best,

Frank

Frantisek (Frank) Borsik


*In loving memory of Dave Täht: *1965-2025

https://libreqos.io/2025/04/01/in-loving-memory-of-dave/


https://www.linkedin.com/in/frantisekborsik

Signal, Telegram, WhatsApp: +421919416714

iMessage, mobile: +420775230885

Skype: casioa5302ca

frantisek.borsik@gmail.com


On Wed, Oct 1, 2025 at 9:25 PM dan <dandenson@gmail.com> wrote:

> I actually really like the title ;)
>
> It's that most of the time people are told they need more bandwidth to
> solve a problem, when they really need lower latency and jitter.  So the
> vast majority of the time 'more bandwidth' as a solution really is a lie.
>
> On Tue, Sep 30, 2025 at 2:47 PM Frantisek Borsik via LibreQoS <
> libreqos@lists.bufferbloat.net> wrote:
>
>> Thanks, Jim. Well, true that - but I wanted to do it either way, because
>> of
>> our dear Dave and - as a conversation starter.
>> As @Jason Livingood <jason_livingood@comcast.com> said - "Bandwidth is
>> dead. Long live latency."
>> https://pulse.internetsociety.org/blog/bandwidth-is-dead-long-live-latency
>>
>> I will do my best to get the audio/video right and to share it with you
>> all.
>>
>> PS: Sending you separate email.
>>
>> All the best,
>>
>> Frank
>>
>> Frantisek (Frank) Borsik
>>
>>
>> *In loving memory of Dave Täht: *1965-2025
>>
>> https://libreqos.io/2025/04/01/in-loving-memory-of-dave/
>>
>>
>> https://www.linkedin.com/in/frantisekborsik
>>
>> Signal, Telegram, WhatsApp: +421919416714
>>
>> iMessage, mobile: +420775230885
>>
>> Skype: casioa5302ca
>>
>> frantisek.borsik@gmail.com
>>
>>
>> On Tue, Sep 30, 2025 at 10:25 PM James Forster <jim@connectivitycap.com>
>> wrote:
>>
>> > 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
>> _______________________________________________
>> LibreQoS mailing list -- libreqos@lists.bufferbloat.net
>> To unsubscribe send an email to libreqos-leave@lists.bufferbloat.net
>>
>

      parent reply	other threads:[~2025-10-01 21:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30 20:24 James Forster
2025-09-30 20:48 ` Frantisek Borsik
     [not found]   ` <CAA_JP8XOeSOqbZJPH=1_oWMD055vOUxHipxJMs8sbsHLu5MHCA@mail.gmail.com>
2025-10-01 21:32     ` Frantisek Borsik [this message]

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=CAJUtOOhiu8CVLARsiMKUkN4s87_VUr17su1Nr_4aManrwkCQAg@mail.gmail.com \
    --to=frantisek.borsik@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --cc=dandenson@gmail.com \
    --cc=jason_livingood@comcast.com \
    --cc=jim@connectivitycap.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