One thing I’m concerned about is recording equipment leaving identifiable information without us knowing about it.

  • HiddenLayer555@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 months ago

    Tons of websites record your mouse, keyboard, and scroll activity, and can play back exactly what you saw on your browser window. This is called session replay. There are pre-made libraries for this you can import so it’s super common.

    • bountygiver [any]@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 months ago

      nah only the minidump is reported back which only contains the memory the crashing stack is using. Sending the full dump would requires uploading gigabytes of data which would cripple any home internet as they mostly have very limited upstream bandwidth.

      • Buddahriffic@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        2 months ago

        Though iirc a system crash report can include a kernel dump, which can contain things like private keys.

        Though realistically, Microsoft controls your OS. They could easily add code to allow them to grab whatever they want from your system without any logging (by your system anyways).

        That actually makes me wonder if there are any apps that run on both a system and the router that system is connected to to determine if the internet traffic as reported by the system (to the user) is the same as what the router sees as a way to detect anything using network resources but bypassing the normal network stack.

        • bountygiver [any]@lemmy.ml
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 months ago

          you certainly can just run wireshark on your PC and your router, then compare them in the end of the day (with your router’s file filtered your PC’s source address)

    • Truscape@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      0
      ·
      2 months ago

      Correction: GrapheneOS has implemented permission controls for sensors. It also has sandboxing and permission scopes to prevent many of those leaks.

      However, Graphene is not available to everyone, and it’s still problematic due to bystanders/passerby.