jrgd

It's funny how EA is attributing their statistic to something can be strongly disproven. When looking at the given statistic they provided, they don't specify the raw count of cheaters banned, but simply the rate. Even giving the generous assumption that EA's statistics aren't significantly flawed, they show an alleged large drop in cheaters bottoming out in the week of Nov. 4, 2024, before starting to rise up again. Does something else coincide with the rate of cheaters dropping in the week of Nov. 4? There is in fact something that does. Season 23 was released the fifth with a large spike of players being brought into the game. Without a more comprehensive statistic graph over several months, it looks like EA is trying to just capitalize on the fact that a large influx of players joining the game will drop the rates of cheaters momentarily, and then passing it off as evidence that Linux cheating was rampant. Quite disingenuous.

I'm not really sure I can support using DNT headers currently. Some good points were made about alongside GPC, DNT being legally recognized for GDPR requests in some countries. I live in the US outside of California, and don't closely follow along to the nuances of either CCPA or GDPR, so correct me if I get something wrong. Given the list of websites in a comment that respect DNT, the notion that DNT is voluntary to handle, and how many websites use to harm users instead (further fingerprinting data points), I don't see why Mozilla should be keeping around DNT for the time being.

Yes, the fingerprinting metric for DNT may not be that unique of a data point if a given user isn't using content blocking extensions and other browser-hardening techniques. It still is however a data point often masked to follow the herd in order to minimize fingerprinting in territories where user privacy isn't enforced by law. If law actually demanded respect to user privacy, I think DNT could work. As it stands though, it really doesn't seem like DNT is well-ingrained in law.

Given the list of sites you listed, I only recognize two websites on the list that claim to support DNT. Perhaps a majority of these sites are from smaller organizations and/or based in the EU? On top, this is only what the sites' privacy policies claim, no? How many of these sites are actively proven to respect DNT beyond claiming that they do?

It really seems like DNT is still considered way too optional for websites to handle and respect. The best way for this to change is for the GDPR to recognize proper DNT handling as mandatory for sites to be compliant in the EU. Furthermore (unlikely to happen anytime soon but would be helpful) is for the US to gain similar privacy laws at the country-level that also defines enforcement.

There is just about zero reason I think nicely asking website admins to monitor and add support for DNT. Given that a majority of the problem with violations isn't with the smallest of independent websites, but those run by larger businesses, I doubt simple activism will work. If just activism for respecting the privacy of users actually did something, I feel like in ~15 years Do Not Track headers would have shown meaningful progress. The only way going forward is deliberate user-enforced destruction of available tracking points granted to websites or law that dictates when and how websites may track users: be it GPC, DNT, or something else. Only when a consensus is being reached should Mozilla and browsers prepare to support the enforced feature.

EDIT: re-reading the list of websites claiming support for DNT, I found a second website I recognize.

Certainly a failure but at least it wouldn't actually be as harmful as it reads, given / is a directory and the assumption you're not root.

A majority of the Linux-native titles I have played work well. It's only a handful of titles that have blatant neglect or malice from the developers, publishers that don't work fully. Dying Light looks to fall under neglect as it doesn't seem to have been updated (except for the inclusion of DLCs) beyond the 2015 build of the game, and seems to be stuck in a console-ready graphics preset.

I started playing Dying Light for the first time recently. Compared to the Windows version, it looks like Techland completely abandoned the Linux native version of the game. Is this update fixing the Linux native version to be on par with Windows?

I can only guess the previous BIOS wasn't enabling every virtualization extension necessary for some applications for some reason then, given that GNOME Boxes did work. Glad you've found a solution.

The explicit denial I saw is multi-genre, multi-artist in ID3 v2.4 I won't be parsed.

EDIT: The source.

Rockbox will only pick up one of a tag (RIP Vorbis) and will only parse up to 500 bytes on higher end players, 240 bytes on other players of the grouped tag (RIP ID3 v2.4).

I did accidentally type the relevant command incorrectly, forgetting that sudo swaps the user before subcommands like whoami will resolve. So that command attempted to add the kvm group to 'root' rather to your user. I have fixed the command in the relevant comment for anyone else reading this thread. You can try sudo adduser "<username>" kvm, manually substituting for your username. As normal, restart after adding the group to your user. Additionally, I have added a warning to the solution in the original comment of why you may not want to keep this solution enabled forever as well as a way to disable it later if desired.

Rockbox unfortunately is built with "dinosaurs" in mind. As a side effect, the project does not intend to properly handle modern ID3, Vorbis tags.

I could use an older Android phone, but would have to find a suitable device to de-Google and load a custom music player app onto (such as Vinyl). Neither my Pixel XL nor Pixel 5a that I own currently are suitable targets (neither have microSD support, my Pixel XL has a damaged headphone jack and needs to be repaired). If you have any recommendations for something used that has a headphone jack, microSD slot, and can bootloader unlock via adb, let me know.

Based on using a local installation without elevated permissions (outside of /usr/(local)), I can only guess of two things happening:

The first is GNOME Boxes asks for elevated permissions when running or otherwise uses Polkit to gain those permissions. Your user by default likely isn't granted access to /dev/kvm and running userland software without additional permissions will inherently not allow KVM access.

To allow this sanely, you can add your user to the KVM group to allow userland KVM access. It can be done via sudo adduser "<username>" kvm and then restarting your computer. To note, this is something that can allow any application to access virtualization without special permissions. If you don't want this change to remain forever, the command sudo usermod -r -G kvm "<username>" followed by a restart can revert this change.

Alternatively, installing Android Studio via the Flathub Flatpak may handle permissions without needing to modify user groups in this case.

The second (unlikely, but possible) problem is the AppArmor profile blocking KVM access for userland. I don't have particularly any experience with creating modified profiles for AppArmor, if this is the cause. I could only offer terrible advice for AppArmor (disabling AppArmor or switching to warn-only, both things I do not recommend doing). Again, it might be worth trying to install Android Studio via flatpak to see if things work better if this is the cause.

I am testing this currently to ensure correctness, but if you're using Android Studio via Flatpak, you may need to enable kvm permissions for the application to have hardware-accelerated VMs. This can be done using Flatseal. The relevant permission (device=kvm) is under the Device section labeled as Virtualization.

Additionally, if problems are occurring outside of Flatpak, you might need to enable certain hardware virtualization technologies from your computer's BIOS (AMD-V, VT-x, VT-d, Intel VT, Virtualization, or some other similar term depending on CPU and motherboard).

EDIT: Doing testing, it seems the default permissions provided for Android Studio's Flathub Flatpak includes device=all. No permissions edits are necessary by default. If there are problems with the /dev/kvm device not being reachable, it is almost certainly due to the necessary extensions not being enabled in the BIOS, or your CPU doesn't support virtualization. Pop! OS 22.04 has the necessary components in software for KVM to function pre-installed, so nothing should be wrong on the OS side.

Superior over what exactly? Most workstation/desktop distros have a graphical software manager and handle drivers in a similar manner.