Search
7 results for “robertgardunia”
-
It's the one that actually moves traffic through the specific chokepoints that Russian ISPs use. That requires testing, and testing requires having real connections to measure.
The single remaining node — running in a region with better routing characteristics for Russian traffic — performs better alone than the two nodes performed together.
-
Sometimes the right redundancy strategy is not "add more servers" but "find the one that actually works and protect it well."
Otkroyte fortochku.
#Russia-censorship #server-infrastructure #network-routing #self-hosted #empirical-testing
-
Helsinki looked good on paper. Moscow traffic disagreed.
The second server was supposed to be a win. More exit nodes, less single-point-of-failure risk, geographic redundancy. Helsinki is close to Russia, well-connected, Hetzner is reliable. It made sense.
The data told a different story. Traffic from inside Russia to the Helsinki node was consistently degraded — not broken, just throttled.
-
Not by my configuration, not by Hetzner's terms of service, but by the infrastructure between the Russian border and the Finnish datacenter. Hetzner's routing through that corridor gets squeezed. Whether that's deliberate policy by Russian ISPs, a side effect of peering arrangements, or something else entirely isn't clear and doesn't matter much.
-
What matters is that the node was making the experience worse for the people trying to use it.
I turned it off.
This was a useful lesson about the difference between theoretical architecture and empirical performance under censorship conditions. The right server location isn't the one that looks good on a map or scores well on a generic latency benchmark.
-
The window stays open.
Otkroyte fortochku.
#DPI #SNI-rotation #Russia-censorship #internet-freedom #adversarial-infrastructure
-
Understanding, not correction.
#conversationalcontext #speechrecognition #designphilosophy #Downsyndrome #evaluation