The Post Ninja

  • 2 Posts
  • 1.37K Comments
Joined 3 years ago
cake
Cake day: July 8th, 2023

help-circle
  • It’s the good old copyright Mexican standoff. If it is ruled that decompilations are illegal, that shoots freedom in the foot, and even legal clean-room decomps can be taken out, but also ai models could be much more copyright restricted. It’s both a win and a loss for everyone, as tightening the copyright noose is exactly what companies want, so they have a lot more ammo to shoot at foss projects and competition with.

    The other way is that this is considered fair use, as the ai is not verbatim recreating code, it’s recreating its own interpretation of the code, which is a flying spaghetti monster that only looks somewhat like the real thing only if you don’t open the hood. This, of course, opens the door to being able to use ai models to break down things legally, a win for decompilation, a win for security researchers, but also a big L as well, as now obscuring code behind closed source is not good enough.

    In either case, hackers and do-bads will run their own models and decompile things faster to find flaws and break stuff. Making it illegal doesn’t stop determined badders from doing it. Pandora’s box is already open, there is no undoing this without society as a whole getting washed away.





  • Blaster M@lemmy.worldtolinuxmemes@lemmy.world•Of course
    link
    fedilink
    English
    arrow-up
    25
    arrow-down
    2
    ·
    4 days ago

    This. As much as I want LibreOffice to succeed (AND I WANT LIBREOFFICE TO SUCCEED SO SIT DOWN YOU IN THE BACK), having converted actual work projects over to LibO and maintain them has been hell, to say the least.

    2026 and tables and text boxes still explode the document into confetti if you look at it funny. Hours of frustratingly reconstructing documents, or reloading progress saves because moving a text box one pixel over makes things explode.

    LibO needs QA and maintenance fixes, badly. If you don’t want LibO to use AI models to bug hunt, then enlist and help fix it. Development in turning LibO from a messy desk project to something actually useable efficiently has taken literal decades already.