Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T17:25:51Zhttps://gitlab.torproject.org/legacy/trac/-/issues/24513Guerrilla user test of support.torproject.org2020-06-13T17:25:51ZIsabela FernandesGuerrilla user test of support.torproject.orgThis ticket is to keep track of tasks related to organizing f2f user testing of our support.torproject.org portal.
(More info to be added by isabela and antonela)This ticket is to keep track of tasks related to organizing f2f user testing of our support.torproject.org portal.
(More info to be added by isabela and antonela)website redesignhttps://gitlab.torproject.org/legacy/trac/-/issues/24505Publish tor relay auto-update instructions2020-06-13T17:25:50ZArthur EdelsteinPublish tor relay auto-update instructionsIn our documentation pages that give instructions on how to set up a tor relay, we should explicitly show how to set up auto-update. Over time that will hopefully decrease the number of relays running out-of-date versions that are have s...In our documentation pages that give instructions on how to set up a tor relay, we should explicitly show how to set up auto-update. Over time that will hopefully decrease the number of relays running out-of-date versions that are have security flaws or other bugs.
We can patch the following pages:
https://www.torproject.org/docs/tor-relay-debian.html.en
https://www.torproject.org/docs/debian.html.en#ubuntu
https://www.torproject.org/download/download-unix.html.en
irl has been collecting instructions here:
https://trac.torproject.org/projects/tor/wiki/OperatorsTipshttps://gitlab.torproject.org/legacy/trac/-/issues/24399Create a consistent set of icons for relay flags2020-06-13T17:25:45ZirlCreate a consistent set of icons for relay flagsRelay Search currently uses a set of icons for relay flags that exist as 16x16 PNGs. Over time we have added new icons but we've never considered consistency across projects or reusability of these icons.
Ideally, we could have icons fo...Relay Search currently uses a set of icons for relay flags that exist as 16x16 PNGs. Over time we have added new icons but we've never considered consistency across projects or reusability of these icons.
Ideally, we could have icons for the following flags that are reusable across projects (meanings are in dir-spec):
* Authority
* BadExit
* Fast
* Guard
* HSDir
* NoEdConsensus
* Running
* Stable
* V2Dir
* Valid
* Exit
Atlas also synthesises additional flags, as does consensus-health:
* Not Recommended - This relay is running a Tor version that is not recommended by the directory authorities and may contain known issues.
* Unmeasured - This relay has not been measured by at least 3 bandwidth authorities and so its consensus weight is currently capped.
* FallbackDir - This relay is hardcoded into the tor source code as a fallback directory.
* IPv6 ORPort - This relay listens for OR connections using IPv6.
* Unreachable IPv6 ORPort - This relay listens for OR connections using IPv6 but the directory authorities failed to confirm it was reachable.
* ReachableIPv6 - This relay has at least one reachable OR port using IPv6. (in votes)
* UnreachableIPv6 - This relay has at least one unreachable OR port using IPv6. (in votes)
* IPv6 Exit - This relay allows exit connections using IPv6.
* Unreachable ORPort - This relay has an unreachable OR address according to at least one directory authority.
* T-Shirt - This relay has met the t-shirt team criteria for a t-shirt (in theory).
* Hibernating - This relay is not currently running, and indicated that it was hibernating in its last known server descriptor.
Ideally these icons would be available for use in projects in the following formats:
* Web Icon Font
* SVG
* 16x16, 32x32 and 64x64 PNGs
If we could also throw in an onion, and relay and bridge icons, a fingerprint icon, AS icon, country icon (maybe a globe), this could be a really useful tool for user facing projects that has consistent UX across those projects.https://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/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/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/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/23437newsletter archive, subscribe and unsubscribed pages2020-06-13T17:25:13ZIsabela Fernandesnewsletter archive, subscribe and unsubscribed pagesComms team is working on a newsletter for Tor Project. This ticket is not about the mailing part of it, but about the pages people will see if they:
1. Want to subscribe to the newsletter.
1. Unsubscribe action is successful - page yo...Comms team is working on a newsletter for Tor Project. This ticket is not about the mailing part of it, but about the pages people will see if they:
1. Want to subscribe to the newsletter.
1. Unsubscribe action is successful - page you see when you click on the link to unsubscribe.
1. Newsletters permanent page
1. Archive of previous newsletters
Example of a newsletter permanent page:[http://37.218.240.202/archive/2017-09-01-first-newsletter](http://37.218.240.202/archive/2017-09-01-first-newsletter)This is useful for us to have people referring to our newsletter on social media, blogs, articles.Attached is a mock done by Steph which we would like UX team to review:Archive will be just a table with one column for newsletter title and one column for the date it was sent/published.Here is an example of the archive (is not using the design from Steph's mock yet):http://37.218.240.202/archiveHiroHirohttps://gitlab.torproject.org/legacy/trac/-/issues/23411Creating a live style guide2020-06-13T17:25:11ZHiroCreating a live style guideHi,
It would be nice to start a live style guide in html/css. Since we have started to use bootstrap in a few projects now (metrics.tpo, blog.tpo), maybe the style guide could be based on bootstrap.
The idea is to create something l...Hi,
It would be nice to start a live style guide in html/css. Since we have started to use bootstrap in a few projects now (metrics.tpo, blog.tpo), maybe the style guide could be based on bootstrap.
The idea is to create something like:
- http://codeforamerica.clearleft.com/
or:
- https://duckduckgo.com/styleguide
I would be happy to create the html/css live page if the ux team could provide me with the styles and components to implement.https://gitlab.torproject.org/legacy/trac/-/issues/23376Build survey form for Onion Browser branding research2020-06-13T17:25:10ZIsabela FernandesBuild survey form for Onion Browser branding researchThe UX team is helping the Onion Browser team with user research, we will be performing a survey around the branding of the app at Apple app store.
This is a problem when users comes to the app store (which contains 20 different apps th...The UX team is helping the Onion Browser team with user research, we will be performing a survey around the branding of the app at Apple app store.
This is a problem when users comes to the app store (which contains 20 different apps that 'connects to Tor') and often are confuse and don't know which one Tor Project recommends (Onion Browser).
Surveys will be something that the UX team will probably do more often and because we want to be very careful with people's data when giving us information, we would like to host our own form instead of using a 3rd party solution out there.
However, this ticket will only talk about requirements for Onion Browser branding survey, not for a long term solution to scale the production and hosting of surveys :) but we would like to point out that this is not a 'one time ask'.
The survey mocks are available here: https://marvelapp.com/4h97d4g/
general tech requirements:
1. Should be hosted by tor
1. Should have a .onion option
1. Should preserve user privacy (no ips logs etc)
1. Should have an admin interface to browse answers
1. Answers should include which set was shown on first question (see below) and if user filled up a form from a .onion address or tpo address
1. Admin interface should have an option to download answers as .csv
Greeting and Thank You screens are pretty straight forward so we won't be talking about those here at this ticket.
Requirements for first survey 1st screen: https://marvelapp.com/4h97d4g/screen/31825745
1. progress bar at the top with first 1/3 complete
1. First question allows only 1 selection
1. First question choices presentation:
1. We will present a set of 5 choices - where one will always be onion browser - to each user answering the survey
1. (pending) Full list of apps to be presented to user
1. (pending) logic for it so we are not bias (how to guarantee one isn't shown more often than the others etc)
1. Each choice thumbnail should have a link to their respective Apple app store page (should we do it like that or should we just have the page screenshot be presented in a larger format, like if you click on the thumbnail image you see the bigger version of it)
1. (pending decision) Text box word count limitation or some limitation for input?
1. Missing from the mock that should be included - after second question we should have a 'next' button so folks can move to the next screen :)
Requirements for the end survey screen: https://marvelapp.com/4h97d4g/screen/31825746 1. Progress bar at the top now shows 2/3 completion
1. Only one answer allowed on first question
1. (pending decision) Text box word count limitation or some limitation for input?
1. Missing from the mock that should be included - after second question we should have a 'next' button so folks can move to the next screen :)
Requirements for 3rd survey screen: https://marvelapp.com/4h97d4g/screen/31825747
1. Progress bar at the top now shows 3/3 completion
1. Country list for drop-down menu could be standard ones (I believe you can easily get it from a l10n library or something)
1. Second question should allow only one answer
1. Submit button should save answers and take user to the 'thank you' screenHiroHirohttps://gitlab.torproject.org/legacy/trac/-/issues/23266Carryover Tasks2020-06-13T17:25:07ZLinda LeeCarryover TasksThis page keeps track of things we need to fix in the old torproject.org that we'll still need to fix when we make a new version of torproject.org.This page keeps track of things we need to fix in the old torproject.org that we'll still need to fix when we make a new version of torproject.org.website redesignhttps://gitlab.torproject.org/legacy/trac/-/issues/22852donate.torproject.org header broken2020-06-13T17:24:57Zstephwdonate.torproject.org header brokenThe header appears off, leaving a chunk of white space and hanging purple.The header appears off, leaving a chunk of white space and hanging purple.https://gitlab.torproject.org/legacy/trac/-/issues/22842Create a knowledge base that's more in-depth than FAQs2020-06-13T17:24:57ZTaylor YuCreate a knowledge base that's more in-depth than FAQsIt would be useful for visitors to our web pages to have access to content that:
* goes into more depth than a FAQ entry
* is more formal than a blog post
* is less comprehensive than a reference manual section
* is more stable than a wi...It would be useful for visitors to our web pages to have access to content that:
* goes into more depth than a FAQ entry
* is more formal than a blog post
* is less comprehensive than a reference manual section
* is more stable than a wiki page
These pages would form sort of a knowledge base or resource section.WebsiteV3HiroHirohttps://gitlab.torproject.org/legacy/trac/-/issues/22427Link to Linus's nightly builds from somewhere?2020-06-13T17:24:46ZRoger DingledineLink to Linus's nightly builds from somewhere?Tor Browser has nightly builds! Did you know?
If you ask search engines for "tor browser nightly" or "tor browser nightly builds", you won't find them though.
I found the link in an old tbb-dev archive. Here it is:
https://people.torpr...Tor Browser has nightly builds! Did you know?
If you ask search engines for "tor browser nightly" or "tor browser nightly builds", you won't find them though.
I found the link in an old tbb-dev archive. Here it is:
https://people.torproject.org/~linus/builds/
Unless, who knows, maybe that is not the best link to use.
In any case, it would seem smart to have a way for users to find this directory.Linda LeeLinda Leehttps://gitlab.torproject.org/legacy/trac/-/issues/22412Add "How report bad tor relays" info to www.torproject.org2020-06-13T17:24:45ZcypherpunksAdd "How report bad tor relays" info to www.torproject.org
http://www.hackerfactor.com/blog/index.php?/archives/763-The-Continuing-Tor-Attack.html
```
Unfortunately, there are no official methods for reporting bad Tor nodes to the Tor Project. The official contact methods do not work.
```
It ...
http://www.hackerfactor.com/blog/index.php?/archives/763-The-Continuing-Tor-Attack.html
```
Unfortunately, there are no official methods for reporting bad Tor nodes to the Tor Project. The official contact methods do not work.
```
It is fairly easy to find (first search result for 'report bad tor relays'):
https://blog.torproject.org/blog/how-report-bad-relays
If that email currently does not send an auto-reply with "thanks, we got your report, we will get back to you within .. days" that might make sense to add.Linda LeeLinda Leehttps://gitlab.torproject.org/legacy/trac/-/issues/22241Implement a proper wiki (just as Mozilla does)2020-06-13T17:24:43ZTracImplement a proper wiki (just as Mozilla does)Just an idea that I got: "Wiki" articles are available in trac, which makes it less likely to be seen https://trac.torproject.org/projects/tor/wiki/TitleIndex
Mozilla for example has its own wiki portal https://wiki.mozilla.org/Main_Pa...Just an idea that I got: "Wiki" articles are available in trac, which makes it less likely to be seen https://trac.torproject.org/projects/tor/wiki/TitleIndex
Mozilla for example has its own wiki portal https://wiki.mozilla.org/Main_Page (and it uses MediaWiki which makes it much more attractive, and has the look of a wiki)
(Of course, already existing articles may be ported to that new portal)
**Trac**:
**Username**: blockflareWebsiteV3HiroHirohttps://gitlab.torproject.org/legacy/trac/-/issues/22201Wireframes for community.torproject.org subpages2020-06-13T17:24:42ZLinda LeeWireframes for community.torproject.org subpages= Objective =
Design how to lay out the content for dev.torproject.org's subpages:
* __community.torproject.org/volunteer__: a page that encourages volunteers, tells what it's like, and houses the community council, and behavioral gu...= Objective =
Design how to lay out the content for dev.torproject.org's subpages:
* __community.torproject.org/volunteer__: a page that encourages volunteers, tells what it's like, and houses the community council, and behavioral guidelines materials.
* __community.torproject.org/outreach__: a page hosting all images, videos, audio, request for pamphlets, worksheets, papers, tutorials, etc. related to community. I think a way to organize all of this would be the main challenge.
* __community.torproject.org/help__: To be completely honest with you, I don't know how I feel about a call for help page because it has to constantly be maintained. Plus, I think that the better thing to do is to just get in contact with the community team lead right away and they can just inform the people of what needs to be done. So instead of listing a bunch of tasks, let's design something that gets the user to get in contact with the community team lead in the least frictionless way.
= Definitions =
* wireframes are rough sketches that illustrate the general idea of the design. A wireframe lets you talk about content placement and layout while abstracting finer details such as font, color, styling, and other considerations.
# Methodology
Antonela will independently sketch her best first design of the sub pages, according to previous sitemapping and content organization work. Linda will then review her design, make comments, and Antonela will iterate once before counting it done for this ticket. But this will just result in the initial designs, and these designs will be iterated on some more with feedback from stakeholders.
# Results
_Linda will place wireframes here once the task is complete. _website redesignAntonelaantonela@torproject.orgAntonelaantonela@torproject.orghttps://gitlab.torproject.org/legacy/trac/-/issues/22163Make it more obvious how to report security related bugs2020-06-13T17:24:40ZGeorg KoppenMake it more obvious how to report security related bugsWe had a report about a bug reporter getting different (and partly) conflicting advice on how to report security sensitive bugs. The canonical way of doing so is mailing to tor-security@lists.torproject.org. However, that seems to be not...We had a report about a bug reporter getting different (and partly) conflicting advice on how to report security sensitive bugs. The canonical way of doing so is mailing to tor-security@lists.torproject.org. However, that seems to be not found easily. We should change that on our website.HiroHiro