From: jahoti via libreplanet-discuss <libreplanet-discuss@libreplanet.org>
To: libreplanet-discuss@libreplanet.org
Subject: Re: federated free software movement
Date: Sun, 21 Nov 2021 01:45:00 +0000 [thread overview]
Message-ID: <a22ac84b-67d8-6c4b-5557-70cccfc2331d@envs.net> (raw)
In-Reply-To: <e2821a86cf9018180f52b965afe24d1e5639ed5d.camel@identicalsoftware.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1352 bytes --]
On 11/16/21 7:45 PM, Dennis Payne wrote:
> I don't see how a federated wikipedia would work. Even if you banned
> obvious trolls, how would you deal with contentious issues? Federation
> isn't some magical technologies that immediately makes everything
> better.
For the case of contentious issues, Stallman did make an interesting
suggestion in his essay proposing a free encyclopaedia that multiple
versions of an article could be offered. I don't know how that would be
technically implemented, yet it might be a viable option.
> An emphasis on self-hosting is not a good idea in my opinion. It is
> great that we are not locked into a commercial provider but most people
> don't want to self-host. Self-hosting is work. Some people will
> certainly do that but thankfully some of them allow the rest of us to
> use their service. While I can run my own mastadon, I don't want to.
>
> (That being said, it should be easy to setup a self-host. I was on a
> Hubzilla instance but it broke and the admin could not figure out how
> to fix it. For Hubzilla they provide support using Hubzilla. So if you
> have a problem on your instance, you need to register on another
> instance so you can ask for help.)
Alyssa Rosenzweig wrote an interesting article on this:
https://rosenzweig.io/blog/the-federation-fallacy.html
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
[-- 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:[~2021-11-22 14:58 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 14:29 federated free software movement Leah Rowe via libreplanet-discuss
2021-11-13 16:30 ` Robert Read
2021-11-13 22:22 ` Jean Louis
2021-11-14 0:41 ` Jacob Hrbek
2021-11-14 0:51 ` Lohan G
2021-11-14 17:04 ` Leah Rowe via libreplanet-discuss
2021-11-14 19:40 ` Paul Sutton via libreplanet-discuss
2021-11-14 20:04 ` Miles Fidelman
2021-11-14 20:27 ` Thomas Lord
2021-11-15 8:33 ` Paul Sutton via libreplanet-discuss
2021-11-16 7:32 ` Yuchen Pei
2021-11-16 12:49 ` Paul Sutton via libreplanet-discuss
2021-11-16 18:21 ` Leah Rowe via libreplanet-discuss
2021-11-16 19:45 ` Dennis Payne
2021-11-21 1:45 ` jahoti via libreplanet-discuss [this message]
2021-11-22 21:49 ` Yuchen Pei
2021-11-23 18:02 ` Paul Sutton via libreplanet-discuss
2021-11-23 21:05 ` Dennis Payne
2021-11-23 21:24 ` Paul Sutton via libreplanet-discuss
2021-11-17 0:51 ` Lohan G
-- strict thread matches above, loose matches on Subject: below --
2021-11-13 14:29 Leah Rowe via libreplanet-discuss
2021-11-14 2:03 Arthur Torrey
2021-11-14 4:18 ` vidak
2021-11-14 19:16 ` Arthur Torrey
2021-11-14 20:26 ` Jean Louis
2021-11-14 20:31 ` Jean Louis
2021-11-16 7:24 ` Yuchen Pei
2021-11-17 1:10 ` Arthur Torrey
2021-11-21 1:34 ` jahoti via libreplanet-discuss
2021-11-27 6:28 ` Jean Louis
2021-11-29 3:22 ` Arthur Torrey
2021-11-29 22:00 ` Yuchen Pei
2021-11-29 23:46 ` Arthur Torrey
2021-11-30 8:04 ` Paul Sutton via libreplanet-discuss
2021-11-30 10:26 ` Jean Louis
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=a22ac84b-67d8-6c4b-5557-70cccfc2331d@envs.net \
--to=libreplanet-discuss@libreplanet.org \
--cc=jahoti@envs.net \
/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).