From: Inemesit Affia <inemesitaffia@gmail.com>
Cc: "Dave Taht via Starlink" <starlink@lists.bufferbloat.net>,
"Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] [Starlink] one dish per household is silly.
Date: Fri, 10 Nov 2023 13:21:26 +0100 [thread overview]
Message-ID: <CAJEhh73_92SsnNzsFTL0v1WYg+t2M=GmKAY8U_iC=gZfPwxTXg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7ot=Q_+3JN68C2WYSLj7gu6mB7qKOKJ+9+5XLVPK2kJw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
Starlink terms of service as at launch with the round dishes required each
user to pay regardless of the number of dishes. Not unusual compared to
other ISP's.
Of course you can share regardless. Cruise liners use 6 to 12 dishes to
deliver service to thousands. And there's people using it for free WiFi in
restaurants and airplanes and schools
On Fri, Nov 10, 2023, 12:44 PM Dave Taht via Starlink <
starlink@lists.bufferbloat.net> wrote:
> My objection to steve song's analysis here:
>
> https://manypossibilities.net/2023/11/starlink-and-inequality/
>
> A) Am I the only person left in the world that shares his wifi? A
> single dishy can easily serve dozens of people which lowers the cost
> per person enormously. Starlink has limited density per cell in the
> first place, so hanging a wired or wireless bridge off of it and
> covering a small town or merely multiple houses, not much of a
> problem. I know of refuge centers in the ukraine serving hundreds of
> people as one example.
>
> B) I keep seeing estimates of service life being 5 years, when at the
> moment I see it being 10 or more.
>
>
> --
> Oct 30:
> https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
> Dave Täht CSO, LibreQos
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #2: Type: text/html, Size: 2220 bytes --]
next prev parent reply other threads:[~2023-11-10 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 11:44 [NNagain] " Dave Taht
2023-11-10 12:21 ` Inemesit Affia [this message]
2023-11-10 12:33 ` Bill Woodcock
2023-11-10 12:55 ` Dave Taht
[not found] ` <e7258d87-6aa6-4d74-91cf-764c5c5e7e28@gmail.com>
2023-11-10 13:53 ` [NNagain] [Starlink] " Dave Taht
[not found] ` <86062ps2-on4p-s855-6ss9-pr475q32q752@ynat.uz>
2023-11-10 15:10 ` Dave Taht
2023-11-10 13:51 ` David Lang
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='CAJEhh73_92SsnNzsFTL0v1WYg+t2M=GmKAY8U_iC=gZfPwxTXg@mail.gmail.com' \
--to=inemesitaffia@gmail.com \
--cc=nnagain@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