From: Valentino Giudice <valentino.giudice96@gmail.com>
To: Michael McMahon <michael@fsf.org>
Cc: libreplanet-discuss@libreplanet.org
Subject: Re: Minds.com
Date: Thu, 21 Sep 2023 19:55:55 +0200 [thread overview]
Message-ID: <CANC0hWj2fnQfnUr0a8uFHNMzRQR0h5ML1d+nAqjEEckTH7qVmw@mail.gmail.com> (raw)
In-Reply-To: <23e8b9c2-a729-f775-e079-e4fcfcaf4511@fsf.org>
[-- Attachment #1.1: Type: text/plain, Size: 2108 bytes --]
> Minds could be categorized as a "free speech zone" social network which
> are typically popular with fascists so count me out.
Fascism and freedom of speech are entirely incompatible and antithetical to
each other.
It could be true that fascist today use free speech platforms, but it is
certainly not what they desire.
From reading from the FSF/GNU websites, it has always been my impression
that freedom of speech is valued by the free software community, in a way
it certainly is not by fascists.
Indeed, filtering what one reads and publicly writes through the erratic
whims of some corporation, typically guided by capitalist interests and the
need to applease advertisers, as it usually happens on most platforms (such
as X and Facebooks), implies restricting one's behavior in a way akin to
what proprietary software leads to.
> The licensing of the minds project is also questionable.
Elgg dual-licenses the project, except plugins, under both the MIT license
and the GPL 2.
Obviously, if someone uses the whole of Elgg, they effectively have to use
it under the GPL 2.
Now, I agree with the GitHub comment, on the Elgg issue, that you
referenced. Indeed, if Elgg is packaged with GPL-2.0 only plugins, it must
have the GPL-2.0-only license (as a package).
However, the issue is specifically about the identifier of the license for
the whole package (for automated tools), which is not what is in question
here.
If someone uses Ellg without plugins, they can do so under the MIT license,
which is, of course, AGPL-compatible.
The project which is actually derived from Elgg is:
https://gitlab.com/minds/engine
Indeed, the situation wasn't clear to me at first, so I asked.
Minds is using the portion of Elgg which is released under the MIT license
and is complying with the MIT license (in a way my dumb self didn't notice
because I looked everywhere except the LICENSE file, which I assumed to be
just the text of the AGPL): https://gitlab.com/minds/engine/-/issues/2647
I do have some issues with Minds, but as far as licensing is concerned, in
relation to Elgg, it seems fine with me.
[-- Attachment #1.2: Type: text/plain, Size: 2322 bytes --]
> Minds could be categorized as a "free speech zone" social network
which
> are typically popular with fascists so count me out.
Fascism and freedom of speech are entirely incompatible and
antithetical to each other.
It could be true that fascist today use free speech platforms, but it
is certainly not what they desire.
From reading from the FSF/GNU websites, it has always been my
impression that freedom of speech is valued by the free software
community, in a way it certainly is not by fascists.
Indeed, filtering what one reads and publicly writes through the
erratic whims of some corporation, typically guided by capitalist
interests and the need to applease advertisers, as it usually happens
on most platforms (such as X and Facebooks), implies restricting one's
behavior in a way akin to what proprietary software leads to.
> The licensing of the minds project is also questionable.
Elgg dual-licenses the project, except plugins, under both the MIT
license and the GPL 2.
Obviously, if someone uses the whole of Elgg, they effectively have to
use it under the GPL 2.
Now, I agree with the GitHub comment, on the Elgg issue, that you
referenced. Indeed, if Elgg is packaged with GPL-2.0 only plugins, it
must have the GPL-2.0-only license (as a package).
However, the issue is specifically about the identifier of the license
for the whole package (for automated tools), which is not what is in
question here.
If someone uses Ellg without plugins, they can do so under the MIT
license, which is, of course, AGPL-compatible.
The project which is actually derived from Elgg
is: [1]https://gitlab.com/minds/engine
Indeed, the situation wasn't clear to me at first, so I asked.
Minds is using the portion of Elgg which is released under the MIT
license and is complying with the MIT license (in a way my dumb self
didn't notice because I looked everywhere except the LICENSE file,
which I assumed to be just the text of the
AGPL): [2]https://gitlab.com/minds/engine/-/issues/2647
I do have some issues with Minds, but as far as licensing is
concerned, in relation to Elgg, it seems fine with me.
References
1. https://gitlab.com/minds/engine
2. https://gitlab.com/minds/engine/-/issues/2647
[-- Attachment #2: Type: text/plain, Size: 184 bytes --]
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2023-09-21 19:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 3:43 Minds.com Valentino Giudice
2023-09-20 15:03 ` Minds.com Michael McMahon
2023-09-20 23:27 ` Minds.com Valentino Giudice
2023-09-21 14:40 ` Minds.com Michael McMahon
2023-09-21 17:55 ` Valentino Giudice [this message]
2023-09-21 18:26 ` Minds.com Michael McMahon
2023-09-21 21:45 ` Minds.com Valentino Giudice
2023-09-21 23:59 ` Minds.com Leland Best
2023-09-23 2:16 ` Minds.com Valentino Giudice
2023-09-21 23:33 ` Minds.com Ron Nazarov via libreplanet-discuss
2023-09-22 2:23 ` Minds.com Valentino Giudice
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=CANC0hWj2fnQfnUr0a8uFHNMzRQR0h5ML1d+nAqjEEckTH7qVmw@mail.gmail.com \
--to=valentino.giudice96@gmail.com \
--cc=libreplanet-discuss@libreplanet.org \
--cc=michael@fsf.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).