This article is kinda misleading. Nearly 40% of Linux devices is the Steam Deck which is AMD only. Subtracting the Steam Deck AMD usage on Linux more or less matches that on Windows.
See the Steam hardware survey for the numbers that this blog spam article is reporting on: https://store.steampowered.com/hwsurvey/?platform=linux
Opt-out helps you capture the group of users that simply do not care about telemetry.
As someone who recently started developing an open-source GUI application for a few thousand users I cannot stress enough how instrumental telemetry has been in fixing a variety of crashes.
Noticed quite an increase in bot posts over on r/titanfall to the point where a retired mod wanted to return to their position to help deal with it. Given that I'm kinda moving away from Reddit I gave them their position back so that I can start moving on.
Ah yeah. I had to do the same. When you said "solution" I was hoping you meant you found a way to resolve the FPS drops while keeping polling at the original polling rate ^^
Both OSes do pre-caching and for both the standard tools to check usage nowadays ignore pre-cached elements when counting RAM usage.
Definitely my iFixit Pro Tech Toolkit. Cost like 70€ but I've repaired dozens of devices with it which otherwise would've gone to waste. Based on that it easily saved me more money than it cost :D
Out of curiosity I might would've but not for long term and given that it seems to require an Instragram account I'm not really interested.
However, I don’t fully understand this part:
there should be an easy way to also access that information in the front end to indicate to the user that what they up/down vote is in fact not private.
But it’s true that my brain today doesn’t really want to work. You mean by some kind of API call can reveal these information?
Basically what I meant is some way for the user to see who up/down voted what. Maybe hovering the up/down vote button shows a field you can click on that say votes or something and that then redirects you to a different page that shows who upvoted and downvoted that specific post/comment. The exact details don't really matter. My point was basically that if something is accessible but only via hidden means that are not obvious to the end-user, they may wrongly assume that information is private. So by making it easily accessible to end-user, you also clearly indicate that that information is publicly accessible ^^
Why would you want to show all information stored on the frontend?
I'm gonna start out by saying that I don't know how lemmy's federation code works. So if I host another instance and federate do I only see the upvote count or also who upvoted? Cause if the only person that can see the count is the admin of the instance the user belongs to, then there's no need to show it in the frontend. If however all you need to do to see upvote count of all lemmy users, is to host your own lemmy instance, then there should be an easy way to also access that information in the front end to indicate to the user that what they up/down vote is in fact not private.
So for me whether up/down voting is private is less of an issue as long as it's clearly communicated. Again if only the instance admin the user is part of can see the count, then that's essentially "private" as you are trusting that entity already ^^
I meant more in regards to the naming, not the rules themselves ^^"
It's been a while since I last checked Vaultwarden (back then it was still called bitwarden-rs). If they added an export feature, then that definitely makes things easier. The export feature in the client isn't enough IMO. Last time I tried it, it didn't export attachments. So if you for example have your SSH key saved in Bitwarden, well then good luck if you loose access to the vault :P
Yup, 40% of that AMD share is the Steam Deck.