vogam7

The people saying everything is fine have got to be software developers who see this only from one perspective. Hate to break it to them, most people we'd expect soon to pay full license fee to keep the project going aren't, and those are exactly the potential customers we'd lose with this laid back mindset to weak areas of this project. Those won't be beta expectations anymore and there will be a lot to prove to doubters of this project to justify the price. Imho plex & immich was genuinely exciting to watch grow naturally, and backing them early felt like a bargain especially towards stable launch. Was it perfect? No, there were delays too. But none I recall having such communication meltdowns close to stable release. I'll be honest, some of the responses here concern me as much as the delays and comm issues themselves. Some say I knew it's part of the process "when I read Q1 2026 I think Q3 2026" maybe, but not this far into this beta with no updated written delay comms. Others react confused when I try to hold the team to their own deadlines. 'I'm glad they're not communicating, that means time is much better spent on making the software...' really? Good teams do both and I'm not asking for daily extensive blog posts of what and why went wrong, just a sentence update across all hexos communication channels setting new expectations. I recall people on this very forum calling out poor communication back in July and October, and the team acknowledging it and promising to improve. Yet here we are. Traveling or not, I still don't understand how the whole team forgot the most anticipated day of their own project, or couldn't break the news of a delay at least the night before. Now whether April Fools or not, yesterday would've been the first day after stable launch with customers paying $300 for a license, needless to say the most expensive nas os on the market. At this point, if the team still offers a refund option, I'd happily take it.. this just isn't for me anymore

Another month, huh? The least you could do is respect the people waiting with some communication ahead of time. Instead it's silence all day on release day and a last-minute delay notice as if it wasn't clear days ago this could happen. You created this self-imposed deadline,, nobody forced it. A delay with advance communication - fine. But the silence until 9 PM? That's just pure disrespect

I'll just say what many are thinking here.. you're launching a hexos local beta just 9 days before the promised stable release date. How could this be included in 1.0 and called stable in under a week of testing? Refunds seem to be the go-to response for anyone who expresses frustration in other threads.. but that's beside the point for those of us who actually want this project to succeed. Missed deadlines are frustrating enough, but the communication issues that still keep coming up alongside them make it worse.. and for a project that depends on people investing in hardware, that trust matters. Server memory and now drives have nearly doubled since the originally promised end of 2025 release date. Every delay has a cost beyond just frustration. A straight timeline update would go a long way. I don't think you meant it this way, but the timing of this post is pretty telling... are we in for another delay?

With only a few weeks left before the stable release, could someone confirm or deny whether single-drive pools still break the HexOS interface? Has this been fixed already? I couldn’t find any recent updates on the forum when searching “single drive pools” since a few posts from Jan / May

'Coming in Q2’ probably means no news until late June. Jokes aside, my biggest gripe is that Hex OS, which was supposed to save us time by eliminating the need to deal with config headaches and dig through TrueNAS manuals, actually <at least for now> introduces more moving parts and points of failure in the TrueNAS and Hex symbiosis. I get that many issues appear to be caused by people updating to unauthorized versions of TrueNAS, but there are also a number caused by unintended Plex or Immich app updates and/or unusual app configurations, forcing the need to find advanced workarounds that the product’s intended novice NAS users likely wouldn’t have to deal with on latest vanilla TrueNAS OS. I appreciate the challenge the dev team is tackling, but maybe this should’ve stayed in closed beta a bit longer