3 ms·
That's why it's important for us who are working on decentralized projects to not use "decentralized" itself as a feature but rather use the side-effects of wha
by diggan 8y ago
That's why it's important for us who are working on decentralized projects to not use "decentralized" itself as a feature but rather use the side-effects of what decentralized technology brings.
The first ones that comes to mind is:
offline-first, local-second and internet-third. Basically, the applications you use day-to-day should work no matter how you are connected. If you are on a local lan, the application should work with the rest of the clients who are on the local lan. Slack would be amazing if when it looses internet connectivity, it simply tries to connect directly to other clients around it.
Performance. Decentralized applications can be much faster than centralized ones, for the majority of the people on the internet. If I'm in South Africa and using a web application with it's servers in US, there is a maximum speed the application can work at, no matter if I'm working with someone next to me, or in China. With decentralization, we can move logic closer to the people needing it.
Security. Less important for the average person but more and more people are caring about it. Apple seems to have a focus on it that actually makes security-conscious people chose them for it. Not having everything going through the same centralized service makes that centralized service less of a target, and decentralized technology usually does a way better job on using encrypted communication because it's needed when you send data peer-to-peer.
If instead of applications writing "It's decentralized!" on their landing pages like that's actually a feature, they explain the benefits of decentralization, I think it becomes a lot more interesting for the average person.
Disclaimer: I work on IPFS, a P2P protocol.