Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T17:23:01Zhttps://gitlab.torproject.org/legacy/trac/-/issues/16406"Tor" is not listed as a project on torproject.org2020-06-13T17:23:01ZArthur Edelstein"Tor" is not listed as a project on torproject.orgIt would be nice to list "Tor" as the first project on torproject.org: on the main page, under "Our Projects" and on https://www.torproject.org/projects/projects.html.enIt would be nice to list "Tor" as the first project on torproject.org: on the main page, under "Our Projects" and on https://www.torproject.org/projects/projects.html.enWebsiteV3cypherpunkscypherpunkshttps://gitlab.torproject.org/legacy/trac/-/issues/14686Consolidate or de-emphasize our many download pages2020-06-13T17:22:46ZMike PerryConsolidate or de-emphasize our many download pagesDuring the UX Sprint, several of the users found alternate download pages other than download-easy, and became confused. If you search for Tor, download Tor, or Tor Browser, you get one of the following links:
https://www.torproject.org...During the UX Sprint, several of the users found alternate download pages other than download-easy, and became confused. If you search for Tor, download Tor, or Tor Browser, you get one of the following links:
https://www.torproject.org/download/download
https://www.torproject.org/projects/torbrowser.html.en
https://www.torproject.org/download/download-easy.html
Each of these has a different flow for downloading Tor Browser, and all but download-easy caused users to stop and become confused. I personally think https://www.torproject.org/download/download should simply redirect to download-easy, and the https://www.torproject.org/projects/torbrowser.html.en page should remove the matrix and either behave like download-easy, or its download button should take the user to download-easy.
We will still need some place to put installation instructions, and the alpha downloads, but those should be broken off into different pages that replace the outdated mess in https://www.torproject.org/docs/documentation.html.en.WebsiteV3traumschuletraumschulehttps://gitlab.torproject.org/legacy/trac/-/issues/13246Augment static sites with a CDN2020-06-13T16:48:48ZAndrew LewmanAugment static sites with a CDNOur current static websites are maintained and mirrored via the sysadmin team. We currently have mirrors serving up content from the US, Germany, Iceland, and Austria. Adding or defaulting to a CDN would allow for global geocaching, impr...Our current static websites are maintained and mirrored via the sysadmin team. We currently have mirrors serving up content from the US, Germany, Iceland, and Austria. Adding or defaulting to a CDN would allow for global geocaching, improved performance of the sites, and availability when Tor's infrastructure is unavailable due to maintenance or failures.WebsiteV3https://gitlab.torproject.org/legacy/trac/-/issues/13134Figure out access rights to new dists.torproject.org2020-06-13T16:48:47ZAndrew LewmanFigure out access rights to new dists.torproject.orgFigure out access rights to new dists.torproject.org so people can upload their precious binaries of love.Figure out access rights to new dists.torproject.org so people can upload their precious binaries of love.WebsiteV3https://gitlab.torproject.org/legacy/trac/-/issues/13133Move www.torproject.org/dists to dists.torproject.org2020-06-13T16:48:46ZAndrew LewmanMove www.torproject.org/dists to dists.torproject.orgMove www.torproject.org/dists to dists.torproject.org.Move www.torproject.org/dists to dists.torproject.org.WebsiteV3https://gitlab.torproject.org/legacy/trac/-/issues/12571online documentation for the ports has gotten muddled2020-06-13T17:22:16Zcypherpunksonline documentation for the ports has gotten muddledWhen I used to proxy apps through Tor the documentation was pretty clear about 9050 being the port to put everything through, while 9150 was the port to control Tor, the port Vidalia used to control Tor. I seem to remember that before To...When I used to proxy apps through Tor the documentation was pretty clear about 9050 being the port to put everything through, while 9150 was the port to control Tor, the port Vidalia used to control Tor. I seem to remember that before Torbutton took over Vidalia's functionality the preconfigured port with the Tor bundle was 9050, as it was just another app routed through Tor, and Vidalia, talking to Tor via 9150, was the controller.
I've been through all the documentation I can find and it still seems to suggest that 9050 is for routing and 9150 is for control. My problem is, 9050 doesn't work for routing on my machine. If I want an app to use the Tor network, I have to socks it to 9150. This is freaking me out.
I'm running 3.6.2 but I sometimes use standalone Vidalia for various utilities it has.
Another area that needs clarification is Orbot - it seems to suggest 8118 is its routing port, but I don't know what its control port is or even whether 8118 is indeed the routing port because the documentation is sparse and murky there too. Or maybe I just need to be pointed to the correct link... but the fact that I can't directly find it and there are contradictory factoids floating around is troubling.
I know the ports for Tor used to be different way back when, because I ended up finding that there are still some really old tutorials that are obsolete kicking around on various computer news sites. Did non-Android Tor once use 8118? Anyway I'm confused, and since I spent the better part of an hour digging around the Tor site and the internet and couldn't geta conclusive answer, I'm filing a bug for better documentation.WebsiteV3https://gitlab.torproject.org/legacy/trac/-/issues/11569Consider making donations part of the download process2020-06-13T17:37:26ZAndrew LewmanConsider making donations part of the download processThe re-designed download-easy page (https://www.torproject.org/download/download-easy.html.en) has resulted in a 2x increase in monthly donations since deployment. Some thoughts to consider:
1. move the donations button closer to the do...The re-designed download-easy page (https://www.torproject.org/download/download-easy.html.en) has resulted in a 2x increase in monthly donations since deployment. Some thoughts to consider:
1. move the donations button closer to the download button.
2. Rework the page so the donations button is first, with a nice reason why donations are needed, but clearly state downloads are still free, and click the download button to skip a donation process
3. Change the page flow so that downloads go to a donation request page first, and then after 10 seconds of no action, redirect to the download-easy page.WebsiteV3https://gitlab.torproject.org/legacy/trac/-/issues/11568Integrate new simple download tor into dist mirrors?2020-06-13T17:22:05ZAndrew LewmanIntegrate new simple download tor into dist mirrors?We have a great new, simple "download tor" page for quick deployment, https://github.com/wpapper/tor-download-web/ or https://wpapper.github.io/tor-download-web/
setting up download mirrors of this site with mirrors of www.torproject.or...We have a great new, simple "download tor" page for quick deployment, https://github.com/wpapper/tor-download-web/ or https://wpapper.github.io/tor-download-web/
setting up download mirrors of this site with mirrors of www.torproject.org/dist should be easy.
Do we setup a new domain of download.torproject.org and it incorporates the site and dist automatically? Do others mirror the download site like they mirror the current www.torproject.org site?WebsiteV3https://gitlab.torproject.org/legacy/trac/-/issues/11289FAQ entry for where Tor's data directory is2020-06-13T17:22:01ZDamian JohnsonFAQ entry for where Tor's data directory isI just took a peek in our faqs to see if there was a "Where is my data directory?" entry I could link to. We don't seem to have one, and [tor's man page](https://www.torproject.org/docs/tor-manual.html.en) says "Store working data in DIR...I just took a peek in our faqs to see if there was a "Where is my data directory?" entry I could link to. We don't seem to have one, and [tor's man page](https://www.torproject.org/docs/tor-manual.html.en) says "Store working data in DIR (Default: @LOCALSTATEDIR@/lib/tor)". I have no clue what that macro expands to, nor would I expect users to. :)
If we can't clarify the manual page then this seems like something we should include in our FAQ since it in turn defines the path of our authentication cookie among other things.WebsiteV3Matt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/10597Create Staging environment2020-06-13T17:21:44ZTracCreate Staging environmentOnce development has progressed on Tor Website 3.0 a Staging environment should exist to which developers can deploy for testing, feedback, etc: `staging.torproject.org` or `beta.torproject.org`.
Another separate staging environment cou...Once development has progressed on Tor Website 3.0 a Staging environment should exist to which developers can deploy for testing, feedback, etc: `staging.torproject.org` or `beta.torproject.org`.
Another separate staging environment could also need to be created for translations: `translations.torproject.org`.
A consideration is whether the Staging environment (or environments) are protected by basic auth or completely public facing.
**Trac**:
**Username**: reyWebsiteV3https://gitlab.torproject.org/legacy/trac/-/issues/10592Consider adding analytics if it can be anonymized.2020-06-13T17:21:43ZTracConsider adding analytics if it can be anonymized.Consider adding some kind of analytics to the new site if it could be anonymized. Although we would love to know who uses the site, we really just need to know what they are doing. It would really help to understand how the site is used...Consider adding some kind of analytics to the new site if it could be anonymized. Although we would love to know who uses the site, we really just need to know what they are doing. It would really help to understand how the site is used, what works, what doesn’t work, etc. It’s much easier to make decisions and set priorities about what to work on when you have this kind of data. It’s might be clear to some what goes in the MVP, but after that you run the risk of spending limited resources on things that don’t matter as much.
**Trac**:
**Username**: seanmraffertyWebsiteV3https://gitlab.torproject.org/legacy/trac/-/issues/10591Create a sitemap for current torproject.org website2020-12-11T15:56:14ZAndrew LewmanCreate a sitemap for current torproject.org websiteDuring the Tor Dev Meeting in Berlin 2015, we decided on new information structure for torproject.org website:
https://trac.torproject.org/projects/tor/wiki/Website/MainSiteRedesign
We also had some suggestions on what to do with the co...During the Tor Dev Meeting in Berlin 2015, we decided on new information structure for torproject.org website:
https://trac.torproject.org/projects/tor/wiki/Website/MainSiteRedesign
We also had some suggestions on what to do with the content that we were removing from the homepage.
The goal of this task is to map all the current content on torproject.org so we can make sure we are not forgetting any page and we have a plan for everything we are moving out of it.WebsiteV3Isabela FernandesIsabela Fernandeshttps://gitlab.torproject.org/legacy/trac/-/issues/10553Show Wikipedia-like donation banner on homepage2020-06-13T17:21:40ZTracShow Wikipedia-like donation banner on homepageWikipedia uses banners with an appeal to donate at the top of the page to raise money. Tor could do the same, (possibly) with the following change:
Instead of / in addition to a generic "we need money to run this service", it could dis...Wikipedia uses banners with an appeal to donate at the top of the page to raise money. Tor could do the same, (possibly) with the following change:
Instead of / in addition to a generic "we need money to run this service", it could display (an excerpt of) a story from a Tor user or developer. "Tor has saved my life while I was in Syria", "I am working on Tor because...", and so on.
We could also add those stories on the donation page itself (maybe in a box with the stories sliding through, like this image gallery: http://foundation.zurb.com/docs/components/orbit.html)
This is somewhat related to #10264 (Ticket).
This Idea came up in the workshop "How you can help Tor" during 30c3.
**Trac**:
**Username**: malexmaveWebsiteV3https://gitlab.torproject.org/legacy/trac/-/issues/10473Integrate our opencrm system with donation/thank you pages2020-06-13T17:21:35ZAndrew LewmanIntegrate our opencrm system with donation/thank you pagesWe need to start keeping in touch with our donors now that we have a few thousand of them. Much like the EFF and FSF, we should integrate our opencrm system into the donation/thank you page to better communicate with our donors.
Step 1 ...We need to start keeping in touch with our donors now that we have a few thousand of them. Much like the EFF and FSF, we should integrate our opencrm system into the donation/thank you page to better communicate with our donors.
Step 1 is to get the opencrm system integrated into the rest of operations.
Step 2 is to tune it for the load it may take
Step 3 is to figure out the workflow from donate through crm registration
Step 4 is to push it liveWebsiteV3https://gitlab.torproject.org/legacy/trac/-/issues/10013Better Reflect Existing Sponsorship Information on the Website2020-06-13T17:21:20ZcypherpunksBetter Reflect Existing Sponsorship Information on the WebsiteThe Tor Project is pretty strong when it comes to financial transparency, but three trivial-to-implement suggestions might make information disclosed by the Tor Project on its 'Sponsors' page more useful to users and other stakeholders:
...The Tor Project is pretty strong when it comes to financial transparency, but three trivial-to-implement suggestions might make information disclosed by the Tor Project on its 'Sponsors' page more useful to users and other stakeholders:
1) Linking directly to the most recent IRS 990 form on the 'Sponsors' page ( https://www.torproject.org/about/sponsors.html.en ) could make details easier to access. Users outside the United States, for example, might not know that IRS 990 forms contain certain details they might not otherwise be interested in.
2) By listing what might otherwise look like end dates on the 'Sponsors' page above, users who don't notice that the information is only current as of 2012 might think that all of Tor's sponsors have left it. Making the "current as of" date more visible on the page and listing something like "2006 - present" instead of "2006 - 2012" might be less confusing. For sponsors offering grants, it seems easiest to just list the expected duration of current grants, where applicable.
3) If a user only reads the 'Sponsors' page, they could be looking at information up to almost two years out of date (1 year and 10+ months as of today) without checking other sources. To offer users more current information, adopting a policy of disclosing all large grants (above an arbitrary threshold, perhaps $200,000 or 20% of Tor's total operating budget for any given year) on the 'Sponsors' page within a month could make the information users might care about most (who sponsors the project now) more timely and relevant. Relatedly, updating the 'Sponsors' page to reflect the specific date (rather than the year) the page was last updated would better inform users in terms of how recently sponsorship information was updated.WebsiteV3Andrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/legacy/trac/-/issues/6851Resume allowing website translations2020-06-13T17:20:33ZRoger DingledineResume allowing website translationsOnce upon a time, we let smart people check out the website svn, edit wml text files on their own, and provide translated versions of each page.
Then we decided to get smarter about it, and switch to various web-based approaches (like r...Once upon a time, we let smart people check out the website svn, edit wml text files on their own, and provide translated versions of each page.
Then we decided to get smarter about it, and switch to various web-based approaches (like running our own pootle, or using other services like transifex). Our translators disappeared. Eventually Andrew deleted all the translations.
I talked to a lot of people the past few days (at the Berlin human rights conference) who were really sad that our website is English-only. We have tsum and try to maintain its translation, which is fine. But we have lots of other content that would be more useful in other languages.
What are the minimal steps to getting our website translations back up?WebsiteV3https://gitlab.torproject.org/legacy/trac/-/issues/5998Different websites for different user communities2020-06-13T17:20:11ZAndrew LewmanDifferent websites for different user communitiesTor's current website tries to serve many different user communities at once. Break out the website into micro-sites for different target audiences. Suggested micro-sites are:
1. novice users new to online privacy, anonymity and tor. (ma...Tor's current website tries to serve many different user communities at once. Break out the website into micro-sites for different target audiences. Suggested micro-sites are:
1. novice users new to online privacy, anonymity and tor. (make this the default)
2. technical users who understand advanced configuration and want to understand Tor's software and if they can help.
3. researchers who want to see designs, specifications, current research areas, how tor fits into the anonymous communications research field, open research questions and projects (great for masters or PhD thesis)
4. law enforcement people who need to know what tor provides, what tor doesn't provide, and what information is available to them for their investigations
5. developers who are interested in hacking on tor software and projects which match their design/coding/language choice skillsetsWebsiteV3Andrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/legacy/trac/-/issues/5489Write up a "how to report bugs and security issues, and what happens then" p...2020-06-13T17:20:01ZNick MathewsonWrite up a "how to report bugs and security issues, and what happens then" post or FAQWe should summarize our current security process on a blog post, FAQ entry, or on the contact page. This hasn't gotten enough attention, since everybody's so busy, but
We should at the minimum let people know:
* What issues to do t...We should summarize our current security process on a blog post, FAQ entry, or on the contact page. This hasn't gotten enough attention, since everybody's so busy, but
We should at the minimum let people know:
* What issues to do this way and what should just go on the bugtracker. And why.
* How to report bugs in general.
* What to expect if you report a security issue.
* Our current issue evaluation and response process, the history thereof.
This should be someplace pretty easy to find. A longer blog post and a shorter faq or contact entry seems smart to me.WebsiteV3Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/3593tor project website lacks functional menus2020-06-13T17:19:19Zcypherpunkstor project website lacks functional menusThe tor project website uses jquery for the donation widget on the download and donation pages. After some analysis, using jquery for enhanced menus may help people find information on your website. currently, even google, bing, and ot...The tor project website uses jquery for the donation widget on the download and donation pages. After some analysis, using jquery for enhanced menus may help people find information on your website. currently, even google, bing, and others have difficulty crawling your website, this makes finding information impossible.
option two is to break up the website into the following sub-sites:
* docs.torproject.org for all documentation,
* research.torproject.org for all research related materials,
* coder.torproject.org for all coding related materials,
* advocacy.torproject.org for all advocacy related materials,
* download.torproject.org for all downloads in a larger, simplified grid (see #3590),
* media.torproject.org already exists but appears to be unused. all images, videos, and css should be served from this site to speed up the website. modern browsers use parallel connections to multiple domains. by hosting everything on www.torproject.org, you are forcing the browser to serialize everything and therefore slow down the site from the user perspective.
I have spoken to "andrew" at the official phone number for your org, as listed in "contact us". As a professional communications manager and optimization expert, these are my comments. "andrew" asked me to open a ticket and summarize our conversation.
I estimate 90% of the world sees your website and thinks you are incompetent. Tor is such great software with such great user stories. Please improve the website to reflect your true organization.WebsiteV3Andrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/legacy/trac/-/issues/3242Research moving the website from svn to git2020-06-13T17:19:08ZAndrew LewmanResearch moving the website from svn to gitFigure out a working model for a centralized git repo of the website, to move off svn.Figure out a working model for a centralized git repo of the website, to move off svn.WebsiteV3