As part of my offboarding, I've updated the build script and documentation for the frontend. The frontend and the way it integrates with the backend is a bit esoteric, so I've prioritized documenting it.
As part of my offboarding, I've updated the build script and documentation for the frontend. The frontend and the way it integrates with the backend is a bit esoteric, so I've prioritized documenting it.
Tests are broken, but is not related to this merge request. As we are heading to deprecate BridgeDB I think is fine to keep those tests broken.
The merge request looks good. I will merge it. Thank you.
As part of my offboarding, I've updated the build script and documentation for the frontend. The frontend and the way it integrates with the backend is a bit esoteric, so I've prioritized documenting it.
The current implementation of BridgeDB gives the user 3 bridges, and a QR code including them all. It's a well-acknowledged fact that it's very difficult to scan this huge QR code from a smartphone. It's almost impossible to scan it from a piece of paper.
It would therefore be great if the QR could include only a single bridge. While this would make the QR code slightly less useful, it would also make it much more usable.
I know that #40052 is already tracking improvements for QR codes. However, they are mostly independent:
I can see two possible implementations:
In Tails, we will be shipping QR code scanning in 5.8. This is expected to happen around December 20. It would be great if BridgeDB could distribute more usable QR codes by that time!
Closes #40056
The translations are being built now, but the https distributor still isn't routing them properly.
We can close this one, we'll revisit this work during the migration to rdsys.
On https://bridges.torproject.org/options/ we have "I need an alternative way of getting bridges!" which mentions email, but it doesn't mention any of our newer mechanisms, like telegram, circumvention settings, etc.
We should either:
or
better not to reuse, but to remove the obsolete text from bridgedb and replace it with a pointer to the tb-manual page.
If the information here is up to date we could potentially reuse [some of] these strings: https://tb-manual.torproject.org/bridges/
(ticket motivated by @donuts when he asked a question about the telegram bridge responder and I went to the obvious place to try to learn the answer and telegram wasn't listed at all.)
On https://bridges.torproject.org/options/ we have "I need an alternative way of getting bridges!" which mentions email, but it doesn't mention any of our newer mechanisms, like telegram, circumvention settings, etc.
We should either:
or
See what we information we have, what we need, and how we can use these statistics.
A lot has changed since this ticket was created. We have other metrics on bridges and most of bridgedb moved into rdsys now.
@meskio I will close this ticket but let me know if you want to keep anything from this for the final work on rdsys.
Yes, let's see what is the next unexpected issue :)