unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Alexandre Garreau <galex-713@galex-713.eu>
To: Jacob Hrbek <kreyren@rixotstudio.cz>
Cc: help-gnu-emacs@gnu.org, Richard Stallman <rms@gnu.org>,
	Jean Louis <bugs@gnu.support>
Subject: Re: no to war in Ukraine
Date: Mon, 28 Feb 2022 16:39:49 +0100	[thread overview]
Message-ID: <5084430.J0GBE4kE0S@galex-713.eu> (raw)
In-Reply-To: <2f3aadc4-4b1e-431e-bdd5-6b6406eb5419@rixotstudio.cz>

Le lundo, 28-a de februaro 2022, 16-a horo kaj 10:57 CET Jacob Hrbek a écrit :
>  > It can, and it would, but nobody have shown any example of this 
> 
> happening (like a specific example of a software used by putin’s army).
> -- Garreau
> 
> Putin literally has linux on his PC and russia _runs_ on linux

That’s unspecific.  If it wasn’t Linux it could be kOpenBSD, kFreeBSD, kNetBSD, Mach, 
whole XNU, NT or Flushia.  It doesn’t change a shit.  And Linux is well known to most often 
be proprietary and for its developer to care little about copyleft and freedom, only about 
efficient development methods.

Now it looks like you are suggesting every software developer, says Linux’s ones, 
implement a surveillance system that asks to each user to identify themselves (for 
instance on the basis of citizenship) in order to use the software.  Some sort of DRM.  And 
you somewhat hope naively it won’t be then used back to do the same kind of oppression 
Putin is doing on Ukraine (if that surveillance system is controlled by US, it would have 
been Iraq, if China, Taiwan, if France, Niger, if Russia, Finland (hell, Linus’ originating 
country), etc. etc.).

Are you really naive enough to think any kind of oppression, control, power is incorruptible?

If it was Czechia, do you think it would be safe against putin’s army materially breakin’ in 
there, cracking it, and using it in their own favor?

Then the US would want to avoid that, and would invade Czechia (at least digitally), just as 
they recently convinced Slovakia to give up on their sovereignty in front of Russia’s threat, 
or like they have shown to illegally store nuclear weapons on antinuclear germany, hidding 
that from its citizens.

