I would love an updated KDX/Hotline server running an a RasPi or similar at home. This was a solved problem 20 years ago. The migration to online based platforms will always lead to network effects and enshittification, for very little gain.
I switched to Capture One a couple years ago and like it - used Lightroom Classic for many years before that, and think I've tried most DAMs over the years.
I ran a Hotline server in parallell with KDX for many years. Came in handy when studying abroad and I wanted to access my files. KDX had screen control as well, which I used to freak my brother out by recording messages and having them play when he was asleep… Good times!
I enjoyed having a "home" online where I could invite friends and strangers – it was so much friendlier than irc.
It's such an incredible flex to have a design system and brand guidelines for a calling card, side of van, oh and here's how to apply logo on a rocket btw.
Love these old design systems and how prescriptive they are.
It's hard to answer that without you saying what you think the obvious benefits are.
Consensus algorithms are important for all kinds of distributed computing problems. A simple example would be failover. If you have a leader database that replicates to 4 others, and you want another node to take over if the leader DB fails, then you need a consensus algorithm to prevent a situation where 2 different machines both think they're the new leader in a netsplit.
There are many other equivalent problems in distributed computing, from atomic transactions to "exactly once" messaging systems.
Asynchronous consensus is a model where you cannot make assumptions about the bounded nature of call timings, whereas in a synchronous model, you can assume everything is bounded.
Byzantine fault tolerance is important for security under byzantine faults, that is to say malicious actors acting deliberately against what the protocol specifies they should do.
