From: Bruce Perens <bruce@perens.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Eugene Y Chang <eugene.chang@ieee.org>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] It's still the starlink latency...
Date: Mon, 26 Sep 2022 13:32:18 -0700 [thread overview]
Message-ID: <CAK2MWOtAZWq8fPk21RcEgt4pUbHV4MZzSufhniafwd3wquraJA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5tsG60vZOMRScFgWudWhvKUn=r8cn9tiQZG6qS0zmr5g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Yes, as an MVNO user, I get thrown off of T-Mobile when the non-MVNO users
want all of the system bandwidth. So we can moderate the statement. But we
definitely observe a problem *at our level.*
Thanks
* Bruce*
On Mon, Sep 26, 2022 at 1:28 PM Dave Taht <dave.taht@gmail.com> wrote:
> I appreciate you grabbing this bull by the horns bruce!
>
> However, it is extremely feasible that for their business class,
> military, and/or ukraine based services they's actually implemented at
> least some of the improvements we've been recommending to them for
> 3 years now. It would be smart if they had and weren't talking about it!
>
> Much like how (at last I heard) verizon puts the at home users in the
> lowest 5g service class, if starlink
> was trying to shed the first bout of residential users and retain
> those that don't care at a high price with less service, they could
> not be more effective at that by their baseline services degrading.
>
--
Bruce Perens K6BP
[-- Attachment #2: Type: text/html, Size: 1527 bytes --]
next prev parent reply other threads:[~2022-09-26 20:32 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 18:35 Dave Taht
2022-09-22 11:41 ` Andrew Crane
2022-09-22 12:01 ` Mike Puchol
2022-09-22 13:46 ` warren ponder
2022-09-22 15:07 ` Dave Taht
2022-09-22 15:26 ` Dave Taht
2022-09-26 15:20 ` Livingood, Jason
2022-09-26 15:29 ` Dave Taht
2022-09-26 15:57 ` Sebastian Moeller
2022-09-26 16:21 ` Dave Taht
2022-09-26 16:32 ` Bruce Perens
2022-09-26 19:59 ` Eugene Chang
2022-09-26 20:04 ` Bruce Perens
2022-09-26 20:14 ` Ben Greear
2022-09-26 20:24 ` Bruce Perens
2022-09-26 20:32 ` Dave Taht
2022-09-26 20:36 ` Bruce Perens
2022-09-26 20:47 ` Ben Greear
2022-09-26 20:19 ` Eugene Y Chang
2022-09-26 20:28 ` Dave Taht
2022-09-26 20:32 ` Bruce Perens [this message]
2022-09-26 20:35 ` Bruce Perens
2022-09-26 20:48 ` David Lang
2022-09-26 20:54 ` Eugene Y Chang
2022-09-26 21:01 ` Sebastian Moeller
2022-09-26 21:10 ` Eugene Y Chang
2022-09-26 21:20 ` Sebastian Moeller
2022-09-26 21:35 ` Eugene Y Chang
2022-09-26 21:44 ` David Lang
2022-09-26 21:44 ` Bruce Perens
2022-09-27 0:35 ` Dave Taht
2022-09-27 0:55 ` Bruce Perens
2022-09-27 1:12 ` Dave Taht
2022-09-27 4:06 ` Eugene Y Chang
2022-09-27 3:50 ` Eugene Y Chang
2022-09-27 7:09 ` Sebastian Moeller
2022-09-27 22:46 ` Eugene Y Chang
2022-09-28 9:54 ` Sebastian Moeller
2022-09-28 18:49 ` Eugene Y Chang
2022-09-26 21:22 ` David Lang
2022-09-26 21:29 ` Sebastian Moeller
2022-09-27 3:47 ` Eugene Y Chang
2022-09-27 6:36 ` Sebastian Moeller
2022-09-27 13:55 ` Dave Taht
2022-09-28 0:20 ` Eugene Y Chang
2022-09-26 21:02 ` Bruce Perens
2022-09-26 21:14 ` Dave Taht
2022-09-26 21:10 ` Dave Taht
2022-09-26 21:28 ` warren ponder
2022-09-26 21:34 ` Bruce Perens
2022-09-27 16:14 ` Dave Taht
2022-09-26 21:17 ` David Lang
2022-09-29 9:10 David Fernández
2022-09-29 19:34 ` Eugene Chang
2022-10-17 13:50 David Fernández
2022-10-17 16:53 ` David Fernández
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAK2MWOtAZWq8fPk21RcEgt4pUbHV4MZzSufhniafwd3wquraJA@mail.gmail.com \
--to=bruce@perens.com \
--cc=dave.taht@gmail.com \
--cc=eugene.chang@ieee.org \
--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