• 1 Post
  • 30 Comments
Joined 1 year ago
cake
Cake day: August 4th, 2023

help-circle


  • I… doubt it?

    I took the liberty of looking in the developer tools as it failed, and there was a 500 response. The connection to Hulu’s servers was all over HTTPS and I didn’t get any certificate warning, so unless my ISP managed to get Hulu’s private key or got with a corrupt registrar willing to issue a valid replacement certificate, no ISP should be able to change response codes on a man-in-the-middle basis or a redirecting-traffic-to-a-hostile-server basis.

    And given how many people have reported issues, I doubt it’s specific to any particular ISPs.

    Net neutrality being dead is a huge bummer, but I don’t think this can be blamed on that.



  • TootSweet@lemmy.worldtoOpen Source@lemmy.mlIf we had libre AI
    link
    fedilink
    English
    arrow-up
    13
    ·
    edit-2
    9 days ago

    The GPL family of licenses was designed to cover code specifically. AI engines are code and are covered in most jurisdictions by copyright. (Disclaimer: I know a lot less about international intellectual property law than about U.S. intellectual property law. But I’m pretty confident what I’ll say here is at least true of the U.S…) But you don’t really have a functional generative AI system without weights. And it’s not clear that weights are covered by any particular branch of intellectual property in any particular jurisdiction. (And if they are, it’s not clear that the legal entity who trained the engine owns those rights on those weights rather than the rights holders who hold rights to the materials being used as training data.) It’s the weights that would make for any biases or purposefully nefarious output. Nothing that isn’t covered by intellectually property can meaningfully be said to be “licensed”, really. Under the AGPLv3 or any other license. To speak of something not covered by any intellectual (or non-intellectual, I suppose) property as “licensed” is just kindof nonsensical.

    Like, since Einstein’s General Relativity isn’t covered by any intellectual property, it’s not possible for General Relativity to be “licensed”. Similarly, unless some law is passed making LLM weights covered by, say, copyright law, one can’t speak of those weights being “licensed”.

    By the way, there are several high-profile cases of companies like Meta releasing LLMs that you can run locally and calling them “Open Source” when there’s nothing “Open Source” about them. As in, they don’t distribute the source code of LLaMa at all. That’s exactly the opposite of “Open Source” and the weights aren’t code and can’t really be said to be “Open Source”. More info here.

    Now, all that said, I don’t think there’s actually any inherent benefit to LLMs, AGPLv3 or otherwise, so I don’t have any interest even in AGPLv3 engines. But I’m all for more software being licensed AGPLv3. I just don’t think AGPLv3 is a concept that applies to any portion of LLMs aside from the engine.










  • Too little too late. The damage is already done.

    And even on that page, they’re still being assholes about Open Source (“Our use of the term ‘open source’ thus far has been not out of carelessness, but out of disdain for OSI approved licenses which nevertheless allow developers to be exploited by large corporate interests.”) while pretending what they’ve done with the FUTO license is some boon to consumer rights (“Fundamentally, our goals are to build great products that don’t abuse people, beat the tech oligopoly, and elevate the rights of programmers developing software that has source code open to public scrutiny and tinkering.”). And they’re still not dropping the effort to dilute the term “Open Source” (“The OSI, an organization with confidential charter members and large corporate sponsors, does not have any legal right to say what is and is not ‘open source’. It is arrogant of them to lay claim to the definition.”).

    Also, just as an aside, as page that the words “legal right” in that last quote link to says, the OSI attempted to trademark “Open Source.” I’m not sure why FUTO seems to think the same reasons why the “Open Source” trademark was rejected won’t apply just as much to the term “Source First” (but they do seem to think that: “we will be making our own term and trademarking it.”)


  • TootSweet@lemmy.worldtoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    27 days ago

    To speak of AI models being “made public domain” is to presuppose that the AI models in question are covered by some branch of intellectual property. Has it been established whether AI models (even those trained on properly licensed content) even are covered by some branch of intellectual property in any particular jurisdiction(s)? Or maybe by “public domain” the author means that they should be required to publish the weights and also that they shouldn’t get any trade secret protections related to those weights?


  • Can you name any real-world examples of this happening?

    Actually, I can. I know before Minetest (a FOSS Minecraft clone (they’d bristle at being called that, but anyway) that has since renamed itself to “Luanti” - I reccommend it, actually) officially supported Android, somebody ported it to Android (I don’t remember what they called the clone) and put it on the play store for money. Now, Minetest wasn’t under a copyleft license, so the clone wasn’t even FOSS (nor was it legally required to be.) I don’t remember any malware being involved. The Minetest community did all heave a collective groan when a wave of clueless people who didn’t realize it was FOSS started joining Minetest servers. People in the Minetest community definitely resented the clone. But beyond that, no real harm came to the game or its players. Some folks paid for an Android Minetest client that didn’t afford them the freedoms guaranteed by the Free Software Definition or Open Source Definition, but at the time the official Minetest client didn’t support Android. Aside from that, I don’t know of any harm that came from any of that. And had Minetest been under a copyleft license, even less harm would have come of that.

    Also, in practice, anyone who’s only out to get a quick buck is going to either avoid copylefted code like the plague or just blatantly violate the terms of the license. They’re unlikely to actually put forth the effort to compose a proper GPL compliance plan. (In fact, the ongoing U.S. court case “SFC v. Visio” is very apropos. Visio is named as a defendnt in that suit specifically for blatantly violating the terms of the GPL. Specifically the copyleft portions.)

    And if someone who does just want to make a quick buck clones some GPLd code and sells it in compliance with the license, I’m still not convinced that does anyone any harm. The GPL was also designed with non-programmer empowerment in mind, specifically allowing the use case where if a non-coder wants a feature added to a piece of GPL’d code, they can commission a coder to add it. But I’m not sure the Grayjay license would allow that even if it would allow one to make changes themselves noncommercially.

    I dunno. You seem to be really hung up on “contrubuting nothing”. And mind you, I don’t think that’s uncommon. That’s a big part of the whole “post-open-source” thing Parens is involved with these days. If FOSS as a whole was floundering right now in a way that money could solve, I maybe could get on board with the idea that there might be improvements that could be made to the existing FOSS paradigm. (Though something like legally-preserved nag screens in source-available software seems at best a clueless and ham-handed approach to that problem.)

    Much more concerning to me is that software respect users’ rights. I mostly won’t use software I don’t feel I can trust (either legally or security-wise.) And FOSS is software I can virtually always trust. When I’m publishing software, I do so under the AGPL v3 because I kinda don’t care if anyone sells it. (Though they can always get a free version from my GitLab (yeah, I switched to GitLab before Codeberg was a thing).) I do care if someone distributes (for money or gratis) my code in a way that doesn’t afford the end user the four freedoms. Which is why I use AGPL v3 over other options like non-copyleft FOSS licenses or noncommercial licenses.

    And, just to repeat this, again, I’m not angry at FUTO for releasing their code under non-FOSS licenses. That’s enough to make me not want to use their software. But not enough to make me resent them the way I do. The anger is at the way they’ve been sabotaging Open Source to the best of their ability while misrepresenting themselves as consumer rights advocates.



  • I don’t mind them asking for money. As I said just a moment ago in another comment, “I’m pissed at them for doing everything in their power to sabotage Open Source specifically to serve their bottom line while also pretending they’re some champion of consumer rights in tech.” I wouldn’t honestly be as pissed at them if they a) had just admitted from the get-go that they were a for-profit company with no actual interest in improving/solving enshittification and b) had never coopted the term “Open Source” or dunked on Open Source.

    But feel free to make a non-profit true open source counterpart if you like

    I don’t need to.


  • One of the goals of source first licenses is to stop enshittification since it doesn’t allow paid clones

    Copyleft prevents enshittification much better than anything in their license. If someone makes a paid clone of some, for instance, AGPL 3.0 program, one person can buy it and release the source code of the paid version and then all of the improvements can be incorporated back into the version from which it was forked.

    Unless the paid clone makers go so far as to break the terms of the license. But that’s not a problem that the Grayjay license solves any better than the AGPL 3.0.

    Grayjay’s license is itself a textbook example of enshittification.

    Not saying I agree with their policy, but I would hope more for-profit businesses make their source code available

    I’m not pissed at FUTO for releasing their source code under a non-FOSS license. I’m pissed at them for doing everything in their power to sabotage Open Source specifically to serve their bottom line while also pretending they’re some champion of consumer rights in tech. And it’s really shitty to use a .org address to further drive home the lie that they’re anything but a for-profit company fucking over consumers to make a profit.


  • If you use too little, it won’t get your clothes as clean. If you use too much, your clothes will come out of the washer still with detergent in them or perhaps you’ll have issues with too much suds leaking out of your washer (or at least out of the tank portion potentially into some of the electronic components.) There’s probably a pretty wide margin of error, though, and you’d have to use a lot too little or a lot too much to see any noticeable difference, though. If you’re happy with the results you’re getting, keep doing what you’re doing. If you feel like doing some experimentation with the amount of detergent you use, hell, everybody needs a hobby.