4 ms·
I get what you are saying about it being easier to move from one walled garden to another (based on the evidence that those moves happen more often than moves f
by cortesoft 11y ago
I get what you are saying about it being easier to move from one walled garden to another (based on the evidence that those moves happen more often than moves from between email providers)... but there is such a huge caveat that those moves are never a move chosen by an individual.
I cannot, as an individual, choose to move from one walled garden messenger app to another - if I do, I cannot message those people that don't. I am stuck going along with the group. This is ok in a lot cases (when the group's priorities line up with mine), but sometimes the things that are important to the group are different than the things that are important to me. For example, I might prioritize security over ease of use, but since the group doesn't, I will never get my wish, and I am stuck on a service that sacrifices security for ease of use.
- schwarrrtz 11y agoWouldn't you still have that problem with a federated system? You could roll your own uber-secure decentralized messaging protocol right now, if you wanted, but if nobody else adopts it then you're basically SOL.
- TuringTest 11y agoThe difference, I think, is that with federated system you can have a partial state where you communicate securely with those that have also adopted the security extensions, while making insecure connections with those who didn't, all within the same application/protocol (by using protocol extensions). Therefore, such features can be gradually adopted by an increasing amount of users. If the system is centralized and it doesn't support security, it's all or nothing; to enable secure protocols, both you and the other party must change to a different app, and you'd have to support both systems in order to communicate with secure and insecure users.