My main issue with hibernation in Linux is that it by default uses the same swap as ram overflow, so it fails if ram+swap is close to full - such as having a huge project of some kind in progress which would be a pain to reopen, one of the situations where hibernation would be very helpful.

This is fixable, I did it on my own laptop, and really wish I wrote everything down because it was a complex and unintuitive process, both getting it to save to a separate swap file from the swap partition (switched on/off in the systemd hibernation scripts), and getting it to boot from said file.

I really wish this was a supported scenario that was easy to set up. It drives me nuts for a feature where failure can mean data loss to have a failure mode easily reached by regular usage.

By contrast, Windows has always had separate swap and hibernation files, and generally works if drivers don’t mess it up (which they can on Linux too, Nvidia.)

Download/source links?

That’s really weird. As far as I know there’s only one common resolution that was 5:4, 1280x1024. Honestly I never understood why that existed when 1280x960 was right there.
But now that I think about it, maybe it worked better for businesses where documents took a lot of screen time and a little less scrolling was nice. That could explain how thrift stores got overloaded with them.

Ok then, why not on F-Droid yet?

Seems like your links answer the question: it’s up to the app playing music, and there are some suggestions of apps that let you choose.

True. But it slightly increases the needed effort.

That’s not the slop part, OP censored it to avoid doxing. Likely a local business that would give away the location.

They are an admin. Not a mere moderator.

Given the quote you were responding to, I totally expected this kind of spike (although in a quick skim I didn’t actually see him using it on a tomato like he usually does)

Nope, it’s explicitly not because of the app version. (Although the feature would have a minimum version.) Google likes to lock updates behind a server-side check so they can gradually enable rollouts and see if it starts bricking phones or whatever (then completely ignore the issue for months if it does)

Oh, that’s good to hear.

It’s more likely than you think

This is a good reminder to finally uninstall it completely after I switched to a different one. I should have done that long ago.

It also happens to be patching a financial vulnerability.

Exactly that. Drivers don’t generally have much UI (I guess module load parameters count) so getting it working is most of the job.

It’s the user facing applications which sometimes feel a bit unpolished. That has definitely improved over the years though.

This is more about open source in general than Linux specifically, but anyway.

Minor details.

I get the impression that often the developers are passionate about getting things working, but once it works it’s hard to keep going to fix ‘papercuts’: minor UI issues, documentation, small usability improvements, consistency, etc. They want to move on to the next big feature.

Of course commercial products can suffer from the same, but if large enough they may have a program manager who assigns people to specific areas like that which get less coverage when it’s based on the devs’ desire to work on them.

Tap to pay works perfectly fine on my plastic cards that don’t run out of battery or need to be unlocked before I tap them. I genuinely don’t see what the big deal is about having it work on a phone.

At least 6 makes sense

Did you actually read the link? They address this in a big red box:

Update: Google has not “backed down” from developer verification

Contrary to a vague mention of a possible “advanced flow” that may eventually allow “experienced users to accept the risks of installing software that isn’t verified”, Google’s description of the program continues to state plainly that:

Starting in September 2026, Android will require all apps to be registered by verified developers in order to be installed on certified Android devices

Until such time that they have shown evidence that it will be possible to bypass the verification process without undue friction, we must believe what is stated on their official page: that all apps from non-registered developers will be blocked once their lock-down goes into effect.

Link for Lemmy clients:

!geckobrowsers@fedia.io