From: Akira Urushibata <afu@wta.att.ne.jp>
To: libreplanet-discuss@libreplanet.org
Subject: Re: why isn't stallman on lp2022 speakers list?
Date: Mon, 21 Mar 2022 08:49:14 +0900 (added by postmaster@msrg2031.rgserv.att.ne.jp) [thread overview]
Message-ID: <2022.03.21.0841.24534@afu.wta.att.ne.jp> (raw)
In-Reply-To: <54103f10998fc4c048b19ae0f63c1d46@basiscraft.com>
It is nice to hear from someone who worked on GNU in the early days.
I thank Mr. Thomas Lord for his contributions to GNU Sed.
Recently there is much talk on this list on preventing Russians from
acquiring free software. I believe we should rather consider how to
accurately inform people around the world about the software they use.
Thomas Lord wrote:
>
> I really loved reading this as someone who once had a
> good job as a GNU project grunt working on tasks like
> improving GNU sed(1), writing code on Sun and HP workstations
> either that the FSF had scored or that kind people at
> Carnegie Mellon let me use for that purpose. It is
> interesting and strange to see how what to me is a long
> and nuanced history is, indeed, for many younger people
> today, a vague and obscure tale about stuff that
> happened before they were born.
>
> It still feels like the movement is only just getting started
> even if it's already changed "everything". :-) And it gives
> me some hope in the face how exploitative and controlling the
> proprietary landscape of cell phones and apps and web-centric
> surveillance have become meanwhile.
>
> Go forth and with destroy(*) with creativity and software
> freedom! (*: freedom-robbing, malicious, ubiquitous, software
> practices).
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2022-03-21 14:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 11:25 why isn't stallman on lp2022 speakers list? Dora Scilipoti
2022-03-13 19:22 ` Adrienne G. Thompson
2022-03-13 20:02 ` Kaio Duarte Costa
2022-03-16 0:12 ` Akira Urushibata
2022-03-16 22:45 ` Thomas Lord
2022-03-20 23:49 ` Akira Urushibata [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-08 21:30 Jim Fulner
2022-03-08 21:42 ` Jean Louis
2022-03-08 23:03 ` Jim Fulner
2022-03-09 0:41 ` Jean Louis
2022-03-08 22:19 ` Thomas Lord
2022-03-05 22:46 Dora Scilipoti
2022-03-06 2:25 ` Kaio Duarte Costa
2022-03-06 16:18 ` Dora Scilipoti
2022-03-06 18:44 ` Dora Scilipoti
2022-03-06 20:50 ` Kaio Duarte Costa
[not found] <881589586.491440.1646362340639.ref@mail.yahoo.com>
2022-03-04 2:52 ` Lori Nagel via libreplanet-discuss
2022-03-04 4:36 ` Jean Louis
2022-03-01 1:34 Dora Scilipoti
2022-02-27 0:02 Leah Rowe via libreplanet-discuss
2022-03-03 18:57 ` Adrienne G. Thompson
2022-03-03 19:21 ` Danny Spitzberg
2022-03-16 22:23 ` Yuchen Pei
2022-03-16 22:37 ` Thomas Lord
2022-03-03 20:04 ` Pedro Lucas Porcellis
2022-03-03 21:33 ` Kaio Duarte Costa
2022-03-04 4:25 ` Jean Louis
2022-03-04 15:21 ` Danny Spitzberg
2022-03-04 15:28 ` Jean Louis
2022-03-04 16:19 ` Danny Spitzberg
2022-03-04 17:17 ` Adrienne G. Thompson
2022-03-05 9:22 ` Danny Spitzberg
2022-03-06 17:52 ` Adrienne G. Thompson
2022-03-06 18:18 ` Danny Spitzberg
2022-03-07 14:57 ` Jean Louis
2022-03-06 21:31 ` Kaio Duarte Costa
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=2022.03.21.0841.24534@afu.wta.att.ne.jp \
--to=afu@wta.att.ne.jp \
--cc=libreplanet-discuss@libreplanet.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).