• WalnutLum@lemmy.ml
    link
    fedilink
    arrow-up
    6
    ·
    7 months ago

    Are all these wacky licenses because the OSI doesn’t have an AGPL (ostensibly anti-cloud) equivalent BSD style permissive license?

    • thesmokingman@programming.dev
      link
      fedilink
      arrow-up
      8
      arrow-down
      1
      ·
      7 months ago

      The ostensible point is to prevent resellers from platforming your code. SSPL is an answer to, say, AWS offering your product much cheaper than you can. RSAL seems to be Redis spinning their own SSPL, BSL, whatever bullshit license because they’re not happy with the existing faux open source cloud licenses that prevent platforming.

      There really isn’t a good way to handle this from an open source perspective. Cloud majors can and will undercut the fuck out of anyone to establish dominance. Ideally you’re providing a better support experience or working with them (until they decide to kneecap you) to maintain your business. Previously Redis had an paid tier that had functionality not available at the OSS level. I think that’s also legit.

      I personally loathe the compliance issues these random shitty fucking licenses throw and don’t think trying to claw back business from majors is the right approach. The little guy is going to follow the path of least resistance which means you’ve made your software enterprise only.

  • bufke@lemm.ee
    link
    fedilink
    English
    arrow-up
    6
    ·
    7 months ago

    With SSPLv1, does that mean one can sell redis hosting as long as everything used to manage it is open source? It says it’s based on AGPL. So if say digitalocean open sourced all their api’s and UI they could still offer managed redis. It seems like the answer is yes but then the blog post also says

    Under the new license, cloud service providers hosting Redis offerings will no longer be permitted to use the source code of Redis free of charge.

    That sounds like no.

    • poVoq@slrpnk.netOP
      link
      fedilink
      arrow-up
      5
      ·
      7 months ago

      This just shows the true intention of the SSPLv1, i.e. to openwash what is in reality a shared-source license.