You might consider something like the friendly elec CM3588 for a DIY option with openmediavault or freenas. I have a big old box currently with spinning metal, but am looking at this as an option now that there are some larger m.2 drives available.
You might consider something like the friendly elec CM3588 for a DIY option with openmediavault or freenas. I have a big old box currently with spinning metal, but am looking at this as an option now that there are some larger m.2 drives available.


I really wish they would ditch the elongated display ratio. It’s wasted space in landscape 99% of the time, makes the top of the display inaccessible with one hand and the phone unnecessarily large in your pocket. The premium on these could be justified when all the features hit that mark but this is poor human ux.


I tried bazzite, which is very close to kinoite, as Fedora itself had a great out of box experience, even on laptops.
Whilst there was a way to get most setups, apps and configs working it was clear I would eventually run into a piece of software that the effort to get it working was not worth it. Some software and development tools are not (yet) designed and maintained to easily work in an immutable environment.
My biggest gripe was that any interaction with os-tree meant that updates now started to take a really long time building the image with high CPU/power usage. I wasn’t ditching Windows to go back to a world of unnecessarily long updates.
For some, I can see the immutable can work well if they want an Android like experience and can accept the software catalog available. It wasn’t the right model for me, as I expected my machine to do more than point and click app install. I would be curious how your typical arch user would find it.
The author demonstrated that the challenge can be solved in 17ms however, and that is only necessary once every 7 days per site. They need less than a second of compute time, per site, to be able to send unlimited requests 365 days a year.
The deterrent might work temporarily until the challenge pattern is recognised, but there’s no actual protection here, just obscurity. The downside is real however for the user on an old phone that must wait 30 seconds, or like the blogger, a user of a text browser not running JavaScript. The very need to support an old phone is what defeats this approach based on compute power, as it’s always a trivial amount for the data center.