_Nemo_

You are correct, it seems to have supported it for a while now, but it got more support now.

I’m afraid MusicBee is not for me since my household has been powered by Linux only for years now. I’ll look into that beets plugin though, which has been recommended to me somewhere in the comments before. Thanks!

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, similar problem. The issue (for now) is that only they owner of the media has write access. With partner sharing, asks you can do is read the media (and add them to albums).

What I do for now: I add my partner’s trash media (photos of receipts and other stuff one snaps pics of for practical reasons and then forgets) to an album: “please delete”. I periodically ask them to go through it and remove anything they want to keep, them have them 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).

What immich will do in the future : they have more granular permissions controls in their roadmap. The feature is likely to come with a greater overhaul of partner sharing. Partner sharing, as of now, is partly “broken” due to 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

Before anybody asks: no, there’s no ETA…

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.

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.

I’ve seen Immich mentioned around here before, but I’ve honestly never set up even a real homelab or sever before, so that’s a bit daunting.

I haven’t been in this space for too long either, but immich is what brought me here. I tried it out locally - no deecated server, just spun up immich on my desktop machine to try it out. And it was just so good it made me want to have a server and learn the ropes.

I’d recommend you try it out this way too. We’ll see each other on the other side of that rabbit hole. ;)

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 guys 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! 👍👍👍

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.