Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: rjmcmahon <rjmcmahon@rjmcmahon.com>
To: David Lang <david@lang.hm>
Cc: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>,
	"Sebastian Moeller" <moeller0@gmx.de>,
	starlink@lists.bufferbloat.net
Subject: Re: [NNagain] [Starlink] FCC Upholds Denial of Starlink's RDOF Application
Date: Fri, 15 Dec 2023 14:05:04 -0800	[thread overview]
Message-ID: <b6cc533839564c1e472b67f431d99bf1@rjmcmahon.com> (raw)
In-Reply-To: <4p61qp8r-p1p1-r83r-n283-315548o163po@ynat.uz>

I surveyed some female telehealth providers. There are a lot of 
subtleties required to make telehealth work well for the providers. 
Their knowledge level is quite fascinating.

I don't see their voices here on these boards either. In education, the 
absence of something being taught is called the null curriculum. This 
group has a huge null curriculum w/respect to female voices - though 
that's my perspective.

https://www.ascd.org/el/articles/reimagining-the-null-curriculum

Bob
> why do you think telehealth won't work over LEO services?
> 
> I've used it personally.
> 
> Even if women use telehealth more than men, that doesn't say that
> women have any particular advantage in moving the bits around that
> make telehealth possible.
> 
> David Lang
> 
> On Fri, 15 Dec 2023, rjmcmahon wrote:
> 
>> Women are the primary users and providers of telehealth services. They 
>> are using broadband to care for our population. They also run most of 
>> the addiction services across our country, whatever the addiction may 
>> be. So gender actually matters. Ask them as providers. Telehealth 
>> doesn't work over LEO (nor does it matter much for men on boats.) Same 
>> for distance learning.
>> 
>> https://www.healthcaredive.com/news/women-more-likely-telehealth-patients-providers-covid-19-pandemic/608153/
>> 
>> As Washington considers which virtual care flexibilities should remain 
>> in place post-COVID-19, experts are flagging that paring back 
>> telehealth access and affordability will disproportionately affect 
>> women, even as a growing share of startups emerge to address women’s 
>> unique health needs.
>> 
>> While women are more likely than men to visit doctors and consume 
>> healthcare services in general, telehealth seems to be uniquely 
>> attractive to women.
>> 
>> Bob
>>> who exactly do you think is calling for there to be no Internet
>>> access? and what in the world does the sex of individuals have to do
>>> with shipping bits around?
>>> 
>>> Starlink (and hopefully it's future competitors) provides a way to 
>>> get
>>> Internet service to everyone without having to run fiber to every
>>> house.
>>> 
>>> As for the parallels with rural electrification, if that problem were
>>> to be faced today, would the right answer be massive public agencies
>>> to build and run miles of wire from massive central power plants? or
>>> would the right answer be solar + batteries in individual houses for
>>> the most rural folks, with small modular reactors to power the larger
>>> population areas?
>>> 
>>> Just because there was only one way to achieve a goal in the past
>>> doesn't mean that approach is the best thing to do today.
>>> 
>>> David Lang
>>> 
>>> On Fri, 15 Dec 2023, rjmcmahon wrote:
>>> 
>>>> Hi All,
>>>> 
>>>> We're trying to modernize America. LBJ helped do it for electricity 
>>>> decades ago. It's our turn to step up to the plate. Tele-health and 
>>>> distance learning requires us to do so. There is so much to follow.
>>>> 
>>>> A reminder what many women went through before LBJ showed up. I'm 
>>>> skeptical a patriarchy under Musk is even close to capable. We 
>>>> probably need a woman to lead us, or at least motivate us to do our 
>>>> best work for our country and to be an example to the world.
>>>> 
>>>> A Hill Country farm wife had to do her chores even if she was ill – 
>>>> no matter how ill. Because Hill Country women were too poor to 
>>>> afford proper medical care they often suffered perineal tears in 
>>>> childbirth. During the 1930s, the federal government sent physicians 
>>>> to examine a sampling of Hill Country women. The doctors found that, 
>>>> out of 275 women, 158 had perineal tears. Many of them, the team of 
>>>> gynecologists reported, were third-degree tears, “tears so bad that 
>>>> it is difficult to see how they stand on their feet.” But they were 
>>>> standing on their feet, and doing all the chores that Hill Country 
>>>> wives had always done – hauling the water, hauling the wood, 
>>>> canning, washing, ironing, helping with the shearing, the plowing 
>>>> and the picking.
>>>> 
>>>> Because there was no electricity.
>>>> 
>>>> Bob
>>>>> On Fri, 15 Dec 2023, Sebastian Moeller via Starlink wrote:
>>>>> 
>>>>>> Hi Frantisek,
>>>>>> 
>>>>>> 
>>>>>>> On Dec 15, 2023, at 13:46, Frantisek Borsik via Nnagain 
>>>>>>> <nnagain@lists.bufferbloat.net> wrote:
>>>>>>> 
>>>>>>> Thus, technically speaking, one would like the advantages of 
>>>>>>> satcom such as starlink, to be at least 5gbit/s in 10 years time, 
>>>>>>> to overcome the 'tangled fiber' problem.
>>>>>>> 
>>>>>>> No, not really. Starlink was about to address the issue of 
>>>>>>> digital divide -
>>>>>> 
>>>>>> 	I beg to differ. Starlink is a commercial enterprise with the 
>>>>>> goal to make a profit by offering (usable) internet access 
>>>>>> essentially everywhere; it is not as far as I can tell an attempt 
>>>>>> at specifically reducing the digital divide (were often an 
>>>>>> important factor is not necessarily location but financial means).
>>>>> 
>>>>> Every Inernet company " commercial enterprise with the goal to make 
>>>>> a
>>>>> profit by offering (usable) internet" don't dismiss a company 
>>>>> because
>>>>> of that. Starlink (and the other Satellite ISPs) all exist to 
>>>>> service
>>>>> people who can't use traditional wired infrastructure
>>>>> 
>>>>>> 
>>>>>>> delivering internet to those 640k locations, where there is 
>>>>>>> literally none today. Fiber will NEVER get there. And it will get 
>>>>>>> there, it will be like 10 years down the road.
>>>>>> 
>>>>>> 	This is IHO the wrong approach to take. The goal needs to be a 
>>>>>> universal FTTH access network (with the exception of extreme 
>>>>>> locations, no need to pull fiber up to the highest Bivouac shelter 
>>>>>> on Mt. Whitney). And f that takes a decade or two, so be it, this 
>>>>>> is infrastructure that will keep on helping for many decades once 
>>>>>> rolled-out. However given that time frame one should consider 
>>>>>> work-arounds for the interim period. I would have naively thought 
>>>>>> starlink would qualify for that from a technical perspective, but 
>>>>>> then the FCC documents actually discussion requirements and how 
>>>>>> they were or were not met/promised by starlink was mostly 
>>>>>> redacted.
>>>>> 
>>>>> what do you consider 'extreme locations'? how long a run between
>>>>> houses is 'too far'?
>>>>> 
>>>>> we've seen the failure of commercial fiber monopolies in cities 
>>>>> with
>>>>> housing density of several houses per acre (and even where there 
>>>>> are
>>>>> apartment complexes there as well) because it's not profitable 
>>>>> enough.
>>>>> When you get into areas where it's 'how many acres per house' the 
>>>>> cost
>>>>> of running FTTH gets very high. I don't think this is the majority 
>>>>> of
>>>>> the population of the US any longer (but I don't know for sure), 
>>>>> but
>>>>> it's very clearly the majority of the area of the US. And once you 
>>>>> get
>>>>> out of the major metro areas, even getting fiber to every town or
>>>>> village becomes a major undertaking.
>>>>> 
>>>>> Is running fiber 30 miles to support a village of 700 people an
>>>>> 'extreme location'? let me introduce you to Vermontville MI
>>>>> https://en.wikipedia.org/wiki/Vermontville,_Michigan which is less
>>>>> than an hours drive from the state capitol.
>>>>> 
>>>>> David Lang
>>>>> _______________________________________________
>>>>> Nnagain mailing list
>>>>> Nnagain@lists.bufferbloat.net
>>>>> https://lists.bufferbloat.net/listinfo/nnagain
>>>> 
>> 

  parent reply	other threads:[~2023-12-15 22:05 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJUtOOi7rSiPTFGVkadh4XPvFOnmzLidX5=7-LTJnoiyPauNag@mail.gmail.com>
     [not found] ` <A8DC9114A92F47D5AAE1D332B5E5007D@SRA6>
2023-12-13 22:38   ` Frantisek Borsik
2023-12-14  2:46     ` Robert McMahon
2023-12-14  6:11       ` Frantisek Borsik
2023-12-14 17:48         ` David Bray, PhD
2023-12-14 18:47           ` Frantisek Borsik
2023-12-14 18:51           ` Nathan Simington
2023-12-14 19:44             ` Frantisek Borsik
     [not found]             ` <f7d6522d-db06-4ee6-a814-76810ad01e1f@gmail.com>
     [not found]               ` <ZXxIdbzif5ogB0IQ@Space.Net>
     [not found]                 ` <02cc2879-ef99-4388-bc1e-335a4aaff6aa@gmail.com>
     [not found]                   ` <ZXxKMZ-pEbS4QAzW@Space.Net>
2023-12-15 12:46                     ` Frantisek Borsik
2023-12-15 13:24                       ` Gert Doering
2023-12-15 13:40                       ` Sebastian Moeller
2023-12-15 18:06                         ` David Lang
2023-12-15 18:51                           ` rjmcmahon
2023-12-15 19:13                             ` David Lang
2023-12-15 21:29                               ` rjmcmahon
2023-12-15 21:42                                 ` David Lang
2023-12-15 22:04                                   ` David Bray, PhD
2023-12-15 22:10                                     ` David Lang
2023-12-15 22:13                                       ` David Bray, PhD
2023-12-15 22:33                                         ` Kenline, Doug
2023-12-15 22:36                                         ` Dave Taht
2023-12-17 21:22                                           ` Tanya Weiman
     [not found]                                         ` <de59330f-e05a-4c2e-9d64-e2821f113e76@gmail.com>
2023-12-19 20:49                                           ` [NNagain] detecting GPT-generated text Rich Brown
2023-12-22 12:23                                             ` le berger des photons
2023-12-22 13:06                                               ` Rich Brown
2023-12-15 22:05                                   ` rjmcmahon [this message]
2023-12-15 22:13                                     ` [NNagain] [Starlink] FCC Upholds Denial of Starlink's RDOF Application David Lang
2023-12-15 22:26                                   ` Dave Taht
2023-12-16  4:16                                     ` David Lang
2023-12-16 17:30                                       ` rjmcmahon
2023-12-16 18:18                                         ` Dick Roy
2023-12-16 18:48                                         ` Robert McMahon
2023-12-16 21:44                                           ` Frantisek Borsik
2023-12-16 22:28                                             ` Robert McMahon
2023-12-17  0:25                                               ` Dave Taht
2023-12-23 21:17                                                 ` J Pan
2023-12-18  8:25                                               ` David Lang
2023-12-17  1:54             ` [NNagain] other fcc services at sea Dave Taht

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

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

  git send-email \
    --in-reply-to=b6cc533839564c1e472b67f431d99bf1@rjmcmahon.com \
    --to=rjmcmahon@rjmcmahon.com \
    --cc=david@lang.hm \
    --cc=moeller0@gmx.de \
    --cc=nnagain@lists.bufferbloat.net \
    --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