[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #31391 [Circumvention/Snowflake]: Do a reachability check before polling for clients
#31391: Do a reachability check before polling for clients
-------------------------------------+-------------------------
Reporter: cypherpunks | Owner: arlolra
Type: defect | Status: closed
Priority: Medium | Milestone:
Component: Circumvention/Snowflake | Version:
Severity: Normal | Resolution: fixed
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: cohosh | Sponsor:
-------------------------------------+-------------------------
Changes (by arlolra):
* status: merge_ready => closed
* resolution: => fixed
Comment:
> However, I'm wondering about the use case in which a user sees the
message that WebRTC has been disabled, goes into their about:config to
enable it, and then cannot redo the check without restarting their web
browser.
This was brought up in comment:5:ticket:31109 as well.
At present, if the `PeerConnection` constructor is in scope and then you
toggle off `media.peerconnection.enabled`, you can still make a
connection. My point being that a configuration hidden behind
`about:config` might benefit from a browser restart since it's unclear how
they're intended to be used.
> Perhaps a solution to any possible confusion here or with the error
messages in general would be a short FAQ section for all of our missing
feature error messages on snowflake.torproject.org (which the user arrives
at by clicking on the "Learn more" link).
Filed as #31902
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31391#comment:14>
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