Proposal to create a collective to own the topic-based Lemmy instances
Proposal to create a collective to own the topic-based Lemmy instances
I have a number of Lemmy instances meant for discussion groups around specific topics. They are not being as used as I expected/hoped. I would like to set them up in a way that they can be owned by a consortium of different admins so that they are collectively owned. My only requirement: these instances should remain closed for registrations and used only to create communities.
You're viewing a single thread.
ITT: People who don't understand IAM or how to build a healthy federated structure. There should be identity services and instances just to host content separately. This way a spammer from a service won't de-federate content from everyone else and there could be easier moderation splitting the task between users and the comms.
lol I think you are right about this. You'll never get these lemmitors to see it i guess.
there could be easier moderation splitting the task between users and the comms.
On the other hand, for some communities moderation of the communities and the members are specific and should not be generalized.
Beehaw is an example that comes to mind, lemmy.ml as well
Even though the community is contained the cloud resources should still be split in two between identity and operations to be in alignment with all the industry best practices and potential for scalability. Remember the unix philosophy is do one thing well.
Beehaw should operate their own Beehaw fediverse IDP (Identity provider) for the users to sign in with, that would manage their tos agreements, privacy policies and user based security. Separately they should operate their Lemmy server which hosts pictures and links organized by communities. They could just use a single IDP for their instance and have the same experience as now only better with better architecture.
Source: I am a cloud services architect.
I'm familiar with IAM concepts, and indeed having a separate IdP and content instances would be a better architecture.
However the reality is that the platforms (Lemmy, Mbin, Piefed) are being developed by very small teams (Piefed is a 2 or 3 people team, and Lemmy might be around 5).
Lemmy is focusing on features delivery (https://join-lemmy.org/news/2024-09-11_-_New_NLnet_funding_for_Lemmy), which could help the platform grow more than a new IAM architecture.
There will probably be a point in time where performance will require a rework, but at the moment, it does not seem to be a priority
But nothing needs to be done to meet this OPs desires for community only instances that are well federated with other instances (IE at least one user is subscribed to each community on each instance). This way those admins just manage those communities and Beehaw and Lemmy.ml can run their combined servers.
The users and the subscribed to communities cause nearly all the load on the servers too, it is a way to keep costs down.
Who would manage all of those community instances?
The current setup works well with the limited number of admins and mods we have overall. I'm regularly looking for mods on communities I mod, there isn't so many of them (e.g. !showsandmovies@lemm.ee )
Also, with the federation currently being broken, mods would need to have an account on each community to be able to get the reports: https://github.com/LemmyNet/lemmy/issues/4744
Regarding costs, the cost of these community instances suggested by OP is around 6500€ per year, so 540€ per month (https://lemmy.world/comment/12595221)
It currently costs 80€ per month to host lemmy.ml, which is the 4th most active instance with 2300 monthly active users
I mean that is what is is asking, he is looking for a team of people to manage the instances in this post. That is what this post is about, he is looking for a team of people to run them as admins while maintaining his (imo correct) vision for how it should be structured.
I forgot to mention the biggest fact- the users are where all the risk are. If people are just posting pictures to your instance of communities you have minimized risk as you can just gatekeep what is posted. Once you allow users in who can then post on other federated communities you take on a lot more risk.