• 0 Posts
  • 68 Comments
Joined 1 year ago
cake
Cake day: July 23rd, 2023

help-circle



  • The correct way to get someone to move to FOSS is to show them how to do it, not tell them it exists. OP already said they can do the YouTube -> captioned gif in 10min so you need to provide a simple tutorial that identifies the tools to use, how to set them up, and how to create a workflow to achieve the goal of some format with captions in under 10min.

    Notice how I explained what was wrong and how to do it? That’s what’s missing from most “you need to use FOSS” posts, including yours.





  • Calling a license by anything other than its name and stated purpose is something I’d dare to call mislabeling. If CC BY-NC-SA 4.0 decides to add “anti-commercial-AI” then and only then is it not mislabeling. That’s like me calling the US copyrights of the books sitting next to me “anti-bitfucker” licenses. They have nothing to do with you at this point in time so it is misleading for me to claim otherwise.

    While you are correct that lemmy itself does not add a license and many instances do not add a license, it’s not as simple as “the user notifies [you] must abides by [their] licenses.” Jurisdiction matters. The Fediverse host content is pulled from matters. Other myriad factors matter. As you correctly pointed out, there is no precedence for any of this so as I pointed out unless you’re willing to go to court and can prove damages it is actually useless.



  • They’re mislabeling the license too. CC BY-NC-SA 4.0 has nothing to do with “anti-commercial-AI.” It provides some terms for using content and, in theory if OP is willing to take someone to court, should provide some basis if the license is being abused. Until there’s actual precedence, though, it’s debatable whether or not sucking up CC BY-NC-SA 4.0 content is a breach of the license. For it to actually matter, someone needs to demonstrably prove 1) CC BY-NC-SA 4.0 content was sucked up by AI, 2) it was their content and it was licensed at the time, 3) the terms of the license were violated, and 4) other legal shit that will pop up during the course of the litigation. “Someone” has to be someone with deep fucking pockets willing to go the distance in many international jurisdictions.





  • This doesn’t appear to cover the cost of the electricity it would take to keep your stuff running. There is no way to pay anything out at all. Seems like a pretty straightforward pump-and-dump where the end users are collecting imaginary points while some company abuses their resources. Every blog and Reddit post I looked at to try to understand this was full of referral links. Equally classic sign of pump-and-dump pyramid scheme.





  • 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.