Thanks! I’m for mass adoption and want admins to succeed. That starts with keeping users educated (and admins covered).

This is largely assumed by someone like yourself or I who understands the implications. I am finding it evident that a lot of people are not aware.

There is also a distinction to a potential screenshot, a scrape or archive no one visits, and a federated copy on a widly used instance you have lost access to.

I edited my comment above to include a project I am working on to hopefully help admins get this across and educate users on how to appropriately engage to their comfort level.

This keeps on being asserted but it is far from true. If defederation happens or your local goes offline, posts/comment history/profile/votes will remain on other widely used instances and out of your control.

A large instance has already defederated with 2 other larger instances. If you run a personal instance I feel it will become very, very common to be be locked out of managing your data.

You can expect defederation to happen all the time as that is a deliberate part of the open federated model.

And that is to say nothing about federation simply breaking sometimes.

I already have been locked out of content that exists on other instances that will remain forever and I’ve only been around a short while. I don’t care personally, but people keep asserting this claim that only bad actors or scrapers will dupe your data. Federated data is very different than a non-federated copy for many reasons and that matters to some people. Everyone should understand deleting your account, or modifying your content will often not remove your content outside your instance, and many people engage outside their local. It will likely exist in federated, Lemmy searchable form forever in some capacity (in the current iteration anyway).

Not trying to spread FUD, but if we want to maintain users they have to be educated as they will find out eventually and not be happy.

I have some working drafts on policies for admins to help them navigate and explain their responsibilities to their users.

It is a bit of a weird read outside of the context, but this is an optional primer I have drafted that will hopefully help explain the distinctions:

https://github.com/BanzooIO/federated_policies_and_tos/blob/main/optional-privacy-policy-intro.md

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.