From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] one dish per household is silly.
Date: Sat, 11 Nov 2023 05:42:36 +0100 [thread overview]
Message-ID: <a9642e63-646f-46cd-8de0-dd76f2dae568@gmail.com> (raw)
In-Reply-To: <CAJEhh73_92SsnNzsFTL0v1WYg+t2M=GmKAY8U_iC=gZfPwxTXg@mail.gmail.com>
Le 10/11/2023 à 13:21, Inemesit Affia via Starlink a écrit :
> 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
Are we sure we dont have a different set of terms of conditions...
Alex
>
> On Fri, Nov 10, 2023, 12:44 PM Dave Taht via Starlink
> <starlink@lists.bufferbloat.net <mailto:starlink@lists.bufferbloat.net>>
> wrote:
>
> My objection to steve song's analysis here:
>
> https://manypossibilities.net/2023/11/starlink-and-inequality/
> <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
> <https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html>
> Dave Täht CSO, LibreQos
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net <mailto:Starlink@lists.bufferbloat.net>
> https://lists.bufferbloat.net/listinfo/starlink
> <https://lists.bufferbloat.net/listinfo/starlink>
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2023-11-11 4:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 11:44 Dave Taht
2023-11-10 12:21 ` Inemesit Affia
2023-11-11 4:42 ` Alexandre Petrescu [this message]
2023-11-10 12:33 ` [Starlink] [NNagain] " Bill Woodcock
2023-11-10 12:55 ` Dave Taht
2023-11-10 13:17 ` Alexandre Petrescu
2023-11-10 13:44 ` David Lang
2023-11-10 15:10 ` Dave Taht
2023-11-10 16:09 ` Alexandre Petrescu
2023-11-10 16:40 ` David Lang
2023-11-10 16:58 ` Alexandre Petrescu
2023-11-10 18:16 ` Alexandre Petrescu
2023-11-10 13:53 ` Dave Taht
2023-11-11 4:50 ` Alexandre Petrescu
2023-11-10 16:11 ` Alexandre Petrescu
2023-11-10 13:51 ` [Starlink] " David Lang
2023-11-13 6:37 ` J Pan
2023-11-13 6:40 ` Inemesit Affia
2023-11-13 16:10 ` J Pan
2023-11-13 16:22 ` Inemesit Affia
2023-11-13 20:34 ` Ulrich Speidel
2023-11-13 20:38 ` Inemesit Affia
2023-11-13 20:42 ` Inemesit Affia
2023-11-14 4:57 ` J Pan
2023-11-14 5:13 ` Ulrich Speidel
2023-11-14 5:18 ` J Pan
2023-11-14 9:04 ` Alexandre Petrescu
2023-11-14 8:50 ` Alexandre Petrescu
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=a9642e63-646f-46cd-8de0-dd76f2dae568@gmail.com \
--to=alexandre.petrescu@gmail.com \
--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