unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>, tomas@tuxteam.de
Cc: guile-user@gnu.org
Subject: Re: GPT-4 knows Guile! :)
Date: Mon, 20 Mar 2023 10:56:38 +0000	[thread overview]
Message-ID: <2cc18425-c5dc-0ff8-1bc2-5c9a97386296@posteo.de> (raw)
In-Reply-To: <87jzzcb9wa.fsf@web.de>

On 3/20/23 00:18, Dr. Arne Babenhauserheide wrote:
> <tomas@tuxteam.de> writes:
>> which has tried to be free (in both senses). For images, there is
>> Stable Diffusion (disclaimer:I don't know much about them). For
>> raw data, there's Common Crawl [3], which is Stable Diffusion's
> Stable diffusion has one of the most evil licenses I’ve read till now:
> using its images seems to be allowed for almost all proprietary uses,
> but illegal for free culture use. See the explicit questions about that
> here: https://github.com/CompVis/stable-diffusion/issues/131
>
> A license that makes its output only usable for proprietary creations
> but not for free culture is like the polar opposite of the GPL or CC
> by-sa: making a tool that gives proprietary creations an advantage over
> Free Culture.

That would double evil, since they most likely trained their stuff on freely 
available things. Basically taking from our culture, but not giving anything 
back and netting the profits.

My biggest concerns about these big machine learning models are:

(1) The laundering character, be it code, other texts, prose and to on, or 
artworks.—What and where are their sources? Complete list of inputs? Where is a 
form, that allows me to make my works invisible to past, present and future 
models they produce, without being tracked by Google and its ilk? How will 
artists and others be able to safely, securely, and unambiguously tell them 
"no"? Oh wait, it is basically impossible to remove something from a learned 
model after the fact. Duh! How about asking beforehand?

In the end it is the same typical kind of shitty behavior we see from entities 
like FB, oh wait, they call themselves "Meta" now lol.: "Oh what you want is 
soooo complicated to do and would be sooo much effort! We cannot possibly be 
expected to do that, so sorry!"—Well then don't start doing what you do in the 
first place! If doing it ethically does not scale, then don't friggin start scaling!

(2) Establishment of paywalls and unethical registration forms. Soon some 
employers might ask their employees to "be more efficient" by using GPT models 
and either buying licenses, or even demanding employees buy them themselves, 
while of course completely neglecting to think about the license terms or what 
happens to the data we input into those prompts. Registration might even require 
us to input personal data, like where we live or our names.

(3) Also no one seems to think about not being able to use these tools on 
ethical grounds: I visited the GTP website and thought: "OK lets give it a 
try.", but then I could not even do that, unless I allowed tech giants to track 
me. No thanks! Tab closed. Given how they seems to act so far, I do not expect 
them to set up any sane login or website any time soon.

(4) It might take years again before any of that gets properly regulated. First 
it might be shittly regulated, because of governments not asking experts or if 
asking experts asking the ones with heavy bias for their employers (like 
consulting Microsoft for publicly in government used software …).

Regards,
Zelphir

-- 
repositories: https://notabug.org/ZelphirKaltstahl




  parent reply	other threads:[~2023-03-20 10:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 16:01 GPT-4 knows Guile! :) Mikael Djurfeldt
2023-03-17 17:25 ` Mikael Djurfeldt
2023-03-17 19:09   ` Damien Mattei
2023-03-17 19:28     ` Damien Mattei
2023-03-18  7:42       ` James Crake-Merani
2023-03-18  8:10         ` Mikael Djurfeldt
2023-03-18  8:29         ` tomas
2023-03-18 10:52           ` James Crake-Merani
2023-03-18 12:00             ` Mikael Djurfeldt
2023-03-18 12:03               ` Mikael Djurfeldt
2023-03-19  8:42                 ` tomas
2023-03-19 23:18                   ` Dr. Arne Babenhauserheide
2023-03-20  1:39                     ` Nala Ginrut
2023-03-20  4:53                       ` Dr. Arne Babenhauserheide
2023-03-20  8:04                         ` tomas
2023-03-20  8:00                     ` tomas
2023-03-20 10:56                     ` Zelphir Kaltstahl [this message]
2023-03-20 11:20                       ` tomas
     [not found]   ` <ZBViQz4I3E4Qb08Q@tuxteam.de>
     [not found]     ` <CAA2XvwJY1mX9rjVvwL3yATSt1+f86JkdkEFa55L8g4rrZ_tX5A@mail.gmail.com>
     [not found]       ` <ZBVyyU8xGng2imNB@tuxteam.de>
     [not found]         ` <CAA2XvwJmCe2DNc+45S8yMtHFhNYZBRS5ukjnZxWzDtt9iT1mmw@mail.gmail.com>
     [not found]           ` <ZBV3/e97xfI14i/M@tuxteam.de>
     [not found]             ` <CAA2XvwJxuECNYf3M+ako3KS8j8OGG6caYVSQY1ygiXaTWxSY0g@mail.gmail.com>
     [not found]               ` <ZBV6eP4DUuBlTymg@tuxteam.de>
     [not found]                 ` <CAA2XvwLOqBr1cxC+ZpVOXdw7Tto7hZCifUO7mFF6wM071T3Dqg@mail.gmail.com>
     [not found]                   ` <CAA2Xvw+pTXC2RO-epuiV-+ChaNWzrdQ4n_ATwutkQ3n7sq5GBw@mail.gmail.com>
2023-03-18  9:23                     ` Damien Mattei

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/guile/

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

  git send-email \
    --in-reply-to=2cc18425-c5dc-0ff8-1bc2-5c9a97386296@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --cc=arne_bab@web.de \
    --cc=guile-user@gnu.org \
    --cc=tomas@tuxteam.de \
    /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).