From: segaloco via COFF <coff@tuhs.org>
To: coff@tuhs.org
Subject: [COFF] Re: [TUHS] Re: Intel ME, UEFI, User Control was Re: Question about BSD disklabel history
Date: Fri, 05 Jan 2024 02:03:16 +0000 [thread overview]
Message-ID: <Mab_yxk1jpkqRmEfN0p90b9FPOeTCoJHfsOo-ipp29MjNZJZCtkFHCsmPE9D_wbOtfV2AgybQF6_FOKW_wr7HuqAnrDtssGhbZJMPOVK4z8=@protonmail.com> (raw)
In-Reply-To: <CAGg_6+NVMFrORBqzrvAYvZMYjL7CKsppiuPFZPJ4BHeusLOr_w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
On Thursday, January 4th, 2024 at 2:14 PM, Nevin Liber <nevin@eviloverlord.com> wrote:
> It isn't about happily throwing away "rights" (whatever that means). It's about we aren't willing to pay for it. It's a tradeoff, and those who want everything hackable haven't shown much value to the rest of us, and there are very real concerns about the costs both in terms of security threats and monetary costs.--
>
> Nevin ":-)" Liber <mailto:nevin@eviloverlord.com> +1-847-691-1404
I've tried (and failed) at a thoughtful response a few times now, so I think I need to at least accept that yeah, I'm in the extreme minority in not preferring convenience over autonomy.
Good luck with this conversation, I don't think I have anything else to contribute, I think I'm on a different world than the prevailing opinions on this stuff...but such is life. Better than an echo chamber that's for sure.
- Matt G.
[-- Attachment #2: Type: text/html, Size: 2345 bytes --]
next prev parent reply other threads:[~2024-01-05 2:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 19:10 [COFF] " segaloco via COFF
2024-01-04 21:20 ` Dan Cross
2024-01-04 22:14 ` [COFF] Re: [TUHS] " Nevin Liber
2024-01-05 2:03 ` segaloco via COFF [this message]
2024-01-05 2:35 ` Dan Cross
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='Mab_yxk1jpkqRmEfN0p90b9FPOeTCoJHfsOo-ipp29MjNZJZCtkFHCsmPE9D_wbOtfV2AgybQF6_FOKW_wr7HuqAnrDtssGhbZJMPOVK4z8=@protonmail.com' \
--to=coff@tuhs.org \
--cc=segaloco@protonmail.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;
as well as URLs for NNTP newsgroup(s).