Generally Plasma. I really like the look of Libadwaita applications, but the GNOME desktop is very much a "do it our way, or take a hike" - and some of the interactions that I've seen in the past between the GNOME group and others... well, lets just say whenever I see drama in the Linux community as of recently its always been either with GNOME or Wayland. That doesn't necessarily instill a lot of confidence in me using either of those.
Definitely, there are less posts here that I feel if I comment its just going to end up going south - especially if I have a differing opinion. Which isn't to say that doesn't happen here on Lemmy, there are certainly topics where if you go against the grain, the exact same thing will happen (some of those topics make sense and are worth "fighting" for, others not so much).
It's called "Caffeinate" (I'm avoiding posting the direct link just so I don't break any self promotion rules), I made it in the Android 7 days when the quick settings Tile API came out to replicate the similar tile that was available in CyanogenMod. It ended up getting way more downloads than I ever expected honestly - I just wanted to try the new API haha.
I know that Caffeinate itself doesn't use up a lot of RAM (the only thing it does when its active is create a persistent notification and creates a wakelock in order to keep the screen active), but perhaps the lower end Samsung device models just have less RAM available, so opening a browser or such kills it.
At the current moment, filtering is an app feature and isn't built into Lemmy itself unfortunately. Lemmy natively lets you block communities and users, but that's about it (with instance filtering coming up in the next version).
I don't think it actually corrupted the SSD, perhaps a module is missing or such, and that's why it goes into emergency mode. Have you tried mounting the drive from say, a live usb?
I published an app on the play store that purely relies on a persistent notification + wakelocks to keep the screen active (since the whole point of the app is to keep the screen awake) - Samsung was definitely the worst when it comes to this for my app, as I would receive endless support emails about people with Samsung devices where it would get killed, even when disabling battery optimization for my app. The other manufacturers listed there came up every now and then, but disabling battery optimization generally did the trick for them.
With there being nothing that I could do for my app, I tried disabling compatibility in the play store for a ton of Samsung models, but then I got even more emails about people wondering why it wasn't available anymore so I re-enabled it, but to this day there's still (AFAIK) zero things I can do to prevent the app from getting killed on those devices.
Thankfully Minecraft Dungeons does work via Proton, though I'm not super familiar with macOS so I'm not sure if Proton works for macOS given that Apple's platforms use Metal rather than Vulkan (though I hear a translation layer is being worked on for Vulkan->Metal).
This is one of the reasons I don't use GamePass, because it all goes through the crappy Microsoft Store which always gives me weird download errors, and when trying to research the issue it just leads to nothing that works.
God forbid you reinstall Windows and have your GamePass games on another drive. It won't let you re-use that partition because the games folder is "owned by someone else" even when you're signed into the same Microsoft account, and it won't let you delete it because its protected by Windows... You either have to nuke the whole partition, delete it from Linux, or go through the whole take-ownership ritual which is buggy at best.
One of the things I love the most about my Pixel watch is being able to listen to Spotify on a run, without lugging my phone with me. Do any of the smart bands have this?
I think that is only if you pass /, I don't think the flag is required for /* which is what is shown here - if I remember right, it's because the * triggers the shell to expand the paths and that flag is only built to protect / (from say, having an empty variable alongside /).
I remember this from when Siri was first released. It was only available on the 4S if I remember right, and with a jailbroken device you could backport it since most of the assets and functionality was already there - sans the authentication keys.
It did not work well at all if you force enabled it on an unsupported device.
Or Always on Display, which usually only supports OLED capable devices could be force enabled on LCD devices, at the cost of your battery life.
Interesting, I'll probably just have to wait till either Bitwarden supports Passkeys, or wait till Firefox on Linux supports cross-device Passkeys (so, my phone for example) as yeah a 25 key limit is not likely to be worth purchasing an upgrade for just yet.
Google definitely supports passkeys, and they were one of the sites that did this. I've just replied to another comment regarding this. I wonder if the Yubikey 4 (I'm not sure how to tell which one I have, since they look about the same) just doesn't support passkeys, which would be... unfortunate.
It'll be even more unfortunate if there's a weird mix of sites that support the Yubikey as a passkey and some only support it as a passkey. My Pixel is supported as a passkey, but Firefox on Linux doesn't support this - only on Windows and macOS. I believe Chrome/Chromium does, which is equally as frustrating as my Yubikey possibly not supporting passkeys.
Strangely enough, Google lets me "add" my Yubikey as a passkey, but then does not let me sign in with it due to it not being "recognized". If I remove it as a passkey, and only use it as a 2FA token, attempt to sign in and use the "Enter your password" option, it will then let me use the key after I've entered my password as a second factor.
So it seems Google has removed the error (or its not triggering anymore) as they will have been one of the first sites I tried to create a passkey for, but it still does not let you use it as a passkey.
Not that I'd be remotely interested in the skin (nor do I play OW2), but really Blizzard? You'd think that with all of the PR issues they've been facing lately with both games, that they wouldn't pull something like this so quickly.
Strangely enough, Google lets me "add" my Yubikey as a passkey, but then does not let me sign in with it due to it not being "recognized". If I remove it as a passkey, and only use it as a 2FA token, attempt to sign in and use the "Enter your password" option, it will then let me use the key after I've entered my password as a second factor.
So it seems Google has removed the error (or its not triggering anymore) as they will have been one of the first sites I tried to create a passkey for, but it still does not let you use it as a passkey.
russjr08 @ russjr08 @outpost.zeuslink.net Posts 2Comments 525Joined 2 yr. ago 
Generally Plasma. I really like the look of Libadwaita applications, but the GNOME desktop is very much a "do it our way, or take a hike" - and some of the interactions that I've seen in the past between the GNOME group and others... well, lets just say whenever I see drama in the Linux community as of recently its always been either with GNOME or Wayland. That doesn't necessarily instill a lot of confidence in me using either of those.