this post was submitted on 21 Jul 2024
138 points (96.0% liked)

Selfhosted

40173 readers
651 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 19 points 3 months ago* (last edited 3 months ago) (17 children)

I get that they're trying to figure out how to monetize it while staying kosher FOSS, and their first wording suggests they'd like to offer per-seat licensing.

What I don't get is what would compel me to get a license. I still can't rely on it for anything serious. I'm basically using it as an UI for the face recognition models and that's shoddy too. They've made it impossible to lean on it for anything else.

I don't want to sound like a hater because they're obviously working hard on it but, God, you can tell they're not professional developers and it's so frustrating. Focus on doing something well, and stop breaking compatibility every other week.

[–] [email protected] 7 points 3 months ago (4 children)

the project is still in alpha, its normal they have breaking changes

[–] [email protected] 0 points 3 months ago (2 children)

Being in alpha and having breaking changes is fine, the question is how many. My impression is that Immich seems to introduce breaking changes far more frequently than what people might be used to from other projects.

And that does go back to professionalism: The better you plan ahead, the fewer breaking changes you have to impose on your users.

[–] [email protected] 2 points 3 months ago* (last edited 3 months ago) (1 children)

Almost all oft their breaking changes over the last few months were about their docker-compose setup and the simplification of the same. They've startend out with multiple purpose-specific (micro) containers, which turned out as a Bad design decision. These changes require manual intervention but seem to be mostly finished, so I don't expect these to be many breaking changes in the forsseeable future.

The better you plan ahead, the fewer breaking changes you have to impose on your users.

I agree. From what I've read, they now have (published) plans for what's ahead.

[–] [email protected] 1 points 3 months ago

I can wait. Until then I will collect picturr folders c:

load more comments (1 replies)
load more comments (13 replies)