unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Joshua Branson <jbranso@fastmail.com>
To: help-guix@gnu.org
Subject: Re: Librem
Date: Wed, 02 May 2018 14:07:07 -0400	[thread overview]
Message-ID: <ygfh8nqylro.fsf@fastmail.com> (raw)
In-Reply-To: <87zi1j2myo.fsf@gmail.com> (Pierre Neidhardt's message of "Wed, 02 May 2018 01:00:07 +0530")

Pierre Neidhardt <ambrevar@gmail.com> writes:

> Chris Marusich <cmmarusich@gmail.com> writes:
>
>> Another option is to find a system that respects your freedom and does
>> not require proprietary software to run.  I have a LibreBoot laptop I
>> purchased from MiniFree, and I love it!  I know that purchasing a
>> replacement computer that respects your freedom can seem like an
>> expensive option, but if you have the money, then it's an option:
>>
>> https://minifree.org/
>>
>> You may also be interested in looking at:
>>
>> https://www.fsf.org/resources/hw/endorsement/respects-your-freedom
>
> How does it compare to Purism?

I believe that minifree sells products that Richard Stallman would
purchase.  Purism is pretty close to something that Stallman would
purchase, but I believe there may be some lingering issues with Intel's
FSP that would prevent Stallman from purchasing a Purism.  You can read
a bit more of it here:  https://puri.sm/posts/measuring-the-intel-me-to-create-a-more-secure-computer/

However, I would argue that currently, Purism is probably the best
company working on making a modern and freedom respecting computing
device.  EOMA68 is another contender. https://www.crowdsupply.com/eoma68/micro-desktop

>
> 	https://puri.sm/products/
>
> Their Librem 13 looks very attractive indeed!  Compared to my Xiaomi Air
> 13", it's seems to be a bit better while also more expansive, but I
> suppose it's the price to pay for a good cause! :)
>
> Any Librem user out there?

  reply	other threads:[~2018-05-02 18:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02 17:25 Installation: Load non-free wifi firmware (iwlwifi) Pierre Neidhardt
2018-03-02 17:41 ` Pierre Neidhardt
2018-03-02 20:13   ` Carlo Zancanaro
2018-03-02 18:04 ` Adonay Felipe Nogueira
2018-03-05 12:32 ` Adonay Felipe Nogueira
2018-03-05 14:00 ` Clément Lassieur
2018-03-23 13:29   ` Pierre Neidhardt
2018-03-25  5:34 ` Chris Marusich
2018-03-25  6:14   ` Pierre Neidhardt
2018-03-25 10:21   ` Hartmut Goebel
2018-03-27  9:45     ` Ludovic Courtès
2018-03-27 22:05     ` Mark H Weaver
2018-04-13 11:55       ` Hartmut Goebel
2018-03-25 10:57   ` Marius Bakke
2018-03-29  5:11     ` Chris Marusich
2018-05-01 19:30   ` Librem (was: Installation: Load non-free wifi firmware (iwlwifi)) Pierre Neidhardt
2018-05-02 18:07     ` Joshua Branson [this message]
2018-05-03  6:47       ` Librem Chris Marusich
2018-05-03  7:44         ` Librem Pierre Neidhardt
2018-05-09  6:07           ` Librem Chris Marusich
2018-05-09 16:58             ` Librem Nils Gillmann
2018-05-04 20:56         ` Librem Joshua Branson
2018-05-04 15:15     ` Librem (was: Installation: Load non-free wifi firmware (iwlwifi)) Christopher Lemmer Webber
2018-05-04 15:17       ` Pierre Neidhardt
2018-05-04 16:32       ` Librem Mike Gerwitz

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ygfh8nqylro.fsf@fastmail.com \
    --to=jbranso@fastmail.com \
    --cc=help-guix@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).