this post was submitted on 26 Aug 2023
19 points (100.0% liked)

Beehaw Support

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


if you can see this, it's up  

founded 2 years ago
MODERATORS
 

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
[–] Seathru@beehaw.org 2 points 1 year ago (4 children)

Not blocked for me. https://beehaw.org/c/hackernews@derp.foo works just fine. And it wouldn't if it were defederated.

[–] MentalEdge@sopuli.xyz 17 points 1 year ago (2 children)

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.

load more comments (1 replies)
load more comments (2 replies)