3 ms·
> Without the network effects, nobody uses them in the first place, and then you're either not true, see [matrix]. You hardly say nobody uses it Still, the re
by kitkat_new 5y ago
> Without the network effects, nobody uses them in the first place, and then you're either
not true, see [matrix]. You hardly say nobody uses it
Still, the reason why it (and Signal) is not used that much in the first place, is the network effect working much better for WhatsApp and iMessage.
> 2. or you try to convince them to use a decentralized service, which almost certainly doesn't have the usability or polish of an app built by a company.
App built by company and decentralized aren't mutually exclusive.
> And if it gets bad, we'll change services. Simple as that.
tell that the people still stuck with WhatsApp
- bastawhiz 5y ago1. I actually don't know a single person who uses matrix. Half of my friends use Signal. Just one data point, but I've literally never had a reason to use or install it. 2. They are, though. Decentralized software necessarily moves slower because everyone needs to upgrade to add new features. Nobody is going to tell their mom to use an app where attachments only works a quarter of time (see: IRC). 3. Nobody is stuck with Whatsapp. My family stopped using it about a year ago. Most of my friends stopped using it a bit after.
- kitkat_new 5y ago> They are, though. Simply a false claim. Prime example: the internet > Decentralized software necessarily moves slower because everyone needs to upgrade to add new features. so...? > Nobody is going to tell their mom to use an app where attachments only works a quarter of time (see: IRC). and IRC is the same as "decentralized services"? > 3. Nobody is stuck with Whatsapp. My family stopped using it about a year ago. Most of my friends stopped using it a bit after. > Just one data point
- bastawhiz 5y ago> Prime example: the internet Email has been around forever. And yet sending an attachment larger than about 50MB is essentially impossible. There will never be an update to email that fixes this.