The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2023-11-23T15:34:15Zhttps://gitlab.torproject.org/tpo/web/support/-/issues/343Slim down the "How to help running Snowflake proxies" entry2023-11-23T15:34:15ZRoger DingledineSlim down the "How to help running Snowflake proxies" entryOn https://support.torproject.org/censorship/how-to-help-running-snowflake/ we have instructions for how to volunteer to be a snowflake, but they are incomplete and out of date compared to the instructions on https://snowflake.torproject...On https://support.torproject.org/censorship/how-to-help-running-snowflake/ we have instructions for how to volunteer to be a snowflake, but they are incomplete and out of date compared to the instructions on https://snowflake.torproject.org/#extension
I have opened https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/87 for the snowflake.tpo page to add the two pieces of info that are currently only on the support entry ("enable webrtc" and "not on a VPN please"), and then when that is done we should remove all the instructions from the support entry.
Though that said, we could also just remove them from the support entry right now, and point to the snowflake.tpo page, and then we won't add a dependency step that doesn't really need to be a dependency. :)https://gitlab.torproject.org/tpo/web/support/-/issues/342How much do we want to highlight the apple monopoly problems re tor browser o...2023-11-23T15:34:14ZRoger DingledineHow much do we want to highlight the apple monopoly problems re tor browser on iOS?I am updating the "Which platforms is Tor Browser available for?" support entry, and I find myself wanting to say something like
"There is no official version of Tor Browser for iOS yet, because [Apple won't allow any underlying browser...I am updating the "Which platforms is Tor Browser available for?" support entry, and I find myself wanting to say something like
"There is no official version of Tor Browser for iOS yet, because [Apple won't allow any underlying browser framework besides its own](https://blog.torproject.org/tor-heart-onion-browser-and-more-ios-tor/). Our best available recommendation is [Onion Browser](https://onionbrowser.com/)."
The more conservative (less confrontational) version might be
"There is no official version of Tor Browser for iOS yet, as explained in [this blog post](https://blog.torproject.org/tor-heart-onion-browser-and-more-ios-tor/). Our best available recommendation is [Onion Browser](https://onionbrowser.com/)."https://gitlab.torproject.org/tpo/web/support/-/issues/341"the Tor Browser" -> "Tor Browser"2023-11-23T15:34:14ZRoger Dingledine"the Tor Browser" -> "Tor Browser"There are still some cases where we say "the Tor Browser" on the support portal.
I checked with Richard and they are fine with unifying our language into calling it Tor Browser.
I think I am just unifying everything to how people talk ...There are still some cases where we say "the Tor Browser" on the support portal.
I checked with Richard and they are fine with unifying our language into calling it Tor Browser.
I think I am just unifying everything to how people talk this year, that is, I am hoping this change surprises nobody.
Example fix, on mullvad-browser/does-this-mean-tor-browser-will-get-less-attention:
```
-We are also working hard on bringing the Tor Browser for Android up to par
+We are also working hard on bringing Tor Browser for Android up to par
```
This naming convention topic is also a candidate for a new section in the https://gitlab.torproject.org/tpo/team/-/wikis/Tor-User-Documentation-Style-Guide. (Is there already a naming style guide? I searched around on google for a while and only found https://styleguide.torproject.org/ so either no there isn't one or yes there is but it is well hidden which is not good news for a style guide. :)https://gitlab.torproject.org/tpo/tpa/team/-/issues/41384Deploy community policies mkdocs build2023-11-08T23:50:58ZGusDeploy community policies mkdocs buildHi,
We're generating the Tor Community policies (https://tpo.pages.torproject.net/community/policies) pages using GitLab-CI + GitLab pages.
Please create `policies.torproject.org` subdomain and redirect to https://tpo.pages.torproject...Hi,
We're generating the Tor Community policies (https://tpo.pages.torproject.net/community/policies) pages using GitLab-CI + GitLab pages.
Please create `policies.torproject.org` subdomain and redirect to https://tpo.pages.torproject.net/community/policiesJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/community/policies/-/issues/12Rename gitlab branch master -> main2023-11-10T19:06:47ZGusRename gitlab branch master -> mainSilvio RhattoSilvio Rhattohttps://gitlab.torproject.org/tpo/web/manual/-/issues/153improve onion service tb-manual page2023-11-23T15:40:02ZRoger Dingledineimprove onion service tb-manual pageI just did a clean-up of the onion service page in the tb-manual: <br>
https://tb-manual.torproject.org/onion-services/
But three issues remain on that page and could use some more help:
* We devote a good chunk of the page to onion se...I just did a clean-up of the onion service page in the tb-manual: <br>
https://tb-manual.torproject.org/onion-services/
But three issues remain on that page and could use some more help:
* We devote a good chunk of the page to onion service authentication, which I would think is a real edge case. Most users never see that or think about it. Should we move it to the bottom and mark it as an 'advanced situation' or something?
* Our advice if the onion service is gone is to try again later. That's probably bad advice, since probably the story is that the onion service has been gone for years and you are clicking on a thing that will never work. Are we comfortable saying that if it's gone it's probably just gone and you should move on?
* We have this awkward phrase "onion site versions of websites" which might be exactly what our style guide tells us to say, or maybe we can simplify to the smoother "onion versions of websites"? I don't remember what our style guide suggests.
There is also a fourth issue we could consider addressing, https://gitlab.torproject.org/tpo/web/support/-/issues/236, which suggests that we document the magic securedrop names too.https://gitlab.torproject.org/tpo/web/support/-/issues/340"I'm behind a NAT/Firewall" needs updating2023-11-23T15:34:14ZRoger Dingledine"I'm behind a NAT/Firewall" needs updatingFirst, it points to portforward.com, which we learn from https://gitlab.torproject.org/tpo/web/support/-/issues/332 is now an ad parking lot.
Second, it points to https://support.torproject.org/tbb/tbb-firewall-ports/ which suggests set...First, it points to portforward.com, which we learn from https://gitlab.torproject.org/tpo/web/support/-/issues/332 is now an ad parking lot.
Second, it points to https://support.torproject.org/tbb/tbb-firewall-ports/ which suggests setting FascistFirewall, but that is a client-only setting and relays can't usefully set it.
We should put together some new instructions for relay operators behind firewalls.https://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/37Publish Lox crates on crates.io2023-11-23T18:05:31ZonyinyangPublish Lox crates on crates.ioPrior to Lox being deployed, we should publish each of the Lox crates on [`crates.io`](https://crates.io/). The crate name and the `crates.io` name should match to avoid confusion/inconvenience.
There are instructions for publishing to ...Prior to Lox being deployed, we should publish each of the Lox crates on [`crates.io`](https://crates.io/). The crate name and the `crates.io` name should match to avoid confusion/inconvenience.
There are instructions for publishing to `crates.io` [here](https://doc.rust-lang.org/cargo/reference/publishing.html)
Once the crates are created, we should update our pipeline to automatically push updates to the documentation as appropriate.onyinyangonyinyanghttps://gitlab.torproject.org/tpo/web/support/-/issues/339"I can’t connect to Tor Browser. Is my network censored?" entry is redundant?2023-11-23T15:34:14Zshelikhoo"I can’t connect to Tor Browser. Is my network censored?" entry is redundant?Please have a review of grammar:
In the sentence: "I can’t connect to Tor Browser, is my network censored?" in the [article with same name](https://support.torproject.org/censorship/censorship-4/) does not sound nature, as it is the Tor...Please have a review of grammar:
In the sentence: "I can’t connect to Tor Browser, is my network censored?" in the [article with same name](https://support.torproject.org/censorship/censorship-4/) does not sound nature, as it is the Tor Browser connect to the Tor network, not user connect to the Tor Browser.
[Edit from Roger: more broadly, this whole entry is redundant with https://tb-manual.torproject.org/circumvention/, which does it better. Can we just remove this entry? Or do we need a tiny placeholder to steer people to the tb-manual page?]https://gitlab.torproject.org/tpo/web/support/-/issues/338Improve on the differences between TB and using other browsers with a system Tor2023-11-13T16:04:16ZemmapeelImprove on the differences between TB and using other browsers with a system TorThe page https://support.torproject.org/tbb/tbb-9/ could have:
- More information about cookie isolation, no history, etc
- A better URL
- That graph with all the non-tor-related privacy features Tor Browser hasThe page https://support.torproject.org/tbb/tbb-9/ could have:
- More information about cookie isolation, no history, etc
- A better URL
- That graph with all the non-tor-related privacy features Tor Browser hashttps://gitlab.torproject.org/tpo/web/support/-/issues/337FAQ or exonerator should mention DNSel2023-11-23T15:34:14ZanarcatFAQ or exonerator should mention DNSelI've been wondering "how do i check if a batch of IPs is a tor exit node" quite a few times in my life, but not often enough to just remember it. plus, it keeps changing. :smile:
This FAQ entry is a good start:
https://support.torproj...I've been wondering "how do i check if a batch of IPs is a tor exit node" quite a few times in my life, but not often enough to just remember it. plus, it keeps changing. :smile:
This FAQ entry is a good start:
https://support.torproject.org/#relay-operators_facing-legal-trouble
It points at https://exonerator.torproject.org/ which goes to https://metrics.torproject.org/exonerator.html which does provide a way to check a single IP. But I have 70 of them here!
Startpage sends me to this Stack Exchange question:
https://serverfault.com/questions/874327/how-can-i-check-if-ip-is-a-tor-exit-node
... which, unsurprisingly, sends us to our old website:
https://www.torproject.org/projects/tordnsel.html.en
... which points at `exitlist.torproject.org` which doesn't work anymore:
```
anarcat@angela:~$ dig +short 81.167.67.80.exitlist.torproject.org
anarcat@angela:~$
```
the proper record is dnsel.tpo:
```
anarcat@angela:~$ dig +short 81.167.67.80.dnsel.torproject.org
127.0.0.2
```
This answer gets it better:
https://serverfault.com/a/1081354/153231
... and also mentions the [bulk exit list](https://check.torproject.org/torbulkexitlist) which is way easier than bouncing around DNS...
So I think the FAQ should be expanded. In fact, there should be a "how do I tell if an IP is a Tor exit relay" question altogether, not just "i'm in legal trouble", which seems like a dubious way to approach the problem, and a separate question.https://gitlab.torproject.org/tpo/community/hackweek/-/issues/31Tweets for the comms team2023-11-30T16:16:40ZemmapeelTweets for the comms team# About the project
* Contact: emmapeel
* Chat: #tor-project on `irc.oftc.net`
* Video room: https://tor.meet.coop/<FILL IN>
# Participants
- emmapeel
- pavel
# Summary
Last year we started a bank of content to tweet, with a cale...# About the project
* Contact: emmapeel
* Chat: #tor-project on `irc.oftc.net`
* Video room: https://tor.meet.coop/<FILL IN>
# Participants
- emmapeel
- pavel
# Summary
Last year we started a bank of content to tweet, with a calendar as well for important dates. This was to be put for translation, and used in our social media.
This year we did a test in weblate with a simpler format ( Here you can see the format for the Spanish translation: https://gitlab.torproject.org/tpo/translation/-/blob/social-content/es.csv?ref_type=heads ) , and we want to review last year's strings and add them to this new format component in weblate. This format is easier to use for the comms team and does not use as much resources as the previous setup with lektor and gitlabCI etc.
Last years repo: https://gitlab.torproject.org/tpo/web/social-bank/
In weblate: https://hosted.weblate.org/projects/tor/social-copy/#translations
# Skills
- We need tweets to use and translate, please add your suggestions to this ticket.
# Links
Last years repo: https://gitlab.torproject.org/tpo/web/social-bank/
In weblate: https://hosted.weblate.org/projects/tor/social-copy/#translations
New repo in gitlab: https://gitlab.torproject.org/tpo/translation/-/tree/social-content?ref_type=headsHackweek 2023emmapeelemmapeelhttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/30design.torproject.org2023-12-08T21:30:56Zdonutsdesign.torproject.org# About the project
* Contact: @donuts
* Chat: **#tor-ux** on `irc.oftc.net`
* Video room: message donuts for the link
# Participants
- @donuts
- @jag
- @nicob
# Summary
The UX Team have been discussing replacing the [existing ...# About the project
* Contact: @donuts
* Chat: **#tor-ux** on `irc.oftc.net`
* Video room: message donuts for the link
# Participants
- @donuts
- @jag
- @nicob
# Summary
The UX Team have been discussing replacing the [existing styleguide](http://styleguide.torproject.org) with a new resource that's wider in scope – e.g. "design.torproject.org". In addition to updating our brand and web guidelines given their evolution over the past few years, we're also considering adding new sections to document our human-centered design principals, user research program, and overall methodology. The revised portal should serve as a central point of reference for external resources too, including for example our Figma libraries for the browser, web and VPN, and any open source design resources we use.
Given the large scope of this project, it's expected that we'll make some progress in planning the structure, content and design of the new portal – however we'll likely need to wait for a second hackweek or future funding opportunity to complete the implementation.
**Hackweek goals:**
- [x] Site map
- [x] Some content planning/development
- [ ] Figma prototype
- [ ] Basic HTML templates (stretch goal)
# Requirements
Institutional knowledge:
- Direct knowledge of the Tor Project's brand, design systems, user experience and/or user research practices.
- Or the ability to communicate your needs as a consumer of this documentation.
Technical skills:
- Graphic and/or web design (required)
- Front-end development (optional)
- Experience with lektor (optional)
# Links
Existing documentation:
- [Tor Project Styleguide](https://styleguide.torproject.org)
- [Community / User Research](https://community.torproject.org/user-research/)
- [User Research repo](https://gitlab.torproject.org/tpo/ux/research)
- [Firefox Acorn](https://acorn.firefox.com/latest/acorn-aRSAh0Sp) (external)
Design libraries:
- [Tor Browser for Desktop](https://www.figma.com/file/RtZ0fqkNMRc7GOjK3FLclz/Tor-Browser-for-Desktop?type=design&node-id=611%3A55&mode=design&t=1YIBBFxWnpmQUHwP-1)
- [Tor Browser for Android](https://www.figma.com/file/LaU3qFpem2xQOfBF6MEYVR/Tor-Browser-for-Android?type=design&node-id=611%3A55&mode=design&t=mjkrcP2LegGQLM8K-1)
- [Icons & Illustrations](https://www.figma.com/file/sd4yASXsToxFECsraTlAsw/Icons-%26-illustrations?type=design&node-id=0%3A1&mode=design&t=jGmz3Uwj5OmdsGoK-1)Hackweek 2023donutsdonutshttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/29Document how to verify reproducibility of build of a mullvad/tor browser release2023-11-30T16:16:39ZboklmDocument how to verify reproducibility of build of a mullvad/tor browser release# About the project
* Contact: @boklm
* Chat: #tor-browser-dev on `irc.oftc.net`
* Video room: no
# Participants
- @boklm
# Summary
I think many users don't know that our builds are reproducible, or how they can rebuild to verify...# About the project
* Contact: @boklm
* Chat: #tor-browser-dev on `irc.oftc.net`
* Video room: no
# Participants
- @boklm
# Summary
I think many users don't know that our builds are reproducible, or how they can rebuild to verify that they get a matching build.
We could generate a `reproducible-build.txt` file in the release directory containing the following informations:
* which git repository to clone
* which commit to checkout
* which command to use to start the build
* which sha256sums to expect after the build finished
* how to remove embedded signatures from exe and mar files we publish to check that they match the unsigned build
# Skills
Need to know how to build Tor Browser.
# Links
* tpo/applications/tor-browser-build#40997Hackweek 2023boklmboklmhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40997Document how to verify reproducibility of build of a mullvad/tor browser release2023-11-30T11:45:24ZboklmDocument how to verify reproducibility of build of a mullvad/tor browser releaseI think many users don't know that our builds are reproducible, or how
they can rebuild to verify that they get a matching build.
We could generate a `reproducible-build.txt` file in the release
directory containing the following inform...I think many users don't know that our builds are reproducible, or how
they can rebuild to verify that they get a matching build.
We could generate a `reproducible-build.txt` file in the release
directory containing the following informations:
- which git repository to clone
- which commit to checkout
- which command to use to start the build
- which sha256sums to expect after the build finished
- how to remove embedded signatures from exe and mar files we publish
to check that they match the unsigned buildboklmboklmhttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/27TPA issue templates2023-11-30T16:16:39ZanarcatTPA issue templates# About the project
* Contact: @anarcat
* Chat: #tor-admin on `irc.oftc.net`
* Video room: https://tor.meet.coop/ana-amp-2kq-z2o
# Participants
- @anarcat
# Summary
An ancient ticket in the TPA issue tracker has been found, and i...# About the project
* Contact: @anarcat
* Chat: #tor-admin on `irc.oftc.net`
* Video room: https://tor.meet.coop/ana-amp-2kq-z2o
# Participants
- @anarcat
# Summary
An ancient ticket in the TPA issue tracker has been found, and it is full of precious metals, behold https://gitlab.torproject.org/tpo/tpa/team/-/issues/29398. The idea is that many (MANY) tickets issued in TPA often require the same basic data. Want a server? How big? who's team? Your PGP key expired? Please ship the key, etc. We waste an inordinate amount of time collecting that information when people open new issues.
The task here is to setup those templates in the TPA issue tracker. The twist is that right now the TPA project doesn't have any code at all: it's a "wiki only" GitLab project, and the code is instead in the tpo/tpa/wiki-replica project, mirrored into the tpo/tpa/team wiki, which shows up as the frontpage for the project. We need to find a way to do this transition cleanly, probably by moving wiki-replica directly into tpo/tpa/team (in which case we lose the homepage) or some other sheninagan.
# Skills
Some experience with GitLab is important. Probably relevant only to TPA people, but other contributors are of course welcome!
# Links
* https://gitlab.torproject.org/tpo/tpa/team/-/issues/29398
* https://gitlab.torproject.org/tpo/tpa/wiki-replica/
* https://gitlab.torproject.org/tpo/tpa/team/Hackweek 2023anarcatanarcathttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/26wiki replacement considerations2023-11-30T16:16:40Zanarcatwiki replacement considerations# About the project
* Contact: anarcat
* Chat: #tor-admin on `irc.oftc.net`
* Video room: https://tor.meet.coop/ana-amp-2kq-z2o
# Participants
- @anarcat
- @shelikhoo
# Summary
[TPA-RFC-38: Wiki replacement](https://gitlab.torproj...# About the project
* Contact: anarcat
* Chat: #tor-admin on `irc.oftc.net`
* Video room: https://tor.meet.coop/ana-amp-2kq-z2o
# Participants
- @anarcat
- @shelikhoo
# Summary
[TPA-RFC-38: Wiki replacement](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-38-new-wiki-service) is a draft from TPA aiming at reviewing whether or not to replace the current GitLab wiki(s) by something else. It's mostly stalled, so let's see if we can move it forward a nudge.
Let's review the requirements to see if they cover what we need and what we want to accomplish. I particularly want to discuss which content we intend to throw "in the wiki" and whether a wiki is the appropriate tool for this. I particularly do *not* feel like it's a good tool for technical team to document their software projects, where alternatives like mdbook, sphinx or mkdocs seem better suited (see the recent torspec change for example).
It's unclear how this should be organized. In Costa Rica we've had an informal discussion about this which was useful, maybe having a BBB call or two to shake things up could move this ahead?
# Skills
Everyone from the community is welcome to join the discussion.
# Links
* https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-38-new-wiki-service
* https://gitlab.torproject.org/tpo/tpa/team/-/issues/40909Hackweek 2023anarcatanarcathttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/25tor-browser-build project survey2023-12-01T14:28:56ZPier Angelo Vendrametor-browser-build project survey# About the project
* Contact: @pierov
* Chat: #tor-browser-dev on `irc.oftc.net`
* Video room: nope
# Participants
- suggested: apps team members and other people who regularly use tor-browser-build or curious about it
- @boklm
...# About the project
* Contact: @pierov
* Chat: #tor-browser-dev on `irc.oftc.net`
* Video room: nope
# Participants
- suggested: apps team members and other people who regularly use tor-browser-build or curious about it
- @boklm
# Summary
We have 120 projects in tor-browser-build.
Understand why we have some them is easy (e.g., Firefox), but some other are platform-dependent (e.g., the shenanigans that macOS signing needs), some other are Namecoin dependencies.
## Dependencies graph
It'd be great to create a graph with all the dependencies.
Hopefully it should contain just a single connected component (`browser`/`release`), or a few additional components that make sense to have (e.g., signing tools).
If we find components that don't make sense to have, we should then purge them from `tor-browser-build` (e.g., dependencies that aren't needed anymore and recursive dependencies).
I'd expect the graph to be directed and cyclical (some components depend on themselves with a different target).
So, we might find also some projects/nodes that just depend on other nodes, without being a dependency for anything.
We might want to purge them as well.
## Project readmes
At the moment, each project is required to have a `config` file, but most have also a `build` file.
It'd be great if we added a `README.md` (or something similar) to each project, to explain:
- what it is
- why we have it
- what we do here if it isn't trivial (e.g., for `browser`) and/or caveats of the build process (e.g., we have to do these additional steps because we cross compile, or we have to do also this for reproducible purposes)
- references (e.g., link to the website, when we follow Mozilla's build script, a reference to these build scripts, or known issues, such as NSIS requiring to be built with GCC).
# Skills
Know tor-browser-build (well, this documentation project might help knowing it more).
# LinksHackweek 2023Pier Angelo VendramePier Angelo Vendramehttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40126Improve Access Keys documentation: explain difference to shortcuts2024-01-24T21:11:50ZemmapeelImprove Access Keys documentation: explain difference to shortcutsWe already have some documentation about Access Keys: https://gitlab.torproject.org/tpo/community/l10n/-/wikis/Localization-for-translators#access-keys
But it needs to be improved.
We need to differentiate Access Keys, that are a way t...We already have some documentation about Access Keys: https://gitlab.torproject.org/tpo/community/l10n/-/wikis/Localization-for-translators#access-keys
But it needs to be improved.
We need to differentiate Access Keys, that are a way to navigate menus, from keyboard shortcuts.
One difference: Shortcuts are the same for all locales, Access Keys depend on the locale.
ref: https://hosted.weblate.org/translate/tor/tor-browser/tb-newidentityproperties/ru/?checksum=73b4988ed95a84d9#commentshttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40125Add documentation section about RTL for developers2024-02-26T19:28:02ZemmapeelAdd documentation section about RTL for developersWhen we release translations RTL some questions are always repeated, and it would be nice to have a documentation that developers can read, with examples and best practices. Also with screenshots to understand the common problems.When we release translations RTL some questions are always repeated, and it would be nice to have a documentation that developers can read, with examples and best practices. Also with screenshots to understand the common problems.emmapeelemmapeel