Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Bruce Perens <bruce@perens.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: Ulrich Speidel <u.speidel@auckland.ac.nz>,
	 Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink power use & satellite tracking
Date: Fri, 17 Feb 2023 11:13:00 -0800	[thread overview]
Message-ID: <CAK2MWOt2kt51ujR8mnMLFHc5=+tUZbN=XJJx90yDx9QnNnutLg@mail.gmail.com> (raw)
In-Reply-To: <20200.1676648584@localhost>

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

My remote site is about 35 mi from the Earth station in Tionesta,
California. It's a waitlisted area. The entire area is low population
density: rural agricultural, forested, or barren, and I can only believe
that it's waitlisted because that Earth station and the next closest one in
Arbuckle, California; serve the San Francisco Bay area, which is a 5-hour
drive from my remote site.

On Fri, Feb 17, 2023, 07:43 Michael Richardson <mcr@sandelman.ca> wrote:

>
> Ulrich Speidel via Starlink <starlink@lists.bufferbloat.net> wrote:
>     > * Whether you consider your cell Starlink virgin territory or close
> to
>     > subscriber saturation (https://www.starlink.com/map might help
>     > determine that - if it's light blue, it's likely the former, if it's
>     > "waitlist" blue but surrounded by light blue areas, or rural and
>
> What's the expected corrolation?
> Higher saturation => higher current?  Or the opposite?
>
>

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

  reply	other threads:[~2023-02-17 19:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 23:08 Ulrich Speidel
2023-02-16 23:12 ` Nathan Owens
2023-02-16 23:14   ` Nathan Owens
2023-02-16 23:25     ` Jonathan Bennett
2023-02-16 23:23 ` David Lang
2023-02-16 23:36   ` David Lang
2023-02-17  1:24 ` Bruce Perens
2023-02-17  5:27   ` Ulrich Speidel
2023-02-17  5:31     ` Nathan Owens
2023-02-17 15:43     ` Michael Richardson
2023-02-17 19:13       ` Bruce Perens [this message]
2023-02-18 10:25       ` Ulrich Speidel
2023-02-18 10:52         ` David Lang
2023-02-18 12:36           ` Ulrich Speidel
2023-02-18 20:13             ` Bruce Perens

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='CAK2MWOt2kt51ujR8mnMLFHc5=+tUZbN=XJJx90yDx9QnNnutLg@mail.gmail.com' \
    --to=bruce@perens.com \
    --cc=mcr@sandelman.ca \
    --cc=starlink@lists.bufferbloat.net \
    --cc=u.speidel@auckland.ac.nz \
    /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