Earlier quoted context omitted.
Lol. That was _before_ these new restrictions. And don't assume that you could setup a simple wireguard server and be done with it. No, it had to be a proper low fingerprint method (e.g., you had to hide the tls-in-tls timing pattern and do traffic shaping). Now, something like dnstt sometimes works, sometimes doesn't. You may be able to open gmail in 10 minutes if it does, and you explicitly have to block the fonts.
> it had to be a proper low fingerprint method (e.g., you had to hide the tls-in-tls timing pattern and do traffic shaping). Can anyone recommend a good book, video course or other material to learn more about these topics?
The way that I see it, its not just a technical problem anymore. It's about making the methods as diverse as possible and to some extent messing up the network for everyone. In other words, we should increase the cost and the collateral damage of widespread censorship. As an anecdotal data point, the network was quite tightly controlled / monitored around 2023 in Iran and nothing worked reliably. Eventually people (ab)used the network (for example the tls fragments method) to the extent that most of the useful and unrelated websites (e.g., anything behind cloudflare, most of the Hetzner IPv4 addresses, and more) stopped working or were blocked. This was an unacceptably high collateral damage for the censors (?), so they "eased" some of the restrictions. Vless and Trojan were the same at that time and didn't work or were blocked very quickly, but they started working ~reliably again until very recently.