[tor-dev] How to present multiple meek backends in Tor Launcher?
David Fifield
david at bamsoftware.com
Sun Aug 3 06:37:08 UTC 2014
On Sat, Aug 02, 2014 at 11:28:08PM -0700, David Fifield wrote:
> I made some test meek bundles that are capable of using the Amazon
> CloudFront CDN as a backend, in addition to Google App Engine that was
> supported before.
>
> https://people.torproject.org/~dcf/pt-bundle/3.6.3-meek-2/
>
> https://trac.torproject.org/projects/tor/wiki/doc/meek#AmazonCloudFront
>
> To test it, go to the pluggable transport screen, and choose
> "meek-amazon" from the selection box.
I opened a ticket to discuss how this user interface can be improved.
https://trac.torproject.org/projects/tor/ticket/12777
While it's easy to add new entries like this (see
https://trac.torproject.org/projects/tor/attachment/ticket/12777/0001-Add-an-option-to-use-meek-through-CloudFront.patch),
I'm worried that it's not so clear for most users. On what are they
supposed to base their decision? How could it be better?
A possibility is that we could include just one option in the bundles,
and distribute the others from BridgeDB or support assistants.
David Fifield
More information about the tor-dev
mailing list