• 5 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle



  • There is a clause about redistribution (1), and it expressly specifies that it applies to “aggregate software distribution containing programs from several different sources”, not single, standalone works.

    That is a weird way of wording it. In practice I doubt there are any OSI-approved licenses that prohibit standalone commercial distribution. If there were, you could trivially comply by just including a “hello world” program to make it an aggregate distribution.





  • The goal of the copyleft movement (which overlaps heavily with the free software movement) is to carve out an intellectual commons that can’t be re-enclosed. This commons is important for a number of reasons, including that it tends to be better for end-users of software in the sense that anti-features can’t really gain a foothold. It does not automatically solve UX issues, nor does it stop people from using the knowledge of the commons to do bad things.

    Much of the strength of the intellectual commons is that it builds on itself, instead of having to re-invent the same things in a dozen or more different proprietary endeavors. If we were to start a “peace software” movement, it would be incompatible with the commons, due to the restrictions it imposes. Peace software can’t build on copyleft software, and none of the commons can build on peace software. These sorts of things were considered, and compatibility was deemed more important than pushing more specific values. This isn’t a matter of the FSF or OSI standing in the way, it’s just that “peace software” would have to go it alone.

    Due to this dynamic, those that want to build “anticapitalist software” would be better served by using the GNU AGPL, rather than a license that restricts commercial use. The AGPL fixes the loophole that the GPL leaves open for network services, and should allow us to carve out a new noncommercial online ecosystem. It should even be used for non-network code, as that code may be repurposed or built upon by network services. I’m glad to see lemmy, kbin, and mastodon using it.








  • Added you to the list of specialized instances.

    Having the NSFW patch will be nice. Hiding NSFW for logged-out users with no way to change it is a really irritating design decision on the part of the lemmy devs. Though the patch used on lemmynsfw doesn’t seem to work right. Maybe ask pornlemmy about the patch that they use? Also, remember to share whatever changes you make, since lemmy is licensed under the AGPL.

    For the incognito patch, could you make it toggle-able, or part of one of the alternate UIs? I like having access to stuff in my browser history. It might be better just to remind people to switch their browser to incognito mode.

    Also, you may want to hammer out an explicit policy early on of what types of content you will and won’t allow, and what kinds of instances you will and won’t federate with. This will help avoid having the kind of drama that happened on lemmynsfw.