#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 dcf): Replying to [comment:7 antonela]: > hey, thanks for all the answers > > >There are basically five states: > >The one who wants to become a snowflake proxy (call him D) waits for a Tor snowflake user (call him F). > >D successfully connects to F. > >F is browsing on Tor so there's data transfer to D. > >F is idle so there are no data transfers. > >F quits and after a timeout D disconnects and goes back to the first step. > > > Great, that gives us: > > 1. waiting [white] > 2. no transferring [fuscia] > 3. connected [green] > 4. transferring [green + rotate] > 5. transferring with peers [+1 white + rotate] I would add a state separate from "waiting" to represent when the proxy is disabled because the user has not opted in. I don't think it's worth distinguishing the states "connected and idle" and "connected and transmitting". It's not well-defined anyway, because a proxy can have multiple connections, some idle and some transmitting. I don't understand the difference between "transferring" and "transferring with peers"-- what's a peer? These are the states I am thinking of: * disabled because not opted in * disabled because of an error (e.g. missing JS, missing WebRTC, unhandled exception) * enabled, no clients * enabled, at least one client (could depict the number of clients) -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27385#comment:8> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
