TL;DR: Please search and subscribe to [email protected] on your instance to cache it on your instance so we can get visibility. We’re moving to our own hosting. Thanks for everything Ruud!

I’m excited to announce some big changes for our Vegan Home Cooks. As many of you know, Lemmy has been our platform of choice and we are hosted on the largest Lemmy instance lemmy.world. However, it’s time for us to evolve and move to our own instance. Let me explain why.

Lemmy.world, while a significant player in the Lemmy universe, has diverged in its vision and management from what we seek in a platform. The admins there have different political and operational views that don’t align with our goals. This is no slight against them; it’s just a matter of different paths.

It’s important to recognize that Lemmy is, at its heart, a passion project. Developed by talented individuals driven by their ideals rather than corporate goals, it operates on a scale that’s more hobbyist than mass-market. This has its charms, but it also means that development isn’t as rapid as one might expect in a more commercial environment.

The thing is, this approach works for many in the Lemmy community. The developers, supported by donations, have been content with this pace and scale. Even major instances have been okay with this grassroots, community-oriented approach. For a platform born out of a communal ethos rather than a corporate one, this isn’t surprising.

However, things started shifting when Reddit made some API changes. Suddenly, Lemmy was thrust into the spotlight as a potential drop-in replacement for Reddit. This influx of users, many with expectations shaped by the slick efficiency of corporate tech, put an unprecedented strain on the platform and its developers. Imagine, a small, community-funded team suddenly dealing with the demands of 50,000 new users. It was a clash of cultures and expectations.

Lemmy.world stepped up during this influx. Run by volunteers, they took a more corporate approach to manage the surge. Their rapid growth brought them under the spotlight, attracting both hackers who exposed major flaws and users who demanded rapid scaling and development.

This brings us to the crux of the matter. There’s a growing rift between the Lemmy developers and the team at lemmy.world. The developers, whose political views differ significantly from many in the Western tech sphere, run lemmy.ml with a distinct set of principles. The arrival of a large number of new users, many with different viewpoints, led to tensions and even bans.

This situation has led to a split within the community. A group of developers, frustrated with the direction and pace of Lemmy, are creating Sublinks – a Lemmy-compatible platform. Their plan? To eventually replace Lemmy, particularly on large instances like lemmy.world, effectively outmoding the original platform.

So, where does this leave us? We’ve been observing these developments and have concluded that the best way forward for our community is to establish our own Lemmy instance. This move will allow us to build a space that aligns with our values and needs, free from the external pressures and conflicts affecting the larger Lemmy ecosystem.

This is a big step, but it’s one that opens up exciting opportunities. We’ll have more control over our platform’s direction and be able to create an environment that truly reflects our community’s spirit and needs. Please search and subscribe to [email protected] on your instance to cache it on your instance so we can get visibility. We’re moving to our own hosting. Thanks for everything @[email protected], you and your team have been a gracious host.

  • hamid@lemmy.worldM
    link
    fedilink
    arrow-up
    3
    arrow-down
    2
    ·
    7 months ago

    I’m not seeing all the comments yet on the new community, just the posts, federation is weird!

    My understanding of the architecture is that we should keep it simple and basically have a 1:1 relationship for instance to communities so that each instance would host a community then there would be larger “identity” instances with user accounts that would access all the federated communities. This would build a lot of resilience into the network so that if any community instance goes down, its cached on the identity instances and not require them to be online all the time and the hardening would need to be on the identity instances. This is I think never going to happen, so I probably will host a few more communities on my new site