Follow up on supporting Immich announcement Hello everybody, Alex from Immich here. What a controversy that we caused with the choice of wording, right? My personal apology to you all. On behalf of...
Alex from Immich here. What a controversy that we caused with the choice of wording, right? My personal apology to you all.
On behalf of the team, we would like everyone to know that we hear your concerns and we appreciate the love and care that you all have expressed for the project. At the end of the day, what we want most is to make sure you are all happy using the app.
With that said, we are working on a change to the word license: we will not call it licensed or unlicensed anymore. What will it be called?
We are still thinking of different options to make the wording less confusing. The new wording will hopefully showcase our intentions properly going forward.
We’re also working on updating the FAQ with more information to clarify those intentions. We just want to provide good software that people will want to pay for whilst not limiting your usage in any way if you can’t.
So expect these changes over the next week. We’re pushing this out now to let you know our appreciation for the feedback you’ve given us.
The amount of purchases in the first 24 hours has been overwhelming. Thanks everyone for the great support!
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.
What I don’t get is what would compel me to get a license.
Ideally nothing. Maybe a sticker or a theme, but nothing important to the function of the tool. If the personal gratification that comes with offering financial support to a FOSS project (along with the resulting product itself) isn’t enough, then this “license” (or whatever they end up calling it) isn’t for you…ideally.
Should I not be able to use the software if I’m donating?
I see these comments going “oh it’s still alpha, we need to encourage them”. Well it should have exited alpha a long time ago, and secondly I’m not going to pay for the mere possibility of it being useful at some undetermined point in the future. Show my something useful now.
If anything, Immich has demonstrated it has no intention of ever becoming a useful project. A perpetual alpha that breaks super often and plans to remain in that state on purpose indefinitely should not be asking for any support.
Even in FOSS you have to show some modicum of practical sense. FOSS was founded on “scratch an itch” not on “break forever”.
Should I not be able to use the software if I’m donating?
You should be able to use it fully regardless of whether you’re donating.
I’m not going to pay for the mere possibility of it being useful at some undetermined point in the future.
That’s fine, by definition, a donation means you’re not paying for anything.
Immich has demonstrated it has no intention of ever becoming a useful project
I take it you haven’t been in the self-hosted photo space long. Even despite their alpha status and frequent breaking of backwards compatibility, it’s still the best experience I’ve had (comparing to Plex, Nextcloud, and Photoprism). But if you can find something better, I’m all ears.
OK but that just means the offer for this particular type of app sucks. It doesn’t make Immich good.
It’s not really uncommon in the selfhosted space, there are some huge gaps. Try finding a multi-account email webapp for example, or a CalDAV/CardDAV webapp.
I don’t follow the argument you’re trying to make. Immich is fast and simple which fits my requirements where others don’t. If you know of a better alternative, I’m all ears.
Immich recently had a bug where it would delete all the photos if you remove a gallery. It has breaking changes and API changes all the time. Why? I don’t know. You do NOT need to break the API every other minor version, it’s super dumb.
That makes it impossible to use it with other users because I can’t control how and when their mobile app gets updated, which means at any given time I have no idea if their apps will work with the server version. And when they do work, they’re buggy.
You can use it just for yourself if you’re very careful but it’s not something I can offer friends or family and promise it’s better than Google Photos or iCloud. Not if it doesn’t work half the time and may delete their photos every once in a while.
A simple alternative is to use a sync app to upload photos from a person’s phone and then use a reliable (doesn’t break all the time) photo webapp to let them browse them. They can still manage their photos locally, and use other services, and other backups and so on, they just have an extra backup + viewer.
Yes, I highly recommend not relying on alpha software ever as your daily driver. I never give my photo viewing software write permissions on my images, so there’s never any risk of losing data. And yeah, I’m not directing anyone outside my household to it, so I currently don’t need to worry about servicing a bunch of users.
The app/webapp mismatch issue has been more annoying that I think it needs to be. I understand the need to make security updates, but breaking compatibility this often is unusual.
But again, my point is, the money you give them is a donation. If you don’t want to donate, then don’t. There should not be any incentive to get you to donate, besides seeing the project continue.
The impetus to pay once is supporting great Foss software. I personally think a donation model works for me but I don’t research human behaviour or marketing either.
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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Copy/paste for the lazy:
–––––
Hello everybody,
Alex from Immich here. What a controversy that we caused with the choice of wording, right? My personal apology to you all.
On behalf of the team, we would like everyone to know that we hear your concerns and we appreciate the love and care that you all have expressed for the project. At the end of the day, what we want most is to make sure you are all happy using the app.
With that said, we are working on a change to the word license: we will not call it licensed or unlicensed anymore. What will it be called?
We are still thinking of different options to make the wording less confusing. The new wording will hopefully showcase our intentions properly going forward.
We’re also working on updating the FAQ with more information to clarify those intentions. We just want to provide good software that people will want to pay for whilst not limiting your usage in any way if you can’t.
So expect these changes over the next week. We’re pushing this out now to let you know our appreciation for the feedback you’ve given us.
The amount of purchases in the first 24 hours has been overwhelming. Thanks everyone for the great support!
Have a great weekend!
Immich team.
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.
Ideally nothing. Maybe a sticker or a theme, but nothing important to the function of the tool. If the personal gratification that comes with offering financial support to a FOSS project (along with the resulting product itself) isn’t enough, then this “license” (or whatever they end up calling it) isn’t for you…ideally.
Maybe a [SUPPORTER] badge?
Should I not be able to use the software if I’m donating?
I see these comments going “oh it’s still alpha, we need to encourage them”. Well it should have exited alpha a long time ago, and secondly I’m not going to pay for the mere possibility of it being useful at some undetermined point in the future. Show my something useful now.
If anything, Immich has demonstrated it has no intention of ever becoming a useful project. A perpetual alpha that breaks super often and plans to remain in that state on purpose indefinitely should not be asking for any support.
Even in FOSS you have to show some modicum of practical sense. FOSS was founded on “scratch an itch” not on “break forever”.
You should be able to use it fully regardless of whether you’re donating.
That’s fine, by definition, a donation means you’re not paying for anything.
I take it you haven’t been in the self-hosted photo space long. Even despite their alpha status and frequent breaking of backwards compatibility, it’s still the best experience I’ve had (comparing to Plex, Nextcloud, and Photoprism). But if you can find something better, I’m all ears.
OK but that just means the offer for this particular type of app sucks. It doesn’t make Immich good.
It’s not really uncommon in the selfhosted space, there are some huge gaps. Try finding a multi-account email webapp for example, or a CalDAV/CardDAV webapp.
I don’t follow the argument you’re trying to make. Immich is fast and simple which fits my requirements where others don’t. If you know of a better alternative, I’m all ears.
Immich recently had a bug where it would delete all the photos if you remove a gallery. It has breaking changes and API changes all the time. Why? I don’t know. You do NOT need to break the API every other minor version, it’s super dumb.
That makes it impossible to use it with other users because I can’t control how and when their mobile app gets updated, which means at any given time I have no idea if their apps will work with the server version. And when they do work, they’re buggy.
You can use it just for yourself if you’re very careful but it’s not something I can offer friends or family and promise it’s better than Google Photos or iCloud. Not if it doesn’t work half the time and may delete their photos every once in a while.
A simple alternative is to use a sync app to upload photos from a person’s phone and then use a reliable (doesn’t break all the time) photo webapp to let them browse them. They can still manage their photos locally, and use other services, and other backups and so on, they just have an extra backup + viewer.
Yes, I highly recommend not relying on alpha software ever as your daily driver. I never give my photo viewing software write permissions on my images, so there’s never any risk of losing data. And yeah, I’m not directing anyone outside my household to it, so I currently don’t need to worry about servicing a bunch of users.
The app/webapp mismatch issue has been more annoying that I think it needs to be. I understand the need to make security updates, but breaking compatibility this often is unusual.
But again, my point is, the money you give them is a donation. If you don’t want to donate, then don’t. There should not be any incentive to get you to donate, besides seeing the project continue.
Just don’t monetarize then. Foss and community driven is just that like many other projects. Clearly these guys are trying to sell the shit
Are you not aware of the countless issues with absolutely unsustainable open source projects out there in the wild?
We need a cultural change and a way to normalize supporting and paying (whoever can afford to) for good open source projects.
The impetus to pay once is supporting great Foss software. I personally think a donation model works for me but I don’t research human behaviour or marketing either.
the project is still in alpha, its normal they have breaking changes
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.
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.
I agree. From what I’ve read, they now have (published) plans for what’s ahead.
I can wait. Until then I will collect picturr folders c:
Alright then. We’ll talk about money when it’s out of alpha and stops breaking.