From: Dave Taht <dave.taht@gmail.com>
To: thejoff@mail.com,
"Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] state broadband offices
Date: Mon, 16 Oct 2023 04:56:41 -0700 [thread overview]
Message-ID: <CAA93jw7L5Vj0Rwb+yk7tqZXzjK2nrxWF=G7+88U_hRsCZi0v=g@mail.gmail.com> (raw)
In-Reply-To: <CAO-LeMxY34zM+=A2Oyz09H-2Hk8cKqkmsaTwEEFdAm3pQwt3cw@mail.gmail.com>
On Mon, Oct 16, 2023 at 12:11 AM le berger des photons via Nnagain
<nnagain@lists.bufferbloat.net> wrote:
>
> here is the best idea I've ever run into regarding getting artificial network connectivity (as opposed to the inborn network we have and have been programmed to ignore or had our pinneal glands poisoned) out to everybody regardless of how few or many neighbors they have:
>
> https://patents.justia.com/inventor/sherwin-i-seligsohn
The patents above have mostly expired, as has the fella who did them.
He woul have been interesting to talk to.
> this went nowhere because the New World ODOR didn't want it to, as it was only good for all of us and none of them.
The x loon project tried to bring suborbital internet via balloon.
Great post-mortum here:
https://storage.googleapis.com/x-prod.appspot.com/files/The%20Loon%20Library.pdf
>
> On Sun, Oct 15, 2023 at 7:37 PM Dave Taht via Nnagain <nnagain@lists.bufferbloat.net> wrote:
>>
>> Since texas has been a focus, here is that broadband office, and many others.
>>
>> https://broadband.money/state-broadband-offices/texas
>> director: https://www.linkedin.com/in/grconte/
>>
>> I started this list in the hope that we could constructively engage
>> across professions, and try to propose ideas that made sense for
>> genuinely improving the internet. As of today... Many more (u)IXPs
>> seem like a huge win for humanity in general, and yet are seemingly
>> absent from the national agenda. So... ring up your broadband office,
>> use your linkedin, have a meeting, ask 'em to join this list for
>> constructive discussions?
>>
>> The website above (broadband.io) has mostly been involved with BEAD,
>> but now as it is moving into more deployment phase. It has often been
>> not fun seeing the earnest young faces on the friday AMAs there, (I
>> did one) also trying to do the right things for our internet, through
>> a sea of lobbyists and incomplete technical information.
>>
>>
>> --
>> Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
>> Dave Täht CSO, LibreQos
>> _______________________________________________
>> Nnagain mailing list
>> Nnagain@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/nnagain
>
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
--
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos
next prev parent reply other threads:[~2023-10-16 11:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 17:37 Dave Taht
2023-10-15 18:00 ` Dave Taht
2023-10-16 7:11 ` le berger des photons
2023-10-16 11:56 ` Dave Taht [this message]
2023-10-16 12:13 ` le berger des photons
2023-10-16 12:16 ` le berger des photons
2023-10-16 19:07 ` le berger des photons
2023-10-16 19:16 ` 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='CAA93jw7L5Vj0Rwb+yk7tqZXzjK2nrxWF=G7+88U_hRsCZi0v=g@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=nnagain@lists.bufferbloat.net \
--cc=thejoff@mail.com \
/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