s96 mega-dev issue on torconnect feature
An issue to track the entire update to the torconnect feature
Links:
- Design Doc: https://docs.google.com/document/d/16NVqOvIOdy26vvH7P94D1kXmXoppKTRmv4T--fMfHjg/edit
- User-flow figma: https://www.figma.com/file/yApSDTlsppvH8w2508zV8k/about%3Atorconnect-User-Flows?node-id=84%3A516
- More User-flow figma: https://www.figma.com/file/Vsh1aPOZGneDX4Zp27mjsK/Sponsor-30?node-id=531%3A2047
- New Moat APIs: tpo/anti-censorship/bridgedb#40025 (comment 2753073)
- Querying new Moat API in tor-browser: #40645 (closed)
Todo:
-
Handle Moat errors properly: - https://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/blob/main/bridgedb/distributors/moat/server.py#L648
- https://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/blob/main/bridgedb/distributors/moat/server.py#L226
<meskio> now you can get two different error codes: 400 and 406 <meskio> 406 is for when it can't find the country for the given IP <meskio> 400 is for malformed requests, for example see:
-
implement new moat APIs and replace existing consumers with new moat module (#40645 (closed)) -
Update the about:torconnect state machine to facilitate the userflow in the above linked figma (#40662 (closed)) - @duncan: what do we do when no settings are available for the user's location? we could either go with a fallback (obfs4?) or leave it to the user
-
#40707 (moved)
-
Update the about:torconnect frontend page to match additional UI flows (#40773 (closed)) -
Update about:preferences page to match new UI designs (#40774 (closed))
User Testing from nah: https://www.figma.com/proto/Vsh1aPOZGneDX4Zp27mjsK/Sponsor-30?page-id=531%3A2047&node-id=717%3A3003&viewport=241%2C48%2C0.08&scaling=min-zoom&starting-point-node-id=717%3A3003&show-proto-sidebar=1
Ping @duncan @meskio
Edited by donuts