It’s not a transcoding power issue. It’s a UI consistency and usability issue. With every device having a slightly different UI, with some apps having issues if playing back natively and some needing transcoding, the experience is inconsistent and frankly doesn’t pass the “wife acceptance factor” test, or the “let your friends use it without needing to handhold them through regular troubleshooting for their particular device” test.
I still don’t use Plex and exclusively use Jellyfin, but it’s still a hard sell to non technical users. Plex has much more polish.
Yes. Your machines would have one main IP address, and one virtual IP address that would be assigned to either machine depending on the priority or health check status. That IP can be on the same physical interface, or a separate one. It’s very flexible, pretty standard config for high availability setups.
I think the universal consensus is that outside of a very specific use case: multiple VDI desktops that share the same image, ZFS dedupe is completely useless at best and will destroy your dataset at worst by causing to be unmountable on any system that has less RAM than needed. In every other use case, the savings are not worth the trouble.
Even in the VDI use case, unless you have MANY copies of said disk images(like 5+ copies of each), it’s still not worth the increase in system resources needed to use ZFS dedupe.
It’s one of those “oooh shiny” nice features that everyone wants to use, but will regret it nearly every time.
My bad it’s actually https://banglejs.com/
Tried https://bangle.js? Loving mine so far. Edit: my bad https://banglejs.com/
The universe does seem rather badly designed these days