diff --git a/src/contributors/02-local-development.md b/src/contributors/02-local-development.md
index 77c649e..32954c5 100644
--- a/src/contributors/02-local-development.md
+++ b/src/contributors/02-local-development.md
@@ -7,13 +7,13 @@ Install the latest Rust version using [rustup](https://www.rust-lang.org/tools/i
 Debian-based distro:
 
 ```bash
-sudo apt install git cargo libssl-dev pkg-config libpq-dev curl
+sudo apt install git cargo pkg-config libpq-dev curl
 ```
 
 Arch-based distro:
 
 ```bash
-sudo pacman -S git cargo openssl pkg-config postgresql-libs curl
+sudo pacman -S git cargo pkg-config postgresql-libs curl
 ```
 
 macOS:
diff --git a/src/users/03-votes-and-ranking.md b/src/users/03-votes-and-ranking.md
index 6eba483..56ee320 100644
--- a/src/users/03-votes-and-ranking.md
+++ b/src/users/03-votes-and-ranking.md
@@ -37,3 +37,7 @@ Comments can be sorted in the following ways. These all keep the indentation int
 Additionally there is a sort option **Chat**. This eliminates the hierarchy, and puts all comments on the top level, with newest comments shown at the top. It is useful to see new replies at any point in the conversation, but makes it difficult to see the context.
 
 The ranking algorithm is described in detail [here](../contributors/07-ranking-algo.md).
+
+# Vote Privacy
+
+Lemmy attempts to limit the visibility of votes to protect user privacy. But due to the way Lemmy works, votes cannot be completely private. Instance admins can see the names of everyone who voted on a given post or comment, and community moderators can see the names for the communities they moderate. This helps to fight against vote manipulation. Additionally, individual votes are federated over ActivityPub together with the corresponding username. This means that other federated platforms can freely choose how to display vote information, even going as far as publicly displaying individual votes.