Personally I would absolutely not want to ever feed my documents into an off-device model, but the point of self-hosted software is that it does what you tell it to and they absolutely should include letting you make bad decisions. decide what’s right for you.

FTFY (although I share your judgment). No disagreement about the rest.

Care to specify what you mean by “that”? It’s been a lot.

Long-time immich user here, similar problem. The issue (for now) is that only the owner of the media has write access. With partner sharing, all you can do is read the media (and add them to albums).

What I do for now with “trash media” (e.g. photos of receipts and other stuff that one snaps pics of for practical reasons and then forgets): I add my partner’s trash to an album named “please delete”. I periodically ask them to go through it and remove anything they want to keep, then have them select and delete everything in that album in batch.

Why this may not be practical for you, OP: you have two “trash producers”, so you’d have to keep a “trash” album for each of them (and sort trash media correctly). This is tedious work and error-prone: if you have only one pic in you “trash” album that your account does not own, selecting and deleting everything will fail, sending you on a hunt for the one misclassified picture in a batch of >200…

What immich may do about this in the future, as according to their roadmap: in the past, they were planning to add “more granular permissions controls”. Right now, they’ve renamed that to

User groups: Manage groups of users and share albums with a group

I hope this will include permissions management as well.

Wither way, the feature is likely to come with a greater overhaul of partner sharing. Partner sharing, as of now, is partly “broken” due to past design decisions: you can’t

• write to your partner’s files
• share facial recognition data: each one needs to classify people in their pictures individually (e.g. both need to tag “Uncle Fred” individually in their own accounts)
• share memories: only pictures owned by you will show up in memories, not your partner’s

And before anybody asks: no, there’s no ETA…

Soon

True, although we must concede there is a difference between the simple machine learning already present in paperless and LLMs where, depending on quantization, CPU-based inference doesn’t get you very far.

Hook up the TikTok repos and you’ll get downgrades every 20 seconds.

I do understand and share people’s hatred of corporate-owned, centralised cloud AI.

I understand (though share to a lesser degree) people’s ethical concerns about how these models were trained (copyright has been broken for a while now, this just exacerbates it).

But this level of outrage about using local models on an opt-in basis strikes me as hysterical.

Feel free to change my mind.

Man, that is so outdated! /s

I’m the violence.

Great, I’ll probably do just that this summer. Thanks for the info!

I’ve got a second deployment of immich that also got stuck somewhere on v1.x. May I ask how you upgraded to the most recent version? Did you just go for 3.0, or did you do “baby steps” in between? (e.g. 1.138 > 2.0 > 3.0)

I do still read the changelogs and compare compose files thoroughly on every major update. With that in place, Immich has not once broken down on me, and I’ve been here from almost the very start.

unless you rip the movie out into a single file first

I don’t see the problem with that. It’s what I’ve done with every single disk I own. Why would I bother with badly-written menus, pointless extra content and tons of ads and copyright warnings I need to sit through before I can watch what I paid for?

You patched the annoying “crash-on-start” bug! 😍 I was collecting diagnostics to help nail it down, but you guys were faster. Keep up the great work! 👍👍👍

Thank you! While that does allay most security concerns, it does beg the question how useful such a vulnerability tracker is if it doesn’t actually show any relevant vulnerabilies and you constantly have to second-guess what it says. Warning signs that aren’t actually warnings because it’s “just a false alarm” quickly teach personell to not take warnings seriously - unti, onel day, it’s not a false alarm…

Thanks for your detailed reply!

To make that happen, the attacker must […] already have access to the server to upload and process the file, which means that security has already failed.

Do I correctly assume that by axis you mean shell or even root level access? If not, any of my regular users (turned rogue…) could upload a poisoned raw file which nextcloud would process to, for instance, generate a thumbnail.