So, obviously an anti Lemmy bias there, and not entirely true, but there are some aspects of federation it can be dangerous to ignore.

There is a different primary privacy focus here, and it provides an extreme level of privacy but places an extreme level of responsibility on the user for their own privacy, more than most places.

There is a distinction to a potential scrape and a system designed to duplicate, often irreversibly at submit.

There are also other things people are often not aware of and the community is not doing a great job communicating. Admins are not doing a great job of protecting themselves either.

For instance many, still don’t know votes here are entirely public.

If you understand this all and are comfortable, great. Many do not prepare themselves and would engage differently if they had a better understanding.

For a take by someone who is pro-federation but not ignoring these concerns see: https://lemmy.ca/post/948217

I feel you didn’t read the original post. It isn’t about expecting privacy, it isn’t a criticism of the fundamentals of Lemmy as many seem to be taking it (there are many ways I explain how it is more private from being tracked and profiled).

It is about understanding how privacy is maintained on a federated platform.

Many users coming from other platforms do not understand the mechanisms here and how they are different.

Take a look for the comment here about vote privacy (the highest voted comment here) or dozens of the other posts where people are coming to this awareness. Many assumed was private due to coming from a platform where this was.

ceddit and others you have noted historically have broken for a variety of different reasons, and the others are are currently not functioning as the API they used was banned May 1st. Pushshift, which these services often used, had a mechanism to remove sensitive data you accidentally posted or otherwise wanted removed.

Archive.org is not searchable, not indexed in mainstream search engines. Also would be responsive to legal requests. It is hard to get a complete profile history on someone.

All of these external sources require a great deal of extra effort from someone to pry.

The concern to be aware of here isn’t that it could be scraped, which yes it can. The concern is that it is duplicated by design, wide and broad, on a platform that somewhat functions as a single entity, the instant you hit submit.

People make mistakes. The Unabomber got caught by doxxing himself with a single phrasing of an idiom. Not complaining, simply saying “be very, very, very, very, very, very, very, very, very careful here”

And ultimately this comes down to different conceptions of privacy, sure, but one of these conceptions is suspiciously impossible to fix yet simultaneously deflective of the other, that other being directly beneficial to companies and any seeking to control mass populations.

Exactly. The privacy goal on federation is different. If people are educated, they can be safer.

You can’t eat your cake and have it too.

I’d also argue stalking has more to do with the mental health issues of the stalker than the victim being to blame for how they interacted with the world. We don’t tell a student not to participate in lectures because someone may latch onto something they said and become infatuated. We punish stalkers instead.

If someone is aware and engaging to their comfort level, no matter how open, I would not blame them, the victim, for being stalked. If someone wanted to be cautious, but they didn’t know the risks here, I would feel guilty for not educating them on how they can protect themselves.

Idk this is a ramble. I see so many things so often that used to be personal responsibility on online safety, that instead of teaching the skills we make tools. And i feel like not teaching good personal safety and protection is goong to doom any project ultimately.

You can’t fix ignorance without education.

Which is the entire point of my post, to encourage education in this space (which again, again, again, is different than what many are coming from with its own unique set of risks)

I appreciate that you are reflecting on how you want to manage your own privacy in this space!

People should be educated enough of the pros and cons as much as possible, although that might mean some would get intimidated and refuse to join.

Bingo. Which would you rather do, talk someone’s pants off, or scare them off or otherwise have them caught with them down?

Also love your local domain.

I’ve had a similar idea. Want to have a race to market? (you’ll have a head start, I’m heading into the domain of managing federation block lists next).

This is the beautiful part of an open platform, we can all steer it and contribute all sorts of wonderful solutions.

Unfortunately not that easy. There is discussion on solutions. There isn’t any now. Platform currently isn’t stable enough to respect mutually federated changes all the time.

Also I did put a disproportionate focus on this no take back component, but the scope is wider than that (see comment below about votes being public when almost everyone coming from a monolith assumes it is private)

