<@U3G2M6LFM> makes a fair point as well regarding ...

# meta

[Zac Sweers]

@okarm makes a fair point as well regarding it being a self-perpetuating cycle. We have people here that are helpers and will go in and reward these kinds of questions too, which creates a positive (but possibly problematic) feedback loop. Same problem happens on r/androiddev - sub rules don't allow dedicates submissions for tech support questions, but there's still a handful of people that will help anyway if someone ignores that rule. I don't think there's an easy way to solve that on kotlin-lang (what are you gonna do - tell them to stop being helpful?), but you can probably find some pathways that lead to community self-moderation via dedicated channels.

I.e. - In a world where you want non-kotlin live SO questions, maybe the question isn't "should we have an android-random channel because one dude was angry that someone shut down his non-kotlin request" and instead be "should we have a dedicated android-eng-questions channel?". I'd be willing to bet that if the latter existed and was well broadcasted, the existing android channel would probably fair better and naturally start bouncing people to there.

Another idea, if you want to keep android focused on kotlin, maybe rename it to kotlin-on-android or something. Similarly could create a structure that similar channels follow (kotlin-on-spring, etc). Just spitballing.

My 2c are that kotlin-lang should be kotlin focused and not just be a gravy train for those wanting a free comp'd slack instance for misc other tangentially related stuff, but it requires more active admin than can probably be resourced right now. There will also be people that rage against any perceived crack down on this, which is probably more grief than anyone at JB wants to deal with.