From what I can read, this press release mentions that they have so far reached an agreement to work together on the project, and they are currently _planning_ on using a KSI blockchain. Too early to say if the project will succeed or not.
> If you ran a database of land ownership records or patient healt data for a whole country, would you really be at ease with only PostgreSQL?
With proper access controls, backup system and proper maintenance, definitely. While the DB engine itself can vary (PostgreSQL, Oracle, whatever Microsoft produces etc.), SQL based database engines are widely used in such scenarios already.
Could you name any projects that are based on a blockchain and which could not have been viable with any other technical solution, such as an SQL-based database like PostgreSQL?
In most cases the beefiest air cooler + the lowest tolerable fan curve (meaning no overheating) will do the job just fine, especially if the CPU TDP is between 35-65W. Alternatively you can also limit the CPU power usage by disabling turbo or doing other tricks that forces it to run slower, but more efficiently.
Fan cooling a Raspberry Pi 4 is such an odd thing to do. You are essentially taking one of the pros of the Pi - quiet and reliable operation - and replacing it with a moving part that will not offer too much benefit and will eventually wear out or start having issues.
I must point out that this does NOT cover ThinkPad T and X series. From the press release:
> Our entire portfolio of ThinkStation and ThinkPad P Series workstations will now be certified via both Red Hat Enterprise Linux and Ubuntu LTS – a long-term, enterprise-stability variant of the popular Ubuntu Linux distribution.
The available power budget and memory bandwidth will be the limiting factors for those new APU-s, just like for the current generation. Given the performance requirements that I have seen for VR I don't think the new APU-s will be able to reach that performance level.
For something less demanding it could be OK, not sure where your use case would fit in the performance requirement scale though.
LowSpecGamer did an experiment with VR and Ryzen APU-s, if you want to get an idea of what performance to expect: https://youtu.be/huT6fp7nzwA
Have you tried out ZFS? It's quite good at resolving failures and data corruption and can be configured in all sorts of combinations, depending on your performance and disk failure tolerance requirements.
I have found myself with a similar issue. Haven't been in the industry for too long (been working for over 3 years), but the constant shitshow that is FE development is really taking a toll on me. No matter what you do, people keep changing things, sometimes for the better, other times for no particular reason other than to work on new shiny things. If what I am writing right now will be thrown out soon or rewritten anyway, then why bother? Same goes for some BE stuff, Go language seems to be the new hip thing to do stuff in, repeating the cycle once more.
I have begun trying to find things I truly care about as a countermeasure to this fatigue, so far it seems to be moving in the direction of just helping with repairing and refurbishing used computer hardware. I know how to do it for my own purposes, it's less mentally taxing, you get to save useful stuff from going to the landfill and you will also help cut down on consumption. It probably helps that the results are immediate (broken device -> working device), but going this route will have a minuscule impact also on a larger scale.
I remember reading somewhere that nowadays a significant chunk of the instructions isn't actually implemented on the CPU using transistors, but by using CPU microcode to sort of emulate these instructions by combining existing ones. Someone correct me if I'm wrong.
Given enough writes, any SSD will eventually fail.
As a related anecdote, I did some stress-testing on a ZFS filesystem with two Kingston NVMe SSD-s in mirrored configuration and at one point I got two random read errors on one drive, which subsequently got corrected by ZFS.
Silent failures might not be the best phrase to use for these situations, but ZFS does let you know that corruption has taken place and you have to acknowledge that message for it to disappear.
I also used btrfs not too long ago in RAID1. I had a disk failure and voila, the array would be read-only from now on and I would have to recreate it from scratch and copy data over. I even utilized the different data recovery methods (at some point the array would not be mountable no matter what) and in the end that resulted in around 5% of the data being corrupt. I won't rule out my own stupidity in the recovery steps, but after this and the two other times when my RAID1 array went read-only _again_ I just can't trust btrfs for anything other than single device DUP mode operation.
Meanwhile ZFS has survived disk failures, removing 2 disks from an 8 disk RAIDZ3 array and then putting them back, random SATA interface connection issues that were resolved by reseating the HDD, and will probably survive anything else that I throw at it.
I remember there being issues with the keyboard swap with some buttons not working as expected, plus you have to tape some pins in order to avoid damaging the keyboard or the laptop itself.
Has anyone have any overview of how robust the security situation is? I attempted to setup Jellyfin behind an nginx proxy with basic auth enabled because I didn't know how trustworthy their security is, but ran into various issues with the setup that couldn't be resolved at the time. It sometimes worked, but mostly ran into issues. This was around the time when the fork happened and Jellyfin was very much a new thing, I have not tried it after that.
> If you ran a database of land ownership records or patient healt data for a whole country, would you really be at ease with only PostgreSQL?
With proper access controls, backup system and proper maintenance, definitely. While the DB engine itself can vary (PostgreSQL, Oracle, whatever Microsoft produces etc.), SQL based database engines are widely used in such scenarios already.