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.
I personally am not a huge fan of this idea. Instances are at the end of the day communities of their own in a way. One community may want to discuss a topic in one way and another community may want to discuss it in another way. This seems to be a way to centralize all discussion around a topic in one community, but we should rather go for decentralized communities.
But hey that’s just my opinion, if others like it, go for it.
You are running an instance that is geared to serve people of an specific region. And I agree that they kind stay between the two extremes of the “group-focused” and “people-focused” instances.
The idea of topic-based instances are for the cases where the culture is more-or-less universal, but it doesn’t mean that they should be absolute. So, if you want to talk about Apple stuff in general, !apple@hardware.watch would make more sense, but if you are trying to reach a group of Apple users in your area, then you can have a community on your local instance as well.
for the cases where the culture is more-or-less universal
When is this ever true? The idea of a “universal culture” is exactly what I mean with this encouraging centralization. Even a specific community (subreddit) on a centralized service like Reddit will have a specific culture that is not in line with any “universal culture” (it’s likely to be skewed towards whatever culture exists in western english-speaking countries, just to mention an example).
I don’t mean universal in the sense of “totalitarian”, I mean it in the sense of “large common denominator”.
Do you think that the conversation around, e.g, python programming or wood turning techniques will vary so much that it warrants many specific flavors?
it’s likely to be skewed towards whatever culture exists in western english-speaking countries
This is good enough for most people and does not hinder the ability of those that are in the minority to create a different/specialized community.
Centralization/decentralization is a spectrum. No one is proposing to force everyone into a single box. The idea is only to combine efforts for the things that exist in common and to avoid unnecessary redundancies.
Community collections should be a thing. Something like /cc/Technology could pull in lemmy.world/ other instances and collections of communities. It makes it easier if one instance dies, an instance de-federates itself, or just wanting to consolidate all the different /c/Technology communities across instances.
It would also be nice if communities had the option to vote on their admins once in a while. Having individuals lord over different communities is a problem in reddit.
Multi communities have been funded: https://join-lemmy.org/news/2024-09-11_-_New_NLnet_funding_for_Lemmy
Excellent! Thanks. Ill take a look at it sometime. https://github.com/LemmyNet/lemmy/issues/818
Last time I checked, there was still discussion on how people want this to work. Because its easy to say, but hard to get everyone to agree.
Yeah I remember asking about it cause it was a feature that existed on Kbin https://github.com/MbinOrg/mbin/issues/486
I even created a dedicated thread on !fedigrow@lemm.ee:
https://kbin.melroy.org/m/fedigrow@lemm.ee/t/426059/Feature-tracking-Multicommunities-multimagazines#comments
That’s an argument that is:
- application specific
- agency-removing (only Lemmy devs can do something about)
- orthogonal to the stated problem
I think this sounds like a good idea. A problem when starting a community is that one wants to find a stable home; it might make sense to set up camp at, say, hardware.watch, but without knowing who operates it it might feel more uncertain than lemmy.world.
And then, as a result, if lemmy.world ever disappears or has problems, it’ll take way too many communities with it.
If these topic-specific instances had some sort of collective ownership, I guess we could more effectively guarantee for their continued survival, and it might be more tempting for existing communities to move over there.
I’d be interested in hearing the thoughts of some admins - would !football@lemmy.world be interested in moving to !football@soccer.forum, given the right organization?
And a piece of constructive feedback: Vague community names like !main@soccer.forum is probably less likely to attract attention than something specific like !nba@nba.space - when searching for a community, people look up the community name rather than the domain.
I’d be interested in hearing the thoughts of some admins - would !football@lemmy.world be interested in moving to
!football@soccer.forum, given the right organization?
I’m not the main mod of !football@lemmy.world so it’s really not my decision to make, but moving the community to a domain with the word soccer in it is a tough pill to swallow. As silly as it may sound, there’s a lot of people that don’t like having football referred to as soccer.
Moving away from lemmy.world and their annoying VPN restrictions would be nice though.
moving the community to a domain with the word soccer in it is a tough pill to swallow. As silly as it may sound, there’s a lot of people that don’t like having football referred to as soccer.
Sounds silly indeed, but I agree (https://feddit.org/comment/2048090 )
I had a feeling that would be an issue!
On the one hand, football@soccer would be a good compromise.
On the other, we’re right, the Americans are wrong. Simple as that. So I sympathise with the lack of willingness to compromise on the matter.
Americans are wrong
Don’t forget Australia, NZ, S Africa, and a few other places like Japan.
Feel free to register a football domain. I will host it for you, free of charge.
As I’m sure my home instance reveals, I do like the idea of focused instances. I think a general sports focused instance would be better than sport specific instances though, at least with lemmy’s current size. It’s not sustainable to pop up an instance for every sport out there, like strongman or arm wrestling.
And people would also have to be able to sign up to the instance. Which if I remember correctly you had a very different opinion on when you spoke to Snowe on !meta@programming.dev about programming.dev. Just from a technical standpoint, the federation latency and general wonkiness is real and is why my football bots are running on Lemmy.world despite programming.dev being my preferred instance. Near real-time communication is important during live games where minutes may drastically change the topic.
And while I’m sympathetic to your cause, inertia is a real thing and lemmy.world is competently run, even if I strongly disagree with their VPN restriction.
If you somehow managed to convince the other sports communities to migrate to a common instance I’d happily follow along though, but I find it very unlikely happen. ReadyUser31@lemmy.world is the one primarily in charge of !football@lemmy.world
New users to lemmy usually aren’t going to join communities if they can’t register there. And people who are really invested in a topic will want to have that domain for their account. You’re cutting off a lot of the users that would grow your communities.
I don’t mind the idea of a collective to handle a bunch of instances, but I feel like you’re going about it the wrong way. When the same person make a bunch of instances about a variety of topics, it looks as if they aren’t that invested in any specific community. From my experience, the most active communities start off with a few people who care almost obsessively about that topic.
Also the idea that communities can be ‘neutral ground’ doesn’t make sense to me. People will leave or join based on how the admins and mods run them, whether or not the users are hosted there. In some situations it might work out fine, but if anyone thinks it’s caused by how you’re running your sites, they may defederate from the whole collection.
aren’t going to join communities if they can’t register there.
Why?! The whole point of federation is to let people join communities even when they don’t have an account in the same server.
the most active communities start off with a few people who care almost obsessively about that topic.
There are two different, orthogonal issues here:
- people that are looking for a community in a niche interest, do not find it, and go back to Reddit.
- people that are in a big instance and create (or sometimes, recreate) a community for a popular topic. This happens quite often and not because they were not satisfied with the existing communities, but just because they could not find them.
The idea of having topic-specific instances is an attempt to mitigate issue #2.
People will leave or join based on how the admins and mods run them, whether or not the users are hosted there.
Not my experience. A few examples:
- No one complained about the mods from !linux@lemmy.ml, yet I’ve witnessed endless discussions about moving away from lemmy.ml.
- Beehaw defederated from LW, so this forced users of these instances to “choose” between the communities and/or create accounts on both of them if they wanted to keep following the whole conversation.
- Personally, I do not want to join or participate extensively in communities that are on LW if we have a topic-specific instance for it. I know that I am not the only one.
Why?! The whole point of federation is to let people join communities even when they don’t have an account in the same server.
For people who’ve used lemmy or the rest of the fediverse yes, but most people don’t know that yet. If someone shares a post from your site with their friends or a facebook group, they’re not going to look into how lemmy works to sign up elsewhere.
- people that are looking for a community in a niche interest, do not find it, and go back to Reddit.
- people that are in a big instance and create (or sometimes, recreate) a community for a popular topic. This happens quite often and not because they were not satisfied with the existing communities, but just because they could not find them.
The idea of having topic-specific instances is an attempt to mitigate issue #2.
I’d prefer it if topic specific instances were more popular too. I just think that letting people making accounts tied to their favorite topics would get more people interested in joining them.
I feel a technical solution like federation pulling in lists of communities with would help more with discoverability.
Not my experience. A few examples:
- No one complained about the mods from !linux@lemmy.ml, yet I’ve witnessed endless discussions about moving away from lemmy.ml.
I’m not sure how that goes against what I said. That’s mostly people disliking the admins.
- Beehaw defederated from LW, so this forced users of these instances to “choose” between the communities and/or create accounts on both of them if they wanted to keep following the whole conversation.
Similar issues could happen even if users are separate from the communities. Beehaw could defederate your instances, and lemmy world could defederate programming dev or something, and people would need other accounts if they want to see everything.
- Personally, I do not want to join or participate extensively in communities that are on LW if we have a topic-specific instance for it. I know that I am not the only one.
Me too. I usually avoid lemmy world communities unless there isn’t an active community elsewhere.
I just think that letting people making accounts tied to their favorite topics would get more people interested in joining them.
Could be, but I guess we now just arguing opinions. And given that I am personally hold the opposite view and I don’t want to be be identified by my interests, I am not going to push for something that I fundamentally disagree with.
I think there may be a challenge or challenges that you haven’t pinned down yet. First is: what problem does this solve?
Second is, how will people know that they are housed under the same roof, so to speak? A small instance dedicated to NBA basketball may be interesting, but if it seems disconnected then people would be wary. Small specialty instances can be shut down without warning for all sort if reasons.A consortium of instances may help with this issue, as long as it is immediately clear through common branding that they are part if the same group.
Third is that different communities have different needs.
Also, if we assume that the entire idea is to have more than one admin, then what change does that actually include?
You now have 3-4 people that can go and randomly delete the whole server instead of 1? Do you know that right now, only 1 person has the credentials to the admin account of whatever server you’re talking about?
