Comcast censorship: People on tor mailing list raised some doubts, so testing again. Started tor relay again (public, not just bridge), and sure, 9 hours after appearing as online at metrics.tor.org, I cannot connect to my Comcast peer. I was able to connect up to that moment, I was testing by socat every 5 minutes.
Now turned off relaying, and trying to see whether and when I am able to connect to that Comcast peer again. I guess they must lift the block after some time, otherwise they would eventually end up blocking all IPs of any ISP which assigns IPs dynamically to its customers.
xmrk ₿ ⚡️ /
npub1zu…2qhzy
2023-06-13 08:22:03
Author Public Key
npub1zues2p7qdajk9hv7xn5ldntj3pufzl3jwzwa4dhlavxdkj27g92q62qhzyPublished at
2023-06-13 08:22:03Event JSON
{
"id": "ebaf28be044d9eefdd55349ccf6ef10bc216ea782ef8765aaa78d3846540da1f",
"pubkey": "17330507c06f6562dd9e34e9f6cd728878917e32709ddab6ffeb0cdb495e4154",
"created_at": 1686644523,
"kind": 1,
"tags": [],
"content": "Comcast censorship: People on tor mailing list raised some doubts, so testing again. Started tor relay again (public, not just bridge), and sure, 9 hours after appearing as online at metrics.tor.org, I cannot connect to my Comcast peer. I was able to connect up to that moment, I was testing by socat every 5 minutes. \n\nNow turned off relaying, and trying to see whether and when I am able to connect to that Comcast peer again. I guess they must lift the block after some time, otherwise they would eventually end up blocking all IPs of any ISP which assigns IPs dynamically to its customers.",
"sig": "7e20d3927a0d4db2b0cebb9efeb8c609811489c21803a217f4f359480a31e37a7e84c933cf43ec80f3c2050e4c6db0465e18e180c78d69a6f69f06e283cf89bc"
}