how to keep the quality of the telegram bridges?

Right now the bridges distributed by the telegram bot have a very small ratio of being blocked, as they are manually handled and rotated when blocked. We are integrating the bot into rdsys and as part of that planning to start using bridges from the bridge authority, at least for the old accounts.

Bridges in rdsys has being rotated, and some old bridges might have being blocked in certain countries when they were assigned to another distributor. Also, censors might discover bridges in the old pool by using and block them and our protections might not be enough. How can we keep the quality of bridges after the move?

The situation might not be attenuated by providing more than one bridge on each request, but a higher number of bridges provided also means make easier for the censor to block them.

Some ideas we discussed today:

• Can we use the country block mechanism of rdsys to stop distributing bridges in certain countries? In telegram we don't know the country where the user comes from, but we do know their locale, maybe we can use this. But that will require maintaining that list manually.
• Should we distribute a small set of well tested bridges that we know they work? We can use the allow list and the locale of the user to provide a list of bridges we want to distribute in a certain country/locale that we have tested they work.