They tested exactly two games

I mean Tom’s Hardware didn’t test anything, the Youtuber they are writing about tested Hogwarts Legacy and Kingdom Come Deliverance 2

I will assert that there are more than two games on the market

Someone should train an llm on these guys

And the hashes are displayed on the website that got compromised

So I just checked:

Gnome apps have themed decorations and vanilla content. It’s misaligned and it doesn’t look good, but it’s rather safe functionnality-wise. Also there’s no ~/.config/gtk-4 so I don’t know how they did it

A lot of other apps are clearly themed, but they are not maintained by signatories of the letter (that I know of)

The only offenders I could find are file-roller and gnome-disk, with gnome-disk having a very small theming issue. They use the same config file as all the apps that want to be themed, so they would have to patch them in order to prevent the theme from applying. Which would prevent user theming and generally be a mess.

No, Debian never had a custom preinstalled theme afaik

I’m not aware of any distro who kept their custom themes after this letter was published. ZorinOS still has some theming, but it looks like they only slightly changed some colors (where the previous one was rather invasive)

Is the franchise still popular nowadays?

Maybe I’m being a bit too nervous, but companies like Fairphone or Framework rely on goodwill from technical people who are ready to pay more for less stuff to encourage their politics. If poeple categorize them as non-rule, they are not going to pay the premium. I think, for a lemmy user, that would set the odds of buying at near-0. again, maybe i’m being too dramatic

I agree that putting pressure this way is a good thing, but the pressure needs to be conditional. If you just mark them as dead before giving them a chance to correct course, they are better off reaching all the way for the customer base of “apolitical” users. The ebassi screen has a parodic tone that reduces the certainty and definitiveness (people will just put FW into question rather than fully discard it. i think), and avoids citing the name directly, limiting the damage to people who already have some understanding of the situation

anyways at this point I think there is enough threat to elicit a reaction on their part, and that we should wait for them before burning everything down. and I hope they can just have a quick fact check and everything will be fine and they will actually have money to donate because they won’t if they keep up the vibe of the first response

I’m being way overinvested ok byeee

Please don’t keep this title if the post reaches the frontpages

It has only been 12h, and they only put up one (awful) placeholder response. Give them a bit of time to look into things before telling the headline-readers to never buy their stuff

Hey so, is this a normal thing in meta analyses ?

We identified 46 studies for inclusion in our analysis. Of these, 27 studies reported positive associations (significant links to NDDs), 9 showed null associations (no significant link), and 4 indicated negative associations (protective effects).

27+9+4 is 40 I think ? What happened to the 6 other papers ? I’m always confused by the whole “we ignored half of the studies and we won’t tell you why”, if they can also ignore some of the 46 studies they selected, what does the 46 number mean ?

If you already have the correct version of the flatpak installed, you can try flatpak build-bundle.

flatpak build-bundle LOCATION FILENAME NAME where

• LOCATION is the path of the repo on disk. Run flatpak info -l org.kde.arianna, and copy the part before /app
• FILENAME is the output file name, preferably .flatpak. Eg: arianna.flatpak
• NAME is the name of the app, here org.kde.arianna

The generated file can be installed with a double-click, or with flatpak install <file>

This is the equivalent of an Android .apk. It contains the app but depends on a runtime. If you want to install it in a few years, odds are the runtime will no longer be available. You can backup the runtime the same way with the --runtime option.

flatpak build-bundle --runtime LOCATION FILENAME NAME where

• LOCATION same as earlier
• FILENAME eg arianna-runtime.flatpak
• NAME is the name of the runtime, which you can get with flatpak info --show-runtime org.kde.arianna

This takes a while, for some reason. Maybe it’s compressing stuff?

The runtime is installed the same way as the app: double click or flatpak install.

Note: I only did this once, and not specifically on Arianna. Hope it works.