Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Nick Buraglio <nick@buraglio.com>
To: Starlink@lists.bufferbloat.net
Subject: [Starlink] starlink disk re-use?
Date: Wed, 12 Jan 2022 20:21:36 -0600	[thread overview]
Message-ID: <CAGB08_fJokqwX6YzAHcS8yyQDpsfNRSzguNe_PsKOG83MQHDxA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 326 bytes --]

What does one do with a dish they are done with? I am more or less done
with the testing I had for my personal dish, and I have good connectivity
so I don't really need to keep paying for the service. Is there a secondary
market for these yet? I see them for exorbitant prices on ebay, but that
seems a bit sketchy to me.

nb

[-- Attachment #2: Type: text/html, Size: 378 bytes --]

             reply	other threads:[~2022-01-13  2:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13  2:21 Nick Buraglio [this message]
2022-01-13  2:36 ` Nathan Owens
2022-01-13  3:10   ` Haudy Kazemi
2022-01-13  6:17     ` Mike Puchol
2022-01-13 20:50 ` Dave Taht
2022-02-02 22:59 ` Dave Täht
2022-02-03 15:48   ` Nick Buraglio

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=CAGB08_fJokqwX6YzAHcS8yyQDpsfNRSzguNe_PsKOG83MQHDxA@mail.gmail.com \
    --to=nick@buraglio.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