From: Dave Taht <dave.taht@gmail.com>
To: Bruce Perens <bruce@perens.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] How I hacked Starlink and got service for free without meaning to
Date: Fri, 16 Sep 2022 16:22:20 -0700 [thread overview]
Message-ID: <CAA93jw4Tdt_3jR0R1dXmOhQ4hhT2mBFTFKp2GPP96Szgosbadw@mail.gmail.com> (raw)
In-Reply-To: <CAK2MWOs4bk8LO7sbskDDkV+BrofsTQ2KZd=g379u0+1JgBghmw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
You are now the world record holder for uplink.
On Fri, Sep 16, 2022, 3:45 PM Bruce Perens via Starlink <
starlink@lists.bufferbloat.net> wrote:
> I have told Starlink about this hole, so it should be closed before anyone
> can take advantage.
>
> I ordered two dishes, using two separate accounts, before you could order
> more than one dish per account (I was on waiting lists for both). I then
> returned using account A the dish I purchased using account B. This closed
> both accounts, but the dish was working fine when I finally got to install
> it at my remote site two days ago. 0 obstructions and 89 MBPS upload in the
> middle of the day, my site is 35 miles from the earth station at Tionesta,
> CA.
>
> I'll give Dave Taht an account to test with when I'm finished configuring.
>
> Thanks
>
> Bruce
>
> --
> Bruce Perens K6BP
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #2: Type: text/html, Size: 1718 bytes --]
next prev parent reply other threads:[~2022-09-16 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 22:45 Bruce Perens
2022-09-16 23:22 ` Dave Taht [this message]
2022-09-16 23:23 ` Jeremy Austin
2022-09-17 0:17 ` Bruce Perens
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=CAA93jw4Tdt_3jR0R1dXmOhQ4hhT2mBFTFKp2GPP96Szgosbadw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bruce@perens.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