Tagging moderators @MonkCanatella@sh.itjust.works and @Ategon@programming.dev.
Would you be open to closing one community and consolidating to the remaining one?
I've also found a redditor who might be interested in helping out.
this post was submitted on 17 Feb 2025
19 points (100.0% liked)
Fedigrow
913 readers
31 users here now
To discuss how to grow and manage communities / magazines on Lemmy, Mbin, Piefed and Sublinks
Resources:
- https://lemmy-federate.com/ to federate your community to a lot of instances
- !fedibridge@lemmy.dbzer0.com to organize overall fediverse growth
- !reddit@lemmy.world to keep tabs on where new users might come from :)
founded 10 months ago
MODERATORS
We typically dont close communities on programming.dev since then theres only one option for things
Ends up having things like people who use the community no longer being able to access the content and being difficult for the community to move off of it if something happens
e.g. beehaw.org is defederated from sh.itjust.works so any beehaw users wouldnt be able to use the community if the programming.dev one is closed
Thanks for the reply! I have a few thoughts.
We typically dont close communities on programming.dev since then theres only one option for things
While multiple options have their advantages, they can also be a source of confusion, especially for new users. I don't think that AutoHotKey has sufficient popularity (or controversy) to warrant more than one community at this time.
Ends up having things like people who use the community no longer being able to access the content and being difficult for the community to move off of it if something happens
Not sure I entirely understand. The original content would still be there, and the community could be reopened if the need arose. Would you be able to clarify what you mean?
e.g. beehaw.org is defederated from sh.itjust.works so any beehaw users wouldnt be able to use the community if the programming.dev one is closed
I'm not sure that I find this example particularly convincing, given Beehaw's fairly aggressive approach to defederation (they defederated from lemmy.world). I assume that most Beehaw users either have alts on other instances or are comfortable with the fact that they are missing out on large portions of the fediverse. In any case, it doesn't look like there has been any activity from Beehaw users on !ahk@programming.dev so far.
Taking the above into consideration, would you reconsider closing the community?
Of course, all of your concerns would be moot if we decide to consolidate to programming.dev, but we'll need to see if @MonkCanatella@sh.itjust.works is open to that.
I think the advantages of multiple communities outweighs the advantages of consolidating. Especially since things can be cross posted between the multiple communities easily
No longer able to access the content is referring to the federation. And the difficult to move off is referring to for example communities that have been attempting to get traction to move off of lemmy.ml
Not posting in the community doesn't mean people there don't interact with it. I have beehaw as an example on hand but im sure there's other federation examples
I think its the kind of subject matter that fits programming.dev well and relying on outside instances for programming content with no mirror on our own site makes us too reliant on those other instances if anything happens in the future (e.g. extreme case but if that instance goes down. Lemmy handles it terribly since the community still exists as a ghost community with no federation but still viewable)
With similar logic we have a lot of the same communities as lemmy.ml communities including programmer_humor, opensource, etc. To give people an alternative spot to the lemmy.ml communities and so that we aren't overly reliant on other infrastructure we can't control within our instances subject matter