Removing Replies on Recruitment Topics

Howdy there… again.

Some of you may remember my original post on the recruitment category, suggesting adding post-approval. That has since been thoroughly debated to a point that if Thomas has to say it’ll never happen one more time his head may explode. As such, I wanted to create another suggestion that has been slightly touched on, but I’d like to hear a more focused debate on: removing the ability to reply from recruitment topics. There are, as always, three principal reasons why: the state of the category right now, the redundancy of being able to reply to a topic, and the flagging system to take down bad posts.

First of all, the current state of #collaboration:recruitment is, by far and away, unacceptable. Most of the community agrees that something has to be done about the current state of the category. To quickly summarize the issues without going into too much detail, many threads that are created in the category fail to meet the guidelines/bare minimum outlined in the topic template, replies to threads are often ending up causing large fights in public forums, and many people are responding to topics that they simply don’t need to respond to. If you look at almost any recruitment topic, you will find one of those three issues with it. The result has been the emergence and/or proliferation of requests to add post-approval to recruitment(wonder who started that), mini-modding, and spam-flagging. This is a pain for moderators, community reps, recruiters, developers, and visitors to the forum. While I still believe that adding post-approval would be far more effective than removing replies, removing replies does solve the issues of mini-modding, fights in public forums, and redundant replies.

Second, replies are redundant to topics for recruitment, since(if people ever followed the template) one of the bare-minimum requirements is a method of contacting the author. Replying to a topic is just another way of communication with the author; the DevForum provides the ability to message, uncensored, another user directly. Most recruitment threads(though granted, not all) provide another method on top of the DevForum for contact, whether it be email, discord, twitter, or even an application. All this is pointing to the fact that replying to a topic isn’t necessary at all. We aren’t moderators, so pointing out flaws or calling out an author for their “sketchy schemes” isn’t our job, at least publicly. If we have an issue with a post, we can message the author privately about it, and hopefully provide constructive criticism that they are receptive to. If the OP is offering another method of communication, almost all of the aforementioned methods are more efficient than the DevForum, either through quickness or the frequency the author checks them. I know for myself at least I check discord far more often than the responses to my DevForum posts. While my experiences aren’t representative of the whole, I still feel that because of the ease of other methods of communication and the fact that there is nothing you could post publicly in a reply that couldn’t also be sent via a direct message, replies to recruitment topics are utterly redundant, and just don’t need to be there.

Finally, for posts that do break the rules, it is always better to flag it than to make a public spectacle out of it. I don’t need to tell anyone who pays attention to Forum Feedback topics how many times the staff and community reps are repeating this to us. I’m sure some of us have noticed that a certain Orthinian Studios has been recruiting across six or seven accounts with almost the same post, and through the use of flagging them, they have all been taken down within 24 hours. This is proof that the flagging system works, meaning there is no reason why we need to take moderation into our own hands. Let the guys who are representing the DevForum take care of it. If you want to send a message to the author, it even has that option. There is no reason why you should need to reply publicly to a post to point out the author’s failures. Simply flag it, write a report, and they will be taken care of.

I know that by removing replies to one of the busiest channels in the forum, we are losing a great privilege. However, I cannot think of a single constructive, positive reason why we should have this privilege at all. It isn’t an end-all solution to the problems of #collaboration:recruitment, but it will ease the current situation.

Happy trails, and stay safe,
CaptLincoln

13 Likes

The funny thing is, I’ve been seeing a lot of recruitment threads lately and I tend to DM almost exclusively now. After going through the previous discussion you mentioned, I started feeling like the public replies to a recruitment topic doesn’t really provide anything.

That being said, vouches by other developers for support of an individual or group is still important if you are looking to portray some credibility. And perhaps we don’t see as many vouches as we see low-quality replies, but I would assume that it would take away from the quality of recruitment topics in general. Although a simple reference section can replace vouching. Maybe it’s not so bad then.

I think I like this a lot more than having the category as a Post Approval monitored one. If people want to argue in DMs about pricing then I guess they will be forced to do so in DMs rather than spamming the reply button. This also gets rid of the “mini-mod” issue discussed last week :slight_smile:

In a way though, we are kind of turning recruitment into a private bulletin board.

3 Likes

If a developer wants to support another’s project, they can like the post. It’s actually stated in the category guidelines to do so. Maybe an author can include their own references for credibility in the OP instead of having them add replies. Theres many ways to get around the support issue. Yes, recruitment will become a private bulletin board, but honestly I think that’s better to what we currently have.

