Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T17:25:42Zhttps://gitlab.torproject.org/legacy/trac/-/issues/24376Search backend for websites - Test and deploy Solr2020-06-13T17:25:42ZIsabela FernandesSearch backend for websites - Test and deploy Solrwebsite redesignHiroHirohttps://gitlab.torproject.org/legacy/trac/-/issues/24371QA of Tor Launcher new UI2020-06-13T17:43:50ZIsabela FernandesQA of Tor Launcher new UI**Follow the steps bellow to test the new UI.**
**Download the alpha 7.5a8:**
https://www.torproject.org/projects/torbrowser.html.en#downloads-alpha
To avoid conflicts you might want to remove your current Tor Browser installation bef...**Follow the steps bellow to test the new UI.**
**Download the alpha 7.5a8:**
https://www.torproject.org/projects/torbrowser.html.en#downloads-alpha
To avoid conflicts you might want to remove your current Tor Browser installation before installing this alpha.
**What to look for:**
* Review copy
* Review UI
* Test all different type of bridges settings
* If possible test proxy settings
Attached to this ticket are all the screens related to the work done that we are reviewing.To get to the configuration wizard, click on 'cancel' as soon as Tor Launcher starts.Kathleen BradeKathleen Bradehttps://gitlab.torproject.org/legacy/trac/-/issues/24309Activity 4.1: Improve how circuits are displayed to the user2020-06-16T01:28:15ZIsabela FernandesActivity 4.1: Improve how circuits are displayed to the user## Problem we are trying to solve:
Many users expect the guard node to change when asking for a new circuit.
There is nothing on circuit display that tells the user the first node is a guard, what guards are, and how it works when Tor c...## Problem we are trying to solve:
Many users expect the guard node to change when asking for a new circuit.
There is nothing on circuit display that tells the user the first node is a guard, what guards are, and how it works when Tor creates new circuits for the user.
## Expected behavior
If no other condition, guards will only change for a client every 3 months. Even if the user pick 'new identity' the guard should stay the same.
## Proposed solution:
First of all we need to update the Tor Browser User Manual to have an explanation about how the guard selection works, it should be in this section:
https://tb-manual.torproject.org/en-US/managing-identities.html
All the solutions below will link to the manual, this will allow us to send the user to a place with more information. And not necessary have to explain everything in the display or UI.
Managing users expectations:
I believe that for now we are better served if we managed user expectation about what will change when they request such change, not in the circuit display.
The current places where the user will be asking for a new circuit are:
1 - Tor Button -> New Identity
At this action, Tor Browser will open a confirmation window (see screenshot: https://trac.torproject.org/projects/tor/attachment/ticket/24309/new_identity_confirmation_window.png)
We should change the text here to set the right expectation about guards.
2 - Tor Button -> New Tor Circuit for this Site
Could we have a tool tip here that helps user know that guards won't change.
Circuit display UI:
keep IP and country name. Add 'guard' to the first node - guard should be a link to manual page.
Add a link at the bottom for "Learn More" which should also link to the manual page.
I am suggesting 2 links to the manual as an intentional effort of over communicating to the user.
## Things I would like to test
* User understanding of Tor Browser User Manual explanation about how guards selection works.
* Did we managed to set the right expectation for user? Test it with New Identity flow and New Tor Circuit flow.
* Do we need both links on circuit display?
## Things I am suggesting to be left for a second iteration or not doing and why
* Suggesting to not add functionality to let user pick a different guard. I think such a feature should be deeply discussed and done as a project of it own. Not as part of this solution.
* Suggestion to leave for a second iteration making the IP addresses linkable to more information about the relay (from atlas).
* Suggestion to not use JS for the more information on the relay feature mentioned above. We should never jeopardize the user safety for 'better UX'. We should be able to deliver better UX within the limitations we have by building a product that has security by design in mind.
## Tickets related to the problem:
* Ticket: https://trac.torproject.org/projects/tor/ticket/16665
* Circuit visualizer needs a cue about guards
This is the main ticket that contains lots of information describing the user problem in the comments posted. Would recommend reading it fully for better understanding.
* Ticket: https://trac.torproject.org/projects/tor/ticket/15239
* Add hyperlinks in tor circuit display to show "more info" about relays
This ticket has some suggestions for displaying more information about the relays (using atlas). We are taking into consideration these suggestions in the hypothesis above.
* Ticket: https://trac.torproject.org/projects/tor/ticket/20805
* Circuit display does not honor or use the UI font.
This ticket is more a bug then a UX issue. Although we should make sure that we set a rule of what font to use in the display, and fall back options. Let's make sure we are aligning this with: Activity 1.2: Make sure Firefox Photon UI works with our style guidelines -- on UX Team roadmap (for March 2018)https://gitlab.torproject.org/legacy/trac/-/issues/24283create a index page for our styleguide.torproject.org (bootstrap fork)2020-06-13T17:25:39ZIsabela Fernandescreate a index page for our styleguide.torproject.org (bootstrap fork)styleguide.torproject.org should have an index page explaining this project, how this resources should be used by anyone and how to use it.
This page will continue to be updated as we make changes to our styleguide.styleguide.torproject.org should have an index page explaining this project, how this resources should be used by anyone and how to use it.
This page will continue to be updated as we make changes to our styleguide.website redesignIsabela FernandesIsabela Fernandeshttps://gitlab.torproject.org/legacy/trac/-/issues/24281Make css changes to styleguide as per designs2020-06-13T17:25:39ZIsabela FernandesMake css changes to styleguide as per designsHere are all the screens done by Antonela for the styleguide.tpo:
https://marvelapp.com/6c5ce44Here are all the screens done by Antonela for the styleguide.tpo:
https://marvelapp.com/6c5ce44HiroHirohttps://gitlab.torproject.org/legacy/trac/-/issues/24280deploy styleguide.tpo (fork of bootstrap following tpo design styleguide)2020-06-13T17:25:38ZIsabela Fernandesdeploy styleguide.tpo (fork of bootstrap following tpo design styleguide)## Background
Back in 2015 The Tor Project partner with Simply Secure to create a design style guide for us. Our goal was to bring brand consistency to everything Tor related.
We presented a V2 of this project at Tor Meeting in Seattl...## Background
Back in 2015 The Tor Project partner with Simply Secure to create a design style guide for us. Our goal was to bring brand consistency to everything Tor related.
We presented a V2 of this project at Tor Meeting in Seattle (Q3 2016). And in 2017 we published a v3 of it with feedback received from the Tor Meeting incorporated to it:
https://media.torproject.org/image/Tor%20Style%20Guide%20v1.3.pdf
## What we are doing?
We decided to apply these styles to http://getbootstrap.com/
Here are some mocks of it:
And build or own version of it that we plan to call: styleguide.torproject.org
This page will have all bootstrap resources already converted to Tor styleguide. Together with other information that our styleguide has such as logo usage and so on.
## Why?
By having boostrap resourced already styled following Tor's design styleguide will be super handy for anyone building a site related to Tor.
Specially for our website redesign, but for other projects from the community as well.website redesignHiroHirohttps://gitlab.torproject.org/legacy/trac/-/issues/24275Testing Lecktor as a possible framework to be used for all portals related to...2020-12-11T12:18:56ZIsabela FernandesTesting Lecktor as a possible framework to be used for all portals related to website redesign project# Requirements
We are looking for a framework that:
* makes it easy for folks to update content
* makes it easy for having mirrored static content
* the internationalization of it works with Transifex
* its easy to haver our stylegui...# Requirements
We are looking for a framework that:
* makes it easy for folks to update content
* makes it easy for having mirrored static content
* the internationalization of it works with Transifex
* its easy to haver our styleguide bootstrap working with it (for building the site theme)
# How to test it
The live test can be accessed here: http://pipeline.torproject.net:9900/
Here is the git repository: https://oniongit.eu/infra/portal
Here is the framework home page: https://www.getlektor.com
Lektor can work as a console tool, like Jekyll. Also, if you have a mac though, you do not have to install anything from the console. You can use the mac desktop app.
https://github.com/lektor/lektor/releases/tag/3.0.1
What the app does is run the local lektor server that will allow you to edit the website as you would in a normal cms.
If you would like to give it a try, you have to clone the git repository for the project first and then open the lektor app and browse to the repository folder.
The idea is that once you make your changes you will be able to make a push and a merge request to the oniongit repository. I understand a small familiarity with git is required in this case.
Please leave any questions or feedback as a comment on this ticket, if you feel working with this framework and if you think it can make your life easier.website redesignHiroHirohttps://gitlab.torproject.org/legacy/trac/-/issues/24260Add metrics timeline events underneath graphs2020-06-13T18:14:26ZKarsten LoesingAdd metrics timeline events underneath graphsWe have been discussing adding metrics timeline events underneath graphs for a while now, last in the [Metrics timeline workshop in Montreal](uploads/org/meetings/2017Montreal/Notes/MetricsTimelineWorkshop) and on a [metrics-team@ mailin...We have been discussing adding metrics timeline events underneath graphs for a while now, last in the [Metrics timeline workshop in Montreal](uploads/org/meetings/2017Montreal/Notes/MetricsTimelineWorkshop) and on a [metrics-team@ mailing list thread](https://lists.torproject.org/pipermail/metrics-team/2017-November/000525.html). I'm moving that thread here, so that we can keep all open discussion points together in one place and expand the discussion to folks who are not on the team mailing list.
Here are some mockups that I made based on dcf's suggestions:
1. Table with three columns: https://people.torproject.org/~karsten/volatile/metrics-news-mockup-1/userstats-relay-country-table.html
2. One line of text per event (plus one line for links): https://people.torproject.org/~karsten/volatile/metrics-news-mockup-1/userstats-relay-country-text.html
3. Indentation with dates set aside and up to three lines per event for description, tags, and links: https://people.torproject.org/~karsten/volatile/metrics-news-mockup-1/userstats-relay-country-indented.html
Here's some feedback from discussing these mockups with iwakeh at last week's team meeting:
- We might want to rename "Possibly related events" to "Events during this time" or just "Events".
- The third mockup above is most readable.
- Maybe we can add some optional JavaScript magic that only displays the first five entries and that lets the user expand the list if there are more entries.
- Listing entries is all we're planning to do now, though we might add annotations to the graph or even mouseovers in the future.
Some open questions are:
- Are we going to list all events in the displayed timeframe or just the ones that are related to the displayed country, (pluggable) transport, IP version, or server type (relay or bridge)?
- We are adding this list only to the graphs in the Users category, because the metrics timeline focuses on those graphs, too, right?
- Should entries be listed in descending order, like on the News page, or in ascending order?https://gitlab.torproject.org/legacy/trac/-/issues/24187Reduce bullet spacing on blog2020-06-13T17:10:22ZstephwReduce bullet spacing on blogChange li margin-bottom from 1.5em to 0.5emChange li margin-bottom from 1.5em to 0.5emHiroHirohttps://gitlab.torproject.org/legacy/trac/-/issues/24133community.torproject.org work2020-12-11T15:56:14ZIsabela Fernandescommunity.torproject.org workThis is the main ticket for the work related to creating community.torproject.org
* Main stakeholders of this project:
* Designer for this project: Antonela
* Developer for this project: Hiro
* PM for this project: Isabela
**Projec...This is the main ticket for the work related to creating community.torproject.org
* Main stakeholders of this project:
* Designer for this project: Antonela
* Developer for this project: Hiro
* PM for this project: Isabela
**Project phases:**
0. content architecture - map current content related to the portal and organize it
1. whiteboard draw organization of the content into pages
2. wireframe these pages
3. create design for these pages [these include design reviews till we are happy with what we have]
4. start organizing content for the pages (with the design already done we will be working with that)
5. update high definition mockups with real content
6. guerrilla user testing #1
7. start coding the pages
8. once content is finished we upload them on transifex for translation to start
9. Once coding is done we can start QA by language (as translations gets complete)
10. [we could do another user test here too before launch if we want - or we can run one after lunch and continue iteration]website redesignPili GuerraPili Guerrahttps://gitlab.torproject.org/legacy/trac/-/issues/24132dev.torproject.org work2020-12-11T15:56:15ZIsabela Fernandesdev.torproject.org workThis is the main ticket for the work related to creating dev.torproject.org
* Main stakeholders of this project:
* Designer for this project: Antonela
* Developer for this project: Hiro
* PM for this project: Isabela
**Project phas...This is the main ticket for the work related to creating dev.torproject.org
* Main stakeholders of this project:
* Designer for this project: Antonela
* Developer for this project: Hiro
* PM for this project: Isabela
**Project phases:**
0. content architecture - map current content related to the portal and organize it
1. whiteboard draw organization of the content into pages
2. wireframe these pages
3. create design for these pages [these include design reviews till we are happy with what we have]
4. start organizing content for the pages (with the design already done we will be working with that)
5. update high definition mockups with real content
6. guerrilla user testing #1
7. start coding the pages
8. once content is finished we upload them on transifex for translation to start
9. Once coding is done we can start QA by language (as translations gets complete)
10. [we could do another user test here too before launch if we want - or we can run one after lunch and continue iteration]website redesignIsabela FernandesIsabela Fernandeshttps://gitlab.torproject.org/legacy/trac/-/issues/24131torproject.org work2020-12-11T15:56:14ZIsabela Fernandestorproject.org workThis is the main ticket for the work related to creating torproject.org main site.
* Main stakeholders of this project: Shari and Communications Team
* Designer for this project: Antonela
* Developer for this project: Hiro
* PM for ...This is the main ticket for the work related to creating torproject.org main site.
* Main stakeholders of this project: Shari and Communications Team
* Designer for this project: Antonela
* Developer for this project: Hiro
* PM for this project: Isabela
## Process:
1. content architecture - map current content related to the portal and organize it
1. whiteboard draw organization of the content into pages
1. wireframe these pages
1. create design for these pages [these include design reviews till we are happy with what we have]
1. start organizing content for the pages (with the design already done we will be working with that)
1. update high definition mockups with real content
1. guerrilla user testing #1
1. start coding the pages
1. once content is finished we upload them on transifex for translation to start
1. Once coding is done we can start QA by language (as translations gets complete)
1. [we could do another user test here too before launch if we want - or we can run one after lunch and continue iteration]
## Translation:
The languages we will support are our tier1 languages :
https://storm.torproject.org/shared/o7Rh2S9bsMNN7Eh7C9cKaqxR371pR1AmpRxbu--nC34
English - EN
Farsi - FA
Spanish - ES
Russian - RU
Simplified Chinese - zh-CN
Portuguese - PT-BR
French - FR
German - DE
Korean - KO
Turkish - TR
Italian - IT
Arabic - ARwebsite redesignHiroHirohttps://gitlab.torproject.org/legacy/trac/-/issues/24130Design/layout for support.tpo based on wireframe2020-06-13T17:25:29ZIsabela FernandesDesign/layout for support.tpo based on wireframeThis ticket will track the design work for support.torproject.org portal.
First version can be found here:
!https://marvelapp.com/4471ig9/screen/34237911This ticket will track the design work for support.torproject.org portal.
First version can be found here:
!https://marvelapp.com/4471ig9/screen/34237911website redesignAntonelaantonela@torproject.orgAntonelaantonela@torproject.orghttps://gitlab.torproject.org/legacy/trac/-/issues/24129support.torproject.org work2020-12-11T15:56:14ZIsabela Fernandessupport.torproject.org workThis is the main ticket for the work related to creating support.torproject.org
* Main stakeholders of this project: Community Team - Alison and Collin
* Designer for this project: Antonela
* Developer for this project: Hiro
* PM fo...This is the main ticket for the work related to creating support.torproject.org
* Main stakeholders of this project: Community Team - Alison and Collin
* Designer for this project: Antonela
* Developer for this project: Hiro
* PM for this project: Isabela
**Project phases:**
0. ~~content architecture - map current content related to the portal and organize it~~
1. ~~whiteboard draw organization of the content into pages~~
2. ~~wireframe these pages~~
3. ~~create design for these pages [these include design reviews till we are happy with what we have]~~
4. ~~start organizing content for the pages (with the design already done we will be working with that)~~
5. ~~update high definition mockups with real content~~
6. ~~guerrilla user testing #1~~
7. ~~start coding the pages~~
8. ~~once content is finished we upload them on transifex for translation to start~~
9. Once coding is done we can start QA by language (as translations gets complete)
10. [we could do another user test here too before launch if we want - or we can run one after lunch and continue iteration]
**Content:**
!https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/Supportwebsite redesignIsabela FernandesIsabela Fernandeshttps://gitlab.torproject.org/legacy/trac/-/issues/23972Add a link to torproject.org's onion service at the bottom2020-06-13T17:25:24ZcypherpunksAdd a link to torproject.org's onion service at the bottomMany sites already do that, for example ProPublica.org has at the bottom a "Browse via Tor" link to its onion serviceMany sites already do that, for example ProPublica.org has at the bottom a "Browse via Tor" link to its onion servicewebsite redesignhttps://gitlab.torproject.org/legacy/trac/-/issues/23971implement multi-step progress bar for new Tor Launcher UI2020-06-13T17:43:49ZMark Smithimplement multi-step progress bar for new Tor Launcher UIThe new Tor Launcher design includes a phased or multi-step progress bar. See: https://marvelapp.com/3f6102d/screen/31457651
This work will require improved bootstrap status/progress reporting from core Tor.The new Tor Launcher design includes a phased or multi-step progress bar. See: https://marvelapp.com/3f6102d/screen/31457651
This work will require improved bootstrap status/progress reporting from core Tor.Kathleen BradeKathleen Bradehttps://gitlab.torproject.org/legacy/trac/-/issues/239252018 Tor Browser donation banner2020-06-16T00:52:11ZArthur Edelstein2018 Tor Browser donation bannerFor Year End 2018 we want a fundraising banner in Tor Browser with a donation button. Let's make the activation time the same for all time zones, so we have a simultaneous launch. Or better yet, we can just launch it immediately on updat...For Year End 2018 we want a fundraising banner in Tor Browser with a donation button. Let's make the activation time the same for all time zones, so we have a simultaneous launch. Or better yet, we can just launch it immediately on update. The banner design is in progress.https://gitlab.torproject.org/legacy/trac/-/issues/23888Creating a Snowflake WebExtension addon2020-06-13T18:18:41ZTracCreating a Snowflake WebExtension addonThe idea is to create a WebExtension that allows one to become a Snowflake bridge by just installing it. That way it only suffices to install an extension and forget about it, unlike the approach of keeping a tab always open with the sno...The idea is to create a WebExtension that allows one to become a Snowflake bridge by just installing it. That way it only suffices to install an extension and forget about it, unlike the approach of keeping a tab always open with the snowflake JS code.
Since it's based on WebExtensions it can be easily deployed for other browsers in their addon store.
I did try to make one myself but I don't have the expertise and time to debug all the problems that resulted. One of the important take aways that I learned in that process was that automatically loading scripts from external sites is prohibited and will result in the addon not passing the review in the addon store, so the `snowflake.js` and `modernizr.js` should be embedded with the addon. However, this would require modifying `snowflake.js` since when it's loaded locally it throws some typeError and doesn't show that there's some connection to snowflake.bamsoftware.com in the browser console. For debugging, to verify that the addon works as intended one may load it from `about:debug` and check `about:networking` in the DNS and WebSockets part.
For the implementation these resources should be loaded in the background to ensure a permanent state with this in the `manifest.json`,
```
"background": {
"page": "pages/Snowflake.html"
},
```
**Trac**:
**Username**: oarelArlo BreaultArlo Breaulthttps://gitlab.torproject.org/legacy/trac/-/issues/23875Facebook's onion site is a single hop onion, but clicking on the Tor onion ic...2020-06-16T01:28:08ZTracFacebook's onion site is a single hop onion, but clicking on the Tor onion icon shows that it is a 6 hop circuit.Facebook's onion site is a single hop onion, but clicking on the Tor onion icon shows that it is a 6 hop circuit.
Roger Dingledine said at Def Con that facebook uses a single hop, here https://youtu.be/Di7qAVidy1Y?t=2135
1. Go to faceboo...Facebook's onion site is a single hop onion, but clicking on the Tor onion icon shows that it is a 6 hop circuit.
Roger Dingledine said at Def Con that facebook uses a single hop, here https://youtu.be/Di7qAVidy1Y?t=2135
1. Go to facebookcorewwwi.onion
2. click on the onion icon in the upper left and it should show that it is a 6 hop circuit, even though it should show that it is a 4 hop circuit.
Tested on 7.0.6 and 7.5a5.
**Trac**:
**Username**: Dbryrtfbcbhgfhttps://gitlab.torproject.org/legacy/trac/-/issues/23735Put a banner when detecting Tor exit node but with a non-Tor Browser on the w...2020-06-13T17:11:54ZcypherpunksPut a banner when detecting Tor exit node but with a non-Tor Browser on the website advising to use TB insteadIn the same spirit of #23721In the same spirit of #23721website redesignHiroHiro