From: jeffb <jeffb@jeffb.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] welcome to new list members
Date: Sat, 14 Jan 2023 12:25:25 -0500 [thread overview]
Message-ID: <CAANw6Q9DdxuAwH9DLnz-T7_seXLhC+L+ZnnP8L7pF4ixgKiRkg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw79_JLwDaMZkY2-QCpu459nCamqtYmmGwCCJppBbnZ1jA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]
Appreciate the acceptance! I found this list as a result of your post on
NANOG last week.
I've had Starlink running as a secondary connection here in Lexington, KY
for about a year now.. happy to have found a technical list to participate
in!
Jeff
On Sat, Jan 14, 2023 at 11:39 AM Dave Taht via Starlink <
starlink@lists.bufferbloat.net> wrote:
> I had not checked the subscriber signups in a while, and wow, we have
> nearly 30 new folk on this list!
>
> Welcome!
>
> There's an awful lot in the archives about starlink here, and the
> discussion ranges from me kvetching about bufferbloat, to folk like
> mike puchol talking about his simulations, oleg his repairs in the
> ukraine... and a ton of tests of various sorts, and endless, endless,
> speculation. please poke through the archives
> https://lists.bufferbloat.net/pipermail/starlink/
>
> Please feel free to introduce yourselves.
>
> --
> This song goes out to all the folk that thought Stadia would work:
>
> https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
--
jeffb | jeffb@jeffb.net
[-- Attachment #2: Type: text/html, Size: 2265 bytes --]
prev parent reply other threads:[~2023-01-14 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 16:39 Dave Taht
2023-01-14 17:25 ` jeffb [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=CAANw6Q9DdxuAwH9DLnz-T7_seXLhC+L+ZnnP8L7pF4ixgKiRkg@mail.gmail.com \
--to=jeffb@jeffb.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