support issueshttps://gitlab.torproject.org/tpo/web/support/-/issues2024-03-25T15:27:33Zhttps://gitlab.torproject.org/tpo/web/support/-/issues/358Add Letterboxing to the glossary2024-03-25T15:27:33ZemmapeelAdd Letterboxing to the glossaryWe need to add Letterboxing to the glossary, as it is a new term that we use on the documentation.We need to add Letterboxing to the glossary, as it is a new term that we use on the documentation.ebanamebanam@torproject.orgebanamebanam@torproject.orghttps://gitlab.torproject.org/tpo/web/support/-/issues/355Please add a FAQ to explain users that disabling RFP is very bad2023-11-23T15:32:50ZPier Angelo VendramePlease add a FAQ to explain users that disabling RFP is very badStarting with Tor Browser 13.0, we decided to lock `privacy.resistFingerprinting`.
RFP is a very important setting.
Disabling RFP makes you easily fingerprintable in a lot of ways, including hardware!
Generally speaking, Mozilla is well...Starting with Tor Browser 13.0, we decided to lock `privacy.resistFingerprinting`.
RFP is a very important setting.
Disabling RFP makes you easily fingerprintable in a lot of ways, including hardware!
Generally speaking, Mozilla is well aware of these fingerprinting vectors and continuously add even more.
At the moment, the protection isn't granular, it's all or nothing (and I'm not saying it's bad - quite the opposite - it's the same philosophy of Tor Browser: normalize everything).
Also, when we send patches to Mozilla, we often gate them behind RFP.
Setting RFP to false is like telling that you don't want a bunch of our patches.
RFP has usability issues (e.g., it constantly resets the zoom level, which can be a big accessibility problem).
We're aware of that and it's in our roadmap.
We've received some feedback against our decision after the release, and we still get from time to time.
I think we could have a FAQ about this.ebanamebanam@torproject.orgebanamebanam@torproject.orghttps://gitlab.torproject.org/tpo/web/support/-/issues/326Explain why/how metrics is reporting that a bridge was blocked in a country2023-11-13T10:21:05ZGusExplain why/how metrics is reporting that a bridge was blocked in a countrySome operators were confused with "blocked in" field in Metrics portal about their bridges (see this thread for example - https://forum.torproject.net/t/bridge-blocklist-ru/2989/3?u=gus). It would be nice to have a support entry explaini...Some operators were confused with "blocked in" field in Metrics portal about their bridges (see this thread for example - https://forum.torproject.net/t/bridge-blocklist-ru/2989/3?u=gus). It would be nice to have a support entry explaining what it means.GusGushttps://gitlab.torproject.org/tpo/web/support/-/issues/310Instructions on setting up bridge relay for Debian / Ubuntu2024-01-30T13:34:35ZRedhill54Instructions on setting up bridge relay for Debian / Ubuntu
1 I am writing about a problem that I had when setting up a Tor bridge relay on a machine with an Ubuntu operating system.
2 On 13 August I put a question with the title “Change instructions or add alternative for adding gpg keys” ...
1 I am writing about a problem that I had when setting up a Tor bridge relay on a machine with an Ubuntu operating system.
2 On 13 August I put a question with the title “Change instructions or add alternative for adding gpg keys” onto Tor Stack Exchange. The link to the question is
A https://tor.stackexchange.com/questions/23269/change-instructions-or-add-alternative-for-adding-gpg-key
3 The one answer received suggested that I put the problem as an issue for the people who manage the website which includes the Tor bridge relay instructions, which is what I am now doing.
4 I followed the instructions on setting up a bridge relay in Ubuntu that I found in two different webpages. The instructions were identical in both webpages as follows.
B https://support.torproject.org/apt/tor-deb-repo/
C https://support.torproject.org/apt/
5 I installed a new version of Lubuntu on a computer, replacing all the programs and data, and then installed the programs for a Tor bridge relay.
6 There was a problem with the gpg key instructions. On Tor Stack exchange I found some advice in the answers to the question “Problem with adding gpg while installing Tor browser: Permission denied” at the link below.
D https://tor.stackexchange.com/questions/23212/problem-with-adding-gpg-while-installing-tor-browser-permission-denied
7 This advice enabled me to get the bridge relay running, but I could not find a way to run nyx using the command “nyx”, but had to use “sudo nyx”. The nyx system gives messages stating that using “sudo nyx” should not be necessary, but if I used “nyx” I got requests for Authentication passwords, or a cookie authentication file, and I could not figure out the password required or gain access to the cookie authentication file. I am aware that it is possible that there may be ways to find the right password or gain access to the cookie authentication file, but I would need further instructions on those actions.
8 Some days later I saw the instructions in the webpage from the link below.
E https://support.torproject.org/relay-operators/
These instructions and commands were different from the instructions at the links B and C. I wonder if the instructions at link E, which includes some shorter commands and fewer “sudo” commands. (NB in the instructions at links B and C, “#” is shorthand for “sudo”).
9 My question is whether the instructions at link E are more up-to-date, and will avoid the need for the change mentioned in link D, and remove the need for the “sudo nyx” command. If this is the case, I presume that the instructions at links B and C will need to be changed in line with those at link E.
10 If you confirm that the instructions at link E should be used, rather that those at links B, C, and D, then I will repeat the process of loading Ubuntu onto the computer and installing the Tor bridge relay, and see if that works as it should.
With thanks in advance for looking at this issue,
Redhill54