From: Ben Greear <greearb@candelatech.com>
To: David Lang <david@lang.hm>
Cc: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink Digest, Vol 12, Issue 6
Date: Fri, 4 Mar 2022 10:21:45 -0800 [thread overview]
Message-ID: <eb47d43f-8bfe-9a73-f47b-c37e627b6e06@candelatech.com> (raw)
In-Reply-To: <712r509p-7on6-5657-3172-n9140n9097@ynat.uz>
On 3/4/22 10:14 AM, David Lang wrote:
> On Fri, 4 Mar 2022, Ulrich Speidel wrote:
>
>> In terms of Starlink - I really think that it's a red herring, at least for now. As I said, if Starlink can't muster anywhere near enough satellite capacity
>> to serve all of a small town in Montana that's surrounded by gateways close by, then it's not going to be replacing the Internet as we know it in a country
>> 60% larger in area and 40 x larger in population. At best it might be able to provide some backup in a relatively small number of places.
>
> It depends on what you set as your requirements. If you are talking about everyone streaming video, you are correct, but if you talk about less bandwidth
> intensive uses, a little bandwidth goes a long ways.
>
> There's also FAR more of a difference between nothing and low bandwidth than between low and high bandwidth.
>
> Telephone audio is an 64Mb stream, without compression, email and text chat are very low bandwidth.
>
> 20 years ago, you could have an office of 100 employees living on a 1.5Mb Internet connection and have people very happy. A single dishy is 100x this.
>
> I agree that Starlink is not a full replacement for hard-wired Internet, and it never will be. But the ability to get that much bandwidth into an area that
> doesn't have wired Internet wihtout requiring special crews to come in and set up the infrastructure (like you would for geostationary dishes) is a huge step
> forward for disaster relief.
>
> With capabilities like this now available, we (the tech community) need to look at options to be able to extend this connectivity from a point source across a
> wider area (ways to do mesh and have it not collapse, understanding channnel allocations, sane directional antenna uses, etc) including how to provide power.
>
> And also take a careful look at the bandwith that apps are using and find ones that are sane to use. Since (almost) everyone has phones as endpoints now, having
> the ability to put a voip app on the phones and have them able to call and text chat freely within the connectivity bubble without any need to use the external
> bandwith, but be able to connect out in a fairly transparent manner (think how long distance calls were something significant 40-50 years ago, but were still
> using the same equipment and basic process). Can such apps indicate to the user if they are talking to someone really local (say sharing the same wifi), or more
> remote, so that they can
>
> How can such apps be made available to the people with phones? (Apple makes it really hard to side-load apps for example), How can the services get bundled
> (raspverry pi or live CD linux images that provide these services and the app images to download for example). What can be done with OpenWRT builds to make
> turnkey conversions of APs into bandwidth-efficient mesh nodes. This includes how a bit of wire can go a long way towards making a wifi system work better.
I've been using some sub $100 android phones for testing. They typically come loaded with crap-ware, but that could
be fixed, and it would be a convenient wifi-only calling phone (and of course it could do a lot more). If someone
has ability to drop a starlink dish, they could add a small pack of phones to the drop. That is way more helpful that
some hacked together rpi or other cumbersome kludge, and at similar price point.
As for a 'voip' app, there are plenty of those already, including shiny 'free' commercial offerings.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2022-03-04 18:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1943.1646344903.1267.starlink@lists.bufferbloat.net>
2022-03-03 23:47 ` David P. Reed
2022-03-04 5:06 ` Ulrich Speidel
2022-03-04 7:00 ` Mike Puchol
2022-03-04 8:41 ` David Lang
2022-03-04 9:44 ` Ulrich Speidel
2022-03-04 17:07 ` Larry Press
2022-03-04 23:58 ` Ulrich Speidel
2022-03-04 17:08 ` Dave Täht
2022-03-04 17:10 ` Dave Taht
2022-03-04 18:14 ` David Lang
2022-03-04 18:21 ` Ben Greear [this message]
2022-03-04 18:30 ` David Lang
2022-03-05 0:14 ` Ulrich Speidel
2022-03-05 6:38 ` Dick Roy
2022-03-05 9:42 ` Ulrich Speidel
2022-03-05 10:10 ` David Lang
2022-03-05 18:26 ` Dick Roy
2022-03-05 15:25 ` Larry Press
2022-03-06 1:50 ` Ulrich Speidel
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=eb47d43f-8bfe-9a73-f47b-c37e627b6e06@candelatech.com \
--to=greearb@candelatech.com \
--cc=david@lang.hm \
--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