this post was submitted on 15 Jun 2023
170 points (98.9% liked)
Lemmy.World Announcements
29026 readers
2 users here now
This Community is intended for posts about the Lemmy.world server by the admins.
Follow us for server news ๐
Outages ๐ฅ
https://status.lemmy.world
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Support e-mail
Any support requests are best sent to [email protected] e-mail.
Report contact
- DM https://lemmy.world/u/lwreport
- Email [email protected] (PGP Supported)
Donations ๐
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
Join the team
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Users on Beehaw would not see anything from Lemmy.world. If it's still federated with Kbin, then they would see that content.
Likewise, anyone on Lemmy.world would not see content or be able to access communities from Beehaw.
So for a Beehaw user, would they see all of the the Kbinner's comments and it would look as if they were talking to themselves? Or would they only see the top level Kbinner comment and nothing else (due to their instance not seeing the Beehaw comment and therefore not seeing children of that comment either)?
Beehaw can pull in content from other instances, but users from those instances cannot comment or post back to Beehaw. If you were interacting with content coming from Beehaw on a different instance, in practice it would feel like you're shadow-banned as nobody on Beehaw would be able to see or reply to you.
So given participant 1, 2. 1 is on .world, 2 is on kbin
P1: message a
P2: message b
P1: message c
P2: message d
Would a beehaw user see just messages b and d? What would it look like they are replying to?
Would they see the comment chain at all as it was started by P1?
There's two different scenarios, a community not hosted on beehaw:
they wouldn't see the chain at all.
On a community hosted on beehaw:
Message a would only exist on world's local copy of the thread, nobody not on world can see it. (This local copy is also not getting updated by anyone not on world.)
Basically, the true thread exists on the instance that hosts the community. Defederation cuts off communication with one server. If it's the server that hosts it, it's a lot more severe.