xmrk ₿ ⚡️ on Nostr: Also wrote about this on stacker.news yestreday - https://stacker.news/items/189001 . ...
Also wrote about this on stacker.news yestreday - https://stacker.news/items/189001 . Suprised by almost no interest.
I have (another) idea to fight it: put some false positives in the public list of tor relays, like Google web server IP address, or something similarly popular. Suddently, Comcast users cannot connect to Google, and Comcast is forced to do something. Well, they could just whitelist Google. And Google could retaliate. Perhaps add many smaller false positives, so it is pain to explicitly whitelist them. But I still feel it is probably a bad idea.
I have (another) idea to fight it: put some false positives in the public list of tor relays, like Google web server IP address, or something similarly popular. Suddently, Comcast users cannot connect to Google, and Comcast is forced to do something. Well, they could just whitelist Google. And Google could retaliate. Perhaps add many smaller false positives, so it is pain to explicitly whitelist them. But I still feel it is probably a bad idea.
quoting note1qqq…09xnComcast blocks all traffic to tor relays. Not just tor-related traffic, but ALL traffic. Have a lightning node and want to pay back your usage of tor by running a tor relay? Forget it, Comcast customers will not be able to connect to your lightning node. This is how I learnt about such blocking. But not just lightning: any self-hosted website is effectively prohibited from running tor relay.
Just use another IPv4 address, right? They are so abundant after all /s. And seems Comcast hasn't yet heard of IPv6.