Atemu

It's a LineageOS thing AFAIK. I'd be a bit surprised if GrapheneOS had it since they're quite close to stock AOSP when it comes to customisations that don't relate to security or privacy.

You should scrub your data regularly with btrfs. That's just a mean to verify the data is in-tact though; to detect corruption.

You cannot really do anything actively to keep the data in-tact. Failure can and will happen. To keep your data safe, you must plan for failure to happen:

Expect a power surge to fry all your disks at the same time.
Expect your house to burn down or flood.
Expect to run the wrong command and istantly hose your entire array.
Expect your backup server to get ransomware'd.
...

Only if you effectively mitigate these dangers will your data stay safe.

Pretty cool!

Have you thought about whether this could also be used for limited write access? A common use-case for abusive image gallery services that you cannot ordinarily fulfil with Immich is shared albums where multiple people that e.g. attended the same event can collect pictures in without complex authentication (just a single shared secret or even just the link to the album).

Ahhhhh whyyyyy, you've got all of these standard response codes made for you, why would you blatantly ignore them like that?!

I know that part.

The other fork has existed for a long while.

Is this your personal phone? If your work were to dictate what you are allowed to install on your personal phone, that'd be a serious overstepping of bounds.

Perhaps you can sneak in f-droid via adb install and give it app installation permissions via ADB though.

What's the history behind this? Why could the changes be done upstream, necessitating a fork?

https://lemmy.ndlug.org/post/1268531

According to the author, that has happened quite a while ago and we're now at the next step.

The Immich app.

Although since it doesn't really function as a full gallery app yet, so I have Fossify gallery installed as a backup to open images in via intent.

I only learned about Aves today and trying it out for the same purpose, I think I like its picture viewer better.

Your browser cannot block server-side abuse of your personal data. These consent forms are not about cookies; they're about fooling users into consenting to abuse of their personal data. Cookies are just one of many many technological measures required to carry out said human rights abuse.

Do you have a better source than a 5 y/o comment in an issue?