No, that is not and has never been the actual requirement.
5 Likes
Manual acceptance would be a great idea to re implement however it just isn’t viable anymore due to the sheer influx of developers that would like to access the forum.
We’ll be here until the rapture occurs by the time developers get manually processed.
I do however, understand your concerns with the professionalism of the forum and I fundamentally challenge the current flawed automated system. I believe a more rigorous structure and process is needed to prove commitment. Some of my ideas include this:
- A question which tests your knowledge and relating to building, scripting graphics etc. You will be given a question related to the aspect of development you have ticked in a ‘tick box system beforehand’. This would have a criteria that checks if the answer has been questioned and marks your work out of 10. I understand this alone would take a while for Roblox to implement however in the long run it would allow for the automated system to coincide with a competitive but committed forum of developers.
Concluding my comment, I can understand your frustrations however I don’t think a reversal back to the manual checks are the right path.
Thank you.
My main point for your statement is not Post Approval was removed, axed, or whatever words you may describe in the dissolution of a certain team, my main point in why I’m discussing and arguing is that based on your point, that the Developer Engagement Team’s plan in removing Post Approval was a bad idea, which caused me to respond why it wasn’t a bad idea in the first place.
We can’t deny the fact that Members would reply on #development-discussion categories and the #updates:announcements categories, unless they’ve installed a solution to that problem, nobody is perfect, and we can’t avoid people posting in the topics at the first place. We can’t just also close down the ability for Members to reply on that certain category, the category and threads there would be useless as some Members also wanted to contribute something to the thread, but are unable to reply.
We cannot under no circumstance, rely on the new Post Approval process to be installed even in posting replies, I’d honestly, think that topics should go through Post Approval, however, creating posts for a topic, and bringing it through the Post Approval process is not really a bright decision, considering the fact, that we can’t really presume this new process would be done either automated or via another team conducted manually by people.
If this would be done through people, then this would just bring back the issue where there would be additional work for the new team to do, what’s worst is that this forum is getting bigger and bigger, and more people post in topics that require Post Approval. I also don’t believe a new automated system would magically approve posts and have the same human understanding in post approving.
In general, applying Post Approval for replies is a horrible idea, and this is why there’s already a flagging system for the issue.
The flag system is ineffective because it takes too long for a community flag to be responded to by the devrel team. With such high volume of replies from members, it would mean that by the time the devrel team is able to respond to the flags, the damage has already been done (in the form of lost productivity, lost discussion, etc).
The only functional parts of the devforums are the help sections. Aside from those, I don’t see why members should be entitled to posting permissions on somewhere like Development Discussion. Nothing that is discussed in Development Discussion is essential to any developer.
Here’s what they need to do:
Lock down topics and replies for Development Discussion. Reinstate Post Approval and the automatic member-to-regular rank up system. Problems solved.
There’s no way around it: the devforums are simply NOT FUNCTIONAL without some form of Post Approval. Development Discussion is a total disaster through and through, and practically everyone agrees with this assessment. We NEED some way to filter and restrict who can post what, otherwise all is lost. If Post Approval cannot be figured out, then we might as well just discard the entirety of the devforums as a failure.
Patience is the key to success, it’s better to always be patient rather than ranting that the flag system is ineffective due to the long response of the moderator team. As long as the post has been flagged, it’s better to not reply on it, I don’t see why it’s a problem to you considering the fact that the community has flagged it and the post has a higher chance of being taken down.
Even though the response for the flagged post to be deleted could be taken long, you could just browse other topics in that category rather than focusing on the ones already hidden due to community flags.
Until the new process comes along, our temporary solution to our situation is to flag irrelevant or off-category topics.
If you’ve read my earlier statement, closing down #development-discussion made it look like you completely destroyed the use of a category. What’s the point of Members being able to see threads there, if they can’t reply, or create topics. Closing it down completely should not be an option, closing the ability for creating topics temporarily at #development-discussion is a more suitable solution rather than closing down the entire category.
Regulars already have #lounge, and we don’t need #development-discussion to be Regular-only, sure I agree they make Regulars to have the ability to make the topics in #development-discussion, but closing down replies for Members would just lose the purpose of the category being made in the first place.
Remember, not all Members who reply at #development-discussion create trash posts, some also have contributive replies about what the thread was talking about.
The only main issue about #development-discussion is the trash topics, not the posts.
There’s no point in ranting that there’s no Post Approval for the forum, we can only be patient until the Developer Engagement Team, could find a solution or replacement for Post Approval, we can’t expect they’re doing nothing about it.
I agree with this, this is why I no longer use the forum, however manual approval isn’t scalable/possible. Here’s a topic which I made which explains why it’s not scalable.
This is not possible people can copy showcases and it’s impossible to tell if it’s copied.
What? How does not knowing what a local variable make you a troller/spammer. Not everyone who enters this forum is a scripter or has to know everything about scripting. People shouldn’t be excluded from the forum for not knowing something about development since some people come here to learn.
Currently, I don’t really have a good solution for this, and it’s pretty hard to stop this (also why the official Roblox forums fell (spammers). But the thing you’re proposing is NOT the way to go.
3 Likes
I’m sorry, but do we really want people in here that have zero development knowledge? At least have them make basic things from the DevHub.
Simple fix: make it a Studio screenshot that has their username in the corner of Studio. Probably can be edited but definitely a lot harder.
Sorry for using an anecdote, I also included the DevEx anecdote.
Yes, I do. How can someone learn without being taught?
8 Likes
There’s so many other resources to make your first steps with, including this forum (read-only). All of the basic questions have been answered either here or developer.roblox.com, so it’s just going to be full of duplicate topics.
By copying showcases I literally mean copying someone’s builds using exploits (synpase:saveInstance()) and pasting it in studio. Or using an uncopylocked place and using that for your showcase.
1 Like
Yes, I mean real people checking it. A staff member cannot tell if a showcase is copied because they would need to search every game on Roblox to see if it’s not copied, O(n) searches at the worst case. This post sums it up better than I do (the same concept applies to searching games).
https://gyazo.com/1609460853e73fc21ea9bc37f13a87b3
I mean, this would definitely be possible, but this not only stops (some) trolls and spammers, but it definitely stops the underage users that won’t know to do this.
Maybe there would be some automatic post that has the screenshots they submitted to get in, and the community could flag if they stole them with evidence.
All this is doing though is scaling up the resources basically adding extra people to check if it’s a copy. However, the number of people will still be too low to check if a game is a copy.
Let’s say we have 100 people who saw that screenshot, most of them wouldn’t really search as vigorously as an actual staff member. Let’s say they do a search vigorously, and since there are about 40 million games on Roblox each person would still have to search 400,000 games at worst case (not to mention people overlapping their searches).
Remember this is only with games, people could just drop a whole free model and call it their showcase (we would also need to search free models now).
Also, this is only with building, how would we search if a scripter is using scripts from the other game or scripts from the toolbox? Many people use the same method to make a simple lazer on Roblox does that mean they copied if a similar script is found?
Scripting and building won’t be the only things we would need to check. Being a game translator, game tester, animator, compositor, animator, and UI designer can still be considered development
It stops some people but not enough to justify resources being spent on this. Also, people don’t even have to exploit to do this, if you search up uncopylocked games on roblox their’s a lot of games that show up.
My point was the person might steal the build/script from someone on the DevForum, so it will catch them.
Wait.
It just hit me, the UGC applications required a video of them doing their work.
Why can’t we do the same thing?
What if someone made a obby laser and a similar script was found on the forum does that make them a copy? There isn’t a lot of ways you can make an obby laser.
Scripting/building isn’t the only things we need to check. We also need to check people who are game testers, game translators, UI designers, animators, and compositors.
That’s because the UGC program requires a certain level of skill, and the thing you’re proposing is saying you need to do at least something.
I can record myself placing a brick down and be accepted into the UGC program.
For scripting, I could just type what the default script says print(“Hello wld”) and record it and get accepted into the forum.
Unless if you’re making it so only a certain range of scripters can come here by making a minimum requirement for their showcase, this won’t work out.
UGC is supposed to be a special program, the forum is more like a public resource where we can post our questions, which is why this type of test doesn’t work.
Sadly, you can’t simply materialize all of the manpower required to moderate acceptance for new members. It is a simple yet unbreakable fact. Any discussion on this topic is futile.
5 Likes
That process is unscalable and infeasible for as large a platform as the devforum. There’s a reason applications were removed in 2019; it was impractical to continue doing so. You’re proposing even more infeasible “solutions” to the problems that were resolved almost 2 years ago.
2 Likes
Results
Community consensus was to have automatic acceptance change.
Interested to see what requests happen next.
3 Likes
When the DevForum was manually selected, only the very top developers were granted in. The purpose of the DevForum is to help developers with problems and issues they have. The chances of the top developers having the same type of issues as newer developers are pretty slim.