UPDATE: This seems to have been reverted as the reply button no longer appears.
bug report
I’m not sure if this would be classified as a bug but I believe it is due to it’s unnatural state.
For context, I’m TL1 (Member).
Usually, both topic creation and post creation in #feature-requests are only for TL2+ (Regular and higher). However, recently (about 16 minutes ago) the “reply” button appeared for TL1 users in #feature-requests:website-features but for no other subcategory in #feature-requests.
(Resized my browser so I could capture everything without having to scroll too much)
This change (if it’s intentional) can create a negative forum experience with people misusing the category and the reply feature (which has just occurred as pointed out by incapaz).
This should be reverted ASAP, users are already admitting to being under 13, admitting to being non-developers, and misusing the category for appealing account bans as well as bumping feature requests with no new information.
Apologies for any inconvenience and thanks for the catch. There’s a problem with a Discourse plugin we are using where it is not correctly populating all of the category settings on the admin UI, and then it defaults those settings once we save it, which happened to include the “restricted replies” section. I’ve fixed it now for all the categories.
Will file a bug report with the maintainer of the plugin.
