←back to thread

1456 points pulisse | 1 comments | | HN request time: 0.261s | source
Show context
milankragujevic ◴[] No.21182863[source]
Hmmm. Would I get banned by the GFW for these two characters? 0x1F1F9 0x1F1FC...? (🇹🇼)
replies(2): >>21183542 #>>21184294 #
jrockway ◴[] No.21184294[source]
The last time I was in China, HN was already banned.
replies(1): >>21184328 #
milankragujevic ◴[] No.21184328[source]
I mean, AFAIK my blog isn't. Yet. I get visitors from China on my post about controlling the world's cheapest quadcopter from a PC via arduino and nrf24l01+...

edit: I just checked, it's accessible from mainland China, though quite slow.

replies(1): >>21185034 #
rdbell ◴[] No.21185034[source]
If anyone else wants to check their website's accessibility from China, I run a service that lets developers proxy HTTP requests through real Chinese (and worldwide) residential ISP customers: https://packetstream.io

We have a worldwide network of real users that install a relay app on win/mac and we proxy customer requests through their home ISP connections like this:

  ```
  developer@Developers-MacBook-Pro-2:~% curl -x http://xxxx:xxxx_country-China@proxy.packetstream.io:31112 https://ifconfig.co/json
  {"ip":"223.166.106.16","ip_decimal":3752225296,"country":"China","country_eu":false,"country_iso":"CN","city":"Qingpu","latitude":31.1539,"longitude":121.1141,"asn":"AS17621","asn_org":"China Unicom Shanghai network"}
  ```
I just tested HN several times from different Chinese IPs and it is indeed blocked:

  ```
  developer@Developers-MacBook-Pro-2:~% curl -v -x https://xxxx:xxxx_country-China@proxy.packetstream.io:31111 https://news.ycombinator.com/
  *   Trying 34.234.216.249...
  * TCP_NODELAY set
  * Connected to proxy.packetstream.io (34.234.216.249) port 31112 (#0)
  * Establish HTTP proxy tunnel to news.ycombinator.com:443
  * Proxy auth using Basic with user 'xxxx'
  > CONNECT news.ycombinator.com:443 HTTP/1.1
  > Host: news.ycombinator.com:443
  > Proxy-Authorization: Basic xxxx
  > User-Agent: curl/7.54.0
  > Proxy-Connection: Keep-Alive
  >
  < HTTP/1.1 502 Proxy Error (destination unreachable)
  < Proxy-agent: PacketStream Proxy
  < Content-Type: text/html
  <
  * Received HTTP code 502 from proxy after CONNECT
  * Closing connection 0
  curl: (56) Received HTTP code 502 from proxy after CONNECT
  ```
If any HN users want free PacketStream credits to test their own endpoints send me an email with your PacketStream username: ronald at packetstream dot io
replies(2): >>21185385 #>>21185520 #