@mojo Tell me you don't know what IPFS without telling me you don't know what IPFS is, lol. What the fuck does IPFS have to do with crypto?

@Kalcifer

@kavides

Oops thank you

@Kalcifer

The long term solution is something like IPFS object storage that's read only for everyone but the author instance. One copy of the data but all instances can read it and it's stored forever in a redundant medium with bitrot protection.

@Sam_uk

I've been running one. showeq.com

The basic service gets overloaded quickly and you'll need to upgrade if you get any traction at all.

Also, since KBin federation is broken, it's not great

@1Fuji2Taka3Nasubi

Yes it does. My KBin node is not federating with KBin.social or only works intermittently.

So... Scientology, but with more Zuck

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.

The RCS issue hits the nail on the head I think. It's really the biggest stumbling block for everyone at this point.

I'm viewing this from KBin and I don't see strikethrough.

I think it confuses everyone. I have no idea why these two things exist in KBin. It's a complete mystery the thought process that went into it.

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.