From: Haudy Kazemi <kaze0010@umn.edu>
To: Starlink@lists.bufferbloat.net
Cc: Nick Buraglio <nick@buraglio.com>
Subject: Re: [Starlink] starlink disk re-use?
Date: Wed, 12 Jan 2022 21:10:03 -0600 [thread overview]
Message-ID: <CACs6+uURCj_UxHBmhUYvdc67E=ahF87r6b422q+1t-DTxqON0w@mail.gmail.com> (raw)
In-Reply-To: <CALjsLJvdOU7C2xxQCRr0ck_VPekdJXppBp7TaGgMdffi+383FQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
A Reddit thread started by wk057 has several replies saying that the
dishes, at least as of two months ago, cannot be reactivated if service is
turned off. It looks like wk057 was/is looking for a dish and service; so
it may be worthwhile contacting him. (If you Google him, you'll find that
he is pretty well known in several tech circles.)
https://old.reddit.com/r/Starlink_Support/comments/qauy1n/used_dishy/
On Wed, Jan 12, 2022, 20:36 Nathan Owens <nathan@nathan.io> wrote:
> You can transfer service to someone else, but they’d need to be in a cell
> with capacity/availability. I believe you contact support to do so.
>
> —Nathan
>
> On Wed, Jan 12, 2022 at 6:21 PM Nick Buraglio <nick@buraglio.com> wrote:
>
>> 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
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
>>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #2: Type: text/html, Size: 2876 bytes --]
next prev parent reply other threads:[~2022-01-13 3:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 2:21 Nick Buraglio
2022-01-13 2:36 ` Nathan Owens
2022-01-13 3:10 ` Haudy Kazemi [this message]
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='CACs6+uURCj_UxHBmhUYvdc67E=ahF87r6b422q+1t-DTxqON0w@mail.gmail.com' \
--to=kaze0010@umn.edu \
--cc=Starlink@lists.bufferbloat.net \
--cc=nick@buraglio.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