[tor-dev] Improving the HTTP interface of BridgeDB: bridges.torproject.org

Aaron aagbsn at extc.org
Mon Mar 11 17:02:18 UTC 2013

On Mon, Mar 11, 2013 at 4:36 PM, SiNA Rabbani <sina at redteam.io> wrote:
> Are we also interested in translating this to other languages? Perhaps
> we can get the Farsi done ASAP, since we now have a country obfsproxy
> users coming to this page soon :)

Yes, I pointed george (asn) in the direction of my TorCheck repo
(https://github.com/aagbsn/TorCheck) which outlines the sort of
templating and i18 work that should make supporting BridgeDB's front
end easier.

> All the best,
> SiNA
> Andrew Lewman:
>> On Mon, 11 Mar 2013 11:08:36 +0530
>> Sathyanarayanan Gunasekaran <gsathya at torproject.org> wrote:
>> In general, these look great.
>> Some nitpicking items:
>>> Here are the .htmls -
>>> https://people.torproject.org/~gsathya/html/index.html
>> 1. The majority of users aren't going to know which obfsproxy browser
>> they're using. I understand the difference, but to make a decision,
>> we should only ship one obfsTBB and assume everyone is using it as a
>> target for this site. I'm guessing we just call the
>> obfsproxy-flashproxy-tbb as obfsTBB and move forward with it.
>> 2. The correct email address is bridges at bridges.torproject.org
>> 3. I think we should scrap "normal bridges" and only promoted obfuscated
>> bridges. In the bigger picture, "normal bridges" are already subject to
>> DPI attack and blocked in many places in the world based on Tor's
>> network signature alone. All bridges should be obfsproxy bridges.
> --
> “Be the change you want to see in the world.” Gandhi
> _______________________________________________
> tor-dev mailing list
> tor-dev at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

More information about the tor-dev mailing list