This is something we’ve gone over a number of times in threads related to the removal of Community Post Approval. If you’d like a summary:
Does not scale well. PA is a manual process and we had to sort through hundreds of messages every now and again. Largest backlog I’ve helped handle is 500+ messages.
Mentally exhausting. There was no quota to fulfill and if we weren’t constantly on the ball, then the inbox would fill right up and we’d have to go through all those requests sooner or later. CPA was comprised of volunteers. We don’t get paid to go through that inbox, we do it because we wanted to.
It’s better if paid staff handle these kinds of processes while encouraging us developers to focus on our own development and activities, not to cast away several hours digging through that inbox. Topping it off with impatience and negative language both on and off the forum for not going through the inbox made those hourly trade offs not too worth it.
There was enough wrong with PA. Change was requested and we volunteers followed up on our end. Developer Relations has not.
For your specific concern, please check out other threads discussing the removal of post approval and related responses about the mental burden it placed upon us.
tl1 users shouldn’t be able to do it on their own as it would result in chaos. The lack of communication from devrel is severely disheartening but there is still hope that we will get any response from them.
Good concept, bad attempt to fix it. You make it seem like everyone who is Regular are “entitled” and anyone who faces your post is “evil”, but that’s not true. Yes, they should be open but fighting like my parents (lol) isn’t really gonna fix it.
Regulars don’t use PA (Post Approval, which is gone) when they rank up. They also get access to #lounge.
Let’s say you look at someone’s rank and sees that it is Regular. They will think, “Oh, so that must mean they did a lot of contributions,” since to rank up to Regular, you needed to use PA a lot. It doesn’t matter about stats. Everybody gets this wrong for some reason.
It used to work like this. There was a major spam issue in the category, which is a big issue since the category is meant to be a resource to Roblox engineers and product to give a slice of what the developer community and userbase want from the platform.