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

Word of warning, I did this (gfx.webrender.compositor.force-enabled) on my Tuxedo OS system with Nvidia and I don’t know if it was just the next time I started Firefox or because said restart was after a big system update, but Firefox crashed on launch every time until managed to get it into safe mode (wasn’t as easy as holding shift) and then turned this back off.

Why is it still considered acceptable to make I and l look the same? I get that “Sans Serif” means avoiding dangly bits, but it doesn’t have to be absolutely 100%. At the very least they could be different heights.

It explicitly says the recordings stay on my device.
But yeah, if it didn’t say that, I’d guess the same.

Finally!

Got it here on my Pixel 7 Pro in the US, and specifically a 2-party state.

It initially said it was ‘pending’ downloading some audio files (I assume the announcement that it’s recording, which is all that’s needed legally) - and after I tapped the download button it seems ready to go.

If my suggestion works, that won’t matter, it will still be logged in on the new install.

Well, that makes a huge difference to the meaning of the question.

I don’t know, but maybe the login is held in a dotfile such as ~/.dropbox or maybe in ~/.config/dropbox or similar, and just backing up that (not to Dropbox!) would be enough to restore being logged in on a different system.

I think of Yahoo as ‘The search engine that malware sets as default to get paid for referrals or something’.

Ok, I’ll try that out. Thanks!

I’m also looking into Lawnchair.

Unfortunately, it hasn’t updated in nearly 3 years, which doesn’t bode well for future Android release compatibility.

Hmm. Doesn’t look like it supports traditional put-them-where-you-want-on-multiple-screens icons. That’s a deal breaker for me, but thank you