When a user lives within an instance, the user is only capable of creating a community in that instance.
My original thought process was the following:
I want to set up an instance in which the focus is nature and science, and so people that share the same interest can join in. However, I do not want to set limits on the types of communities that can be created, because I also want users to be able to build communities about their other interests without needing to be searching for another more appropriate instance.
However, after reading comments from a few users, I have considered a different perspective too. Users that join into this instance may appreciate being able to browse specifically content about science and nature when sorting through "Local", and diluting this content with off-topic communities can worsen that experience. By setting a tighter boundary on the types of communities that are created, we may be able to provide a better "Local" experience for the average user.
So - I would like to hear from you.
Would it be worth restricting the topics of allowable communities, even if that means that some users will need to hop in between instances to create their communities?
If yes, than how should the boundaries be drawn?
Some cases are easy to define. A sports-betting community is certainly off-topic, and a Nature Sketching community certainly on-topic.
But what about a community about "Sensors"? One can argue sensors fall into 'engineering' and not necessarily 'science', but I still think that there is significant enough overlap. So, if anyone has some good tips on how to define the boundaries, please let me know.
Of course, even the boundaries can be 'soft', and common sense can be used, but I think users would appreciate knowing what to expect.