> - People don't want to run a server... Do they not? I think this is the most important point the article made. Most people really don't want to run a server,

> - People don't want to run a server... Do they not? I think this is the most important point the article made. Most people really don't want to run a server, why? because they don't even know what a server is. However they do have some tangible sense of some program they download and run on their device. So the only way for the masses to have truly decentralised infra is to make sure those programs are nodes in the decentralised networks. > Or are most APPs simply not build as with server capabilities? This. I don't know why, maybe there just aren't enough interested developers to build clients for this stuff that works like e.g a bittorrent client. The irony seems to be that most people making these "decentralised" apps are only interested in making portals into centralised platforms connected to a blockchain. Or maybe the design of the protocols simply doesn't lend itself to independent clients directly connecting to each other. I think bittorrent is a really good example of how to do this stuff well. People will complain and say the masses don't use it, but it's been around for a couple of decades now and it "just works" and continues to "just work" and every client is a server, it is truly decentralised, with federated infra only to distribute metadata. I think the only reason it's not used by the masses is because 90% of what it's used to distribute is copyrighted material. If web3 (or lets just call it what it is - NFTs, or the next blockchain fad) are to work in a truly decentralised manner, then whoever is designing these protocols needs to keep the whole picture in mind, end to end, to ensure clients are equal - to design it in such a way to actively work against the trend to centralised platforms, make them irrelevant.