Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Matt Taggart <matt@lackof.org>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] spacebee
Date: Tue, 13 Mar 2018 21:16:28 -0700	[thread overview]
Message-ID: <0d5055ee-8890-8d25-83c4-314086754793@lackof.org> (raw)
In-Reply-To: <CAPjrEw87LruVGpnohFHP9RNUP_Pu8aiKyUzVJdX23r3+2ERtZg@mail.gmail.com>

On 03/13/2018 10:47 AM, Christopher Robin wrote:

> With all the noise around this launch, I haven’t been able to find info 
> on expected operational lifespan vs expected orbit decay. LEO’s can 
> still last for decades. The only thing I’m finding is an expected use 
> for 6mo to 2yr, but not sure how long after that the Spaceebee will stay 
> in orbit and/or be responsive with positional data.
> 
> While just 4 of these things in space isn’t a major concern, rogue 
> launching objects into space isn’t a scalable solution. This is 
> especially true as the cost of launching comes down into the “cheap” 
> startup range. These types of companies aren’t usually concerned 25yr 
> impact plans, and most wont last long enough to be around to assist if 
> any problems occur past that 2-3yr window.

To possibly bring this tangent back to the topic for this list...

A space start-up launching inexpensive devices into orbit with no plans 
for support, upgrades, or disposal is not totally unlike the situation 
we're in with consumer routers and other IoT things. When you think of 
it on that scale it gets quite a bit more scary....

It's the standard business tricks of shifting profit forward at the 
expense of the future and externalization of costs.
(The nuclear industry is another good example, but that's a whole other 
tangent).

-- 
Matt Taggart
matt@lackof.org

  parent reply	other threads:[~2018-03-14  4:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12  4:13 Dave Taht
2018-03-12 16:25 ` dpreed
2018-03-13 18:31   ` Dave Taht
2018-03-12 16:26 ` Jim Gettys
2018-03-12 17:18   ` dpreed
2018-03-12 17:34     ` Christopher Robin
2018-03-12 19:10       ` dpreed
2018-03-12 20:29         ` Christopher Robin
2018-03-13 16:12           ` Jim Gettys
2018-03-13 16:52             ` Dave Taht
2018-03-13 17:03               ` Jim Gettys
2018-03-13 17:31                 ` Dave Taht
2018-03-14  1:49                   ` Jonathan Morton
2018-03-13 17:47                 ` Christopher Robin
2018-03-13 18:25                   ` Dave Taht
2018-03-14  4:16                   ` Matt Taggart [this message]
2018-03-13 17:49               ` valdis.kletnieks
2018-03-13 18:06                 ` Dave Taht
2018-03-14  4:08                   ` Matt Taggart
2018-03-15 20:22               ` Ray Ramadorai

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0d5055ee-8890-8d25-83c4-314086754793@lackof.org \
    --to=matt@lackof.org \
    --cc=cerowrt-devel@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