mudeth

SD cards don't perform wear leveling while ssds do. This is why there are specific SD cards meant for surveillance cameras. They have additional wear levelling circuitry at the expense of speed.

So photographers who fill up their sd cards end up writing over the same spots repeatedly and wear them out.

More secure: any bootloader tampering happening via physical access to the device will trip the warning.

More compatible: some apps (banks usually) flag an unlocked bootloader as a security threat.

The skybox in E1 is from China FYI! E2 is from Zion National park. So if you really want to, you can explore them :)

A thread on DW with sources.

I default to nanoreview when I do a Google search. It's pretty comprehensive and easy to scan.

Thanks. I have a pretty old install so my module list is a relic of the time but it makes sense why it still works for me. I'll edit.

There are workarounds:

Install magisk, add the app to the zygisk denylist before first run.

Install ~~universal safetynet fix and magisk hide props config (modules for magisk).~~

For some apps, you may have to install them in island so that they can't detect the magisk app.

Appreciate the pointers!

That's the one, thanks! I better get to it before Fossil pulls the app. You need to extract a private key from the paired app correct?

Not hybrid watches but Garmin watches have a passive LCD screen that is readable under reflected light and the app is excellent, albeit proprietary.

I have a Fossil hybrid and Garmin Instinct and wear the instinct most of the time. I find the Fossil app too basic and it drains battery. I have heard about an open source app that can sync to them however.

That was my impression as well. But since I'm on a low-RAM VPS any overhead in RAM adds up, and I wanted to know how process deduplication works before I get into it.

Yes this is what I want to do. My question is how docker manages shared processes between these apps (for example, if app1 uses mysql and app2 also uses mysql).

Does it take up the RAM of 2 mysql processes? It seems wasteful if that's the case, especially since I'm on a low-RAM VPS. I'm getting conflicting answers, so it looks like I'll have to try it out and see.

Aren't containers the product of compose files? i.e. the compose files spin up containers. I understand the architecture, I'm just not sure about how docker streamlines separate containers running the same process (eg, mysql).

I'm getting some answers saying that it deduplicates, and others saying that it doesn't. It looks more likely that it's the former though.