The #development-discussion channel has become extremely controversial (mainly with new members) and many users are complaining about how it’s become extremely off-topic/spammy.
My idea would be to a manual review like #collaboration:recruitment does. This would regulate duplicate posts a lot and it would solve the spammy posts and conflict in #forum-feedback.
If Roblox is able to address this issue, it would improve my experience using the forum so there would be fewer arguments in #forum-feedback and it would reduce the duplicate posts and useless posts.
This would also allow all users to post discussions without anybody being affected.
#collaboration:recruitment doesn’t have a manual review though? I would support turning on moderator approval for topics though, Discourse supports this natively.
Most likely just tl1 users, considering tl2 users generally have more experience using the forum and being able to use it correctly without need of much help
New members just need to learn how the basic rules of the forum like not reply with things like: “thanks” and just likeing the post instead I think people are being very sensitive about this and I do not think it needs any attention. I have never seen any actual spam in the forum it is regularly moderated. I think integrating this with the initialization tutorial would be good though.
All I am saying is that flagging repetitive posts does not take much work. I think people are overexaggerating the severity of this. I am a relative new member to the forum and I don’t think that the new members are allowed to skip the tutorial to become a member.
No, you are able to skip it for some reason. Might be a good idea to ask meta.discourse.org to require it before promotion.
And flagging doesn’t work at large scale. It works for getting rid of individual topics, but it doesn’t fix the problem of users not thinking their topics through before posting, or users posting just for the sake of posting to farm stats, which is the problem.
As-is, you can literally type “skip” 10 times and get the badge. It would require serious refactoring to get it to the point where it makes sense to require it.