Leaderboard

it is going to be very similar to this guide

@jonp I work in software development so all of this is painfully familiar. When I saw the Immich struggles, I immediately thought "I bet they had a solution ready and it was obliterated by one of those updates". That reminds me of the classic: "There are no solutions, only trade-offs." Any half-decent team of developers is capable of making work almost any feature and solving almost any issue. If you are thinking "couldn't they just do X?", the answer is that they probably could. However, that would always be at the cost of something else being worse, broken or delayed... or it would take too much time, require too many people or cost too much money (usually at least two out of three).

Appreciate the criticism and we take it in stride. I respect everything you and others post, both good and bad. Sometimes raw emotional responses can cause gut check reactions of "you're kicking my baby" but I don't let myself see it that way. You're obviously passionate about our project or you wouldn't be here pointing out all the ways in which we can do better. I also respect not wanting a refund and I look forward to the day when I see a post from you saying, "ok, this was totally worth it and I'm glad I bought." 💯 Agreed. Our CTO has a proposal for us this quarter to do exactly what you're talking about. It's premature to share but know that we are on the same page and intend to do this. We intentionally built the global HexOS messaging system for this back with the Q2 release. We now want to expand that to include notifications for app-specific issues like this. But keep in mind that was not the original plan for 1.0 so the scope is no increasing, which is fine, but we still have other projects and objectives to hit, one of which is the Local UI which is a much bigger project than I think anyone realizes. It's complicated by the fact that our actual footprint on the ISO today is very small and we do not want to bake any of our UI into that ISO either. Instead, we have to build a full container/app for this which we are doing, but it's a huge project and we have a senior dev completely focused on it right now. I feel like a broken record saying this, but a big part of our struggles this year is bootstrapping the business. Money doesn't solve everything, but it sure as heck would have helped to hire a lot more developers and app specialists right at the beginning of this year, but we opted for a more fiscally conservative approach to hiring to ensure we don't grow too big too fast and make commitments to employees we can't keep without proving our business model first. Expansion is a big part of our plans for 2026 and will help us get more focused on individual layers of the software. Sure, but that comes with its own set of challenges and problems. Again, everything is still in flux and user data is not at risk. The worst anyone should have to deal with is reconfiguring immich from scratch which of course isn't ideal, but let's be honest here, it's also not the end of the world or an unrealistic expectation given the beta nature of both us and Immich itself. Comms of course could be better, always. But we are doing the best we can with what we have for now and we would just ask people to be patient while we work through it. This was all part and parcel of participating in the beta and if that's not going to work for anyone, waiting to deploy until more polish is applied would be the right approach. I've already spent hours reading and replying here and the more we try to get ahead on comms, the less time we spend on building and getting to a release. Every hour is a choice and often there are no options that will satisfy everyone. Still totally understand the frustrations, but this is the last I'll be commenting on this today so I can get back to work with the rest of the team. Our new docs site is a great place for us to put a guide for immich issues and resolving them in the future. Stay tuned for more, but know that we don't have the ability to always drop everything we are doing to shift focus to an issue like this when we are in the middle of other projects. There can be a lag time and that is something everyone here will have to accept while participating in the beta. Again, if that doesn't work for anyone, wait for the polish to come before deploying.

😞 I totally get this disappointment. I don't even blame you. We are targeting a more casual user and I can see how users like yourself may have had a higher expectation closer to that of a video game beta, where it's really software that's functionally complete, but just testing integrity of the infrastructure for multiplayer and game balance. You might find a bug or two, but nothing too crazy because part of the purpose of the beta is to build hype for the game prior to release, as we just saw with Battlefield 6 Open Beta. All of that said, we did say this was beta and listed out all the risks in the very first post you read to get it downloaded and installed. Furthermore, we actually had a second fix in for th migration issue for Q3 but due to another immich update, it broke again literally the day before the Q3 release and we missed it because QA was the week prior. This was just a very unfortunate coincidence. It seems like you specifically may be very frustrated with us and not happy with your experience. If you would like, I will refund your purchase. We don't want anyone feeling raw about their transaction, so if you want to take me up on that, feel free to drop me a DM. We are a small but growing team and will speak to our plans to get even better about this for post 1.0. We will be building an Apps team that will be responsible for ensuring our curations remain solid and that we handle these types of issues better. This analogy was spot on. Appreciate you taking the time to lay that all out.

Not affiliated with HexOS, but here's a quick analogy to explain what's actually going on behind the curtain for a layman. HexOS are assembling a car, which is being built on an existing Chassis (TrueNAS) that has over the past 12 months had some pretty significant structural changes. While the changes are good and will make the final car better, it means the development of the car is complicated because the way the seats bolt in, and the size of the windscreens are changing while they're assembling the car. HexOS said 'This car is still being built, you can use it, but if you need to drive for your job you should wait until HexOS is finished before selling your old car'. HexOS are in the process of upgrading the driving wheel, figuring out A\C, and putting in the car seats, which keeps them pretty busy. While the car drives, it's not really a production car just yet. The radio manufacturer decided to change the wiring requirements all of a sudden with the new model they released, so HexOS need to tweak the wiring so the radio keeps working. All of this is happening while thousands of people are driving the car, and asking when the A\C will work, or when the new seats will be available. You can fix it by taking the radio out and putting it back in yourself (re-installing Immich) Or you can wait until they have time to fix the wiring in the back-end, which they will do eventually. A car without a radio still drives. Again, this is a beta. Stuff will break, and until they reach 1.0, expecting everything to work 100% and non-critical issues to be fixed quickly is just a recipe to be disappointed.

Its disappointing that out of the very limited amount of apps initially provided, Immich and Plex both still have issues. I appreciate this is early adoption but at minimum I think the HexOS team should write clear documentation on how to overcome these issues (even if this takes you away from the deck into truenas)