LibrePlanet discussion list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Arthur Torrey <arthur_torrey@comcast.net>
Cc: Yuchen Pei <hi@ypei.me>, Jean Louis <bugs@gnu.support>,
	vidak@riseup.net, libreplanet-discuss@libreplanet.org
Subject: Re: federated free software movement
Date: Sat, 27 Nov 2021 09:28:04 +0300	[thread overview]
Message-ID: <YaHP9IRMLCA/y06y@protected.localdomain> (raw)
In-Reply-To: <1734838452.315801.1637111420644@connect.xfinity.com>

* Arthur Torrey <arthur_torrey@comcast.net> [2021-11-17 04:12]:
> 3. Reality check - You have a repair shop - customers come to you
> with hardware that needs fixing and needs proprietary tools to do
> so.  Which benefits your business more - gritting your teeth and
> using the tools, or telling the customers they made a bad choice in
> hardware and sending them away???

That is matter of ethical attitude or viewpoint that hardware shop
owners have.

You do not appear to have the same ethical viewpoint as me. So people
are different, but please do not push on this mailing list how people
shall be opportunistic for money and succumb to proprietary
software. It is really wrong list for such propaganda.

There are companies that have ethical viewpoints and sell such
hardware that does not require proprietary software.

LibrePlanet is all about free software.

> 4. Personal reality - I mentioned earlier that I need a proprietary
> closed software program that only runs on a proprietary OS in order
> to adjust the programming on my power chair...  I got a comment back
> that I should figure out how to do it w/ Free Software.... 

LibrePlanet is all about free software. That you have hardware and
software that does not give you freedom is already clear.

How about presenting the power chair and how it looks like, that
people can see how it can be replaced or made with free software?
Start a project, ask for help, let us understand what exactly is the
hardware that you wish to run, so maybe interested parties find way to
provide similar hardware and software without proprietary chains.

> So let me see, I have a proprietary undocumented piece of hardware
> that I need to totally reverse engineer from the hardware
> communications protocol to it's internal data structures, along w/
> how to read and write to it (as a non-programmer) OR use an existing
> set of non-free tools that already does what I need?  (and there is
> *NO* commercially available Free Software compatible wheelchair
> control hardware, I'm using what is arguably the most open of the
> available systems) Tough decision....(NOT!)  If I wasn't already a
> Free Software supporter, where do you think I might have told the
> person telling me to figure out how to use free software to stick
> his GNU?

😀 How about you show first that wheelchair on picture and video, that
we understand features and functions of it.


-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/

_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss

  parent reply	other threads:[~2021-11-29 16:32 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-14  2:03 federated free software movement Arthur Torrey
2021-11-14  4:18 ` vidak
2021-11-14 19:16   ` Arthur Torrey
2021-11-14 20:26     ` Jean Louis
2021-11-14 20:31     ` Jean Louis
2021-11-16  7:24       ` Yuchen Pei
2021-11-17  1:10         ` Arthur Torrey
2021-11-21  1:34           ` jahoti via libreplanet-discuss
2021-11-27  6:28           ` Jean Louis [this message]
2021-11-29  3:22             ` Arthur Torrey
2021-11-29 22:00               ` Yuchen Pei
2021-11-29 23:46                 ` Arthur Torrey
2021-11-30  8:04                 ` Paul Sutton via libreplanet-discuss
2021-11-30 10:26                   ` Jean Louis
  -- strict thread matches above, loose matches on Subject: below --
2021-11-13 14:29 Leah Rowe via libreplanet-discuss
2021-11-13 14:29 Leah Rowe via libreplanet-discuss
2021-11-13 16:30 ` Robert Read
2021-11-13 22:22 ` Jean Louis
2021-11-14  0:41 ` Jacob Hrbek
2021-11-14  0:51 ` Lohan G
2021-11-14 17:04 ` Leah Rowe via libreplanet-discuss
2021-11-14 19:40   ` Paul Sutton via libreplanet-discuss
2021-11-14 20:04 ` Miles Fidelman
2021-11-14 20:27 ` Thomas Lord
2021-11-15  8:33   ` Paul Sutton via libreplanet-discuss
2021-11-16  7:32 ` Yuchen Pei
2021-11-16 12:49 ` Paul Sutton via libreplanet-discuss
2021-11-16 18:21 ` Leah Rowe via libreplanet-discuss
2021-11-16 19:45   ` Dennis Payne
2021-11-21  1:45     ` jahoti via libreplanet-discuss
2021-11-22 21:49       ` Yuchen Pei
2021-11-23 18:02         ` Paul Sutton via libreplanet-discuss
2021-11-23 21:05           ` Dennis Payne
2021-11-23 21:24             ` Paul Sutton via libreplanet-discuss
2021-11-17  0:51   ` Lohan G

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.gnu.org/mailman/listinfo/libreplanet-discuss

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

  git send-email \
    --in-reply-to=YaHP9IRMLCA/y06y@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=arthur_torrey@comcast.net \
    --cc=hi@ypei.me \
    --cc=libreplanet-discuss@libreplanet.org \
    --cc=vidak@riseup.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).