From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: tomas@tuxteam.de
Cc: guile-user@gnu.org
Subject: Re: GPT-4 knows Guile! :)
Date: Mon, 20 Mar 2023 00:18:31 +0100 [thread overview]
Message-ID: <87jzzcb9wa.fsf@web.de> (raw)
In-Reply-To: <ZBbLCMS7ffsyvyjT@tuxteam.de>
[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]
<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.
Some quotes:
> Does this mean that the CreativeML Open RAIL-M license makes output
> from the model incompatible with copyleft Free Culture and Free
> Software licenses, so it would for example be illegal to use any of
> the output in Wikipedia? Is there legal uncertainty about that?
…
> The first thing to say is that this license is about as far away from
> open source as it could possibly get.
…
>> "No use of the output can contravene any provision as stated in the License.".
> A Japanese lawyer I know told me that, in general terms, releasing
> output under the CC-BY could be a violation of the license if such a
> provision exists. (* He is not familiar with this license and has not
> reviewed it in detail)
No answer from the developers.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2023-03-19 23:18 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 [this message]
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
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=87jzzcb9wa.fsf@web.de \
--to=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).