Leaderboard

defintely also check out the prices for seagate exos drives, they are surprisingly affordable. its very possible your cpu despite its age is more than adequate for transcoding. i would test it on its own first prior to committing to a gpu. a gpu would add idle power draw and the costs do add up over time.

Looks like a solid system. No dramatically oversized boot drive, Intel NIC, CMR HDDs (if you stay with the Red Plus variant, absolutely avoid SMR drives) Depends on what your needs are, but as a NAS with only plex and not to many streams in parallel, this should be up to the task. You can edit a post 5-10min after you posted it, after that you can no longer edit it.

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.

It's not about delivering on a milestone promise, it's about how customers experience the product. Imagine being someone who thinks they're buying a "plug and play" NAS software, meant to hide the complexities. They particularly like the idea of local image storage. They pay $200 for HexOS. They install it, see Immich, and find that it doesn't install. Assuming this person was not involved in the forums, this was their experience of the product between the time app installations and updates stopped working in last year's TrueNAS version, and the delivery of the Q2 update where (if I remember correctly) there was a prompt to update TrueNAS. And now? Same thing. A new customer would again see a broken feature. Assuming they do go to the forums they see it's supposedly "top priority" to fix, but a month and a half later the response is "wait and see in Q3". Your perspective as a company seems to be entirely technology focused, but you have users now. Who are customers. They're not all geeks. They don't all read forums. I think it would be a good idea to spend a bit more time considering how they experience the product and any issues with it. That doesn't necessarily mean throwing everything else on the back burner to hurry up and fix an issue immediately, but at least surfacing information in the HexOS interface where most people would expect it to show up, might be a good idea. I can think of no good reason for instead letting users just try and fail to use a feature that is currently known to be broken. My intent here isn't to bash. It's the same type of feedback I give our R&D department where I work, when they try to release products that are fine for a technical person, but six months away from being ready for consumers. They can get laser focused on making the technical side work, and aren't always able to take a step back and think like a user. If you (as in the company) don't really care, fine, it's your business. I think you _should_ care more than you seem to be doing, is all I'm saying. 🙂 I won't flog this horse any more now. No need to respond, I just hope it's taken onboard as constructive feedback.