Caretaker of Sunhillow/DS8.ZONE. Free (Libre) Software enthusiast and promoter. Pronouns: any

Also /u/CaptainBeyondDS8 on reddit and CaptainBeyond on libera.chat.

AI Disclosure: No “generative AI tools” are used to produce any work attributed to “Captain Beyond of Sunhillow” (here or elsewhere).

  • 0 Posts
  • 151 Comments
Joined 6 years ago
cake
Cake day: March 27th, 2021

help-circle
  • Captain Beyond@linkage.ds8.zonetoOpen Source@lemmy.ml•Ban AI Slop?
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    6 days ago

    To be frank, you appear to be set on pre-punishing a solo developer for sharing a family-and-friends project based on a rather cursory examination. Doesn’t that run somewhat contrary to the spirit of FOSS?

    “The spirit of FOSS” entails the users having the four freedoms (to use, modify, share verbatim copies, and share modified copies) of the source code. You’ve suggested that this project is primarily binary-only with only intermittent source code dumps, meaning that until these binaries have corresponding source code they are neither FOSS in letter nor in spirit, and thus inappropriate for this community as well as for !aials@lemmy.ml, which is for AI-assisted FOSS. Given that you’ve suggested you will only provide source code for “major revisions” this suggests that “minor versions” never will be FOSS. Effectively you’re promoting a proprietary product here that may or may not have intermittent source code snapshots.

    Furthermore, the fact that you seem to consider it a great effort to “sanitize” the source code for public release suggests that what is being shared with the public is not in fact the corresponding source code to the binaries you upload.

    As you pointed out the MIT license does allow you to make proprietary derivatives, so nothing you’ve done is “wrong” or illegal. That doesn’t make it not proprietary.

    Edit: I’m a different person than the admin who removed your post. I’m not suggesting your project is slop or that the effort you’ve put into it is inconsequential. I’m just saying that binaries without source code are not FOSS even if you publish occasional snapshots of selected releases. I’d probably be more favorable to this approach if there were FOSS builds from the source code snapshots, or maybe if only the FOSS releases were on github and the proprietary ones somewhere else - but that’s probably asking a bit too much.




  • You raise a good point. “Build” in software engineering has a very specific meaning: typically binary artifacts are “built” from source code. Source code I think is typically “written” but of course if you’re using a generative program you can’t say you wrote it…

    I’ve seen an LLM-user claim that “AI is the compiler of natural language” so I suppose if the prompt is source code then the generated code could be considered a build artifact. But, yeah, I don’t think people generally say they “build” code.








  • IMO insisting that free software options be “no-AI” while accepting proprietary stuff is backwards. In the proprietary world it’s the norm that as the end-user you aren’t entitled to know how the software is built, because that’s considered a secret. Your favorite proprietary developers could be using “AI” and you’re not supposed to know about it. In the proprietary world as long as it looks good and does what you want it to do it doesn’t matter how it’s implemented.

    If you’re insisting on being free of “AI” then as a consequence you have to insist on at least source-availability. As far as I know Obsidian isn’t even that.









  • The public domain is a concept in copyright law where a work has no copyright holder, either because the copyright expired or because (in TempleOS’s case) the copyright was voluntarily relinquished. However, note that it’s entirely jurisdiction-dependent (for example, it’s not always even possible to relinquish a copyright, and copyright expiration also varies by jurisdiction). As copyright is a state-granted monopoly on distribution rights, if no one has that monopoly, there are no restrictions on copying and hence the freedom to modify and distribute the source code is available to all. Note that copyright is automatic upon the creation of a work and does not need to be registered, so either an explicit declaration from the author or knowledge that the copyright term is expired is needed to know something is in the public domain.

    In short, if something is in the public domain (as the preferred form for modification i.e. source code) it is free software and open source, but the idea that public domain is somehow incompatible with FOSS is a somewhat reoccurring talking point that came up very recently. I don’t know where this came from but I imagine it has something to do with the discourse on copyright on LLM generated work.

    However, it’s usually best to use an explicit license so you can affirm your intent to release the software as free.

    FSF recognizes public domain as a category of free software (although, in their pedantry, they are quick to point out that it is not a “license”):

    https://www.gnu.org/licenses/license-list.html#PublicDomain

    OSI says more or less the same thing although they also elaborate on the actual legal complications of the public domain, and recommend explicitly using a license if possible:

    https://opensource.org/faq#public-domain


  • TBF he’s correct on that one, Linux actually is just the kernel and the OS normally built around it is the project he started ~7 years before Linux was ever a thing. Given his OS project had a political/ethical message that Linux completely disregards, it’s completely understandable he might be a tad irked that his work is lumped in under the kernel guy’s.

    Even if it sounds silly to us “normal users” if you put yourself in his head it makes sense.