They could have easily crammed the Steam Deck full of stuff to make it hard to use for piracy - locking down everything, making it usable only to play games you legitimately own, force you to go through who knows what hoops in order to play games on it. That’s what Nintendo or Apple or most other companies do.

But they didn’t, because they realized they didn’t have to. It’s 100% possible to put pirated games on the Steam Deck - in fact, it’s as easy as it could reasonably be. You copy it over, you wire it up to Steam, if it’s a non-Linux game you set it up with Proton or whatever else you want to use to run it, bam. You can now run it in Steam just as easily as a normal Steam game (usually.) If you want something similar to cloud saves you can even set up SyncThing for that.

But all of that is a lot of work, and after all that you still don’t have automatic updates, and some games won’t run this way for one reason or another even though they’ll run if you own them (usually, I assume, because of Steam Deck specific tweaks or install stuff that are only used when you’re running them on the Deck via the normal method.) Some of this you can work around but it’s even more hoops.

Whereas if you own a game it’s just push a button and play. They made legitimately owning a game more convenient than piracy, and they did it without relying on DRM or anything that restricts or annoys legitimate users at all - even if a game has a DRM-free GOG version, owning it on Steam will still make it easier to play on the Steam Deck.

  • Square Singer@feddit.de
    link
    fedilink
    English
    arrow-up
    14
    ·
    11 months ago

    Tieing down a Linux installation is actually pretty easy.

    • Lock the BIOS down so that it can only boot a Valve-signed OS
    • Remove root access on the OS
    • chown root:root on anything you don’t want the users to touch

    It’s pretty much the same as Android device vendors are doing.

    • AnonTwo@kbin.social
      link
      fedilink
      arrow-up
      2
      arrow-down
      8
      ·
      11 months ago

      The…arm-based systems that use a different kind of BIOS?

      If even Apple isn’t doing it on x86, I don’t see why Valve would start.

      • justJanne@startrek.website
        link
        fedilink
        English
        arrow-up
        4
        ·
        11 months ago

        Microsoft actually locked down the BIOS on several Windows 10 S devices to prevent users from installing non-MS OSes with enforced MS-only secure boot.

      • Square Singer@feddit.de
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        11 months ago

        Have you heard of Android running on x86?

        I had an x86 Android tablet and that was exactly as locked-down as an ARM Android device.

        But anyhow: I can lock down a x86 laptop or PC the way I was describing within a very short time.

        So again:

        • Put a password on the BIOS
        • Set Secure Boot on
        • Wipe all Secure Boot keys and put your own in there
        • Encrypt the disk so that you can’t just plop the drive into another PC and modify its content
        • Set the root user to “Can only login with private key” and don’t give the key to the customers
        • Remove all users from sudoers
        • Use chown root:root and chmod 700 on anything you don’t want the user to touch

        And if a company was doing this to their products (e.g. the Steam Deck), they’d replace the first 3 steps with a custom BIOS which just doesn’t let you change anything in regards to Secure Boot and Secure Boot keys. That way, removing the BIOS battery won’t help.

        There are countless embedded devices using an x86 PC at their core, where they did exactly that. (E.g. ATMs or medical devices)

        Also Chromebooks are exactly that.

        And the Playstation 5 does the same thing, only it’s based on FreeBSD.