[tor-dev] bridge:// URI and QR codes

[meskio]

Hello,

We have a messy situation to share bridges between devices. BridgeDB and Tor
Browser have QR codes but they use different format for them. There has being
some attempts to standarize a bridge URI[0][1], but it looks like we never
finished that work.

Pier has produced an RFC of a bridge URI proposal:
https://gitlab.torproject.org/tpo/applications/team/-/wikis/Design-Documents/Bridge-URI-RFC

If you have an application that uses (or plan to use) bridge URIs or QR codes 
I'm interested on your take on that proposal. Do your application already have 
any kind of support for bridge URIs or QR codes? If so how do they look like?  
Will it break things if we change them?

What do you think of the proposal? How can we improve it?

Thank you.


[0] https://gitlab.torproject.org/legacy/trac/-/issues/15035
[1] https://gitlab.torproject.org/tpo/applications/fenix/-/issues/40189

-- 
meskio | https://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 My contact info: https://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20220718/ec91db4f/attachment.sig>