From: Jean Louis <bugs@gnu.support>
To: Yasuaki Kudo <yasu@yasuaki.com>
Cc: andrew <andrew@andrewyu.org>, Whistler <whistler_wmz@163.com>,
libreplanet-discuss@libreplanet.org
Subject: Re: (renamed) Misc mailing list
Date: Mon, 18 Apr 2022 15:39:27 +0300 [thread overview]
Message-ID: <Yl1b/z5YApGDLgA3@protected.localdomain> (raw)
In-Reply-To: <32805584-1B78-47AC-B940-202D5748CA08@yasuaki.com>
* Yasuaki Kudo <yasu@yasuaki.com> [2022-04-18 15:27]:
> (I have just 'replied all' from my (God forbid, proprietary!) IPhone
> so forgive me, the addresses in To or CC are pretty arbitrary)
That is absolutely not a problem. Almost all people come to know free
software from proprietary software.
> I often wonder what my escape hatch would be, if I lived in North
> Korea or something. I might learn how to be a good singer, a
> computer programmer, or anything else and stay away from politics.
Exactly.
> But there are many in-between states where the regime may mimic a
> shambolic 'democracy' just for the show, or strongly suppress
> unwanted opinions by murder, kidnap, etc and the majority would
> happily live without questioning too much, and not call the state
> totalitarian. The regime will allow a certain range of public
> discourse that are irrelevant or useful to the regime.
Yes, like EU "democracy".
> In such cases, and I suspect PRC may qualify, (But I don't know the
> country well enough) the discussion of Free Software might be within
> the permitted range of discourse, as its purported aim is just to
> promote a particular form of software licensing, no big deal.
I think in PRC there is no problem with free software, except in
government sections where they should know more about it.
Russia is now officially to reject US based proprietary software,
because it is US software, and thus will focus more on free
software. Same thing may happen in China.
--
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
next prev parent reply other threads:[~2022-04-19 14:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 7:01 Quick Check on COVID Lockdowns andrew via libreplanet-discuss
2022-04-11 3:10 ` Yasuaki Kudo
2022-04-13 5:59 ` Jean Louis
2022-04-13 21:09 ` Yasuaki Kudo
2022-04-13 23:05 ` Yuchen Pei
2022-04-14 15:28 ` (renamed) Misc mailing list andrew via libreplanet-discuss
2022-04-14 21:30 ` Jean Louis
2022-04-15 1:01 ` andrew via libreplanet-discuss
2022-04-15 19:56 ` Jean Louis
2022-04-16 10:47 ` andrew via libreplanet-discuss
2022-04-18 6:27 ` Jean Louis
2022-04-18 3:25 ` Whistler
2022-04-18 4:00 ` Whistler
2022-04-18 6:34 ` Jean Louis
2022-04-18 6:32 ` Jean Louis
2022-04-18 6:40 ` andrew via libreplanet-discuss
2022-04-18 7:30 ` Jean Louis
2022-04-18 10:53 ` andrew via libreplanet-discuss
2022-04-18 12:09 ` Jean Louis
2022-04-18 13:45 ` andrew via libreplanet-discuss
2022-04-18 12:26 ` Yasuaki Kudo
2022-04-18 12:39 ` Jean Louis [this message]
2022-04-18 12:52 ` andrew via libreplanet-discuss
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=Yl1b/z5YApGDLgA3@protected.localdomain \
--to=bugs@gnu.support \
--cc=andrew@andrewyu.org \
--cc=libreplanet-discuss@libreplanet.org \
--cc=whistler_wmz@163.com \
--cc=yasu@yasuaki.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 read-only IMAP folder(s) and NNTP newsgroup(s).