LibrePlanet discussion list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: Dennis Payne <dulsi@identicalsoftware.com>
To: Akira Urushibata <afu@wta.att.ne.jp>,
	libreplanet-discuss@libreplanet.org
Subject: Re: Voting machines not AI code
Date: Tue, 15 Aug 2023 13:35:47 -0400	[thread overview]
Message-ID: <7313ec2b44211a6e576d81704b0dd51b65207502.camel@identicalsoftware.com> (raw)
In-Reply-To: <2023.08.15.07.55.26.366199275@afu.wta.att.ne.jp>

You want to write a message with the subject "GPL on AI generated code"
make the message about that.

You want to write a post about the problems of proprietary code in
voting machines that's fine. Find good examples or explain what could
be the problem.

Don't go to the 2020 USA election. It is not a useful example of the
advantages of free software. It wouldn't of mattered how the election
was done. Fraud claims happened because the result wasn't what Trump
wanted. If the software was free software, he still would have claimed
poll workers scanned different voter forms or changed the data on the
drive or whatever.

-- 
Dennis Payne
dulsi@identicalsoftware.com
https://mastodon.gamedev.place/@dulsi



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

  parent reply	other threads:[~2023-08-16 14:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14 22:55 GPL on AI generated code Akira Urushibata
2023-08-15 16:33 ` Runxi Yu via libreplanet-discuss
2023-08-15 17:35 ` Dennis Payne [this message]
2023-08-16 20:21   ` Voting machines not AI code Ali Reza Hayati
2023-08-16  0:34 ` Non-free software in voting machines Akira Urushibata
2023-08-16  3:41 ` GPL on AI generated code Alexandre Oliva

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=7313ec2b44211a6e576d81704b0dd51b65207502.camel@identicalsoftware.com \
    --to=dulsi@identicalsoftware.com \
    --cc=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).