wkrp
wkrp
I see, thanks. If I understand @mmmray, the letter was not about blocking access to Nitter servers, but asking the operators of those servers to block some specific accounts. (The...
> > On 2021-12-07, www.torproject.org and its IPv4 and IPv6 addresses were added to the [Unified Register of blocked sites](https://eais.rkn.gov.ru/en/) in Russia, meaning that ISPs have an obligation to block...
In November 2023, some Azure customers got an email informing that domain fronting will be disabled in Azure on 2023-11-08. > Action required: Azure Front Door/Azure CDN blocking domain fronting...
> In November 2023, some Azure customers got an email informing that domain fronting will be disabled in Azure on 2023-11-08. The announced date of 2023-11-08 (yesterday) has been pushed...
> * You can also induce TLS record splitting by [padding the ClientHello to a large size](https://ntc.party/t/http-headers-tls-padding-as-a-censorship-circumvention-method/168/2). @ValdikSS [reports](https://ntc.party/t/%D1%81%D0%BE%D0%BE%D0%B1%D1%89%D0%B5%D0%BD%D0%B8%D1%8F-%D0%BE-%D0%BD%D0%B5%D0%B4%D0%BE%D1%81%D1%82%D1%83%D0%BF%D0%BD%D0%BE%D1%81%D1%82%D0%B8-%D1%80%D0%B5%D1%81%D1%83%D1%80%D1%81%D0%BE%D0%B2-%D0%BE%D1%82%D0%B4%D0%B5%D0%BB%D1%8C%D0%BD%D1%8B%D0%B5-%D0%B1%D0%BB%D0%BE%D0%BA%D0%B8%D1%80%D0%BE%D0%B2%D0%BA%D0%B8-%D1%82%D1%81%D0%BF%D1%83/4625/52) that the strategy of padding the ClientHello is being blocked in...
The [conference page for the paper](https://www.ndss-symposium.org/ndss-paper/massbrowser-unblocking-the-censored-web-for-the-masses-by-the-masses/) has resources from the conference presentation: * [Slides](https://www.ndss-symposium.org/wp-content/uploads/24340-slides.pdf) * [Video](https://www.youtube.com/watch?v=k78C234RH80&list=PLfUWWM-POgQtF16H5N56CmIAUtZY7SC5-&index=6) by Milad Nasr
Maybe others can comment with more specific advice about transports or the network situation in the UAE. Shadowsocks supports UDP proxying, which will be required for WebRTC, but with WebRTC...
I was looking at some [OONI results](https://explorer.ooni.org/chart/mat?test_name=stunreachability&axis_x=measurement_start_day&since=2023-12-31&until=2024-02-01&time_grain=day&probe_cc=CN) today and I noticed that the DNS name **stun.l.google.com** also now apparently resolves correctly. stun.l.google.com was on the [original list of affected domains](https://github.com/net4people/bbs/files/9690188/affected_google_domains.txt)...