Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T18:27:26Zhttps://gitlab.torproject.org/legacy/trac/-/issues/10831Captchas are not accessible for blind users2020-06-13T18:27:26ZTracCaptchas are not accessible for blind usersHi,
There are no way for blind users to solve captchas on bridge.torproject.org, would it be possible to add a way to make it possible please?
A solution could be to provide an audio captcha, using combinations of numbers or in all case...Hi,
There are no way for blind users to solve captchas on bridge.torproject.org, would it be possible to add a way to make it possible please?
A solution could be to provide an audio captcha, using combinations of numbers or in all cases, something spelled.
I think Recaptcha gives the possibility to add it, but I used it a long time ago so I am not sure it is still the case.
**Trac**:
**Username**: PZajdahttps://gitlab.torproject.org/legacy/trac/-/issues/5965Flag important sections of Torbutton code for preservation2012-07-10T18:50:14ZMike PerryFlag important sections of Torbutton code for preservationI should do a pass over the Torbutton code and mark the sections that we want to keep (or toss) somehow, to make #5709+#1506 easier.I should do a pass over the Torbutton code and mark the sections that we want to keep (or toss) somehow, to make #5709+#1506 easier.Mike PerryMike Perryhttps://gitlab.torproject.org/legacy/trac/-/issues/4113Clean up and post Tor Browser Design Doc2011-10-07T23:53:09ZMike PerryClean up and post Tor Browser Design DocThe design doc needs to be merged and cleaned up a little before posting. More will still need to be done to get it out of draft status, but let's just post it first.The design doc needs to be merged and cleaned up a little before posting. More will still need to be done to get it out of draft status, but let's just post it first.Mike PerryMike Perryhttps://gitlab.torproject.org/legacy/trac/-/issues/3846Recruit build test/signoff volunteers2020-06-13T01:07:49ZMike PerryRecruit build test/signoff volunteersI still think it is a good idea to get tor-talk volunteers to commit to testing builds for us. We created this table for them to fill in but then forgot about it: https://trac.torproject.org/projects/tor/wiki/doc/build/BuildSignoff
Ther...I still think it is a good idea to get tor-talk volunteers to commit to testing builds for us. We created this table for them to fill in but then forgot about it: https://trac.torproject.org/projects/tor/wiki/doc/build/BuildSignoff
There also used to be a pastebin or google doc with a testing checklist + instructions in it? Is that lost forever?Mike PerryMike Perryhttps://gitlab.torproject.org/legacy/trac/-/issues/3330Evangelize private browsing improvements2011-06-16T02:10:21ZMike PerryEvangelize private browsing improvementsWe should write a blog post describing our ideal private browsing mode. Along the way, I should add my thoughts about the ThirdParty cookie policy to the Mozilla bugzilla, and also review and comment on their Privacy Roadmap.We should write a blog post describing our ideal private browsing mode. Along the way, I should add my thoughts about the ThirdParty cookie policy to the Mozilla bugzilla, and also review and comment on their Privacy Roadmap.Mike PerryMike Perryhttps://gitlab.torproject.org/legacy/trac/-/issues/3324Mike Perry's Iteration Report 201106122011-06-16T15:23:15ZMike PerryMike Perry's Iteration Report 20110612# Goals
[[TicketQuery(keywords=~MikePerryIteration20110612,format=table,col=component|summary|points|actualpoints,order=component)]]
Interviews, emails, etc: 6 pts, Actual: 10 pts
# Fires
[[TicketQuery(keywords=~MikePerryIterationFires2...# Goals
[[TicketQuery(keywords=~MikePerryIteration20110612,format=table,col=component|summary|points|actualpoints,order=component)]]
Interviews, emails, etc: 6 pts, Actual: 10 pts
# Fires
[[TicketQuery(keywords=~MikePerryIterationFires20110612,format=table,col=component|summary|points|actualpoints,order=component)]]
# Metrics
Goal Points: 23
Goal Points Done: 5
Actual Goal Points Done: 35
Fires Done: 1
Actual Points Done: 36Mike PerryMike Perryhttps://gitlab.torproject.org/legacy/trac/-/issues/3098Review other W3C-Identity Workshop submissions2011-05-15T05:49:38ZMike PerryReview other W3C-Identity Workshop submissionsI need to review 5 papers by Sunday as part of participation in the W3C-Identity workshop.I need to review 5 papers by Sunday as part of participation in the W3C-Identity workshop.Mike PerryMike Perryhttps://gitlab.torproject.org/legacy/trac/-/issues/3060Review JonDos Design + Profile2011-05-31T00:55:06ZMike PerryReview JonDos Design + ProfileWe need to review the JonDos Firefox profile and work with them towards a shared web fingerprint.We need to review the JonDos Firefox profile and work with them towards a shared web fingerprint.Mike PerryMike Perryhttps://gitlab.torproject.org/legacy/trac/-/issues/1991Recognize poor guard performance and switch?2020-06-13T17:46:35ZRoger DingledineRecognize poor guard performance and switch?Ticket #1919 showed that the expected performance when using guards is comparable to the expected performance when picking the fastest guards. The penalty from using the slowest guards is especially noticeable in the 1MB and 5MB torperf ...Ticket #1919 showed that the expected performance when using guards is comparable to the expected performance when picking the fastest guards. The penalty from using the slowest guards is especially noticeable in the 1MB and 5MB torperf runs.
What property is it about the guards that lets us guess when we have the slow ones? Can we sum the bandwidth of our top three guards and realize that it's significantly below the average?
Ultimately I expect we'll want the Tor client to be able to recognize that it's chosen a poor set of guards and swap in a faster one so it's not in the bottom, say, 20%.