Don’t ceade to emotion and fear as you’ll end up more fragile for defending freedom(

>  > I am really, really, deeply sorry, we are in the same shit rn.  I try
>  > 
> 
> to keep calm by thinking of it like an abscess we have to burn out at 
> some point.  Putin always have been a threat anyway.  Some solution have
> 
 to be found.
> 
> 
>  > Unfortunately, nobody in this list has a solution.  Even your 
> 
> propositions are dummy, inefficient, and misdirected (you were 
> suggesting to remove freedoms of the people oppressed by the same 
> oppressor, and among the most numerous one to protest against him). -- 
> Garreau
> 
> I proposed asking yourself an ethical question whether releasing your 
> work could be used as a major enabler in russian military,

Yes it could.  And if I make food, and sell it, it could be reselled to russians.  That’s no 
reason to, say, engineer a selective bacteria that would pretendously only target russian 
DNA, put it in food, and write on it «not for russians!!!».  That would be very stupid and 
would do more harms to humans in general and russian resistance against putin that to the 
russian military (that has access to all the other food anyway).

The only narrative I can see to support that is both the one that ignores that DRM is both 
ineffective and elitistly ends up always turning back against the general public (but some 
crackers), and the narrative that if something just is needed, the whole world will gather 
together in favor of it (no, you cannot trust the whole world to act in a single direction 
coordinately, it never happens that way but in US movies).

> if yes then 
> take appropriate steps to either de-weaponize it

Do you write weapons? because your stance and speaking point really puzzles me, why 
worrying about that? what are your works that could be used against ukrainians?

Also it looks like DRM.

> or impose appropriate
> restrictions to make the software not accessible to them

You mean censorship.  Ok that’s slightly less uneffective, but still is.  Russians already are 
used to avoid their own govt’s censorship, they’d avoid most easily yours.  How would you 
do that??

> or not as
> harmful and i proposed integrating a VPN for FSF associate members for
> FSF to moderate and move our sensitive projects on it.

Why?

> Note that those are projected to be a _TEMPORARY_ measures so i would 
> even go as far to implement malware that triggers when RU IP is assigned
> to the system.

In the end you would harm more antiputin ppl than proputin one, so by defending 
oppression (in general, for the sake of liberation), and attacking freedom, you would in the 
end… defend oppression (russian’s one) and attacking freedom (including of ukrainians).

You seem to be under the effect of so strong emotion that the subliminal narrative of 
oppression grows in your mind so much that it can bypass reason and turns back against 
yourself.  Please hold a minute and reflect a bit about actual consequences.

That’s sad but sometimes we are helpless.  It happens.  Even dosomethingite and running 
in the wrong direction won’t help.


  reply	other threads:[~2022-02-28 15:39 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-26 12:31 phantom invasion and ghostly resistance Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-26 14:36 ` Jean Louis
2022-02-27  8:57   ` Christopher Dimech
2022-02-26 23:57 ` no to war in Ukraine Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-27  0:02   ` Jacob Hrbek
2022-02-27  0:17     ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-27  0:18       ` Jacob Hrbek
2022-02-27  0:24         ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-27  0:59           ` Po Lu
2022-02-27  8:46         ` Alexandre Garreau
2022-02-28  9:17       ` butterfly effect Jean Louis
2022-03-01  9:47       ` no to war in Ukraine Uwe Brauer
2022-03-01 10:35         ` goncholden
2022-03-01 10:45           ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-01 11:00             ` goncholden
2022-03-01 12:37               ` Uwe Brauer
2022-03-01 13:09                 ` goncholden
2022-03-01 13:12                   ` Uwe Brauer
2022-03-01 13:35                     ` goncholden
2022-03-01 14:02                     ` goncholden
2022-03-01 14:34                       ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-01 14:52                         ` Jacob Hrbek
2022-03-01 15:29                           ` goncholden
2022-03-01 14:05                     ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-01 13:59               ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-01 10:41         ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-27  1:10     ` Dmitry Gutov
2022-02-27  1:27       ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-27  8:48       ` Alexandre Garreau
2022-02-27 11:18       ` Jacob Hrbek
2022-02-27 11:35         ` Christopher Dimech
2022-02-27 18:31         ` Dmitry Gutov
2022-02-27 18:40           ` Christopher Dimech
2022-02-28  9:23           ` Jean Louis
2022-02-28  9:22         ` Jean Louis
2022-02-28  9:19       ` Jean Louis
2022-02-28 13:22         ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-28 13:45           ` Samuel Banya
2022-02-28  9:16     ` Jean Louis
2022-02-28 11:46       ` Jacob Hrbek
2022-02-28 12:42         ` Christopher Dimech
2022-02-28 13:35           ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-28 14:44             ` Alexandre Garreau
2022-02-28 14:49               ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-28 13:50         ` Alexandre Garreau
2022-02-28 15:10           ` Jacob Hrbek
2022-02-28 15:39             ` Alexandre Garreau [this message]
2022-03-01  4:24           ` Richard Stallman
2022-03-01  9:22             ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-01  4:24           ` Richard Stallman
2022-02-27  7:49   ` Alexandre Garreau
2022-02-27  8:05     ` Po Lu
2022-02-27  8:39       ` Christopher Dimech
2022-02-27  8:58         ` Alexandre Garreau
2022-02-27  9:23           ` Christopher Dimech
2022-02-27  8:53       ` Alexandre Garreau
2022-02-27  9:51         ` Christopher Dimech
2022-02-27 11:19           ` Alexandre Garreau
2022-02-27 11:44             ` Christopher Dimech
2022-02-27 10:12         ` Po Lu
2022-02-27 10:22           ` Christopher Dimech
2022-02-27 10:25             ` Po Lu
2022-02-27 11:15               ` Christopher Dimech
2022-02-27 11:31                 ` Alexandre Garreau
2022-02-27 11:54                   ` Christopher Dimech
2022-02-27 11:48                 ` Po Lu
2022-02-27 11:53                   ` Eli Zaretskii
2022-02-27 12:00                     ` Christopher Dimech
2022-02-27 12:06                   ` Christopher Dimech
2022-02-27 12:14                   ` Alexandre Garreau
2022-02-27 10:52             ` tomas
2022-02-27 11:24               ` Christopher Dimech
2022-02-27 11:24             ` Alexandre Garreau
2022-02-27 11:48               ` Christopher Dimech
2022-02-27 11:54                 ` Po Lu
2022-02-27 12:13                 ` Alexandre Garreau
2022-02-27 11:22           ` Alexandre Garreau
  -- strict thread matches above, loose matches on Subject: below --
2022-02-27  3:25 emacsq
2022-02-27  8:09 ` goncholden
2022-02-27  8:51 ` Alexandre Garreau
2022-02-28 15:26   ` emacsq via Users list for the GNU Emacs text editor
2022-02-28 15:30     ` emacsq via Users list for the GNU Emacs text editor
2022-03-01 17:13 Humberto Freitas
2022-03-01 17:11 ` goncholden
2022-03-01 19:33 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-01 19:54   ` goncholden
2022-03-01 20:05     ` Emanuel Berg via Users list for the GNU Emacs text editor

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=5084430.J0GBE4kE0S@galex-713.eu \
    --to=galex-713@galex-713.eu \
    --cc=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    --cc=kreyren@rixotstudio.cz \
    --cc=rms@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).