UPDATE: seems like this has been fixed with the update to 0.18.1 https://programming.dev/instances
I can see their posts so I know they aren't actually banned
https://programming.dev/instances
looks like maybe they had their domain name set with the https:// in it and that was breaking stuff? has this been fixed in the Lemmy code yet? we shouldn't have to manually ban invalid domain names
It looks like midwest.social is listed as both
linkedandblocked. Quite strange. That instance is rather benign, as far as I can tell. @[email protected] , did we block that domain temporarily due to federation load issues?I think it's literally blocking a misconfigured domain name, like at one point their config might've had the domain name specified as "https://midwest.social" when it should be just "midwest.social"
since federation by default is allow-all, any bugs like that should be fixed so we don't have to manually block all the bad config values possible, or imagine if an instance was maliciously using invalid config values
@[email protected] yes, @[email protected] is correct, we were having tons of retries bogging down the server due to attempts to connect to the https://midwest.social domain. I think it should be fixed in the 0.18.1 update, which I hope to roll out in a few hours.