As I understand they weren't building tunnels, so every time a legit client wanted to it has to wade through all the bad nodes to find a good one, so everything slowed right down. I was building at about 3% success rate during the issue which enables general eepsite browsing but torrenting was essentially dead
Agreed; I have no idea how you'd implement that across multiple ASNs, which is definitely a requirement for multi-cloud or geo-redundant architectures.
Seems like you'd be trying to work against the basic design principles of Internet routing at that point.
You can configure your assigned network numbers that other AS are allowed to announce certain networks of your own. Not uncommon for in examples authoritative name server addresses.
Chan yin-lam case is one that always sticks in my head.
I can well believe correlation is sometimes the answer but the odds of an award winning swimmer doing a midnight dip and washing up naked the next day, with a rushed police investigation and extremely expedited cremation is a fair bit to accept as coincidence
I checked Chan Yi Lam’s Wikipedia page. It was ruled a suicide. The conspiracy theories surrounding this case are absurd and out of control. People even challenged her mother’s identity, forcing a DNA test to be done, and yet the crowd still continued to harass her mother.
https://yggdrasil-network.github.io/ for the most part enables this - otherwise I2P and Tor for the most part facilitate this with the bonus encryption element.
We might one day have it natively with ipv6 adoption increasing.
Yes, I use flux which has a similar HelmChart/HelmRelease resource. One of the things that took me a while to "get" with K8s is operators are just clients running on the cluster.