2/ The definition of a dApp is that it should be built on a decentralized blockchain platform. This simply means that the application is and cannot be controlled by a single entity but by its own user base (governance tokens are important).
3/ Why can dApps only run on Web3 and not on Web2? Web 2 is the version of the internet that most people use on a daily basis. Web2 is centralized because all data is stored on servers owned by a handful of companies like Amazon/CloudFare.
4/ Web3 is the decentralized version of Web2. Data is not stored on servers owned by a handful of companies. Users are in control over their own data and so on. The middle-men are being cut out on Web3. You get what you see on Web3.
5/ This brings me to the point of why dApps can't run on Web2. dApps require decentralized infrastructure to function as dApps. Otherwise, they'd be called Apps and Web3 would be Web2. Think of things like censoring, blocking, banning, etc.
6/ This goes against the principles of what Web3 makes Web3. Therefore, most self-proclaimed Web3 blockchains -aren't- actual Web3 blockchain protocols. This is unfortunate and misleading, as we would be using Web2 but see it as Web3.
7/ Web3 allows apps to run securely and without interference, which then, and only then, turn them into decentralized apps. There is no single point of failure. Web3 won't be able to bring the entire system down.
8/ Besides the technical aspect, Web3 offers true transparency, which offers trustless transactions/collaborations/agreements and so on. This is certainly not possible with Web2, which is also prone to online scammers who abuse Web2.
Remember to always reply to the first thread when you make a threadstorm, it makes it easier for your readers to browse the whole thing without too many clicks! Nice threadstorm!
2/ The definition of a dApp is that it should be built on a decentralized blockchain platform. This simply means that the application is and cannot be controlled by a single entity but by its own user base (governance tokens are important).
3/ Why can dApps only run on Web3 and not on Web2? Web 2 is the version of the internet that most people use on a daily basis. Web2 is centralized because all data is stored on servers owned by a handful of companies like Amazon/CloudFare.
4/ Web3 is the decentralized version of Web2. Data is not stored on servers owned by a handful of companies. Users are in control over their own data and so on. The middle-men are being cut out on Web3. You get what you see on Web3.
5/ This brings me to the point of why dApps can't run on Web2. dApps require decentralized infrastructure to function as dApps. Otherwise, they'd be called Apps and Web3 would be Web2. Think of things like censoring, blocking, banning, etc.
6/ This goes against the principles of what Web3 makes Web3. Therefore, most self-proclaimed Web3 blockchains -aren't- actual Web3 blockchain protocols. This is unfortunate and misleading, as we would be using Web2 but see it as Web3.
7/ Web3 allows apps to run securely and without interference, which then, and only then, turn them into decentralized apps. There is no single point of failure. Web3 won't be able to bring the entire system down.
8/ Besides the technical aspect, Web3 offers true transparency, which offers trustless transactions/collaborations/agreements and so on. This is certainly not possible with Web2, which is also prone to online scammers who abuse Web2.
Remember to always reply to the first thread when you make a threadstorm, it makes it easier for your readers to browse the whole thing without too many clicks! Nice threadstorm!
Lol! This is a good opportunity to learn, gotta try it again :P