1 Like

In the about for recruitment,

Please do not start lengthy discussions in this category. You should only reply to topics when you are interested in the opportunity being offered.

Lengthy discussions are happening all the time. Locking them like bulletin board is the best choice.

1 Like

I totally agree. The #collaboration category is a mess, and the only replies I usually see are one of the following 3:

looks good, might hire you

your work is bad, get more experience

OMG HE USED FREE MODELS BAN HIM

These examples are exaggerated.

However, since Regulars are more trusted users of the forum, perhaps we could limit replies to Regulars only?

They already have their own private section that we members cannot access. I think removing the entire category and leaving the private one for Regular members is not going to bode well with many people, especially those that actually use Recruitment properly. Besides, what is the point of replying if all you are doing is asking questions or giving a discord handle? That can easily be done in a private message, and it shouldn’t really make a difference if you are a member or a regular at that point, either. Like others have said, there’s really no benefit in replying publicly.

2 Likes

I fully agree. A certain studio that has been named in your group are using 6-8 alt accounts to get more people to be interested. Not only that, but they try to get people interested by repying to their own posts saying: “Yooo, any one inrsted? U gys nede to emmm” and such, completely messing up this forum or as you like it, category.
Going on to the title, removing replies such as spam, personal attacks, or abusive comments are 100% the way to go.

I made the mistake once, of pointing a scammer out in a public post, saying:
Would not recommend this guy, he doesnt pay”. Mhm, big mistake. I thought I was doing a favour to everyone, but then a day later, @Sailor_Bea gave me a PM saying the post was removed since it broke a rule.

I stopped doing that straight away - instead, I just flagged the post for moderation, and hey! No rule breaking for me! Instead, they accepted the flag and the post got removed.

To anyone reading this - always remove them or flag them, don’t reply to those who try bring you down :wink:

2 Likes

Going to bump this since I feel this is still relevant right now, perhaps more then ever.

However I also wish to offer an alternate solution, only locking replies to members, why? I personally don’t feel regulars contribute to the problem at all currently, and even if there is one less then preferable reply, other regulars will most likely know to have the decency to not start a fully fledged argument publicly.

I find the recruitment catagory is the root of crappy posts and rule breaking on the forum, roots we need to pull up.

1 Like

So prevent regulars from replying but allow members??? Is this a typo?

A lot of members use #collaboration:recruitment. In fact I don’t often see regulars as much on there anyways. I think the proposed solution (making them locked instantly like #bulletin-board) would be better as you can always discuss in DMs. And 99.99999999999% of the posts on there include a Discord tag so talks are also brought there as well.

Only locking replies to members, means as stated. That you only lock members from replying, if it’s another typo your referring to then my bad, but I think my message is obvious.

The only reason for my suggestion is ilas I said I don’t feel regulars contribute to the problem at all, therefor should be able to keep posting

Oh my bad. I misunderstood and misread it. I interpreted it as “prevent regulars from replying, but allow members to reply” and “regulars contribute to the problem”. I didn’t notice the “not” somehow. that is what you get when your native language isn’t english

1 Like

Alright so just got finished reading through another entire argument + flagging it, these are actually very unreasonably common.

You get people complaining about pay, use of free models, or taking personal business into a public topic instead of continuing it in a DM. I honestly can’t think of any type of discussion that should go on publicly on there so I still support this request.

Topics can be closed but only replied to by the OP like #bulletin-board.

Suggest this for #collaboration:portfolios as well.

(sorry for accidentally bumping with an unfinished reply lol, finally done)

Once more, toxicity in #collaboration.




image

This type of behavior seriously makes the forum look unprofessional, especially considering #collaboration is a public category you can view even while logged out.

You know how one of the pinned PSA’s say this.

image

Every single bullet point was broken, as well as these:

image

Please, remove replies.

3 Likes

Well this is getting worse I already saw three topics like this, in two weeks.

Well I feel like collaboration channel should just be removed from the forum it’s a really trick business and brings a whole lot of issues such as scamming. Probably why investing got removed to, but now we have the same problem with other roles being hired.

Collaboration is really shady usually and people have a lot of misinterpretations of the agreement. A lot of people here are under 18 and don’t want to be involved in legal issues.

1 Like