The Post Ninja

  • 5 Posts
  • 691 Comments
Joined 3 years ago
cake
Cake day: July 8th, 2023

help-circle







  • They’re cost effective when you set an arbitrarily low speed limit on a historically fast stretch of road. In order to support the $5000+/mo cost of each speed camera, you need to be handing put speeding tickets lile they’re going out of style, which incentivizes doing the first part.

    It’s the speed trap town, automated. Also an American problem. Build a town that uses the highway as a main street so you can enforce an arbitrarily low speed limit in city limits and catch people that miss the first speed limit change sign. Because 99 percent of traffic is passing thru, they are less likely to fight it in court. Easy money for the people running the town.

    Also they used to use all sorts of tricks, like posting multiple speed limit change signs in short sequence (65->55->45->35 in the same 1/4 mile (400m for you metric people)), then making sure at least one of those signs is partially obscured by an overgrown tree or in the middle of a bend or camo’ed between city info signs, where you’re less likely to see it while concentrating on everything else.


  • Been a bit of a bother trying to find the actual info and not a rage piece that makes FOX News look sane. And I don’t touch that agency with an 11ft pole.

    From what I remember reading, Linus uses LLMs to help during bug hunting - the second pair of eyes. This is actually a useful part of the AI models - they may be awful at code writing, but they do seem to have some capability when looking over code as a first line proofer. That is, it’s useful for you to get a direction as to where to look further with issues.

    As for the Assisted-By tag being removed, it was a matter that no one was really using it, making it functionally useless.


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