• altphoto@lemmy.today
    link
    fedilink
    arrow-up
    10
    ·
    16 days ago

    That’s why all my devices running that piece of shit stay at work. Far away from my network.

  • FiniteBanjo@programming.dev
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    16 days ago

    TBF nVidia and Intel components supposedly had the same sort of capability for many years now: unique device ids.

    But yeh, fuck windowsm

  • fubarx@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    15 days ago

    Early iPhones all had unique UDIDs that were SDK accessible. It wasn’t long before it was used to connect location data to devices and devices with specific users. Apple’s solution was to yank it away from developers and go with an identifier the users could rescind and reset (the ADID). It still let apps track people, but there was always the risk users would reset it and break the chain of data gathering.

    The real solution is to limit access to the information as-needed. Like for maintenance, or warranty repairs. Everybody else can go pound sand. In the desktop/laptop world, a lot of hardware vendors just blithely let anyone access unique hardware IDs, which leads to the same privacy outcome.

  • Marija_@programming.dev
    link
    fedilink
    arrow-up
    3
    ·
    15 days ago

    Every time something like this comes out I’m reminded how much telemetry exists that most users never think about.

  • refalo@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    16 days ago

    Linux distros have the same kind of device ID mechanism (/etc/machine-id or /var/lib/dbus/machine-id)… the only difference is how applications use it.