Defederated by Beehaw, no idea why
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?
It doesn't look like your instance is defederated from beehaw
sent from my beehaw™ account
Hey there, can you reach out to me on matrix? @penguincoder:hive.beehaw.org
If they defederated your instance pretty sure this post won't reach them. Try making a post from another instance
I'm posting from https://lemm.ee/, I simply set my display name to 'irdc@derp.foo'.
Huh, it's impossible to tell from jerboa
Tap the username to see "irdc@derp.foo@lemm.ee".
That tripped me out on jerboa too. I just clicked on their username, and then I could see that it's a lemm.ee account
That doesn't work if you're from lemm.ee as well
True, I didn't think of that
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.
perhaps they started whitelisting?