Discussion
Loading...

#Tag

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Kevin Karhan :verified:
@kkarhan@infosec.space  ·  activity timestamp 4 days ago

@landley @eruwero @maybeanerd but if your goal is to "commit asset-denial" against GAFAMs then shure, #AGPLv3 is a shure-fire method to have neither corporate users nor -sponsors…

  • If you expect to be paid to maintain #FLOSS you need to find a company willing to do that, and they certainly won't do AGPL but either #openwashing with " #SourceAvailable" shit like #SSPL or choose #0BSD up to #GPLv2.
  • Copy link
  • Flag this post
  • Block
Strypey
@strypey@mastodon.nzoss.nz  ·  activity timestamp last month

A couple of years back, a bunch of projects started switching to proprietary Source Available licenses like #SSPL. I predicted that they would soon regret it, as they started to be replaced with forks of their own software. Feeling pretty smug reading this ...

"Redis bets big on an open source return

The company is hopeful that changing its license will allow it to better compete with the Valkey fork."

#MattAsay, May 2025

https://www.infoworld.com/article/3975620/redis-bets-big-on-an-open-source-return.html

(1/2)

#SourceAvailable #Redis #Valkey

  • Copy link
  • Flag this post
  • Block
Log in

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.0-rc.3.21 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct
Home
Login