I think from the perspective of beehaw, it’s more relieving rather than spooky. There’s nothing stopping someone from hopping over here to lemmy.world to make an account. It’s just that comments and posts from here don’t get copied over to beehaw, so it makes it less work to curate and moderate what’s showing up for beehaw-specific accounts.
I was thinking about that yesterday, not only can it become an echo chamber for the server, kind of the point of thing like a digital house/hotel, but it gets weirder because there’s comments on the same page but it’s in a parallel universe of comments. I dunno, feature not a bug?
Yeah it’s definitely a different way of going about things in general. It’s an interesting situation. I’d call it a feature of the platform because, at the end of it, the instance owns the data and has the “canonical” version of it, in the sense that it’s the origin.
If beehaw had the option of staying federated while having an instance-wide whitelist/blacklist of communities and users, then they would’ve gone that route, I bet. They mentioned wanting more granular moderation tools.
No one Lemmy instance can forcibly administrate another, so anything that’s added on top of the act of de-federating is actually less restrictive.
I think from the perspective of beehaw, it’s more relieving rather than spooky. There’s nothing stopping someone from hopping over here to lemmy.world to make an account. It’s just that comments and posts from here don’t get copied over to beehaw, so it makes it less work to curate and moderate what’s showing up for beehaw-specific accounts.
I was thinking about that yesterday, not only can it become an echo chamber for the server, kind of the point of thing like a digital house/hotel, but it gets weirder because there’s comments on the same page but it’s in a parallel universe of comments. I dunno, feature not a bug?
Yeah it’s definitely a different way of going about things in general. It’s an interesting situation. I’d call it a feature of the platform because, at the end of it, the instance owns the data and has the “canonical” version of it, in the sense that it’s the origin.
If beehaw had the option of staying federated while having an instance-wide whitelist/blacklist of communities and users, then they would’ve gone that route, I bet. They mentioned wanting more granular moderation tools.
No one Lemmy instance can forcibly administrate another, so anything that’s added on top of the act of de-federating is actually less restrictive.