From: David Lang <david@lang.hm>
To: Larry Press <lpress@csudh.edu>
Cc: Kurtis Heimerl <kheimerl@cs.washington.edu>,
David Lang <david@lang.hm>,
Starlink list <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink no longer available to the Ukrainian army?
Date: Fri, 14 Oct 2022 12:35:20 -0700 (PDT) [thread overview]
Message-ID: <4rn1o59p-36nq-87q9-3n78-828r0qppp221@ynat.uz> (raw)
In-Reply-To: <BYAPR03MB3863209C8AFFEFCEDB8DA96DC2249@BYAPR03MB3863.namprd03.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 3770 bytes --]
some interesting tidbits in that article
1. 25k dishes rather than the 15k I had heard befor
2. they are providing full business rates rather than consumer rates
2a. it's interesting that they can do this with the consumer dishes, although a
lot of what I saw shipped were the gen1 (round) dishes, which may be better than
the gen 2 consumer dishes.
yes, the companies who manufacture the weapons have been paid in full.
I think it's worth pointing out that Starlink was never intended to be the
entire communications infrastructure for a country. I think it would be a very
interesting thing to investigate what the actual density of users and data usage
is (there is a graph posted, but I haven't tried to get a good enough copy of it
to see the units). It could confirm/refute the "starlink can't scale" argument
David Lang
On Fri, 14 Oct 2022, Larry Press wrote:
> SpaceX has given a more detailed statement of expenses to the Pentagon:
> https://www.cnn.com/2022/10/13/politics/elon-musk-spacex-starlink-ukraine/index.html
>
> They have been "paid" in favorable publicity and have tested/refined things like mobile connectivity.
>
> Aren't the companies that supply weapons, ammunition, etc. paid?
>
> Larry
>
>
> ________________________________
> From: Starlink <starlink-bounces@lists.bufferbloat.net> on behalf of David Lang via Starlink <starlink@lists.bufferbloat.net>
> Sent: Friday, October 14, 2022 10:28 AM
> To: Kurtis Heimerl <kheimerl@cs.washington.edu>
> Cc: Starlink list <starlink@lists.bufferbloat.net>
> Subject: Re: [Starlink] Starlink no longer available to the Ukrainian army?
>
> Having now read more info on this, less significant than the $80m total figure
> is the $20m/month figure he quoted. With 15k dishes as the figure that they sent
> (separate from whatever has been purchased on the commercial side), that works
> out to 1.3k/dish/month, which is very high.
>
> now, not being able to deploy reliable ground stations inside Ukraine could be
> driving up costs, plus the ongoing battle against jamming. But in his tweet he
> also cites satellite costs, which should not be allocated as "Ukraine related"
> costs (and I don't think the cyberdefense and jamming defense work should be
> either)
>
> David Lang
>
> On Fri, 14 Oct 2022, Kurtis Heimerl via Starlink wrote:
>
>> This thread (https://urldefense.com/v3/__https://twitter.com/dim0kq/status/1580827171903635456__;!!P7nkOOY!reUDfoQpkbJ6YAQ6h436UHdL9D0lnxDeqlc29JPUsrl8V_02dlWYYFi4zfQ-CCRLKetEGxza7FjOyJDcUURE6WtPnA$ )
>> strongly argues that Starlink is largely paid for their service, at
>> least on the consumer side. I imagine there are significant
>> operational expenses in dealing with the various actors involved but
>> not on the basic model.
>>
>> On Fri, Oct 14, 2022 at 9:06 AM Juliusz Chroboczek via Starlink
>> <starlink@lists.bufferbloat.net> wrote:
>>>
>>>> In essence, once you give something away for free, not even setting the
>>>> expectation that it’s a “freemium” model, it’s very hard to get out of it. If
>>>> you then claim your costs are way higher than what analysis work out, eyebrows
>>>> raise way above the hairline.
>>>
>>> Uh. Hmm.
>>> _______________________________________________
>>> Starlink mailing list
>>> Starlink@lists.bufferbloat.net
>>> https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/starlink__;!!P7nkOOY!reUDfoQpkbJ6YAQ6h436UHdL9D0lnxDeqlc29JPUsrl8V_02dlWYYFi4zfQ-CCRLKetEGxza7FjOyJDcUUSVCxIH-w$
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/starlink__;!!P7nkOOY!reUDfoQpkbJ6YAQ6h436UHdL9D0lnxDeqlc29JPUsrl8V_02dlWYYFi4zfQ-CCRLKetEGxza7FjOyJDcUUSVCxIH-w$
>
next prev parent reply other threads:[~2022-10-14 19:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 12:06 Juliusz Chroboczek
2022-10-14 12:45 ` David Lang
2022-10-14 13:05 ` Juliusz Chroboczek
2022-10-14 13:11 ` David Lang
2022-10-14 14:17 ` Mike Puchol
2022-10-14 18:26 ` Juliusz Chroboczek
2022-10-14 20:44 ` Mike Puchol
2022-10-16 17:31 ` Steve Stroh
2022-10-16 17:56 ` Dave Taht
2022-10-16 18:28 ` Vint Cerf
2022-10-14 12:51 ` Mike Puchol
2022-10-14 13:13 ` Juliusz Chroboczek
2022-10-14 14:15 ` Mike Puchol
2022-10-14 16:05 ` Juliusz Chroboczek
2022-10-14 17:13 ` Kurtis Heimerl
2022-10-14 17:28 ` David Lang
2022-10-14 18:16 ` Juliusz Chroboczek
2022-10-14 18:32 ` Larry Press
2022-10-14 19:32 ` Benjamin Henrion
2022-10-14 19:35 ` David Lang [this message]
2022-10-14 20:07 ` David Lang
2022-10-14 22:29 ` Dave Taht
2022-10-15 16:51 ` Larry Press
2022-10-16 6:42 ` Sebastian Moeller
2022-10-16 8:45 ` Bruce Perens
2022-10-16 16:31 ` Dave Taht
2022-10-16 17:00 ` Sebastian Moeller
2022-10-16 19:55 ` Brandon Butterworth
2022-10-16 20:25 ` Bruce Perens
2022-11-02 3:50 ` [Starlink] 25 years of open source - where we went wrong, and how to fix it Dave Taht
2022-10-14 19:13 ` [Starlink] Starlink no longer available to the Ukrainian army? tom
2022-10-14 19:41 ` David Lang
2022-10-14 20:09 ` Dave Taht
2022-10-16 17:50 ` Steve Stroh
2022-10-16 17:57 ` Nathan Owens
2022-10-16 18:01 ` Dave Taht
2022-10-16 18:29 ` Vint Cerf
2022-10-16 18:33 ` David Lang
2022-10-16 18:44 ` Sebastian Moeller
2022-10-16 19:03 ` Brandon Butterworth
2022-10-16 19:37 ` Ulrich Speidel
2022-10-16 19:51 ` David Lang
2022-10-16 20:37 ` Michael Richardson
2022-10-16 20:52 ` Bruce Perens
2022-10-16 22:17 ` Brandon Butterworth
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=4rn1o59p-36nq-87q9-3n78-828r0qppp221@ynat.uz \
--to=david@lang.hm \
--cc=kheimerl@cs.washington.edu \
--cc=lpress@csudh.edu \
--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