- Use distributed, federated services like Lemmy, mastodon etc.
- Support the hosts with our own funds.
- Moderate our own communities.
The second point is the most important. Reddit happened because they are a corporate entity seeking profit. Let’s own our social media platforms by actively contributing funds to them.
You must log in or register to comment.
Unsure how distributed federated services prevents the reddit downfall, aside from corporate greed. Which can also be solved through legally binding agreements/foundation-controlled companies. Among many other solutions that can avoid funding, stability, and consistency issued federated services have and will continue to have.
It’s all a tradeoff. To tradeoff corporate greed you now have community fragmentation and fragility risks as any instance can be taken down whenever, and any unhappy user that created communities can solely kill them off (As stated by some users threatening to do so in another thread).
What you should be talking about is how do you mitigate these tradeoffs. What should others do to make the fediverse more successful? If you want it to be successful than talking about these hard problems in a semi-flenal way is required.
#2 sounds good to say, but barely works in practice when you’re talking about infrastructure costs in the tens of millions of $ per year for something at scale…
Essentially saying nice things that don’t effectively translate into reality doesn’t solve problems. It just perpetuates a lack of critical thinking.
OK good point but think about your tone dude! You’re coming across like you think we are stupid and I’ll offer the benefit of the doubt that you don’t intend that side effect.
My tone is such that it addresses the nativity of posts like this. Especially when said nativity pushed for potentially counterproductive or harmful mindsets that prevent real solutions from being discovered.
Nativity must be addressed if hard problems are to be solved. It’s a baseline.
A small slice of users are going to understand broader technological, community, funding, and survivability nuances. As such these should be explained so we’re not simply hand waving necessary complexity away. Encouraging deeper discussion from others who would otherwise pass posts like these up because of the low quality.
It’s the difference between talking about niceties, vs actually working towards solutions. These are hard problems, and should be recognized as hard otherwise they go unsolved.
The more readers know about the rest of the iceberg the better. The more knowledgeable folks you attract to a discussion by encouraging critical thinking the better.
I don’t disagree with your analysis. I just think your tone is counter-productive. Good luck getting your message across.
This needs to be the way forward. The community needs to own itself, support itself, etc. The alternative is what just happened where the community is abused for someone else’s gain.
I agree to a point, but this is also how you get communities that are REALLY easy to squash. Because they’re fragile and incoherent. Bad actors can easily overwhelm them, astroturf, go after hosting…etc and small self funded communities won’t have the manpower, tools, or resources to combat it.
You want to build a strong community that lasts, and is resilient.
So how do we make our communities more resilient, well resourced, less fragmented, and also accessable for member growth?
We could self-host using our own computers and infrastructure, and secure them from hackers.
Can we?
For real, can we assist with hosting using our own servers as distributed nodes? I have business fiber and plenty of dedicated compute just hanging around. I’d happily host nodes to assist with stability, redundancy, and general compute/networking.
You literally can just download the Lemmy program and install it on any computer you want to use as a server. I used to run Mastodon servers a few years ago, and it’s not without its hurdles, but with some Linux knowledge and a little bit of server admin knowhow, you absolutely could.
You’d need a computer you’re gonna use as a server, put Linux on it, then install NginX or Apache on it, then Lemmy, then set everything up and get a domain name to attach to the computer’s IP. Question mark, profit. It might be a bit of an oversimplification, but with some research and work, it can be done.
I mean to contribute distributed resources to existing instances. Not so much make new ones. Assuming Lemmy has a protocol for distributed resources built on something like the raft consensus algorithm.
I’m mobile ATM, so not at home, trying to learn as I go. The goal being by the time I’m home I’ll know enough to provision resources if such a concept is a thing.
I have a whole cluster at home with business internet, so plenty of ready to go resources 🤔
Lemmy isn’t distributed like that. Each instance does its own user and community management with local storage and processing. The community content - posts and comments - gets distributed to any other instance that asks for it, and that instance then presents it to its users. The result is that the content is replicated & distributed across many instances, and the load of presenting that content to users is shared.
So, running your own instance, where you’re the only user, will cause that instance to fetch whatever communities you’ve subscribed to via API. That probably reduces, slightly, the load on those servers, but it’s not going to be a huge effect.
Running your own instance and getting a dozen or a hundred friends to use it instead of lemmy.world or feddit.de, on the other hand…
Ah gotcha.
Isn’t that a hard barrier/limit to scale then (as well as support)? Would it even be possible to run say a 5 million user Lemmy instance with a single write postgres DB (I assume compute can be load balanced, you can utilize CDNs for media content, can heavily cache the API, and that it supports read replicas?)
Nevermind 10, 30, or 50 million user communities 🤔
Though at that point you’re essentially just lighting your bank account on fire for infra costs.
