Meta Issue for tracking the meek-azure to meek rename. --- ## Tasks in rough timeline/dependency order: - communications; explain migration/upgrade path and timeline: - send emails: - [x] Guardian Project, tor-dev - open issues: - [x] CalyxOS: https://gitlab.com/CalyxOS/calyxos/-/issues/3400 - [x] OnionShare: https://github.com/onionshare/onionshare/issues/2044 - [x] Ricochet-Refresh: https://github.com/blueprint-freespeech/ricochet-refresh/issues/249 - fixed in 3.0.36 - [x] Orbot: https://gitlab.com/guardianproject/tormobile/orbot/-/issues/18 - [x] OnionBrowser: https://github.com/OnionBrowser/OnionBrowser/issues/527 - tor browser strings: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/44069 - community; updates to website: - Tor Browser manual: - https://gitlab.torproject.org/tpo/web/manual/-/issues/187 - Support Portal - Community - Snowflake pages - simultaneous: - tor-browser: TorSettings migration logic to move existing meek-azure usage to meek usage - tor-browser-build: update pt_config.json with new name - https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/41532 - rdsys: handle/map requests for meek-azure to meek (i.e. for legacy systems still using the old name) - https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/272#note_3231854 - blog post - overview of the meek-azure to meek name change (targeted to developers, could be opportunity for broader comms if that's desired)