Skip to content

consider not giving out the moat SR2 bridges on telegram

Our analysis conclusions from last week's work with @shelikhoo include:

  • Around 45 of irl's dynamic bridges say "bridge-distribution-request moat" in their descriptor, and around 10 of them say "bridge-distribution-request none" in their descriptor.

  • I hear that rdsys is giving out all 55ish of them via telegram+new. That is, the moat ones are given out via both moat and telegram+new, and the none ones are given out via telegram+new.

  • The moat ones are getting blocked in China because they're enumerating moat. The none ones continue to work in China.

  • All of the bridges are working fine in Turkey / Russia.

So if the above is right, that means some of the bridges we're giving out via telegram are already blocked because they had been given out via moat too.

So: giving out all 55 via telegram is optimal in every country but China, but giving out only the 10 via telegram is optimal for China.

Do we know whether the telegram+new channel is getting any use in China? If yes, we can make it work better by not including the moat ones in the pool of telegram+new responses.

Edited by Roger Dingledine