revolutions per minute - a new metric for measuring responsiveness
 help / color / mirror / Atom feed
From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: Dave Taht <dave.taht@gmail.com>,
	Jeremy Austin <jeremy@aterlo.com>,
	 Jeremy Austin via Rpm <rpm@lists.bufferbloat.net>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Rpm] [Starlink] It's still the latency, starlink!
Date: Sun, 17 Jul 2022 00:31:26 -0700	[thread overview]
Message-ID: <CAJUtOOh-C6hAZo+=y9AyP6TyNhD4AdWHcpiQ6sEXpff0EzaXtw@mail.gmail.com> (raw)
In-Reply-To: <CACw=56+Jzmew=-ym0soVOiW4uS6RMhKhQ6_yd_Ag3ES3r6S5Qw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2260 bytes --]

But when I see all those people from the saying that this new FCC
shenanigans are “good for the people”…I wanna die.

Say what You want about Ajit Pai, but he was not that demented like this
Biden’s lady.


*Sent on the move.*

*F.*

*https://www.linkedin.com/in/frantisekborsik
<https://www.linkedin.com/in/frantisekborsik>*

*+421919416714* <%2B421919416714> (Signal, Telegram, WhatsApp)
*+420775230885 <http://+420775230885/> *(iMessage)

*Skype: *casioa5302ca


On 17 July 2022 at 8:17:04 AM, Jeremy Austin via Rpm (
rpm@lists.bufferbloat.net) wrote:

> We will keep preaching it.
>
> This also feeds into the frustration around the manipulation of the US
> (FCC) federal definition of broadband. I care little about a 1000/500
> connection with 2000 ms of latency under load; I’d much rather have a
> 100/20 that never exceeds 100 ms!
>
> <sigh>
>
> Jeremy
>
> On Sat, Jul 16, 2022 at 8:23 PM Dave Taht via Starlink <
> starlink@lists.bufferbloat.net> wrote:
>
>> there's three "lovely" new speedtest results here, showing nearly 5sec
>> of uplink latency under load.
>>
>> If only more folk would realize it's not the bandwidth, but the working
>> latency.
>>
>>
>> https://www.pcmag.com/news/starlinks-massive-growth-results-in-congestion-slow-speeds-for-some-users
>>
>> --
>> FQ World Domination pending:
>> https://blog.cerowrt.org/post/state_of_fq_codel/
>> Dave Täht CEO, TekLibre, LLC
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
>>
> --
> [image: Company logo]
> *Jeremy Austin*
> Sr. Product Manager
> *Preseem | Aterlo Networks*
> Book a call: https://app.hubspot.com/meetings/jeremy548
> 1-833-773-7336 ext 718 *|* 1-907-803-5422
> jeremy@aterlo.com
> www.preseem.com
>  [image: facebook icon] [image: twitter icon] [image: linkedin icon] [image:
> youtube icon]
> [image: Ask us about our new features today!]
> <https://preseem.com/2021/10/news-preseem-wins-wispa-service-of-the-year-award-2021/>
> _______________________________________________
> Rpm mailing list
> Rpm@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/rpm
>

[-- Attachment #2: Type: text/html, Size: 9471 bytes --]

  reply	other threads:[~2022-07-17  7:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-17  4:23 [Rpm] " Dave Taht
2022-07-17  6:17 ` [Rpm] [Starlink] " Jeremy Austin
2022-07-17  7:31   ` Frantisek Borsik [this message]
2022-07-18 12:54     ` Mike Conlow

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/rpm.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJUtOOh-C6hAZo+=y9AyP6TyNhD4AdWHcpiQ6sEXpff0EzaXtw@mail.gmail.com' \
    --to=frantisek.borsik@gmail.com \
    --cc=dave.taht@gmail.com \
    --cc=jeremy@aterlo.com \
    --cc=rpm@lists.bufferbloat.net \
    --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