You Should Know

So you have raw database access and you can see that data. Why is this surprising? The systems I've used that solve storing data encrypted have massive usibility hits around exchanging and authenticating keys to a point where it sucks so bad I just want to disable it (matrix is a good example, non question their key exchange bullshit is hindering their adoption). I'm not saying this couldn't be fixed but should it? Most services that use a database will be inline with your discovery of how Lemmy uses that database. Storing something encrypted that is meant to be viewed publicly is the same outcome with more steps. If someone cares enough to monetize it just patch the code to change whatever behavior you don't like. I havent seeing anything about an acceptance test for Lemmy instances or anything that requires someone to use an unaltered version of Lemmy. How do you know the server admin isn't already doing all of this? You don't. Don't expect privacy in public spaces.

So you can get the users voting on posts on other instances?

Could it be anonymized, so you can get exact up/downvote data from your instance, but when it comes to other instances you only get the absolute up/downvotes?

So you have raw database access and you can see that data. Why is this surprising? The systems I've used that solve storing data encrypted have massive usibility hits around exchanging and authenticating keys to a point where it sucks so bad I just want to disable it (matrix is a good example, non question their key exchange bullshit is hindering their adoption). I'm not saying this couldn't be fixed but should it? Most services that use a database will be inline with your discovery of how Lemmy uses that database. Storing something encrypted that is meant to be viewed publicly is the same outcome with more steps. If someone cares enough to monetize it just patch the code to change whatever behavior you don't like. I havent seeing anything about an acceptance test for Lemmy instances or anything that requires someone to use an unaltered version of Lemmy. How do you know the server admin isn't already doing all of this? You don't. Don't expect privacy in public spaces.

So you have raw database access and you can see that data. Why is this surprising? The systems I've used that solve storing data encrypted have massive usibility hits around exchanging and authenticating services to a point where it sucks. I'm not saying this couldn't be fixed but should it? Most services that uses a database will be inline with your discovery of how Lemmy uses that database. Storing something encrypted that is meant to be viewed publicly is the same outcome with more steps. If someone cares enough to monetize it just patch the code to change whatever behavior you don't like. I havent seeing anything about an acceptance test for Lemmy instances or anything that requires someone to use an unaltered version of Lemmy. How do you know the server admin isn't already doing all of this? You don't. Don't expect privacy in public spaces.