20
Defederated by Beehaw, no idea why
(lemm.ee)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Aug 2023
20 points (100.0% liked)
Beehaw Support
2794 readers
1 users here now
Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.
A brief FAQ for lurkers and new users can be found here.
Our September 2024 financial update is here.
For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
Not blocked for me. https://beehaw.org/c/hackernews@derp.foo works just fine. And it wouldn't if it were defederated.
That's not the case. For viewing/posting to communities and messaging users to "stop working" they have to be "purged" as well as defederated.
You can still message a user or post to a community from a formerly federated instance. But those interactions will never make it off-instance. The message won't get delivered, and your post will only be seen when viewing the community from your instance. But you can do those things.
After defederation, content stops syncing, but without additional action (a purge), nothing else happens. The user profiles, communities and even local functionality, remains.
Thanks for explaining that. I’ve been using links like the above to test if one instance is available from another rather than looking through the /instances list. I guess it’s a poor test (and probably not any less work than just checking the lists).
Indeed it does. However, comparing it to https://derp.foo/c/hackernews and sorting by new reveals that posts more recent than 5 days ago were never sync'ed. In addition, https://beehaw.org/instances shows derp.foo as blocked.
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: !hackernews@derp.foo
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: !hackernews@derp.foo