Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)FA
Posts
0
Comments
830
Joined
5 mo. ago

  • How are they gonna trace that to you?

    The modern Internet is essentially about spying on you as much as possible and then selling the data to whoever wants to buy it. Linking identities with devices/browsers is worth a lot of money and so most every website/app has a way of linking you to the devices and software that you use.

    Unless the user took some pretty extreme measures to create the account, they've likely logged in from a phone/ip/browser that has been linked to their real identity at some point in its lifetime. That link will be sold to data brokers and used to tie the random handle to you, the person. Then the State Department just buys that information.

    Alternatively, you should be assuming that sovereign entities with the means are reading all public network data. There's a lot of information that you can learn from that as well. Like, over time, the posts from the 'random' account could be strongly correlated to the times that you were accessing the site even if all of the data was encrypted with HTTPS.

    Alternatively, alternatively. There is a threat known as Store Now Decrypt Later (SNDL). The idea is basically: Quantum Computers are coming and they can break some cryptographic primitives. If someone saves all of the encrypted traffic that they would want to read, in a few years they will have the means to read that data. We won't know when this moment occurs, because it'll likely be a secret, but we do know that it will happen and so you should additionally assume that anything that isn't using post-quantum encryption, which transited a public network, will be read and used to link you to your identities.

    This is, essentially, the core thing that the Privacy community is attempting to mitigate.

  • In Steam, add this to the launch options games where you crash in order to enable logging to a text file:

     
             PROTON_LOG=1 %command%
    
    
      

    (-from: https://github.com/ValveSoftware/Proton/wiki/Proton-FAQ)

    Then there will be a log file of the game in your home directory, named steam-$GAMEID.log.

    When you're reading that log, the error that causes the freeze should be in the end of the log somewhere.

    If you just want to log the output of the Steam -d command (if you can't find a crash in the proton log, for example) you can use tee, explained here since you should not just run random terminal commands you find online without knowing what they do: https://www.geeksforgeeks.org/tee-command-linux-example/

     
             steam -d | tee ~/steam.log
    
    
      

    It'll write the output of steam -d to the terminal so you can read it, and also to the steam.log in your home directory.

  • We're about to be seeing a lot of people with the wrong political opinions being targeted using this data.

    Trump is already calling the protesters terrorists. Using this data to eliminate his political opponents would be pretty on brand for Trump.

    Every felon he makes now is one less person voting against him in the next election.

  • All data.

    Your Facebook information, Gmail emails, Insta DMs, etc. It's all for sale and federal law enforcement are buying it. Things that they would normally need a warrant to get, they can simply pull up from a data broker.

    Everything that's collected is sold. If it is for sale, law enforcement is buying it. Everything is collected.

  • If you want it to still be steam OS and compatible with games then you couldn’t use kernel.org kernels that’s the point.

    If a person stands to make a lot of money figuring out how to use a regular, non-anticheat kernel then they will do it. It would be a lot less difficult to do when the kernel code is open source.

    For anti-cheats, it isn't the case, as with Windows, where you can semi-trust that the kernel isn't lying. If an anti-cheat runs and wants to see what DMA devices are connected it uses the kernel to do that and it trusts that the kernel isn't lying. You could trivially modify the Linux kernel's source code to not list a specific card when asked by a kernel module.

  • He's just being pedantic.

    Technically 'ls' has kernel access because it depends on system calls in order to produce its output.

    System calls are the mechanisms through which programs request services from the Linux kernel, allowing them to perform tasks like file management, process control, and device management. Any program that's running on your machine has the access required to make syscalls and so you could say they have access to the kernel. They won't have kernel-level privileges, so they can't act as the kernel, but they do have access. Obviously the original user was referring to kernel anti-cheat modules which act as the kernel with all of the same privileges.

  • The language about collecting and using data have been in TOSs for basically every online service since the early '00s.

    I'm not saying that this is okay. The data that these services collect, which we've given them unlimited rights to, has only become more valuable and the incentives for these companies are always for them to gather more data about you.

    You can use archive.org if you want to look at older policies from the same company. But, if you pull up any other game with an online component you will see that they all are essentially "Don't cheat our services or hide your identity, We're going to collect your data and use it how we want, and you have to enter into binding arbitration" with various levels of detail and verbosity.