[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #27385 [Obfuscation/Snowflake]: https://snowflake.torproject.org/embed is confusing

#27385: https://snowflake.torproject.org/embed is confusing
-----------------------------------+------------------------
 Reporter:  cypherpunks3           |          Owner:  (none)
     Type:  defect                 |         Status:  new
 Priority:  High                   |      Milestone:
Component:  Obfuscation/Snowflake  |        Version:
 Severity:  Major                  |     Resolution:
 Keywords:  snowflake, ux-team     |  Actual Points:
Parent ID:                         |         Points:
 Reviewer:                         |        Sponsor:
-----------------------------------+------------------------

Comment (by antonela):

 hi, i came back and i have questions

 The user flow is described as:

 1. Volunteers visit websites which host the “snowflake” proxy `(where does
 it happen? On Tor Browser? any browser?)`.
 2. Tor clients `(do you mean relays or the browser?)` automatically find
 available browser proxies via the Broker (the domain fronted signaling
 channel).
 3. Tor client and browser proxy establish a WebRTC peer connection
 `(where?)`.
 4. Proxy connects to some relay `(to another tor client?)`.
 5. Tor occurs `(what it means? that tor gets 100% bootstrapped?)`.

 So, we have two types of users:

 1. people who host snowflake
 2. people who "activate" snowflake

 Lets back to the 1. item, what do you need from users at this moment?

 - Do we want users clicking at the snowflake badge to open a new tab?

 In which of the above steps does occur that the user **clicks** at the
 badge and get moved to [https://keroserene.net/snowflake/options.html]?
 And, when the user arrives there, what we need?

 - We need the browser client with webRTC enabled.
 - We need a user who agreed on saving the world - clicked on YES.

 I'm experimenting with using a natural-language user interface to improve
 `options.html.` The action is very simple and I don't think we need any
 more UI artifact to encourage the user’s action.

 0
     Do you want to help censored users access the Tor network?
     Some description of what is happening. You can go a bit technical
 here.
     [Yes] [I want to learn more]

 1

     We need WebRTC to work. [Enable WebRTC]

 2.0

     Snowflake Proxy is ACTIVE.
     Thank you for contributing to internet freedom! [OFF Snowflake]

 2.1

     Snowflake Proxy is OFF.
     Do you want to help censored users access the Tor network? [Activate
 Snowflake]

 I made a quick prototype, you can click it here
 https://marvelapp.com/ebf367j/screen/47360204


 ** The badge**
 I made two options for a better badge. Can we still animate it when is
 enabled like now? Can I animate it with a little css? What do you think
 about to have it rotating when is active? :)

 Check a quick prototype [https://snowfl4k3.glitch.me/
 https://snowfl4k3.glitch.me/]

 If we export/use svgs, then the site owners can customize the snowflake
 icon color so easy.


 Sorry if I'm asking basic questions, i just want to be sure that i
 understand all the flow.

 Let me know what do you think!

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27385#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs