- cross-posted to:
- technology@beehaw.org
- technology@lemmy.ml
- reddit@lemmy.ml
- cross-posted to:
- technology@beehaw.org
- technology@lemmy.ml
- reddit@lemmy.ml
Reddit has informed moderators of communities that are still private in protest that they will lose their mod status by the end of the week. Thousands of communities went dark earlier this month to push back on the company’s planned API pricing changes.
yes, they post to each other’s sites
Nice, still trying to wrap my head around the separate instances. If they were truly federated, wouldn’t they all tie into each other or am I missing something?
Yup. I’m from kbin.
So am I…
…and I am also on lemmy.world! Wheee!
They don’t tie into each other in the sense that they share login credentials or anything like that. But they do send messages - posts, comments, favourites, etc. - to each other, if those messages are requested, creating a network of synchronizing content mirrors.
They do.
https://lemmy.world/post/828058?scrollToComments=true
This is the lemmy world link. you can see kbin users comments there.
I think the best analogy is email. Email is built around standards, and it doesn’t matter if you use outlook or gmail. That’s similar to the fediverse (the standard) and knime/lemmy (the email providers in the analogy).
The thread you are commenting on is on a lemmy instance, lemmy.world, submitted by a user registered on that instance.
You and I are both users registered on kbin.social.
We can all see each other’s submissions, submit content on communities, comment on them, etc.
If you are registered on a kbin instance, you’ll be using the kbin Web UI to view the same content. That’s what differs.
Also remember that with the cross-instance propagation within the federated servers you can never really delete your post(s). (At least that’s how it was explained to me…)
When you delete a post, your home instance sends a federated deletion command. If every server is running lemmy/kbin as-is, then your post will be completely gone. But anyone could modify their instance to not delete posts.
I think if you want GDPR style deletion, you would have to contact each instance admin individually.