From: Mike Puchol <mike@starlink.sx>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
starlink@lists.bufferbloat.net, Dave Taht <dave.taht@gmail.com>
Subject: Re: [Starlink] loon postmortem
Date: Thu, 24 Feb 2022 00:22:23 +0300 [thread overview]
Message-ID: <7e60b87c-1ff5-437b-864c-ebd12704a385@Spark> (raw)
In-Reply-To: <CAA93jw5+h80__Hi7-aFEwBRLNwQtip13uYnPC4xWRy3y5vr3Yw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
Back when they were launching commercial services in Kenya, I started a three-part series on Loon, which I didn’t finish as they shut down while I took a break to learn about LTE networks: https://mikepuchol.com/loon-why-moonshots-matter-6e4fbb015281
It was really interesting to then read the “lessons learned” document, which showed I was correct on some things, wrong in others, and naive in a few :-)
Best,
Mike
On Feb 23, 2022, 20:02 +0300, Dave Taht <dave.taht@gmail.com>, wrote:
> this is long...
>
> https://storage.googleapis.com/x-prod.appspot.com/files/The%20Loon%20Library.pdf
>
> I wished they'd gone with the fixed wireless strategy.
>
> --
> I tried to build a better future, a few times:
> https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
>
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
[-- Attachment #2: Type: text/html, Size: 1640 bytes --]
prev parent reply other threads:[~2022-02-23 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 17:02 Dave Taht
2022-02-23 21:22 ` Mike Puchol [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/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=7e60b87c-1ff5-437b-864c-ebd12704a385@Spark \
--to=mike@starlink.sx \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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