this post was submitted on 02 Jan 2024
60 points (73.1% liked)

Fediverse

27910 readers
1 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to [email protected]!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 1 year ago
MODERATORS
top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 48 points 10 months ago (22 children)

Privacy is a reverse idea on the Fediverse. I know it's a hot take, but by design the Fediverse is never going to be private and people should stop assuming it is.

When you send out a comment/like/post/whatever, you are literally broadcasting a message to any other instance listening. It essentially just says

{
  messageId: 42,
  message: "This is some message",
  action: "comment"
}

and if you want to delete that message it's essentially

{
  messageId: 42,
  action: "delete"
}

While Lemmy and Mastodon respect that, anyone can build any fediverse app and simply choose not to use it. Anyone can build a search engine and can choose to respect the delete or not. Any instance could defederate from them if they don't like that, or they may not care. The point however is that ActivityPub is designed this way, and there really isn't a better way.

If your comment has been sent out to other instances - well then it's there already. You can't delete it without some form of just asking politely that they delete it. They have it already, it could be stored in their DB, duplicated in other DBs, aggregated and sent to AI, searchable, whatever. They have it. There is no concept of "delete" on the fediverse. It's asking nicely for them to delete it.

[–] [email protected] 12 points 10 months ago (1 children)

The thing most people get wrong is privacy friendly =! private. If you say something publicly (on the internet) you can assume it will stay for ever, if not directly then via some sort of archive. The privacy part of Lemmy/Mastodon is them not collecting data on what you look at to sell it. If you want something private then don’t use Social Media, because what you say publicly will stay public.

[–] [email protected] 3 points 10 months ago

The privacy part of Lemmy/Mastodon is them not collecting data on what you look at to sell it.

Nor requesting your real name and ID, phone number...

load more comments (20 replies)
[–] [email protected] 25 points 10 months ago (1 children)

this seems like nonsense. as if youre going to limit who can see your public posts... the fediverse is opt-out not opt-in. you opted-in when you signed up with an AP federating platform.

if you dont want to federate, dont use a federating platform. if you want privacy, dont use a platform designed for public distribution.

[–] [email protected] 2 points 10 months ago (1 children)

It's not as much about seeing, it's about using, and profiting from.

This post under CC-BY-NC-SA.

[–] [email protected] 5 points 10 months ago

U know activpub supports adding licences to things but lemmy doesnt want it. Pixelfed and peertube already have it but lemmy told me i was an idiot for wanting to licence my content.

[–] [email protected] 23 points 10 months ago* (last edited 10 months ago) (1 children)

If something is on a public unencrypted website, it isn't private.

Unfortunately certain people have chosen to mislead users about this.

You may as well post your ass on a billboard then complain that people look at it.

[–] [email protected] 1 points 10 months ago (1 children)

Fediverse software has followers-only posts, direct messages, local-only posts … Mobilizon and Streams even have private groups.

[–] [email protected] 13 points 10 months ago* (last edited 10 months ago) (2 children)

None of that is private. It's all readable by anyone with an admin account.
As a general rule. If it's not end to end encrypted, assume it's public.

[–] [email protected] 0 points 10 months ago

"Readable by anybody with an admin account" is not the same as public. And as a bunch of people involved in January 6 found out, end-to-end-encrypting something doesn't keep mean it won't get revealed. So the general rule is assume anything you say online could be made public; use Signal (or some other encrypted messaging that you trust) and limit distribution to a small number of trusted people to reduce the chances of that happening -- but don't count on it!

[–] [email protected] 21 points 10 months ago

Might spund a little conspiratorial but this fubdamentally breaks what federation means and specificly gives enormaus power to larger instances. Also the language of it by calling it consent feels like its meant to evoke a certain emotional reaction almost like its part of a larger phyop.

Also there is no such thing as privacy on the fediverse. There is anonymity if ur carefull.

[–] [email protected] 20 points 10 months ago (2 children)

