HamSwagwich

@mojo Just keep telling people you don’t know what IPFS is without coming outright and saying it. Lol.

“IpFs GeTs PaId In FiLe CoIn”

IPFS is a protocol, you nitwit. That’s like saying “ActivityPub is gets paid in Filecoin” Makes no fucking sense. Build a Fediverse layer on IPFS, no crypto needed. FFS get educated before you start trying to talk to adults.

Jesus… just stop.

@Kalcifer

@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

@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.

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.