From: David Lang <david@lang.hm>
To: Hal Murray via Nnagain <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] Starlink
Date: Mon, 18 Dec 2023 00:15:36 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.2312180013430.20826@nftneq.ynat.uz> (raw)
In-Reply-To: <20231216225752.352EC28C1C3@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
I agree with your questions
yes, Available bandwidth is shared between users. I don't know what you get if
you are the only person there, but I can say that I'm in the LA metro area (far
from rural) and I get enough bandwith to work remotely on Starlink.
My local makerspace also has Starlink and it's enough that having a (small)
group of users operating at the same time is not a horrid experience.
David Lang
On Sat, 16 Dec 2023, Hal Murray via Nnagain wrote:
> Frantisek Borsik said:
>> The only way to deliver it to them in a reasonable timeframe is Starlink.
>
> What sort of bandwidth/latency do I get from Starlink if I'm the only user in
> a large area?
>
> The spectrum is shared. Does the bandwidth per user go down as more users in
> the antenna footprint become active? How many users per square mile/km can
> Starlink support at the current target bandwidth? ...
>
> What fraction of the country is rural enough that it won't get fiber? How
> much of that is sparse enough so that Starlink will work?
>
> What should I be asking?
>
>
> --
> These are my opinions. I hate spam.
>
>
>
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
prev parent reply other threads:[~2023-12-18 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 22:57 Hal Murray
2023-12-18 8:15 ` David Lang [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/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.2312180013430.20826@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=nnagain@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