Well the decentralized nature of the Fediverse helps spread out the cost. For example you can rent a VPS (virtual private server) for like ten or twenty dollars a month and throw a Lemmy instance on it. That’s where many Lemmy instances are currently living. There’s your own time involved in maintaining the instance, but the cost should remain pretty stable.
Conversely, a centralized service where all users have to be supported by an individual or company owned cluster of machines can get very expensive. I can’t imagine the operating costs for a site like YouTube with the demand for data storage and bandwidth.
Well I think it depends on the balance of growth between nodes and users. If growth of users and growth of instances is proportional, it should be sustainable.
That leaves the question of how well Fediverse software can deal with increasing node numbers. I hope that engineering question has been properly considered. It’s like the available number of IP addresses when they initially designed TCP/IP, they never considered four octets might not be enough for future growth.
Nothing on the Internet seems to indicate that use distribution will be even. Power law is going to get involved and some nodes are going to get massive.
Well yeah that will happen. Initially I looked for instances with the biggest subscription base. Then after some reading about the Fediverse I realized that kind of thinking does not apply. You get everything regardless of which node you’re on (barring any defederation). Maybe most will realize that, but you’re probably right most will not. We’ll see how it goes.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Well the decentralized nature of the Fediverse helps spread out the cost. For example you can rent a VPS (virtual private server) for like ten or twenty dollars a month and throw a Lemmy instance on it. That’s where many Lemmy instances are currently living. There’s your own time involved in maintaining the instance, but the cost should remain pretty stable.
Conversely, a centralized service where all users have to be supported by an individual or company owned cluster of machines can get very expensive. I can’t imagine the operating costs for a site like YouTube with the demand for data storage and bandwidth.
The cost gets spread out, but not completely. You are also going to run into problems if an instance takes off.
The costs are manageable now, but is that sustainable?
Well I think it depends on the balance of growth between nodes and users. If growth of users and growth of instances is proportional, it should be sustainable.
That leaves the question of how well Fediverse software can deal with increasing node numbers. I hope that engineering question has been properly considered. It’s like the available number of IP addresses when they initially designed TCP/IP, they never considered four octets might not be enough for future growth.
Nothing on the Internet seems to indicate that use distribution will be even. Power law is going to get involved and some nodes are going to get massive.
Well yeah that will happen. Initially I looked for instances with the biggest subscription base. Then after some reading about the Fediverse I realized that kind of thinking does not apply. You get everything regardless of which node you’re on (barring any defederation). Maybe most will realize that, but you’re probably right most will not. We’ll see how it goes.
The hosting costs isn’t on the user end, but the instance end.