[–] 0 points 4 days ago (7 children)

Yes, because that has worked so well in the past for alcohol, cannabis, homosexuality, or nuclear proliferation.

A list of examples where prohibition didn't work is quite far from an argument that it never works, Plato. Leaded gasoline, CFCs, asbestos, DDT, should I go on?

This class of models is already perfectly capable of finding and exploiting vulnerabilities in software, and is within spitting distance of the frontier.

If you think frontier models are close to Qwen running on your 5090, you're completely devoid of any knowledge on the subject and therefore this discussion becomes meaningless.

  • source
  • parent
  • context
  • [–] 1 point 4 days ago (12 children)

    What should the good guys do?

    Legislate AI away, except for the already existing open models that run on consumer-grade GPUs and are therefore orders of magnitude weaker and can't be used to break down any systems.

    Or penalize heavily any company developing a model that is subsequently used to invade a system, stopping this madness of separating the models from the operators of said models.

  • source
  • parent
  • context
  • [–] 3 points 4 days ago (15 children)

    AI can be useful in some circumstances

    And the point is that this statement can be true AND we can still think AI should cease to be used. The "useful in some circumstances" benefit does not justify the ethical and environmental cost.

  • source
  • parent
  • context
  • [–] 17 points 5 days ago (21 children)

    get past there built in kneejerk reaction to anything AI related

    Maybe because it's not kneejerk. We know how AI works, what it takes to have it running, how it was built, who controls it. For many people, the ends do not justify the means (and that's if we assume fixing CVEs on Linux is somehow worth the very problematic ends AI is leading us towards anyway).

  • source
  • parent
  • context
  • [–] 5 points 6 days ago

    Well, it was hard enough because it still needed some work and about 18 months to get to a crappy build but yeah

    Note how it took months of no progress then mere weeks after the first jailbreak was released. The jailbreak is the innovation here, the emulator itself barely changed to accommodate the Switch 2, relative to the initial work of building the Switch 1 version.

  • source
  • parent
  • context
  • [–] 5 points 6 days ago (1 child)

    Google doesn't care about the profitability today. Just look at how they are integrating the AI into Maps, Android, Search and now those "Googlebooks".

    What they want is for you to die, and for a whole new generation that can't interact with computers or information in any other way except a chatbot that can filter and control what they see. That's when profits go through the roof.

  • source
  • [–] 28 points 6 days ago (5 children)

    As I understand it the way this usually goes is finding a vulnerability but there‘s nothing mentioned.

    It wasn't mentioned because it was already disclosed and people are already using it, it's extremely popular. The Switch 2 was jailbroken using SmileBASIC as a userland exploit plus a filesystem exploit for privilege escalation. If the game can run in a jailbroken Switch, you can decrypt and dump it.

    Then as far as emulation is concerned, the Switch 2 is just a Switch 1 with a newer Nvidia chip, updating the emulators isn't that hard.

  • source
  • parent
  • context
  • [–] 3 points 1 week ago (3 children)

    See? You’re almost helpful. But I do have to ask you if that password manager has a name?

    Sure, had you asked about a solution rather than trying to write some sort of gotcha. KeePassXC is a fully complete password manager, better than whatever subscription crap you'd rather push, and it stores everything into an encrypted local db file you control. Now guess what I'd recommend for syncing that file across other devices.

  • source
  • parent
  • context
  • [–] 4 points 1 week ago (2 children)

    The vast majority of people don’t know the difference between 2FA and passkeys, and you want them to manage their own self hosted solutions for everything?

    I didn't mention self hosting nor do I think it's necessary, unless you consider any service running in your desktop as "self hosting".

  • source
  • parent
  • context
  • [–] 15 points 1 week ago* (26 children)

    I said this before, will say it again: do not migrate to another subscription service.

    People went through all the trouble to migrate from Google to Proton, then now they must migrate from Proton to whatever else, and the cycle will repeat again.

    Subscription services, cloud software, they all strip you of agency and control. You don't have direct access to the files, you don't control the GUI, they are filled with proprietary formats, you are at their hands if they decide to change something you like, or pricing, or if they simply go nuts.

    Keep your things in your computer. Need they synced? SyncThing will do that for you on any device imaginable.

  • source
  • parent
  • context
  • [–] 26 points 1 week ago* (4 children)

    Users love big tech. They pretend not to, but they love their shackles.

    For instance, when Twitter was bought by Elon and people had that big migration wave... Mastodon was right there, a fully matured ecosystem, same or even better features... yet the majority picked Bluesky, the "features" Bluesky offered are there in Mastodon, the only difference is Bluesky is also owned by private tech bros.

  • source
  • parent
  • context
  • [–] 2 points 1 week ago

    It's simple, really. Steam allows 18+ games, but it treats them under a special regime, you can fully disable them from view. AI games should be the same.

    "Oh but developers will just lie" yeah they can lie about having a +18 asset in the middle of the game too, but as soon as they are caught and it's proven, they are banned. Same if they hide malware.

    "Oh but no game developer will disable Claude from VSCode, now what?"

    There's a difference between the kind of AI slop that dominated the latest demo fest vs using Claude in an IDE.

  • source
  • parent
  • context
  • view more: next ›