On Wed, May 02, 2018 at 03:40:44AM +0000, Yawning Angel wrote:
I will emphasize (again, since I seem to recall doing so when Google originally stomped down on meek) that the collateral damage concept behind meek doesn't need to come from CDNs.
Any entity that is willing to risk network operators going "it's unfortunate for the users, but too bad, example.com is getting blocked because it enables Tor" that has sufficient bandwidth can run a client facing endpoint.
There isn't even particularly a need for the domain to be something clients contact extremely frequently (which is a property that made CDNs attractive in the first place), due to use cases involving using domain fronting as a signaling channel rather than a bulk transport mechanism.
That's a good point. Back in the day we were trying to get Wikimedia to run https://en.wikipedia.org/meek or similar, but it never went anywhere.