Or something about packaging. Or I used a function that has a different implementation for debug mode out of its intended purpose. Or

Only thing worse is not finding the bug that only happens in release mode

In addition to ‘just write anything and stick with it’, getting someone who knows what they’re doing to look at your code and criticize it can be useful.

I don’t follow your thought process. I didn’t say every running process could kill the lock screen or if it can kill the lock screen it can access everything else, I said any process that kills the lock screen has to be running. And as the attacker with physical access doesn’t know the password they can’t run anything to kill the lock screen. The only way for them to unlock it is if they already have malware on the device, in which case their physical access isn’t the cause of the problem.

How so? The lock screen is to prevent physical access while you’re away, and an attacker can’t kill it without having access in the first place. Any process that can kill it would already have access to your session.

Them who? What happened?

… Brazil is one of the first countries this’ll go into effect and I also remember something about how that first batch of countries was chosen because their governmemts support this change.

IBM?

:(. Depressing

Same thing happened to me, and there is a delete all button. Go to Google photos > top right profile pic > backup is off (or whatever it says when it’s on) > top right gear > undo backup for this device.

I made fun of the Liberux Nexx before due to its outdated cpu being promoted as new but this is making me change my mind. Speed isn’t worth the walled garden. I have concerns about the battery life but all it takes to remedy that is a powerbank. Banking apps might be a problem but if I find their websites wanting I can just use them on an old cheap android.

It is disappointing that the Liberux Nexx missed its fundraising goal and had to open a new one. And the new one is only 10% of the way there, with no prototype and delivery on next summer. That’s cutting it very close with the timeline of these restrictions. https://www.indiegogo.com/projects/liberux-nexx--3#/

BTW, the Google blog post webpage has a link to a feedback form. Doubt it will do anything, but if you want an abyss to yell that’s good as any: https://docs.google.com/forms/d/e/1FAIpQLSfN3UQeNspQsZCO2ITkdzMxv81rJDEGGjO-UIDDY28Rz_GEVA/viewform

deleted by creator

How did the volume slider go under that image?

How does it even get into emergency mode without the efi partition?

It does claim to be ‘much faster’ than even OBS’ new no copy recording mode so there must be something more

Is there a technical explanation of this? The git page just says that it’s much faster without explaining how

Euphonica tries to make minimal and sensible assumptions about your library’s folder structure.

Tracks from different releases (albums) should not be put in the same folder. Preferably, all tracks of the same release should be put in the same folder.

How hard is it to stop making this assumption? Why is almost every music player adamant on making it?

Not every song belongs to an album, songs released together might belong to different albums and not every album is released at once. Not to mention folders can serve any kind of organization need other than grouping songs of an album.

The word ‘Canadian’ belongs in the title

The malware, which must be planted on an unlocked device

So it’s a backup tool

Elisa would be close to ideal if it didn’t assume music always belong to an album