>Everybody has to host their own content Yeah, this won't work. Like at all. This idea has been tried over and over on various decentralized apps and the probl

>Everybody has to host their own content Yeah, this won't work. Like at all. This idea has been tried over and over on various decentralized apps and the problem is as nodes go offline and online links quickly break... No offense but this is a very half-assed post to gloss over what has been one of the basic problems in the space. It's a problem that inspired research in DHTs, various attempts at decentralized storage systems, and most recently -- we're getting some interesting hybrid approaches that seem like they will actually work. >Domain names should be decentralized IDs (DIDs) This is a hard problem by itself. All the decentralized name systems I've seen suck. People currently try use DHTs. I'm not sure that a DHT can provide reliability though and since the name is the root of the entire system it needs to be 100% reliable. In my own peer-to-peer work I side-step this problem entirely by having a fixed list of root servers. You don't have to try "decentralize" everything. >Proof of work time IDs can be used as timestamps Horribly inefficient for a social feed and orphans are going to screw you even more. I think you've not thought about this very hard.