sinnerdotbin
joined 2 years ago
Due to the nature of such an open policy in sharing information (how open federation actually functions) could be frightening for someone uneducated on what privacy totally means, I have created this optional privacy policy introduction that will prime the user for what they are engaging in.
Personally I think everyone should be walking around with no pants, but I'd rather we talk each other's pants off than scare off, or find our pants removed by surprise.
https://github.com/BanzooIO/federated_policies_and_tos/blob/main/optional-privacy-policy-intro.md
I have an optional introduction statement I am going to add which might temper it a bit. People are blissfully unaware of how bad current closed platforms are for privacy, the data sharing between them, and what that means for them and society.
Despite some of the open and entirely public aspects of federated services, with some education it is far more private; you are not tracked right from the gateway through all your online (and offline) travels. How you carry yourself during those travels is what gives you control of your privacy.
I have had this concern for a few days and adapted the Mastodon privacy policy (adapted from the Discourse policy) and published it https://github.com/BanzooIO/federated_policies_and_tos/blob/main/lemmy-privacy-policy.md
Discussion on this has been started: https://lemmy.ml/post/1431759 and https://lemmy.ml/post/1431930. Open to any recommendations
You're right. Apologies.
There are many other models, some discussed in this post. All come with their own set of upsides and downsides.
For a small community, which Lemmy original was, straight up votes work great. Unfortunately it doesn't scale. Reddit is a perfect example.
You're right, there is only up/down vote systems with a user base that is in no way verified or otherwise restricted to a single vote/real person, or corporate algos.
There are plenty of different models. Do I fault the Lemmy devs for using it? No. Is it ideal for content discovery? Not really.
The idea is to gauge community interest/relevance and facilitate content discovery. I feel it is becoming a bit dated method of accomplishing this and easily gamed.
It isn't truly immutable though, and could be dangerous to propagate the idea that it is 100% immutable
Why would someone think that?
Because the comment I replied to, the actual thing I am addressing, makes an assertion that isn't entirely true and could lead someone uninformed into believing they can have their information removed platform wide.
What is the difference?
Not everyone is concerned with someone digging up dirt or wildly compromising material. Most people aren't special enough to be worried about that.
Most archives won't be globally search indexed. An archive won't show up on a federated search. There is more legitimacy to a federated version over someone reposting a screenshot (at least in perception, how federated could be altered or forged is another topic).
I also mention there are other reasons one might want to remove content. Just look at reddit right now, some may simply want to revoke support for a platform sometime in the future.
Sure, there could be a future where this is addressed. It isn't right now.
I don't disagree with you in the larger discussion on persistence of data. I am adding context to a scoped subtopic of it.
I'm behind Lemmy, but I've made an informed decision on what that means for my data.
That isn't what I am speaking to, and the fact someone could make a copy or it is archived somewhere doesn't make the statement that you can always remove your data from the platform true. And there is a difference between a potential copy and an original federated, distributed, and indexed version. There are also reasons someone might want to remove their data other than simply being worried about the actual content of it.
People need to be aware of the persistence of data, but people also have to understand the technology they are using to make their own informed decisions on how they engage.
This is assuming your local is still federated. If your local gets defederated you currently have no control over any previously federated copies of your posts / comments / votes.
Only PostgreSQL at the moment. I also don't believe it currently supports SSL connection to Postgres so you'll want to run it on the same machine or have a tunnel to your DB.
There is zero chance you'll get it running on anything else without significant code change.