This Great Barrington Declaration is more restrictive than current laws in my Eastern European country.
For example, it says "Retired people living at home should have groceries and other essentials delivered to their home. When possible, they should meet family members outside" but in my country there is no such lockdown for any age group.
It says "Young low-risk adults should work normally, rather than from home" but in my country employers aren't required to stop allowing young people to work from home (before 2020 working from home without breaking laws was basically impossible in my country).
A large phase 3 trial in Brazil showed that two doses, administered at an interval of 14 days, had an efficacy of 51% against symptomatic SARS-CoV-2 infection, 100% against severe COVID-19, and 100% against hospitalization starting 14 days after receiving the second dose.
Pfizer and Moderna vaccines aren't easily available outside of "first world" countries because of vaccine nationalism.
The largest ISP in Kazakhstan believes that it should be able to intercept all TLS traffic on their network: https://bits.blogs.nytimes.com/2015/12/03/kazakhstan-moves-t.... Because there are no technical differences between your TLS interception and what Kazakhtelecom is doing and no legal differences in most non-Western countries, I believe that all software should be changed to make TLS interception as hard as possible.
DirectAdmin, the most popular webhosting control panel in my country.
In my opinion this is not a bug because when I need to test a website, I often create an invalid hostname on the server and add the server's IP address to my computer's /etc/hosts. When I need HTTPS, I upload a certificate for the test hostname signed by my private CA.
I can create "773c7d.13445a.acme.invalid" in almost all shared hosting control panels I have access to.
When I send an HTTP request with Host: 773c7d.13445a.acme.invalid, the server responds with a file from ~/domains/773c7d.13445a.acme.invalid/public_html or a similar directory available through my FTP account.
When I connect using openssl s_client ... -servername 773c7d.13445a.acme.invalid, the server sends a certificate configured for 773c7d.13445a.acme.invalid in my control panel.
Is this a problem for Let's Encrypt? Doesn't Let's Encrypt's verification require creating files with random names in http://example.com/.well-known/acme-challenge where example.com is the certificate's common name?
When I click on "Investing in operations" or "Updating our policies", I see US-formatted dates such as "August 28, 2017", so foreign probably means non-US.
All traffic to/from some IP addresses is blocked, additionally all Chinese DNS servers respond with random A records when the domain name is banned, for example:
$ host facebook.com 202.97.0.6
facebook.com A 8.7.198.45
$ host facebook.com 202.97.0.6
facebook.com A 243.185.187.39
$ host facebook.com 202.97.0.6
facebook.com A 243.185.187.39
$ host facebook.com 202.97.0.6
facebook.com A 46.82.174.68
$ host facebook.com 202.97.0.6
facebook.com A 59.24.3.173
In 2003-2004 I had a non-SSL IRC server in a German datacenter and found that something between my server and large British ISPs was rewriting all "ISON <nickname>" strings in TCP streams to "PRIVMSG <nickname> :!kapa". I moved the IRC server to another IP address and never had this problem again.
I think that GCHQ was monitoring the network traffic and had a bug in their IRC protocol implementation.
For example, it says "Retired people living at home should have groceries and other essentials delivered to their home. When possible, they should meet family members outside" but in my country there is no such lockdown for any age group.
It says "Young low-risk adults should work normally, rather than from home" but in my country employers aren't required to stop allowing young people to work from home (before 2020 working from home without breaking laws was basically impossible in my country).