A word of caution: Lemmy has a serious number of bugs in its web front-end. A lot of "spinning forever" bugs instead of reporting errors, and other such issues.
I don't know how solid the backend is, but instances are crapping out on ~10,000ish users on smallish dedicated servers, suggesting severe bottlenecks in the code. Current discussion seems to suggest RAM bottlenecks and a lot of swapping.
Lemmy wasn't quite ready for the #RedditBlackout. But I think its still in a "workable enough" state to experiment with. Some communities (ex: Beehaw.org) are worried about growing faster than needed (human-side scaling, not machine side). Since Beehaw.org is trying to recruit specific kinds of people / posting patterns.
So I guess what I'm saying is... Lemmy tech stack is good enough for Beehaw.org. I dunno if its good enough for Lemmy.world (which is very "Reddit-like" in open enrollments / ease of community making).
I don't know how solid the backend is, but instances are crapping out on ~10,000ish users on smallish dedicated servers, suggesting severe bottlenecks in the code. Current discussion seems to suggest RAM bottlenecks and a lot of swapping.
Lemmy wasn't quite ready for the #RedditBlackout. But I think its still in a "workable enough" state to experiment with. Some communities (ex: Beehaw.org) are worried about growing faster than needed (human-side scaling, not machine side). Since Beehaw.org is trying to recruit specific kinds of people / posting patterns.
So I guess what I'm saying is... Lemmy tech stack is good enough for Beehaw.org. I dunno if its good enough for Lemmy.world (which is very "Reddit-like" in open enrollments / ease of community making).