DNS caching at play. The registrar has pointed it to their own nameservers, and that gets cached in lots of places.
Their domain expired a month ago, this is pretty normal for a registrar to do with expired domains.
Updated Date: 2025-02-11T17:35:29Z Creation Date: 2021-01-12T00:35:25Z Registrar Registration Expiration Date: 2025-01-12T00:35:22Z
With the way the bricks are laid, wouldn't it distribute the weight across the entire base?
Can you link me to an example please? Pictrs has been giving me troubles, but everything should be working now.
Fixed now!
Every morning my cat is waiting for me in the bathroom. He rolls around at my feet, and then guards me from the countertop while I shower.
If I somehow beat him, he screams and hammers on the door to be let in.
Doh, taking a look! We made a bunch of changes today that were supposed to be all seamless 😅
What's it doing when you say doesn't load?
Can you hit f12 to open your dev console, go to old.lemmy.ca, and paste any errors that show up in the console tab?
Can you clear your cache / hold shift +refresh?
I believe you can reply locally on your instance to dead communities, but that data would never be replicated to other instances. The fediverse isn't really a mesh network, more like a hub and spoke on a per community level.
Hmmm, unlikely. The only major impact from this switch should have been a complete flushing of our cloudflare cache.
<Canadian>
Sorry</Canadian>
I think your browser cached a bad redirect that was up briefly =(Sorry, fixed!
Yes because you're applying enough heat to change the chemical composition of the food.
Reheating, nah.
Valid, but it's run by a group in the UK that runs several of the popular ones. It's prooooobably not going anywhere.
It's probably torrent clients doing a ping test of peers to check latency. Ops VPN server replies to the ping so they look close, even though they're not.
I can't imagine a client that would ship an ip2geo db to bother trying to look up locations. Just doesn't make any sense.
Sh for shell scripts.