CoyoteFacts

This might be the funniest possible direction for this to go. Purported savior of X11 and anti-DEI dogwhistling developer writes X11 code so bad, asked to leave commit history.

It’s important to use services with a workflow that works for you; not every popular service is going to be a good fit for everyone. Find your balance between exhaustive categorization and meaningless pile of data, and make sure you’re getting more out than you’re putting in. If you do decide that an extensive amount of effort is worth it, make sure that the service in question is able to export your data in a data-rich format so that you won’t have to do it all again if you decide to move to a different tool.

Isn’t one of the problems with X that applications can log your keystrokes in other applications and record your screen? Obviously you shouldn’t be installing compromised software, but who knows if Borderlands 2 now includes some malicious code in its DRM or something.

By default, Wine/Proton has access to your full Linux filesystem under the virtual Z:/ drive from within the Wine environment, so any dedicated adversary could include your Linux stuff into its data collection. The odds of this already occurring are probably low-ish. You can use bubblewrap raw to start sandboxing resources (e.g. blocking network access or masking directories), or there’s a project called sandwine which presumably auto-configures the important stuff through bubblewrap (though I’ve never gotten around to trying it). Wine itself can also be configured to drop the Z:/ drive through its winecfg tool.

Without a dedicated configuration, I’m not sure Wine has any real priority or guarantee about sandboxing your original system from Windows executables, which is also why it’s important to remember that Windows malware can still do damage when running on a Linux system. The malware doesn’t really even have to be aware that it’s running in Wine if it just tries to encrypt any files it can reach.