From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: Jim Forster <jrforster@mac.com>, Sina Khanifar <sina@waveform.com>
Cc: Dave Taht <dave.taht@gmail.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
Eugene Y Chang <eugene.chang@ieee.org>,
Colin_Higbie <CHigbie1@higbie.name>,
libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] [Starlink] It’s the Latency, FCC
Date: Wed, 1 May 2024 09:23:35 +0200 [thread overview]
Message-ID: <CAJUtOOjyC65_dRiRr68SS5us++SdmqbF2o3_ocdSSQzGpeDqMg@mail.gmail.com> (raw)
In-Reply-To: <177B7A46-A7F3-4F70-B975-30323E015F7A@mac.com>
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
Thanks for the comments, Jim. I'm adding Sina
<https://www.linkedin.com/in/sinakhanifar/>, CEO at Waveform, to the
conversation. Maybe he will have some answers...
All the best,
Frank
Frantisek (Frank) Borsik
https://www.linkedin.com/in/frantisekborsik
Signal, Telegram, WhatsApp: +421919416714
iMessage, mobile: +420775230885
Skype: casioa5302ca
frantisek.borsik@gmail.com
On Wed, May 1, 2024 at 5:28 AM Jim Forster <jrforster@mac.com> wrote:
> I kind of like Waveform BB test, but a couple issues:
>
> * From some places in India? and Southern Africa, the closest server they
> use is far away. Consequently the base latency is much higher than most
> content, which these days comes from CDNs.
>
> * I don’t mind the ads, but I did get a comment from someone I referred to
> it, that the site was ‘mostly about trying to sell some gear’. WF could
> alleviate that with an explanation of who they are, etc. Maybe it’s there
> & I missed it?
>
> — Jim
>
> On Apr 30, 2024, at 6:02 PM, Dave Taht via LibreQoS <
> libreqos@lists.bufferbloat.net> wrote:
>
> he also had a waveform result as best as I recall. Simpler than running
> flent.
>
> On Tue, Apr 30, 2024 at 2:23 PM Frantisek Borsik <
> frantisek.borsik@gmail.com> wrote:
>
>> Here are the tests Dave was talking about:
>>
>> [image: image.png]
>>
>
>
[-- Attachment #2: Type: text/html, Size: 4203 bytes --]
next prev parent reply other threads:[~2024-05-01 7:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2779.1714503924.1074.starlink@lists.bufferbloat.net>
[not found] ` <MN2PR16MB339176B8EE09E7A4D7F1EECCF11A2@MN2PR16MB3391.namprd16.prod.outlook.com>
[not found] ` <1A972680-ECA5-42CA-BE8B-6BBD46FF5E74@ieee.org>
2024-04-30 21:07 ` Dave Taht
2024-04-30 21:22 ` Frantisek Borsik
2024-04-30 22:02 ` Dave Taht
2024-04-30 22:03 ` Dave Taht
2024-05-01 3:27 ` Jim Forster
2024-05-01 7:23 ` Frantisek Borsik [this message]
2024-04-30 21:22 ` Eugene Y Chang
2024-04-30 21:35 ` Frantisek Borsik
2024-04-30 21:53 ` Eugene Y Chang
2024-05-01 0:54 ` David Lang
2024-05-01 7:27 ` Frantisek Borsik
2024-05-01 7:32 ` Brian Munyao Longwe
2024-05-01 13:25 ` Jim Forster
2024-05-01 13:48 ` Brian Munyao Longwe
2024-05-01 13:57 ` Dave Taht
2024-05-01 8:48 ` [LibreQoS] [Starlink] musings on disruption and competition [was] " Sebastian Moeller
2024-05-01 21:24 ` Eugene Y Chang
2024-05-01 19:26 ` [LibreQoS] [Starlink] " Eugene Y Chang
2024-05-14 16:05 ` 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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJUtOOjyC65_dRiRr68SS5us++SdmqbF2o3_ocdSSQzGpeDqMg@mail.gmail.com \
--to=frantisek.borsik@gmail.com \
--cc=CHigbie1@higbie.name \
--cc=dave.taht@gmail.com \
--cc=eugene.chang@ieee.org \
--cc=jrforster@mac.com \
--cc=libreqos@lists.bufferbloat.net \
--cc=sina@waveform.com \
--cc=starlink@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