UPDATE: @[email protected] has responded
It is temporary as lemmy.world was cascading duplicates at us and the only way to keep the site up reliably was to temporarily drop them. We’re in the process of adding more hardware to increase RAM, CPU cores and disk space. Once that new hardware is in place we can try turning on the firehose. Until then, please patient.
ORIGINAL POST:
Starting sometime yesterday afternoon it looks like our instance started blocking lemmy.world: https://lemmy.sdf.org/instances
This is kind of a big deal, because 1/3rd of all active users originate there!
Was this decision intentional? If so, could we get some clarification about it? @[email protected]
As someone working on integrations I’d also have to leave if we’re permanently blocking the largest instance, but I’d like to give SDF the benefit of the doubt here. Maybe this was just a temporary measure to deal with the insane load from yesterday?
You are absolutely welcome to do that.
I’d really rather not leave, though! I like it here – but being forced to choose does put me in a bind when it comes to being able to build the things that I want to build. Lucky for me then that today won’t be the day where such a decision is thrust upon me.
For me lemmy still doesn’t work. At least not without U.S. VPN. Otherwise I get error: 502 Bad Gateway
Maybe it’s just not fully up yet.
I don’t know if geoblocking is a thing, but just FYI: there are additional Lemmy SDF instances for EU & JP regions which may work better depending on where you’re based.
Ah, seems like blacklisted IP. Since I am behind CG-NAT the public IP is simultaneously shared between many users. I tried disconnecting and reconnecting to the network which changed my public IP, and it works now.
We really need the IPv6.
I noticed that with Mullvad it’s also doing that, I think it might be an anti-spam system?