It’s fine if single instances do consent-based federation that prioritize safety over openess, but why should it become the default for all instances? It will result in instance protectionism and an overall decline in discussion quality. Making it opt-in means people will connect less likely with folks from other instances, meaning people will mainly stay on their instances, meaning it supports tribalism in the Fediverse. More safety usually comes at a cost, too. In this case: less interaction with other instances.

But if you federate with instances that you trust good enough in the first place, constent-based federation is not necessary imo.

[–] [email protected] 1 points 10 months ago* (last edited 10 months ago) (11 children)

No wait, I was wrong Its not necessarily instance protectionism. For especially vulnarable groups consens-oriented federation might make sense.

The question is whether this is the desired state for all instances and I would disagree here. I think this falls under a bigger societal debate: should the fediverse become a place were all potentials of harm are completely erased? In other words: should the Fediverse become a safer space?

First of all, minorities should be protected as by the laws of many countries. However, what harm looks like beyond that should be dynamically defined in social debate. Now you want to skip that and erase all potential out of the stand.

This ignores that these societal norms change over time and that a certain risk is part of the human condition. There always needs to be a balance between freedom and protection for the whole society. But as said before, safer place are also needed, but they dont work as blueprint for the whole society.

Early christian groups can also considered safe places. You are aligned here with what to me are totalitarian argumentation patterns that thrive for a garden eden that will never exist.

That doesnt mean that we shouldnt thrive for certain ideals but not for things that cannot and shouldnt be expected of people, like giving up their free will for complete safety.

load more comments (11 replies)
[–] [email protected] 1 points 10 months ago

@[email protected]

prioritize safety over openess

[–] [email protected] 17 points 10 months ago (1 children)

I don't expect anything I post here to be private.

[–] [email protected] 6 points 10 months ago

On Lemmy? Certainly not. But on other fediverse software, there are followers-only posts, direct messages, local-only posts ... none of it's encrypted, but still it's not public.

[–] [email protected] 2 points 10 months ago* (last edited 10 months ago) (1 children)

Tbh I'm struggling to imagine what this would look like in something like Lemmy. It seems to be describing an extreme form of setting your account to private, but this only really makes sense in a situation where you have followers who are friends and family. How would I decide who to "approve"?

[–] [email protected] 1 points 10 months ago (1 children)

Great point, I should be more explicit in the article. On Lemmy, it would look like a couple of things:

  • today, another instance's request to federate is accepted unless it's explicitly blocked. This means that bad actors can get away with stuff until they're discovered and blocked (although it makes it easier for good actors to federate). Consent-based federation turns that around: a request to federate isn't accepted unless it's approved. One way an instance admin could decide whether or not to approve a request is to look at FediSeer to see what other instances are saying about the requestor.

  • at the individual level, it would mean that people would start out by participating in local communities (and maybe even just seeing posts from their instance, not sure about that), and could then choose to have their posts federated out

[–] [email protected] 4 points 10 months ago (1 children)

That sounds like it punishes small instances... a lot. What would starting an instance look like? Do you start with a huge list of servers to inspect and approve?

[–] [email protected] 1 points 10 months ago

For new instances, the easiest thing is to start with the list of an instance that the kind of moderation you agree with. If I were starting up an instance in the Lemmy world, I might go with the current federation list of lemmy.blahaj.zone or beehaw.org (although others might make differnet choices), in the Mastodon world I might use awoo.space as a starting point.

There's certainly a need for tools to make this more scalable. "Recommended lists" are a likely next step; there isn't much software support for this yet, but it's similar enough to blocklists that they're also fairly straightforward; it would be up to the new instance admin to decide how many to inspect or whether just to trust the list. And tools are also needed to address the challenge in the other direction: how do existing instances decide whether or not to accept the request? Instance catalogs like fediseer can help. Another possibility that I mention and link to in the article is "letters of introduction"; federations of instances (which I'll talk about in the next installment) are another.