jonp

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.

@mill3000 can you take care of this gentlemen's request? Thank you!

😞 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.

To be fair, we actually did fix the issue referenced in that post. However, additional issues have crept up especially with the recent updates to Immich in preparation for their 2.0 release. One major change they made actually requires users to go through a migration process (a choice by the app developers). It's important to remember that Immich is a free-to-use self-hosted solution, which means that sometimes they may need to do things like this as opposed to the slick polish you'd see on a commercial product. That being said, we're still incredibly impressed with Immich and see it's future very bright.

We actually began the VM work last year but it started breaking as TrueNAS was making changes to the underlying stack. As such, VMs were delayed as a feature. 25.10 promises even more improvements to the VM stack and API so we aren't going to resume work on them until that is stabilized. In the meantime basic start and stop functionality exists in our command deck so if you create a VM in TrueNAS it will show up for basic controls in our UI.

We've discovered a handful of different issues with immich plaguing users. We are on the case and it's a priority issue for us!

Agreed. Thread has run it's course.

Good catch. @jerod we should probably map those folders automatically for qBittorrent.

Thank you for the thoroughly detailed report! This definitely helps. @jerod and the team and looking into this further and exploring different paths to resolve.

I think there may be a few gremlins at play here and it's worth spending a little time investigating given the amount of feedback we see here.

We've stated previously our intentions to skip past 25.04 entirely in favor of 25.10 when it drops. The Q3 update is for the Command Deck.

Team and I are reviewing it tomorrow a bit deeper. Thought we had this resolved for all but apparently not 😡

You may need to clear your browser history on Chrome. I thought the deck was down for a sec because of your post and I couldn't find my server, but it turned out my Internet had gone down at the same time. Apologies to our dev team for starting a false alarm ;-).

Investigating!

Fyi, Q3 update went live today along with a new docs site: docs.hexos.com We are listening to you guys!

Hey all. Q3 update coming Monday. Bunch of other goodies and content with it.

Fair point. We are planning to update the site for end of year with more content and details. I'll make sure this gets addressed. There are three types of issues that can exist for a given app: issues with the app itself (responsibility of the app developer), issues with the TrueNAS-cataloged container (responsibility of TrueNAS), and issues with the app curation itself (responsibility of HexOS). For issues with the app, if we can clearly identify the problem, we have no problem carrying the torch up to the app author to get proper visibility if required. For issues with the cataloged app in TrueNAS, we can escalate to TrueNAS directly for intervention if we can identify the root cause properly. For issues with the curation, we can quickly modify our curation using the new system to push out a fixes. We also will have a new docs site that will launch with the Q3 update explaining out the curation system works and how others can participate to help us fast-track the curation of other apps while we continue to work on core features.

We officially announced our intention to delay VM support as part of the Q1 status update back in March. Since then, its important to note that TrueNAS pivoted their VM strategy again when they decided to drop Incus for traditional VMs and go back to their previous implementation with libvirt (as of 25.04.2). Due to all of this, we decided it would be best to restart the VM implementation in 2026 once development is finalized. I can see the confusion here, but we never promised all of these features would be delivered with the 1.0 release. Our focus on 1.0 is achieving platform stability. Furthermore, you're forgetting one pretty major feature that wasn't listed on the site: Local UI. This is the next feature we are focusing on after the Q3 release. Snapshots and Buddy Backups are still possibilities for this year, but likely would continue to carry the "beta" tag into 2026 to give more time for public testing. The Q3 update is nearly complete, which will carry some pretty big features including MULTIPLE new curated apps and folder support for Apple Time Machine/Quotas. Furthermore, we will have a new "Experimental Features" toggle that will enable users to create Encrypted folders as well as provide access to our new app templating/install scripts solution.

So actually we do want to have an official discord (in fact, we already have it "parked" so-to-speak), but we want to wait to roll it out when we can be more prepared to manage it. Our team is entirely revving on dev cycles right now and adding comms platforms to manage to an already thinly spread set of resources is only going to overwhelm and delay development. Bottom line is that I'm all we've got for official comms right now and I'm spread insanely thin at the moment. I really want to hire someone to take over communications for me, but the timing for that is more likely Q4 or even Q1 2026.

I dig tunnels 😉

100%. We are opening that up this week and doing a little forum reorg. Support forums will still be locked to paid customers only, but announcements will be opened up.

Definitely appreciate the feedback. We acknowledge there are multiple areas for improvement, especially in how we communicate and relay information.

Thoroughly agree. We will improve the labeling of updates going forward.

In early June, there was an issue with HexOS where users couldn't download and install either of our curated apps. That issue was resolved with the Q2 update allowing users to update to 24.10.2.2. Separately, an issue with the storage configuration on Immich creeped up at the end of Q2 as well. Apps is the refocus of our attention for Q3 as we prepare to deploy a new templating system for curations that should improve our efficiency at both supporting what we have and adding more. We delivered on our promises for Q2 and now we're working on Q3. Not everyone is going to be happy with the pace, the order we choose to attack things, or how we communicate. All I can ask is to judge us based on what we deliver this year.

I'm deeply disappointed to hear this. We did have a banner on the forums for a while pointing to the Q2 update, but the post itself is still where all of our update posts have been going: the Announcements forum. In addition, there have been multiple Command Deck updates since then that have seriously improved deck.hexos.com performance and responsiveness, as well as resolved a significant networking bug. Check out the Announcements forum and specifically posts by @jerod (our CTO). FYI, I'm Jon (the CEO and Co-Founder). Clearly we're missing some simple comm relays (like the Q2 update dropping) and some of our terminology could be more clear (differing from major and minor updates, OS vs. Command Deck as well). I do apologize for that, as comms are ultimately my responsibility right now. I've told our dev team to stay out of the forums beyond reading posts and communicating with @mill3000 on relevant support tickets. No blame on them for their lack of activity here. And while I greatly appreciate your input and desire for a dev-blog, we honestly just don't have the appetite to do it right now. Writing blogs wasn't part of the job description for the dev team either. We're putting all of our effort and the capital that was entrusted to us by customers (like you) towards building the product. I'm not sure what you mean by this comment. Is there an app you're trying to bring to HexOS that you've developed? I get it. You feel strongly about the devlogs. 😮‍💨 I don't. We're not even making big investments in marketing right now (our website is still the same from after launch week). All the capital is going towards making this thing really great (including backing/funding the ZFS AnyRaid project). Maybe that changes in the future when it makes more sense to me. Right now, each on-the-clock keystroke from our dev team goes to writing code or communicating ideas internally to further the project. I provide updates as I can and when there's something important to say (such as a release dropping). Clearly you're missing some of those and I'm struggling to understand how and why. It's important that I get this sorted because if it's happening to you, I'm sure it's happening to others as well. Especially as we're now moving at a faster pace than we were in the first half of 2025 and anticipate more frequent updates moving forward. I feel this too. 🤦‍♂️ I see the purchases you made and when you made them. @mill3000 referred to you as an OG and he's not wrong. No worries, I ignored all the BS from your post....mostly ;-). I definitely recommend checking your server for the Q2 update (the Command Deck will immediately be different if you haven't noticed already) and if you haven't, apply the available OS update from the Activity card on the dashboard. We have a lot more in store for Q3. I'm working on a few blog posts now. one to catch everyone up from June, and another to talk about our upcoming plan for apps. Thanks for taking the time to let us know how you're feeling. I'm confident if you purchased based on the vision you saw from us last year, you'll be happy you did by the end of this year. If you ultimately feel sour about this and want a refund now, let me know and we'll take care of it for you.