From 4ebf63ce1fb3a81e5a4c12aafaf69946e3ee16a4 Mon Sep 17 00:00:00 2001 From: Felix Ableitner Date: Fri, 13 Sep 2024 16:45:23 +0200 Subject: [PATCH] and and --- src/users/03-votes-and-ranking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/users/03-votes-and-ranking.md b/src/users/03-votes-and-ranking.md index f4bf319..241dc19 100644 --- a/src/users/03-votes-and-ranking.md +++ b/src/users/03-votes-and-ranking.md @@ -38,4 +38,4 @@ The ranking algorithm is described in detail [here](../contributors/07-ranking-a # 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 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. +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.