Roskomnadzor continues to destroy the Internet: it's Google's turn
Never was and here again. The “teachings” on blocking Amazon AWS (which Amazon ended up asking for a problem resource “on the way out”) did not have time to die, as Roskomnadzor continued: from the end of March, googleusercontent.com, the technical domain of Google, has been added to the registry.
Now the registry has 286 addresses owned by Google.
It is not known what exactly was the cause. The reason for this is the “rubber” Ordinance No. 27-31-2015 / Id4082-15, with the help of which more than 10 thousand resources have already been blocked . According to the same resolution, the IP addresses of the Amazon web services were also blocked (which suggests - did Zello move to Google?).
Some news resources were quick to report blocking the entire googleusercontent.com, which is not entirely true. It is not the entire domain that is blocked, but its subdomains. The story from Amazon AWS is exactly the same, when thousands of virtual machine addresses of this service were entered into the registry (but AWS was not completely blocked). However, the good is still not enough, the address remains in the registry for years. Even after the problematic content disappeared from it long ago.
')
Blocking googleusercontent.com in its entirety would have unpredictable consequences, since there lies content used by both Google’s services and a host of third-party sites.
Update: Roskomnadzor has confirmed that this is another round of hunting for Zello.
Now the registry has 286 addresses owned by Google.
It is not known what exactly was the cause. The reason for this is the “rubber” Ordinance No. 27-31-2015 / Id4082-15, with the help of which more than 10 thousand resources have already been blocked . According to the same resolution, the IP addresses of the Amazon web services were also blocked (which suggests - did Zello move to Google?).
Some news resources were quick to report blocking the entire googleusercontent.com, which is not entirely true. It is not the entire domain that is blocked, but its subdomains. The story from Amazon AWS is exactly the same, when thousands of virtual machine addresses of this service were entered into the registry (but AWS was not completely blocked). However, the good is still not enough, the address remains in the registry for years. Even after the problematic content disappeared from it long ago.
')
Blocking googleusercontent.com in its entirety would have unpredictable consequences, since there lies content used by both Google’s services and a host of third-party sites.
Update: Roskomnadzor has confirmed that this is another round of hunting for Zello.
Source: https://habr.com/ru/post/357866/
All Articles