Yeah. I can see a case made on either side.

This is the point I am trying to drive home. Even with zero comments, zero posts, you could doxx yourself accidentally with votes alone. You came here from another platform and had a certain expectation of how privacy works here. It does intuitively feel like it should be private.

You are trading some privacy for censorship resistance and community safety in this case, because the goals are different here.

If you trust your admin to keep your IP and email private, and you manage your comments and posts carefully, I encourage you to let your voice be heard and upvote every sinnerdotbin’s pantless picture post of the week (just don’t like the posts in a different, very small and niche category that can link to you publically as you are the chair of the board at never-nude.social, and there are only 5 members who always like the same posts) . If you are in a country where that support might end with you in a work camp, I’d maybe advise against it in case your local turns out to be a honeypot.

There is a privacy component to federation that the world really would benefit from, but it will be lost if people are not informed. Incredibly private if you are aware how to navigate it. Horrible if you aren’t.

Unless a user is viewing from kbin, which interoperates here. It is entirely in view to the kbin UI (and Mastodon I believe).

It’s the same camp.

I’m not making the claim other platforms are better because you might be able to slip in a ninja edit before it is captured. I am making the claim that if you are not on high alert here, more than ever, it will bite you.

For better or worse, some people are coming here from other services expecting a measure of control of their data that you don’t get here.

The experimental aspect of this space is the other thing I feel warrants more explicit warning about, and noted in my policy template.

Votes are entirely public, Lemmy just made a UI choice not to show them. They show up if someone views it from kbin and ultimately something that could be mined from a self hosted admin.

I think this information may make some of those who profess “everything is saved on the internet and why care” change their tune.

Saves I am not sure about yet. Think that may be locals only.

Edit: community subscriptions are another. I believe the admin that hosts the community has access to the sub, but this may also be available to anyone self hosting. Haven’t confirmed anything regarding subs yet, maybe that is locals only too.

Also USA does have laws regarding site usage by children. This was brought over from the Mastodon policy I adapted.

Praise your local admins! And help them out by petitioning them to study their local laws and come up with proper policy and TOS

You’re almost there.

Only if your home server remains unfederated. Even then other users of the server will be able to see everything. And will be more likely to remember, like miss Busy Body.

Uh, a, if not the primary point in my post?

Your IP, your email, will remain private at your local if your admin is responsible. If you act to your comfort level in your engagement, you will remain private in the public sphere.

If you self host, or find an admin you have incredible trust in, you should remain untraceable if you manage your engagement responsibly.

Though another thing I highlight in the policies is this is experimental software. Leaks can and will happen. We have a voice and can play an active part in preserving that privacy.

Recorder is always on by default with your engagement; recorder is always off by default when it comes to things that automatically identify you. It is the opposite in a monolith service.

Hell, our phones know more about us and how to exploit us than Lemmy ever will. I do appreciate your post but I just think that it’s a product of the ‘connected’ world we live in.

Yeah, awesome. That is another thing I am raising awareness of. What this actually protects you from, being tracked and profiled. That is an amazing feature of federation getting lost in data safety.

Booo to miss Busy Body.

It does to many, thus the awareness of how it works here, that is all.

If you don’t think it matters, or you understand enough to be sure never to expose yourself in a way that you are uncomfortable with that is awesome! Many are waking up to a realization of the nature of things here they were previously not aware of, and some are growing very uncomfortable with that now that they can’t adapt their previous engagement to that knowledge.

I don’t think the word “privacy” is a good word for the concept. I believe “user data control” or “right to be forgotten” is more appropriate for the “deletion issue”. However, there are few privacy issues such as instance admins having access to private messages and the potential for a hack to expose users e-mail addresses and usernames.

This has been debated, and is very dependent on the context. It is a very broad concept to try to address and the lines do get blurred on the definition of what is “private data”. The hope here is to partition the responsibilities of the admin from the user.