![]() ![]() Ticket #30317: This patch updates our "howto" box, which explains how one adds bridges to Tor Browser. ![]() ![]() Relay Search now shows a bridge's distribution mechanism and links to this info page, so bridge operators can learn more. Ticket #33008: We added an info page to BridgeDB which explains its distribution mechanisms.This was no easy feat but thanks to Damian Johnson (atagar), who did most of the heavy lifting, we are now done! Ticket #30946: Python 2 is no longer supported, so we ported BridgeDB's code base to Python 3.Thanks to Armin Huremagic (agix) for fixing this issue! This patch replaced these phrases with simpler language. Ticket #31528: BridgeDB used a bunch of silly phrases across its UI that made it unnecessarily difficult to translate and interact with.This patch changes this behavior, so bridges can actually change their distribution mechanism. This means that if a bridge would change its mind and re-configure its distribution mechanism using the BridgeDistribution config option, BridgeDB would ignore it. Ticket #33631: So far, BridgeDB remembered only the first distribution mechanism it ever learned for a given bridge.Keep in mind that you need to send requests from either a Gmail or a Riseup address. We also simplified the language in the autoresponder's reply. Many people didn't, so we tried to ease the pain by making the autoresponder reply with obfs4 bridges even if the user sent an invalid request. Ticket #30941: Our email autoresponder was notoriously difficult to use and would only respond with bridges if you got the email commands right.We just released and deployed BridgeDB version 0.10.1. With BridgeDB, we tackle the problem of how to get bridges to censored users while making it difficult for censors to get all bridges. When ISPs or governments block access to the Tor network, our users rely on bridges to connect. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |