moat and connect assist broken for people who can't reach domain front

Last week we scrambled to work on getting Snowflake working again now that cdn.sstatic.net seems to be migrating from fastly to cloudflare: #42120 (closed)

But we're using that same domain front for moat and for connect assist, right? So those have quietly broken for those users too?

And the hope of changing the snowflake bridge line in circumvention settings didn't accomplish what we wanted, because if you need the new snowflake line (because sstatic.net doesn't work for you), you can't get it (because sstatic.net doesn't work for you).

Suspicion supported by a sad user in #tor for whom moat was timing out, and confirmed by both me and @trinity-1686a just now because we are affected by the bug.

Long term the solution includes tpo/anti-censorship/team#111 but maybe short term we just shift settings like extensions.torlauncher.bridgedb_front and follow the snowflake lead to foursquare?