The post implies that ISPs are doing the throttling — but in fact, ISPs have little control over it lately.
This kind of tampering is mostly done on TSPU devices (Technical Measures for Threat Counteraction), which is fully controlled by Roskomnadzor.
ISPs have little control over it — the system is highly centralized, and Roskomnadzor can carry out sophisticated and targeted actions.
For example, they're able to swiftly block some services and networks in specific regions and/or on specific types of connections (cellular vs wired, or even exact ISPs), or to perform
For example, when YouTube blocking first began, TSPUs were only throttling it on wired networks. This created an unfair advantage for cellular ISPs, prompting many people to cancel their wired internet contracts and switch to mobile networks.
Since there were no legal grounds for the block, and the government even denied the blocks, trying to blame the throttling on Google, some ISPs just started circumventing the blocks, effectively counteracting the TSPU blocks.
They soon had to stop doing that because of warrants and threats from Roskomnadzor — but it clearly illustrates that ISPs have virtually no control over internet blocking — in either technical or legal terms.
As for Cloudflare specifically — there’s more to the story, and I’m disappointed the post didn’t include more details.
Roskomnadzor is blocking TLS 1.3 ECH — and they are doing it for Cloudflare specifically, forcing Cloudflare users to disable ECH on their domains if they want their websites to be accessible in Russia when using up-to-date browsers.
This also means that, for the website using Cloudflare to be accessible, it needs plaintext SNI. Cloudflare also does not allow domain fronting.
This has allowed Roskomnadzor to implement selective allowlist-based blocking on Cloudflare networks, which is a new step in Russian internet censorship.
It feels like Cloudflare could've done a more in-depth analysis of selective blockings, since they probably can see whether there are statistically noticeable differences in metrics for different domains.
References (some are in Russian):
On some regions having some services like Telegram blocked for months:
- Having a dark theme seems logical for an app focused circadian rhythms, would be nice to have a dark appearance
- Not being able to switch between days by swiping felt quite annoying: the Home page requires two taps to change to another day, and the Progress page needs one — but it could’ve been a swipe. And the calendar on the Day page can’t be swiped down, only closed by tapping on the (x).
I hadn’t even realized that Apple had rolled out Time in Daylight — Apple Health hasn’t promoted or highlighted it like it does for other new Categories, and even then, the visualization still feels lacking.
I have been trying to get more consistent morning natural light exposure lately, so this is perfect timing!
Yeah unfortunately you have to have the screen exposed for a few minutes each time you go outside.
I spoke to the team at Apple, they said as long as you have a couple of minutes in the sunlight while you're on a walk it will then use sensor fusion to count the rest of the time outside.
I have worked from iPad + Raspberry Pi 400 setup exclusively for two weeks as an experiment.
I usually ran code-server on the Raspberry Pi and connected to it from the iPad to read and write code, but I found GitLab’s built-in Web IDE to be quite usable too (it’s based on code too afaik).
As for reading code for review purposes — if you don’t need to compare it locally, and built in Merge/Pull Request review of GitLab/GitHub/etc are enough, experience on iPad isn’t much different from desktop.
Doing all of this without a physical keyboard makes it much more painful though.
TL;DR: use GitHub/GitLab’s web interfaces, have a physical keyboard.
