HamSwagwich

What do you mean “quickly?”

That’s correct and that’s the problem. If a given community server goes down, that community basically just becomes an archive. It really needs to be able to continue without the host instance, similar to how a mesh works. Each remaining server routes around the dead node.

There is also the problem of search engine indexing… If a given server goes down, that information is lost to the search engine, even though it’s still on other nodes.

Which also leads to duplicate content problem for search engines, as ECU m each node of a given community contains the same information for a given post, making it crappy to index and search.

Indeed it would. The CO2 would trigger the breathing reflex and panic. Hypoxia does not trigger that and you start to lose yourself, similar to being drunk.

I’ve been investigating this more. It seems to be a problem with Kbin.social… I can view anything on lemmy instances from Kbin, but I can’t view anything on Kbin from lemmy instances. I can’t search my own name, I can’t search Kbin.social communities from Lemmy (tried lemmy.world and beehaw.org) … so I don’t know what to do. This problem basically kills kbin.social for me if it won’t federate properly.

I don’t know if it’s temporary, but you can’t post from Lemmy.world to Kbin, or even see any federated content from KBin. Also, anything I post from KBin doesn’t show up on Lemmy.world.

Also, if you go to Lemmy.world and view this thread, there’s 174 comments and counting. They aren’t showing up here. Something is wrong with Lemmy.world federation.