Defederated by Beehaw, no idea why (lemm.ee)

submitted 1 year ago by irdc@lemm.ee to c/support@beehaw.org

16 comments fedilink hide all child comments

I just noticed my private instance, https://derp.foo/, was recently defederated by Beehaw. Thing is, I have no idea why. Was my instance accidentally included in some bulk defederation to get rid of spammers, or is there something specific to my instance?

you are viewing a single comment's thread
view the rest of the comments

[-] MentalEdge@sopuli.xyz 20 points 1 year ago

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.

[-] Seathru@beehaw.org 5 points 1 year ago

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).