Noticed I haven’t seen any Beehaw posts recently, and then saw that we are on Beehaw’s instance banlist. Anyone know what informed that decision?
We’re not open signups and we don’t even host any mildly-questionable content.
Crashdoom ( @crashdoom@pawb.social ) English17•1 year agoFixed! Similar confusion with Lemmy.world the other day — We had some downtime blips at the point that lemmy.world became overloaded so they temporarily defederated us to avoid excessive retry attempts. Beehaw copied that list to avoid similar issues!
Should be all good now going forward, but you can take the URL to a post / comment and search it here to make it appear on pawb.social.
Lionir [he/him] ( @Lionir@beehaw.org ) English9•1 year agoThank you for contacting us about this! Sorry about the issue. (This is also a federation test!)
Crashdoom ( @crashdoom@pawb.social ) English6•1 year agoAll good! Thanks for being so awesome y’all :3
Spitfire ( @Spitfire@pawb.social ) English2•1 year agoThanks!
atomic peach ( @atomicpeach@pawb.social ) English4•1 year agoSeems to have started 5 days ago based on when we stopped getting posts in our instance. Their modlog doesn’t appear to show any specific issues with us. That was right around a big maintenance upgrade for them (and us, iirc). Might’ve been related to that and just getting a ton of errors thrown at their server?
Spitfire ( @Spitfire@pawb.social ) English1•1 year agoThat’s weird… as far as I can tell Pawb.social shouldn’t have done anything detailed on their list of why they defederate: https://docs.beehaw.org/docs/important-questions-decisions-and-reflections/on-defederation/
Any way we can reach out and see why they chose to?