From: Paul Sutton via libreplanet-discuss <libreplanet-discuss@libreplanet.org>
To: libreplanet-discuss@libreplanet.org
Subject: Re: federated free software movement
Date: Mon, 15 Nov 2021 08:33:36 +0000 [thread overview]
Message-ID: <39835c25-7381-1432-a079-d62a78cb7683@disroot.org> (raw)
In-Reply-To: <08963fd909cf95f9b08528b74ed10ffc@basiscraft.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 3363 bytes --]
On 14/11/2021 20:27, Thomas Lord wrote:
>
> I think the FSF should have gone in this direction a long
> time ago.
>
> I think it is a very good idea to add to what you described:
>
> a. Distributed decentralized business models that are NOT
> "getting paid to program" or "getting paid to contribute
> to a software development project".
>
> b. Those business models aimed at spreading the personal
> use of free software, and enjoyment of software freedom,
> by people who don't program or who don't identify
> as programmers
>
> c. That includes both service and HW provisioning components.
>
> d. These businesses should be designed to keep product prices
> low, to increase accessibility -- yet include enough of a
> human element to be hard to reproduce at large scale.
>
> e. The businesses should achieve real economies of scale through ...
> federation.
>
> Trivial boring example: Entry level desktops, preloaded, with
> support -- and a federation of those businesses that cooperates
> freely to maintain the shared distribution they use.
>
> Of course, that kind of thing can be infinitely specialized -- e.g.
> a federation of small businesses that provide DAWs (music production
> and performance software).
>
> The idea is to make enough money to live comfortably without
> trying to hoard software, supporting a lifestyle of cooperating
> on maintaining and extending that software freely.
>
> -t
+1
We could add to this that the environmental impact is that we also get
to use older hardware longer, I think there is some research somewhere
on the cost making new laptops vs using older laptops for longer until
they just stop working.
I know there are movements such as free cycle that that take hardware
and recycle it, this also creates jobs etc.
Paul
>> What if there was a combined Free Software, OSHW and Right to Repair
>> group, providing ideological leadership in a peer to peer fashion via
>> federated services (including Git-based code hosting) and an emphasis
>> on teaching how to self-host your own federated hosting
>> infrastructure?
>>
>> I'm discussing this on my twitter too:
>> [1]https://twitter.com/n4of7/status/1459522798892859399
>>
>> And on Mastodon. [2]https://mas.to/@libreleah/107270135261193137
>>
>> However, I'm also seeking discussion here on this list.
>>
>> I wish to gauge the public's response before I proceed for real. Plus,
>> I intend to bring people onboard to help me start this new initiative.
>>
>> References
>>
>> 1. https://twitter.com/n4of7/status/1459522798892859399
>> 2. https://mas.to/@libreleah/107270135261193137
>>
>> _______________________________________________
>> libreplanet-discuss mailing list
>> libreplanet-discuss@libreplanet.org
>> https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
>
> _______________________________________________
> libreplanet-discuss mailing list
> libreplanet-discuss@libreplanet.org
> https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
--
--
Paul Sutton, Cert Cont Sci (Open)
https://personaljournal.ca/paulsutton/
Pronoun : him/his/he
OpenPGP : 4350 91C4 C8FB 681B 23A6 7944 8EA9 1B51 E27E 3D99
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 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-15 8:34 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 [this message]
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
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=39835c25-7381-1432-a079-d62a78cb7683@disroot.org \
--to=libreplanet-discuss@libreplanet.org \
--cc=paulsutton@disroot.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).