As a kid I was intrigued by telephones. I got hands on two old rotary phones and I wanted them to talk together. I wired them in series with a battery. Despite my dad telling me it never gonna work - it kinda worked. You could hear the other side just well! It just did not ring.
I've made a great effort in making the phones ring. At that time I did not know it needs 90V (fortunately - I'd probably hurt myself). I figured out it needs AC, but how do you produce AC with only a battery? I even made a hack to rapidly reverse polarity using a relay in self-oscillating mode, only to get shocked by the induced voltage by the relay coil and no ring.
(Now I see that maybe if I used the coil voltage it would actually ring!)
This great article brought back nice memories of tinkering with the phones.
How does SQLite handle HA setups? The minimum I want is reliable automatic failover in reasonable time for user-facing service. Ideally an active-active setup.
Is it just a minimal set of unmodified files and Windows will gracefully degradate to this? Or did he need to patch everything to be able to strip it down?
No, the author is presenting an idea that $25 a month can buy you a node. That fits adding a new node to the network, not taking over an existing node.
The assumption is the adversary controls x of N nodes. When x=N the probability of discovering the onion service IP is 1. But the adversary can not achieve this situation as he only controls the additional nodes. The existing nodes still stay in the network, they do not disappear. The ratio is not x/N but x/(x+N).
How do you solve event schema changes? I mean event has some data attached to it. The schema of this data may need to change in time. How to replay older events that do not match current schema? Do you keep all versions of event reactors to be able to replay old events?