Opened 18 months ago

Closed 8 months ago

#25722 closed enhancement (fixed)

Put an opt-in button on the main snowflake page

Reported by: dcf Owned by:
Priority: Medium Milestone:
Component: Circumvention/Snowflake Version:
Severity: Normal Keywords:
Cc: dcf, arlolra Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by dcf)

When you go to https://snowflake.torproject.org/snowflake.html for the first time, you get the message "Not opted-in." You have to go to https://snowflake.torproject.org/options.html, click "Yes", then go back to snowflake.html before you start being a proxy. (options.html doesn't have the proxy code.)

The discoverability at https://snowflake.torproject.org/index.html is worse: it doesn't say anything about opting in: you have to intuit that you should click on the badge to get to options.html, then go back again before you start being a proxy.

I propose that both these pages should have a Yes/No button right there on the page. Clicking Yes should do both:

  1. set the opt-in cookie
  2. start up the proxy (without needing to refresh the page)

Additionally, options.html should have a copy of the proxy code, so after you click Yes, it starts working immediately, without having to go to another page.

Child Tickets

Attachments (1)

0001-Move-the-Yes-No-buttons-into-index.html-redirect-opt.patch (7.8 KB) - added by dcf 9 months ago.

Download all attachments as: .zip

Change History (8)

comment:1 Changed 17 months ago by arma

Keywords: ux-team added
Severity: MinorNormal

I agree, this is confusing. In fact, I'm not even sure what the current pages actually do. Can somebody summarize the current situation for each of the major pages?

I suggest that one heuristic is: anywhere there is the cool camouflage snowflake image, that means your snowflake is working and enabled.

So for example, on https://snowflake.torproject.org/ I see the camouflage snowflake image, and there's even the text right underneath that says "If it animates, then congratulations" which to me means that I should sit there watching it to see if it starts animating. If it never will, because I didn't really sign up, then I'll be doing a lot of sitting and staring. :)

I'm adding the ux-team tag because this is exactly the sort of user flow thing that isabela and antonela should get involved for.

comment:2 in reply to:  1 Changed 17 months ago by cypherpunks

Replying to arma:

I agree, this is confusing. In fact, I'm not even sure what the current pages actually do. Can somebody summarize the current situation for each of the major pages?

options.html has the cookie JS code. snowflake.html has the snowflake.js code, but it needs a cookie to run the thing. embed.html has the snowflake parts and a link in the body to the options page, it also needs a cookie.

comment:3 Changed 9 months ago by dcf

Description: modified (diff)

comment:4 Changed 9 months ago by dcf

Status: newneeds_review

Here's a patch that copied the UI and logic from options.html to index.html. options.html is deleted and redirected to index.html. When you click a button, besides setting a cookie, the page reloads itself to make the proxy immediately active/inactive.

Here is what it looks like:
https://snowflake.torproject.org/staging/bug25722/

I think the page can use some design refactoring, but let's not do that here; let's do it in #27385 or another ticket.

comment:5 Changed 8 months ago by dcf

Any objection to this?

comment:6 Changed 8 months ago by antonela

Keywords: ux-team removed

I worked on this UI at #27385. Since is not considered, I'll remove ux-team label from here. Thanks!

comment:7 Changed 8 months ago by dcf

Resolution: fixed
Status: needs_reviewclosed
Note: See TracTickets for help on using tickets.