this post was submitted on 16 Nov 2023
604 points (97.5% liked)
Technology
59457 readers
3211 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Decentralization is expensive too judging by some of the sentiment I've seen around running Mastodon and Lemmy/Kbin instances.
Right? People simply expect someone else to pay the bills.
And why wouldn't they? 90% of the software people use daily is free (as in beer), so of course being told that's going to change is going to cause upset. It takes a lot for people to want to pay money for something that, to those who don't value free (as in freedom) software, is no different than the costless alternative.
Yup, it has a cost, but there's perhaps a one or two orders of magnitude cost difference between hosting instant messaging + calls with something like XMPP, and hosting mastodon/Lemmy/Kbin (or why I do the former but not the later, and why I'm ok to pay for the service, esp. considering that my instance's business model isn't, unlike Reddit, to re-sell influence and data).
How does does decentralization avoid the costs that Signal laid out in the blog posts?
I laid it out elsewhere in this thread, but in short, costs grow non-linearly with scale: you can run thousands of users on a RPi, but a million users requires whole datacenters. Decentralization not only helps with not requiring "whole datacenters" in the first place, they also enable maximization of resources: if you have a NAS at home, or a RPi hanging around, a router idling somewhere, or an abandoned smartphone in a drawer, you can probably host enough accounts for all the people that you've ever met in your life. And there are hundred of thousands of such underused devices everywhere, which, put together, would be sufficient to host the whole world multiple times around.
The other issue is sustainability: with this centralization comes single point of failure. It's no big deal witnessing the disappearance of one or few providers of a federated network. Accounts and data can be migrated easily. For most users, it's invisible. Now compare this to Signal running into financial issues: you are contemplating million of users losing access to their account and their data, and having to re-bootstrap their whole social graph elsewhere. This is another level of "cost", or price to pay, for centralization.
Who is maintaining all these "unused" devices that you will want working pretty consistently? Who is responsible for replacing hardware when it dies? Who is looking into it when someone stops receiving messages? What happens when the person hosting thousands of users just stops wanting to do it? Who migrates these accounts?
Frankly, your argument sounds more like wishful thinking than anything practical. You've basically described the plan as "Magically some devices in someone's basement will suddenly start running a messaging service, maintenance free, from now until the end of time".
This isn't wishful thinking, this is in defense of a model where our digital needs would be distributed at a level lower than that of the tech majors, which was commonplace before everything on the internet was so consolidated.
I'm not saying that everyone should self-host, I'm saying that federated services could be hosted at family&friends/regional/national levels, simultaneously, and deliver a resilient service at a negligible cost. Hardware, which is very much a problem for Signal & al right now, wouldn't be in a distributed model, and could be donated and repurposed easily. My example was perhaps a bit too extreme, but I think you get the gist of what I'm saying.