Posting to see if the defederation has affected my ability to post on here.
I’m requesting that
- One person on the beehaw.org instance reply to know if y’all can see my posts or not.
- Someone from the beehaw.org instance tell me if they can see my community through the beehaw instance: https://beehaw.org/c/[email protected]
(I’m from lemmy.world, but I don’t have a beehaw account)
My understanding is that we still have a local version of all the beehaw communities, but it will not actively sync with the original beehaw version. Consequentially, our posts won’t show up on any instance with an active federation with beehaw. So until they decide to federate again, this community is effectively cut off and only lemmy.world folks can post here.
Communities that are not originally from beehaw should be unaffected.
This sounds like the right explaination. I’ve joined a lot of pretty active Beehaw communities and now there aren’t any new posts that are younger than 15 hours on any of them…
our posts won’t show up on any instance with an active federation with beehaw.
Wait, so any other independent instance that federates with beehaw will actively not federate with lemmy.world? Like if instance “Whatever” federates with beehaw, “Whatever” automatically blocks lemmy.world? So it’s basically like a lemmy.world embargo from beehaw?
Nope, it’s just beehaw that independently defederated with lemmy.world and sh.itjust.works. This has no affect on communities not hosted on beehaw.
So basically if there’s a community [email protected], then beehaw.org serves as an information hub of sort for that community. All syncing between different instances goes through the original, but lemmy.world will no longer receive the beehaw syncs. If a user from lemmy.ml posts, it doesn’t come directly to us, it uses wherever the community lives as a bridge. In this scenario, because we’re cut off from the sync, we would not see any comments from users outside of our instance.
[email protected] however uses lemmy.ml as the hub. Because lemmy.world is federated with lemmy.ml, our local version is being kept up to date with the original and is not affected. So if someone from beehaw.org commented on [email protected], we’d be able to see it because it’s a different instance acting as the information hub.
Let me know if that helps, or if there’s anything I need to clarify!
ahhh, yes. that helps. thank you very much!
Nope. My user @[email protected] cant see your post in [email protected] . But I can access https://beehaw.org/c/[email protected] .
awww, that’s sad. I understand beehaw’s decision, but I don’t like it from my perspective.
