3 ms·

>> if it runs on top of web2 it doesn’t classify as web3 in my book. Then web3 providers need to buy their own hardware and data centers instead of using web2

>> if it runs on top of web2 it doesn’t classify as web3 in my book. Then web3 providers need to buy their own hardware and data centers instead of using web2 cloud infrastructure: https://www.vice.com/en/article/wxdnxy/amazons-server-outage-took-down-a-decentralized-crypto-exchange https://www.vice.com/en/article/wxdnxy/amazons-server-outage... https://coinmarketcap.com/alexandria/article/coinbase-down-as-amazon-web-services-suffers-outage https://coinmarketcap.com/alexandria/article/coinbase-down-a... https://decrypt.co/44321/70-of-ethereum-nodes-are-hosted-on-centralized-services https://decrypt.co/44321/70-of-ethereum-nodes-are-hosted-on-...

3np 5y ago
You’re not wrong. Or at the very least: - Software needs to be built and distributed with local-first in mind. Self-hosting should be trivial, encouraged and accommodated for. Preferably transparently to the user. (Self-hosting a web browser and its built in password manager is already something people do, as a silly example of why it doesn’t have to be a worse UX). In the example of a “dapp”, this could mean the web app in source-available (not necessarily “real open source”) and provided as a zip file ready to run in a local browser and/or electron app. Possibly via IPFS or similar. It should not depend on phone-home to any particular hard-coded server, domain, or SaaS. - For stuff that is hosted in DCs, opt for smaller providers. Get infrastructure, not SaaS. Ie avoid managed services in AWS/GCP/Azure/Ali, instead get VMs or servers with someone else.