commit d2395c15bced91ecea0bd64875273f2ed9248bd9
Author: emma peel <emma.p...@riseup.net>
Date: Sat Oct 9 18:38:40 2021 +0200
better internal links
---
content/onion-services/advanced/client-auth/contents.lr | 2 +-
content/onion-services/advanced/dos/contents.lr | 2 +-
content/onion-services/advanced/https/contents.lr | 2 +-
content/onion-services/advanced/opsec/contents.lr | 2 +-
content/onion-services/setup/contents.lr | 8 ++++----
content/onion-services/talk/contents.lr | 10 +++++-----
content/outreach/meetup/contents.lr | 10 +++++-----
.../community-resources/tor-exit-guidelines/contents.lr | 2 +-
.../community-resources/tor-relay-universities/contents.lr | 4 +++-
content/relay/setup/bridge/centos-rhel-opensuse/contents.lr | 4 ++--
content/relay/setup/bridge/debian-ubuntu/contents.lr | 4 ++--
content/relay/setup/bridge/docker/contents.lr | 4 ++--
content/relay/setup/bridge/dragonflybsd/contents.lr | 4 ++--
content/relay/setup/bridge/fedora/contents.lr | 4 ++--
content/relay/setup/bridge/freebsd/contents.lr | 4 ++--
content/relay/setup/bridge/netbsd/contents.lr | 2 +-
content/relay/setup/bridge/openbsd/contents.lr | 4 ++--
content/relay/setup/bridge/windows/contents.lr | 2 +-
content/training/checklist/contents.lr | 6 +++---
content/training/risks/contents.lr | 2 +-
content/user-research/how-to-volunteer/contents.lr | 12 ++++++------
content/user-research/open/contents.lr | 2 +-
22 files changed, 49 insertions(+), 47 deletions(-)
diff --git a/content/onion-services/advanced/client-auth/contents.lr
b/content/onion-services/advanced/client-auth/contents.lr
index 24cb573..14f80c9 100644
--- a/content/onion-services/advanced/client-auth/contents.lr
+++ b/content/onion-services/advanced/client-auth/contents.lr
@@ -28,7 +28,7 @@ If no authorization is configured, the service will be
accessible to anyone with
### Service side
-To configure client authorization on the service side, the
`<HiddenServiceDir>/authorized_clients/` directory needs to exist. Following
the instructions described in the section
[Setup](https://community.torproject.org/onion-services/setup/) will
automatically create this directory.
+To configure client authorization on the service side, the
`<HiddenServiceDir>/authorized_clients/` directory needs to exist. Following
the instructions described in the section [Setup](../../setup/) will
automatically create this directory.
Client authorization will only be enabled for the service if tor successfully
loads at least one authorization file.
For now, you need to create the keys yourself with a script (like these
written in
[Bash](https://gist.github.com/mtigas/9c2386adf65345be34045dace134140b),
[Rust](https://github.com/haxxpop/torkeygen) or
[Python](https://github.com/pastly/python-snippits/blob/master/src/tor/x25519-gen.py))
or manually.
diff --git a/content/onion-services/advanced/dos/contents.lr
b/content/onion-services/advanced/dos/contents.lr
index 297e88b..80b6ecb 100644
--- a/content/onion-services/advanced/dos/contents.lr
+++ b/content/onion-services/advanced/dos/contents.lr
@@ -32,7 +32,7 @@ Onionbalance is available for [v3 onion
services](https://blog.torproject.org/co
If you have users you trust, give them dedicated onion service and client
authorization credentials so that it can always be available.
For users you don't trust, split them into multiple addresses.
-That said, having too many onion addresses is actually bad for your security
(because of the use of many guard nodes), so try to use [client
authorization](https://community.torproject.org/onion-services/advanced/client-auth)
when possible.
+That said, having too many onion addresses is actually bad for your security
(because of the use of many guard nodes), so try to use [client
authorization](../client-auth/) when possible.
### Captchas and cookies
diff --git a/content/onion-services/advanced/https/contents.lr
b/content/onion-services/advanced/https/contents.lr
index 9122a0e..dda57df 100644
--- a/content/onion-services/advanced/https/contents.lr
+++ b/content/onion-services/advanced/https/contents.lr
@@ -34,7 +34,7 @@ We compiled some topics and arguments, so you can analyze
what's the best for yo
1. As anyone can generate an onion address and its 56 random alphanumeric
characters, some enterprise onions believe that associating their onion site to
an HTTPS certificate might be a solution to announce their service to users.
Users would need to click and do a manual verification, and that would show
that they're visiting the onion site that they're expecting.
-Alternatively, websites can provide other ways to verify their onion address
using HTTPS, for example, linking their onion site address from an
HTTPS-authenticated page, or using
[Onion-Location](https://community.torproject.org/onion-services/advanced/onion-location/).
+Alternatively, websites can provide other ways to verify their onion address
using HTTPS, for example, linking their onion site address from an
HTTPS-authenticated page, or using [Onion-Location](../onion-location/).
2. Another topic of this discussion is user expectations and modern browsers.
While there is extensive criticism regarding HTTPS and the CA trust model, the
information security community has taught users to look for HTTPS when visiting
a website as a synonym of secure connection, and to avoid HTTP connections.
diff --git a/content/onion-services/advanced/opsec/contents.lr
b/content/onion-services/advanced/opsec/contents.lr
index 6debce0..5120d12 100644
--- a/content/onion-services/advanced/opsec/contents.lr
+++ b/content/onion-services/advanced/opsec/contents.lr
@@ -20,7 +20,7 @@ Onion services operators need to practice proper [operational
security](https://
For some security suggestions please make sure you read over Riseup's ["Tor
Hidden (Onion) Services Best Practices"
document](https://riseup.net/en/security/network-security/tor/onionservices-best-practices).
Also, here are some more anonymity issues you should keep in mind:
- - As mentioned
[here](https://community.torproject.org/onion-services/setup/), be careful of
letting your web server reveal identifying information about you, your
computer, or your location.
+ - As mentioned [here](../../setup/), be careful of letting your web server
reveal identifying information about you, your computer, or your location.
For example, readers can probably determine whether it's thttpd or Apache, and
learn something about your operating system.
- If your computer isn't online all the time, your onion service won't be
either.
This leaks information to an observant adversary.
diff --git a/content/onion-services/setup/contents.lr
b/content/onion-services/setup/contents.lr
index 807ed06..f9f40c4 100644
--- a/content/onion-services/setup/contents.lr
+++ b/content/onion-services/setup/contents.lr
@@ -25,7 +25,7 @@ For the technical details of how the onion service protocol
works, see our onion
## Step 0: Get a working Tor
As part of this guide, we will assume you have a functional Tor in your
machine.
-To set up Tor, please follow the [Tor installation
guide](https://community.torproject.org/onion-services/setup/install/).
+To set up Tor, please follow the [Tor installation guide](./install/).
Tor should be up and running correctly for this guide to work.
You should also know where Tor's configuration files are.
@@ -109,7 +109,7 @@ If it doesn't work, look in your logs for some hints, and
keep playing with it u
It is important to note that an onion service configured like this will be
readable by anybody who knows or discovers the address.
You can make onion services require authentication, and only users with a
private key will access the service.
-Read more about [Client
authorization](https://community.torproject.org/onion-services/advanced/client-auth/)
documentation.
+Read more about [Client authorization](../advanced/client-auth/) documentation.
## (Optional) Step 5: Running multiple onion services
@@ -157,11 +157,11 @@ Some onion site operators may not want to disclose their
onion service location.
Therefore, you need to configure your web server so it doesn't give away any
information about you, your computer, or your location.
That is not an easy task, and these resources will help on how to make this
possible:
- * [Operational
Security](https://community.torproject.org/onion-services/advanced/opsec/).
+ * [Operational Security](../advanced/opsec/).
* [Onion services best
practices](https://riseup.net/en/security/network-security/tor/onionservices-best-practices)
by Riseup Collective.
* [OnionScan](https://onionscan.org/) is a tool to check if your onion site
is leaking information that could compromise your anonymity like your server IP
address.
Finally, if you plan to keep your service available for a long time, you might
want to make a backup copy of the `private_key` file somewhere.
-Now that you have an onion site working, you may want to deploy
[Onion-Location](https://community.torproject.org/onion-services/advanced/onion-location/),
or use tools like Docker,
[Heroku](https://gitlab.torproject.org/hiro/onions-on-heroku),
[Terraform](https://gitlab.torproject.org/hiro/terraform-onions),
[Ansible](https://galaxy.ansible.com/systemli/onion) or
[stem](https://stem.torproject.org/tutorials/over_the_river.html) to automate
the management of your onion services.
+Now that you have an onion site working, you may want to deploy
[Onion-Location](../advanced/onion-location/), or use tools like Docker,
[Heroku](https://gitlab.torproject.org/hiro/onions-on-heroku),
[Terraform](https://gitlab.torproject.org/hiro/terraform-onions),
[Ansible](https://galaxy.ansible.com/systemli/onion) or
[stem](https://stem.torproject.org/tutorials/over_the_river.html) to automate
the management of your onion services.
If you have a static website, but never installed Nginx or Apache, another
project to try is [OnionShare](https://onionshare.org), where running an onion
site will be easier: guided with a graphic interface and with minimal
configuration.
diff --git a/content/onion-services/talk/contents.lr
b/content/onion-services/talk/contents.lr
index 6196620..07be9be 100644
--- a/content/onion-services/talk/contents.lr
+++ b/content/onion-services/talk/contents.lr
@@ -33,17 +33,17 @@ These talking points will help to explain how onion
services offer multiple priv
### How Onion Services Work
A potential adopter has probably already heard about the Tor Project, the
network and even Tor relays, and that's great!
-[Tor relays](https://community.torproject.org/relay/types-of-relays/) are part
of a [public infrastructure](https://metrics.torproject.org/rs.html#toprelays),
where Tor users encrypted traffic is routed around to reach out the open
internet.
+[Tor relays](../../relay/types-of-relays/) are part of a [public
infrastructure](https://metrics.torproject.org/rs.html#toprelays), where Tor
users encrypted traffic is routed around to reach out the open internet.
Onion services aren't like a Tor relay in the network.
An onion service on the Tor network behaves like any other Tor clients.
The Onion Service to become available on the network connects to rendezvous
nodes.
-A client that wants to access the onion service does the same.
+A client that wants to access the onion service does the same.
This means that connections from the client to the server never leave the Tor
network.
-In contrast to running a [Tor relay](https://community.torproject.org/relay),
running a Tor Onion Service does not result in your IP address being publicly
listed anywhere, nor does your service relay other Tor traffic.
+In contrast to running a [Tor relay](../../relay), running a Tor Onion Service
does not result in your IP address being publicly listed anywhere, nor does
your service relay other Tor traffic.
-For a broader understanding, read [Onion Services
overview](https://community.torproject.org/onion-services/overview/) and watch
this talk: [DEF CON 25 - Next Generation Tor Onion
Services](https://www.youtube.com/watch?v=Di7qAVidy1Y).
+For a broader understanding, read [Onion Services overview](../overview/) and
watch this talk: [DEF CON 25 - Next Generation Tor Onion
Services](https://www.youtube.com/watch?v=Di7qAVidy1Y).
### Freedom of Press and Censorship Circumvention
@@ -139,4 +139,4 @@ Using them eliminates all metadata that may be associated
with the service other
### One onion a day keeps the surveillance away
-Now that you know all the benefits of onion services, you may want to set up
an [onion site](https://community.torproject.org/onion-services/setup/) and
read about the [protocol
overview](https://community.torproject.org/onion-services/overview/).
+Now that you know all the benefits of onion services, you may want to set up
an [onion site](../setup/) and read about the [protocol overview](../overview/).
diff --git a/content/outreach/meetup/contents.lr
b/content/outreach/meetup/contents.lr
index ce4cfca..d01e340 100644
--- a/content/outreach/meetup/contents.lr
+++ b/content/outreach/meetup/contents.lr
@@ -31,19 +31,19 @@ After confirming a local and date, create a poster and an
online invitation to s
### Step 3
-Find a meetup facilitator and draft an agenda, for example, question & answer
about Tor, how to setup relays.
-Read and follow our [best
practices](https://community.torproject.org/training/best-practices/).
+Find a meetup facilitator and draft an agenda, for example, question & answer
about Tor, how to setup relays.
+Read and follow our [best practices](../../training/best-practices/).
### Step 4
-Before the meetup, organize the space. Buy some chips and snacks, hang some
[posters](https://community.torproject.org/outreach/kit/) nearby the local, so
people can find easily.
+Before the meetup, organize the space. Buy some chips and snacks, hang some
[posters](../kit/) nearby the local, so people can find easily.
If you have some printed materials and/or Tor swag, put it on a table.
### Step 5
-Load your presentation and wait a few minutes to people arrive.
+Load your presentation and wait a few minutes to people arrive.
During the activity take notes about questions, how many knew about Tor
before, how many are relay operators, etc
### Step 6
-After the meetup, clean up the space, remove the posters and upload your notes
to [Tor Community
Team](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-community-team)
mailing list.
+After the meetup, clean up the space, remove the posters and send your notes
to the [Tor Community
Team](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-community-team)
mailing list.
diff --git a/content/relay/community-resources/tor-exit-guidelines/contents.lr
b/content/relay/community-resources/tor-exit-guidelines/contents.lr
index 2f56184..b5308fc 100644
--- a/content/relay/community-resources/tor-exit-guidelines/contents.lr
+++ b/content/relay/community-resources/tor-exit-guidelines/contents.lr
@@ -123,7 +123,7 @@ If you have your own experience of abuse handling, just
share it on our public m
Please read all the technical details before getting started. If you have any
questions or need help, please contact us at
[tor-relays](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays).
-* [Tor Relay Guide](/relay)
+* [Tor Relay Guide](../../)
* Set up an informative website on the exit IP(s) on port 80.
diff --git
a/content/relay/community-resources/tor-relay-universities/contents.lr
b/content/relay/community-resources/tor-relay-universities/contents.lr
index 95a4b52..fc4f369 100644
--- a/content/relay/community-resources/tor-relay-universities/contents.lr
+++ b/content/relay/community-resources/tor-relay-universities/contents.lr
@@ -72,7 +72,9 @@ If the authorities contact your university for logs, be
pleasant and helpful.
Tor's default log level doesn't provide much that's useful, so if they want
copies of your logs, that's fine.
Be helpful and take the opportunity to explain to them about Tor and why it's
useful to the world. (If they contact you directly for logs, you should send
them to your university's lawyers -- acting on it yourself is [almost always a
poor idea](/relay/community-resources/eff-tor-legal-faq/)).
-If there are too many complaints coming in, there are several approaches you
can take to reduce them. First, you should follow the tips in the [Tor relay
documentation](https://community.torproject.org/relay), such as picking a
descriptive hostname or getting your own IP address. If that doesn't work, you
can scale back the advertised speed of your relay, by using the
`MaxAdvertisedBandwidth` to attract less traffic from the Tor network. Lastly,
you can scale back your exit policy.
+If there are too many complaints coming in, there are several approaches you
can take to reduce them.
+First, you should follow the tips in the [Tor relay documentation](../../),
such as picking a descriptive hostname or getting your own IP address.
+If that doesn't work, you can scale back the advertised speed of your relay,
by using the `MaxAdvertisedBandwidth` to attract less traffic from the Tor
network. Lastly, you can scale back your exit policy.
Some people have found that their university only tolerates their Tor relay if
they're involved in a research project around anonymity.
So if you're interested, you might want to get that started early in the
process -- see our [Research Portal](https://research.torproject.org/).
diff --git a/content/relay/setup/bridge/centos-rhel-opensuse/contents.lr
b/content/relay/setup/bridge/centos-rhel-opensuse/contents.lr
index 8a75476..6d222fd 100644
--- a/content/relay/setup/bridge/centos-rhel-opensuse/contents.lr
+++ b/content/relay/setup/bridge/centos-rhel-opensuse/contents.lr
@@ -119,8 +119,8 @@ To confirm your bridge is running with no issues, you
should see something like
### 6. Final notes
-If you are having trouble setting up your bridge, have a look at [our help
section](https://community.torproject.org/relay/getting-help/).
-If your bridge is now running, check out the [post-install
notes](https://community.torproject.org/relay/setup/bridge/post-install/).
+If you are having trouble setting up your bridge, have a look at [our help
section](../../../getting-help/).
+If your bridge is now running, check out the [post-install
notes](../post-install/).
---
html: two-columns-page.html
diff --git a/content/relay/setup/bridge/debian-ubuntu/contents.lr
b/content/relay/setup/bridge/debian-ubuntu/contents.lr
index 9a8aff8..200332b 100644
--- a/content/relay/setup/bridge/debian-ubuntu/contents.lr
+++ b/content/relay/setup/bridge/debian-ubuntu/contents.lr
@@ -82,8 +82,8 @@ To confirm your bridge is running with no issues, you should
see something like
### 6. Final notes
-If you are having trouble setting up your bridge, have a look at [our help
section](https://community.torproject.org/relay/getting-help/).
-If your bridge is now running, check out the [post-install
notes](https://community.torproject.org/relay/setup/bridge/post-install/).
+If you are having trouble setting up your bridge, have a look at [our help
section](../../../getting-help/).
+If your bridge is now running, check out the [post-install
notes](../post-install/).
---
key: 2
diff --git a/content/relay/setup/bridge/docker/contents.lr
b/content/relay/setup/bridge/docker/contents.lr
index 5cf2eb1..a3d1e0a 100644
--- a/content/relay/setup/bridge/docker/contents.lr
+++ b/content/relay/setup/bridge/docker/contents.lr
@@ -62,8 +62,8 @@ This will return a string similar to the following:
obfs4 1.2.3.4:1234 B0E566C9031657EA7ED3FC9D248E8AC4F37635A4
cert=OYWq67L7MDApdJCctUAF7rX8LHvMxvIBPHOoAp0+YXzlQdsxhw6EapaMNwbbGICkpY8CPQ
iat-mode=0
```
-Make sure to check out the [post-install
notes](https://community.torproject.org/relay/setup/bridge/post-install/).
-If you are having trouble setting up your bridge, have a look at [our help
section](https://community.torproject.org/relay/getting-help/).
+If you are having trouble setting up your bridge, have a look at [our help
section](../../../getting-help/).
+If your bridge is now running, check out the [post-install
notes](../post-install/).
### 4. Advanced usage
diff --git a/content/relay/setup/bridge/dragonflybsd/contents.lr
b/content/relay/setup/bridge/dragonflybsd/contents.lr
index 0d449f8..a30f67f 100644
--- a/content/relay/setup/bridge/dragonflybsd/contents.lr
+++ b/content/relay/setup/bridge/dragonflybsd/contents.lr
@@ -128,8 +128,8 @@ To confirm your bridge is running with no issues, you
should see something like
### 6. Final Notes
-If you are having troubles setting up your bridge, have a look at [our help
section](https://community.torproject.org/relay/getting-help/).
-If your bridge is now running, check out the [post-install
notes](https://community.torproject.org/relay/setup/bridge/post-install/).
+If you are having troubles setting up your bridge, have a look at [our help
section](../../../getting-help/).
+If your bridge is now running, check out the [post-install
notes](../post-install/).
---
subtitle: How to deploy an obfs4 bridge on DragonflyBSD
diff --git a/content/relay/setup/bridge/fedora/contents.lr
b/content/relay/setup/bridge/fedora/contents.lr
index bd953f4..6e2a730 100644
--- a/content/relay/setup/bridge/fedora/contents.lr
+++ b/content/relay/setup/bridge/fedora/contents.lr
@@ -87,8 +87,8 @@ To confirm your bridge is running with no issues, you should
see something like
### 5. Final notes
-If you are having trouble setting up your bridge, have a look at [our help
section](https://community.torproject.org/relay/getting-help/).
-If your bridge is now running, check out the [post-install
notes](https://community.torproject.org/relay/setup/bridge/post-install/).
+If you are having trouble setting up your bridge, have a look at [our help
section](../../../getting-help/).
+If your bridge is now running, check out the [post-install
notes](../post-install/).
---
html: two-columns-page.html
diff --git a/content/relay/setup/bridge/freebsd/contents.lr
b/content/relay/setup/bridge/freebsd/contents.lr
index d954e06..50921b0 100644
--- a/content/relay/setup/bridge/freebsd/contents.lr
+++ b/content/relay/setup/bridge/freebsd/contents.lr
@@ -103,8 +103,8 @@ FreeBSDlatest: {
### 7. Final notes
-If you are having trouble setting up your bridge, have a look at [our help
section](https://community.torproject.org/relay/getting-help/).
-If your bridge is now running, check out the [post-install
notes](https://community.torproject.org/relay/setup/bridge/post-install/).
+If you are having trouble setting up your bridge, have a look at [our help
section](../../../getting-help/).
+If your bridge is now running, check out the [post-install
notes](../post-install/).
---
subtitle: How to deploy an obfs4 bridge on FreeBSD
diff --git a/content/relay/setup/bridge/netbsd/contents.lr
b/content/relay/setup/bridge/netbsd/contents.lr
index f81e965..37af844 100644
--- a/content/relay/setup/bridge/netbsd/contents.lr
+++ b/content/relay/setup/bridge/netbsd/contents.lr
@@ -84,7 +84,7 @@ To confirm your bridge is running with no issues, you should
see something like
### 5. Final Notes
-If you are having troubles setting up your bridge, have a look at [our help
section](https://community.torproject.org/relay/getting-help/). If your bridge
is now running, check out the [post-install
notes](https://community.torproject.org/relay/setup/bridge/post-install/).
+If you are having troubles setting up your bridge, have a look at [our help
section](https://community.torproject.org/relay/getting-help/). If your bridge
is now running, check out the [post-install notes](../post-install/).
---
subtitle: How to deploy an obfs4 bridge on NetBSD
diff --git a/content/relay/setup/bridge/openbsd/contents.lr
b/content/relay/setup/bridge/openbsd/contents.lr
index 4fc5f65..0c86c1e 100644
--- a/content/relay/setup/bridge/openbsd/contents.lr
+++ b/content/relay/setup/bridge/openbsd/contents.lr
@@ -85,8 +85,8 @@ To confirm your bridge is running with no issues, you should
see something like
### 6. Final notes
-If you are having trouble setting up your bridge, have a look at [our help
section](https://community.torproject.org/relay/getting-help/).
-If your bridge is now running, check out the [post-install
notes](https://community.torproject.org/relay/setup/bridge/post-install/).
+If you are having trouble setting up your bridge, have a look at [our help
section](../../../getting-help/).
+If your bridge is now running, check out the [post-install
notes](../post-install/).
---
subtitle: How to deploy an obfs4 bridge on OpenBSD
diff --git a/content/relay/setup/bridge/windows/contents.lr
b/content/relay/setup/bridge/windows/contents.lr
index 26e8789..9b6a011 100644
--- a/content/relay/setup/bridge/windows/contents.lr
+++ b/content/relay/setup/bridge/windows/contents.lr
@@ -95,7 +95,7 @@ To confirm your bridge is running with no issues, you should
see something like
### 6. Final notes
-If you are having troubles setting up your bridge, have a look at [our help
section](https://community.torproject.org/relay/getting-help/). If your bridge
is now running, check out the [post-install
notes](https://community.torproject.org/relay/setup/bridge/post-install/).
+If you are having troubles setting up your bridge, have a look at [our help
section](https://community.torproject.org/relay/getting-help/). If your bridge
is now running, check out the [post-install notes](../post-install/).
---
subtitle: How to deploy an obfs4 bridge on Windows
diff --git a/content/training/checklist/contents.lr
b/content/training/checklist/contents.lr
index 88065d0..2ba9852 100644
--- a/content/training/checklist/contents.lr
+++ b/content/training/checklist/contents.lr
@@ -8,13 +8,13 @@ Complete this checklist before running a Tor training.
## Prepare
- * I read and agree with the Tor Project [Code of
Coduct](https://community.torproject.org/training/code-of-conduct/)
+ * I read and agree with the Tor Project [Code of Coduct](../code-of-conduct/)
- * I read the Training [Best
Practices](https://community.torproject.org/training/best-practices/)
+ * I read the Training [Best Practices](../best-practices/)
* I have an agenda for the training
- * I reviewed my [training
slides](https://community.torproject.org/training/resources/)
+ * I reviewed my [training slides](../resources/)
## Security Protocol
diff --git a/content/training/risks/contents.lr
b/content/training/risks/contents.lr
index bc65942..061f775 100644
--- a/content/training/risks/contents.lr
+++ b/content/training/risks/contents.lr
@@ -44,7 +44,7 @@ However, we may be able to put you in touch with lawyers who
are capable of addr
Some relevant resources include:
* [EFF Know your rights](https://www.eff.org/issues/know-your-rights)
- * [EFF Tor legal
FAQ](https://community.torproject.org/relay/community-resources/eff-tor-legal-faq/)
+ * [EFF Tor legal FAQ](../../relay/community-resources/eff-tor-legal-faq/)
* [OONI disclaimer](https://ooni.io/about/risks/)
---
color: primary
diff --git a/content/user-research/how-to-volunteer/contents.lr
b/content/user-research/how-to-volunteer/contents.lr
index 754db35..b6da55b 100644
--- a/content/user-research/how-to-volunteer/contents.lr
+++ b/content/user-research/how-to-volunteer/contents.lr
@@ -18,12 +18,12 @@ Please remember to update the issue as your research
evolves.
Not all of the data collected in our research is disclosed to the public, but
our general findings are.
To protect our participants' privacy we take care to anonymize their responses
and avoid recording our sessions.
-If you're already familiar with the Tor Project and user testing, have a look
at our [current needs for user
research](https://community.torproject.org/user-research/open/) and see which
study better suits you.
+If you're already familiar with the Tor Project and user testing, have a look
at our [current needs for user research](../open/) and see which study better
suits you.
Remember to drop us an email telling us about your plans so we can follow and
support your research.
-As a volunteer we also ask that you read and follow our [Code of
Conduct](https://gitweb.torproject.org/community/policies.git/tree/code_of_conduct.txt),
as well our [Guidelines for
Research](https://community.torproject.org/user-research/guidelines/).
+As a volunteer we also ask that you read and follow our [Code of
Conduct](https://gitweb.torproject.org/community/policies.git/tree/code_of_conduct.txt),
as well our [Guidelines for Research](../guidelines/).
-**Why do we run Demographics?**
+### Why do we run Demographics?
We don't collect personal data in our
[Demographics](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%20activities/2020/user_demographics-en.md),
and all questions are optional.
We believe it's important to collect basic demographics to help us understand
if we are meeting our mission regarding diversity and inclusion.
In addition, collecting these demographics is required for specific studies to
support human rights.
@@ -44,16 +44,16 @@ We also ask anyone running research not use software hosted
by third parties lik
After conducting your research, it's normal to be excited to see your feedback
implemented as soon as possible.
However all feedback must be discussed internally across the different teams
at the Tor Project first.
This means that it's often necessary to run the same research more than once
to validate your findings, and meet the expectations of the engineers,
developers, designers, researchers and others at Tor.
-Please read our
[Guidelines](https://community.torproject.org/user-research/guidelines/) to get
to know this process more.
+Please read our [Guidelines](../guidelines/) to get to know this process more.
## Checklist
- Read the guidelines on [how to do user research with
Tor](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/README.md).
- Read and follow our [Code of
Conduct](https://gitweb.torproject.org/community/policies.git/tree/code_of_conduct.txt).
- If you don't have one yet, [request a Gitlab
account](https://support.torproject.org/misc/bug-or-feedback/).
-- Open an issue in the [UX Research
Repository](https://gitlab.torproject.org/tpo/ux/research/-/issues).
+- Open an issue in the [UX Research
Repository](https://gitlab.torproject.org/tpo/ux/research/-/issues).
- Subscribe to the [UX mailing
list](https://lists.torproject.org/cgi-bin/mailman/listinfo).
-- Learn more about our users by reading [Tor's user
personas](https://community.torproject.org/user-research/persona).
+- Learn more about our users by reading [Tor's user personas](../persona/).
---
color: primary
---
diff --git a/content/user-research/open/contents.lr
b/content/user-research/open/contents.lr
index 91d34df..d8f36ef 100644
--- a/content/user-research/open/contents.lr
+++ b/content/user-research/open/contents.lr
@@ -19,7 +19,7 @@ html: two-columns-page.html
body:
These are our current needs for testing Tor products, as well as methodologies
and testing scripts.
-Before running Tor user research, be sure you read our [Guidelines to becoming
a user researcher with
Tor](https://community.torproject.org/user-research/guidelines).
+Before running Tor user research, be sure you read our [Guidelines to becoming
a user researcher with Tor](../guidelines/).
### Tor Browser for Desktop
* [Tor Browser
Usage](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%20activities/2020/browser-usage.md)
_______________________________________________
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
