Allow scanning the QR code of emails from firstname.lastname@example.org into Tails
Getting bridges by email instead of Moat might be a valid option when Moat doesn't work for some reason. I'm not sure how possible it is for a censore to block Moat since it uses Meek in the backend.
Bridges over email can be very useful anyway until we have Moat.
Typing obfs4 bridges inside Tails would be a nightmare as they are very long:
obfs4 220.127.116.11:8080 401E5912C821FBB913D2BD89368C246A241C0512 cert=avfemQzJey18ZvPrTjpE86PbZR2gsf0nJsC/HabjtKoLV4ip6RVR6FRGMQnnszsrhQm3RA iat-mode=0 obfs4 18.104.22.168:12346 26AE211EB6EF3D10D13436884029D1CC236F3582 cert=p9L6+25s8bnfkye1ZxFeAE4mAGY7DH4Gaj7dxngIIzP9BtqrHHwZXdjMK0RVIQ34C7aqZw iat-mode=0 obfs4 22.214.171.124:18462 05BFD8CE8C66BED061E4268A55D82C966DED051E cert=g6JJOZggoTukko23appohuA9jBNlahdaSBHb11xwGmtkNU4A4QOXO4Yup+Pd/UX91do/cg iat-mode=0
We could allow users to scan a QR code within Tails to copy bridges obtained by email on their phone for example.
This is blocked by https://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/issues/40008. (Closed by not deployed as of 2021-05-19.)
Python code of the email distributor: https://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/tree/develop/bridgedb/distributors/email.
Also, right now the captchas of Moat are not accessible: https://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/issues/10831.
I wonder whether scanning the QR might provide a viable alternative for blind people until then if it has good UX.
I managed to scan the (pretty big) QR code from bridges.torproject.org from my phone into Tails using zbarcam.