this post was submitted on 15 Jun 2023
41 points (100.0% liked)

/kbin meta

16 readers
2 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago
 

There was a post about how beehaw was defederating from shitjustworks and lemmy.world about 6 hours ago. Are we involved in that, as are we a subset of lemmyworld?

https://beehaw.org/post/567170

How does this affect us? I still see beehaw posts on my 'all' page, but any content I engage with is effectively visible, I want to be sure

you are viewing a single comment's thread
view the rest of the comments
[–] le__el@lemmy.world 15 points 1 year ago* (last edited 1 year ago) (1 children)

Replying from lemmy.world to check :)

EDIT: Shortly after the post, it was sent to the original kbin instance.

After 8 minutes, my reply apparently didn't make it to beehaw, so I assume all new comments from lemmy.world users, even on posts of third instances, are really banned on beehaw.

[–] LegendofDragoon@kbin.social 7 points 1 year ago (2 children)

And I'll reply back so you're sandwiched by kbin users.

Can either of you beehaw users see his post?

[–] le__el@lemmy.world 4 points 1 year ago

Just got your reply here on lemmy.world and only the top message seems to be on beehaw. My reply and your sandwiched reply both apparently didn't show up there

[–] le__el@lemmy.world 2 points 1 year ago* (last edited 1 year ago)

If you try to make another non nested comment (or reply directly to your original post) and it show up on beehaw, we can be sure that the federation is running and the comments (and nested comments) that involves the defederated instances are all completely banned from there.

EDIT: Catch42's comment also didn't show up there yet, so the federation seems to be is a big laggy.

EDIT2: And now Catch42's commented showed up there, so the federation synced up and the comment thread that involved any user from defederated instances didn't show up.