cross-posted from: https://lemmy.ca/post/948217
Sensationalist title yes, but this is something that is partially true.
TLDR; I am not spreading FUD. This space can be more safe than many, for the privacy aspect it was actually designed to maintain, which is the complete opposite privacy principle to where most new people are coming from. A monolith platform provides a measure of control over how public your engagement is while leaving you open to being tracked; open federated protects you from being tracked with a cost of having less control over how public your engagement is (and will remain). Some people do not understand this and will change the way they engage if they understand.
There is a lot of misinformation I am seeing (or at least glossed over information) that will potentially lead less informed to peril. I am hoping to provide clarity and maybe shift the attitude of some of the more technical among the community. Not everyone is educated in the same domains, and not every one will grasp some of these concepts easily.
Every thread started along the lines of āDiscovered X in Lemmy is not privateā is followed up with a comment āEh, not really an issue. And I reviewed the code myself, an account deletion removes everything from the dbā. I push my glasses up: āAckchyually, that isnāt really true in practice. If defederation happens, or otherwise disconnected, (which always will happen in some capacity) a copy will remain in Lemmiverse, foreverā. This is followed up with āwell duh, that is how federation works, and everything you post on the internet is copied and there forever. It is no different than a scrape or a screenshotā.
There are nuanced but very important distinctions to a scrape or screenshot and a federated, distributed, indexed copy. Those distinctions will change the way many engage with the platform.
Most people are not having screenshots taken of every post they make, when they make them. Most donāt have to be concerned with wildly compromising material tanking their run for office. It takes a high degree of intent and effort for someone to go to external, and unauthorized sources of duplication. It may not be a complete profile history. Most archives are not going to be indexed and easily searchable on mainstream search engines. Unauthorized archives can get sued into oblivion or otherwise disappear.
Not everyone is able to grasp a platform that acts kind of like a single entity but is not a single entity, especially if they are a refugee from a monolith platform. Many just see it as a single entity initially and when they see āremoved from the dbā they will assume any such action means platform wide.
A federated copy is automatic and effectively instant by design. A federated copy will be a complete profile. A federated copy will show up in federated searches. A federated copy could end up readily showing up in external indexes. A federated copy may have engagement the user isnāt notified of. A user on an instance where defederation has happened may easily come across an entire profile history in a frozen state. Attention can be brought to content that the user desires censored because it will say āeditedā or ādeleted by user Xā and a SnoopyJerkison could just switch to an instance account that has a copy with two clicks in the official app.
I have made an informed decision on how I will engage by recognizing this. Iāve accepted the folks my local are always going to see my spelling as impecabā¦ impeccibahhā¦ very good, while some other local may see me as the philistine that I am before an edit. I will inevitably doxx myself in some way but it might be nice to have a stalker. Itās just me and the damn dog on our private fiberglass island here and she isnāt much of a conversationalist. I am in a place in life where Iām pretty comfortable with myself and have no problem walking around here with no pants on. Not sure why I recently got onto using pant idioms at every opportunity, but I have accepted that if it follows me around with folks replying, āI know you, youāre that guy with no pants!ā, I wonāt be able to go back and remove the sources of the reference platform wide.
Iāve made comments I cringe a little at. Entirely benign and nothing Iām losing sleep over, but in haste they were not expressed in my usual voice nor really contributed to the discussion. If I had hesitated longer I would not have responded. Point being: Iām the one ringing alarm bells about this and I am still having to remind myself of the nature of federation.
Some people may not be comfortable with this, or could become less comfortable later. They should not be led to believe that it is a simple matter of āthe internet doesnāt forget, but you can delete it from the platformā and understand they need to be very cognizant and thoughtful in how they engage because federation is very unforgiving and really doesnāt forget. This is a feature, not a bug. At its core, federation is balancing many goals. From censorship resistance, community safety, to privacy. It can actually provide an extreme level of privacy. But people will make mistakes, that will remain here, right in their face, if they arenāt extra careful. It wonāt be in some dark archive. It wonāt be in a screenshot never taken and never posted. The reminder of an accidental slip up will be here to perpetually haunt them. They will leave (likely traumatized by it for years to come).
A federated copy will have the perception of being more legitimate, true or not. The common, non-technical, person wonāt understand if they find something you post hosted on a site you are ideologically opposed to, which it will be. Imagine my embarrassment at the next Pantless-Meeting-Pantless event when I get stopped at the door and shown the posts they believe I have actively made on ānever-nude.socialā. āButā¦ butā¦ federation!ā. āOk Captain Kirk. Hereās your pants. Now scram!ā
Some want to have assurance they can remove content platform wide for other reasons. Revoking support for a platform is one that seems to be in vogue right now. Iāve seen posts like āthat site we hate is restoring our retracted posts!ā. But Iāve seen cases right here on Lemmy where a user has censored all their content, only to come across that same content on other widely used instances completely intact.
This loss of edit access happens fast. Every user at this local will be aware of the high profile cases of defederation. This is a feature by design, and one you can expect more of I suspect. There are also simply errors in federation at times. Iāve lost access to copies on a popular instance the second I posted them.
Maybe this will change. It will be a monumental challenge. And it isnāt the case now. Users have to fully understand this.
āSo what, screw the normies. Let them find out the hard way. Itās getting too crowded here anyway. Like you pantless sinnerdotbin! Git outta here if you donāt like it here in the wwwild-wild-westā.
Yet another aspect some are failing to recognize: many of the instances exist in places where they do take privacy very seriously. There are laws about disclosing collection, use and retention of data. One day you may visit your trusty local and you may find a blank page with a single statement: āI keep having very expensive embodied suits appear on my doorstep holding crisp manilla envelopes. I may be breaking the law. I am shuttering immediatelyā. Hope I didnāt want a reputation of wearing buttless-chaps instead of no pants ācause I aināt got access to modify any of it now.
Iāve seen admins advising others to block EU in their firewall because they are aware of this liability and the lack of a privacy policy. That is a big part of the world that will have limited contribution to this movement.
Policies go a long way to establish user trust. I have gained a high level of confidence in some admins. They are competent, capable, and thoughtful about their users. People have been investigating hardening beyond what I would expect from any admin. They could showcase this level of care and intent by explaining it in their policies.
Privacy policy frameworks can also help new admins navigate responsibilities that keep their users, and the wider platform, safe.
Donāt hand wave this aspect away with ādonāt post anything you donāt want public on the internetā. This is a totally different beast. Educate those not as fortunate as you to understand how this actually works. It is designed for your actual traceable information to be kept safe by the gatekeepers, the admins. Users must be highly aware: everything else you do here is public in a way you may never have experienced before.
Donāt hand wave the concern about post/profile/vote/message privacy, explain how the privacy goal is different here and how one might mitigate the aspects they are not comfortable with.
I have started a project where I intend to provide basic policy frameworks that one might use as a point of reference and I would very much like further input on it.
https://github.com/BanzooIO/federated_policies_and_tos/
These policies are going to be terrifying for the uninitiated. I have drafted an optional privacy policy preface that may help admins express the clear distinctions between their responsibility, their usersā responsibility, and the actual real privacy goals in this emerging space.
https://github.com/BanzooIO/federated_policies_and_tos/blob/main/optional-privacy-policy-intro.md
- End transmission, engage pantalon. Zip
Hey folks, guy in the cross post. Thanks for doing that @[email protected] , I feel it is an important discussion for people to be a part of across the Lemmiverse.
Seems there is some positive engagement on here, and maybe a couple that are a bit confused. Iām going to assume they arenāt just curmudgeons because why would you waste time commenting if you werenāt making an expression of interest in good faith, but maybe not ready to fully invest yet?
To expand on the TLDR; many new users are coming from monolith platforms (such as reddit; Meta; etc) into the brave new world of federated platforms (like Lemmy) without fully understanding the difference in privacy principles between these two models. Many, more experienced, users do not understand it fully themselves and they make potentially dangerous assertions, or at least ones that could mislead less experienced users into believing Lemmy behaves in a way that it doesnāt.
Itās all fine and good to say āEverything posted on the internet stays. Never post anything you donāt want publicā, but in practice, and especially people coming from monolith platforms, they may make mistakes if they are not highly cognizant of some distinctions between the two models of public, social engagement.
If you are certain youāll never, ever have any risk of making such a mistake, the subtle distinction wonāt matter to you. If you arenāt sure (it is very easy to trip up here) you are going to want to be educated on where some of the potential hazards are, and you will want to be very, very, very careful. Like you never have been before.
Even some of the most confident, letās call them, āperfectly private postersā, often get a little shook when I inform them their votes are entirely public, when they had previously made an assumption they were not due to familiarity with a monolith platform where votes are private. It seems intuitive that they should be private here, but that is not the case. This is a very prevalent misunderstanding right now, and very eye opening to some.
I much prefer the model of federated because it really gives the user the full control of their privacy to engage to the level they are comfortable with. But it can be very dangerous if not managed appropriately.
I also feel the wider community is not doing a very good job of communicating this, which is validated by the chord it seems to have struck over on Beehaw. But I come with solutions: a haywire, but comprehensive essay on some of the things a user should be aware of. I have also started a project that provides templates for privacy policies so that admins can add accountability to their instances while also protecting themselves.
Anyway, a very complex subject many are still learning to navigate, and not something easily reduced to a tldr; As it is, this version is half the length of the original, and you would have been half way through it by now if you just went to the source.
If you have any questions, Iām here to answer them.
When you say votes arenāt private, does that mean instance admins could theoretically see them in their database, or do you mean everybody can see them? If itās the second, where can I see my votes?
Everyone can see them if they use kbin and I think Mastodon which Lemmy interoperates with (ie. Kbin users often see and engage with posts on Lemmy and vice versa). Sign up to kbin if you want to see yourself.
All admins have access, and a rouge admin could very easily mine it.
I can see an argument for it, but does make you take pause on how you will use that feature doesnāt it?