Can we start giving out strikes for stupid uses of community resources

Forum Help
1

It has got to the point it is evident flagging posts is not helping solve the over riding issue, and it seems the quality of the community resources category is getting crappier by the day.

Now you ask, whats changed since the last post where you were on the breaking point?

Well now i’m broken, We are literally at the point, people are posting stuff they made in the category, without actually giving the thing they have made and / or saying they will release it in like a months time.

Now either they are utter morons or are simply abusing the system, its literally in the name fo the category ’ community resources’ that you need to give a resource for the community, like learn to read at least the category title.

Now, you can most likely tell from the title of the post that what I want at this point is rather radical, pretty much unheard of to this point, so im going to explain myself a bit.

So why do I not just propose a strike for misusing categories? Well in most cases, I can understand its an honest mistake, just a new user getting a bit confused / not realising. This is something I have personally done a few times before and can honestly happen to the anyone once or twice a year.

So what makes this different? Its hard to explain, but typically people misuse categories just out of mistake, however here it is evident the poster knows what the category for, hence why they are discussing their resource, yet they blatantly go against the category in the fact they don’t actually open source it.

The reason why I think this is such an issue?
The other day I talked to someone who did this very act, and they had a response that I honestly thought was very fair, it was along the lines of ‘Well if others do it, then why can’t I?’

Naturally I went with a response favoured by teachers of ‘If your friends were drinking poison would you drink with them?’, Yet still he did have a point, and one that scares me.

We are at the stage where it is now being deemed normal to break the category guidelines

I feel this helps prove my point further, normally people accidents break misuse guidelines, out of confusion or simply being new. But here we have people breaking rules, purely because everyone else is breaking rules.

Now this is what I deem unacceptable, and this is why, I believe a strike should be appropriate for anyone misusing categories which is obviously done deliberately.

I understand there will be conflict to this, and i’m happy for that to be expressed. Of course in an ideal scenario bringing back post approval is better, however it is evident that is not possible hence my more radical solution. Flagging has not worked, we need change.

48 Likes
2

I agree. It’s getting irritating to navigate through #resources:community-resources without having to see non-substantial topics. I’ve also seen a few unacceptable ones, very few with vulnerabilities built in to it, and some dealing with obfuscation, up to a point where I’m getting tired of hitting the flag button to flag these posts.

6 Likes
3

Strikes are a bit more difficult to handle because those can only be done by DevRel/DevEng; not Community Sages, which are the people who lock most of those threads. We have been discussing internally of making Community Resources require Post Approval again (see the 3 previous threads about this), but no guarantee this will happen.

Edit: Community Resources is not being moved back to Post Approval.

8 Likes
4

As stated at the end of my post, this solution is based on the assumption that community post approval will not be coming back any time soon, based on what I’ve found in the previous threads I’ve made about this. The reason for the radicalness of the solution is simply because of the reasoning behind this rule violations.

Would it be viable for sages to have the power to hand out strikes? I personally wouldn’t see the issue with that.

5

I agree, there are just people who find stupid glitches in games or Roblox in general, use free models and tell that they made it or just copy another commmunity resources post. It’s begging to be like the Asset Selling category that got removed, I hope that the DevForum Staff will soon do something about it.

1 Like
6

Yes, we need to stop that category from being flooded with not relevant or unacceptable posts. Couple of things though:

  1. I think that users should be given a strike depending on if they already have gotten a warning before for committing that very act. For example, if a person got their post archived for being a hub topic and they do it again, that time they post again should be when they get a strike.

  1. Literally the same thing happened to me. A person created a hub topic and I just posted that they’re not really allowed anymore. Then shortly after, his post got flagged. Next, he DMmed me and blamed me for having his post taken down. I tried to reassure him that it was against the rules and if you break them, the consequences are inevitable. Plus, everyone’s gotten flagged at least once in their DevForum “career”, so just learn from your mistakes and move on. That is exactly when he said, “I saw many other posts, why didn’t they get flagged”?

  2. Following up on that quote by the person, the main problem here is that new people see these unacceptable posts (such as hub topics) and see that they have many likes on them (some of them have 50+). This makes them believe that it’s okay for them to do so and the community actually likes it. But, the discussion behind the scenes in this Forum Feedback category is overlooked by them due to the hub topic having more attention, so they never know that it’s against the rules. They make their own post, hoping to get the same number of likes and support and get flagged. I don’t know how the flagging system works exactly, but one thing’s for sure, posts with 50+ likes are much harder to take down via flags than ones that are just starting out. Hence, why that guy’s post got flagged and removed immediately while the older hub topics still remain.

  1. Exactly what happens with scenarios like from #3. It takes only a couple of posts to start a “trend” (specifically a bad one). There needs to be something done about those original topics so that everyone gets a clear message on what not to do.

  2. As per minor things like not posting in Resources because the module isn’t open-soruced–that shouldn’t contribute to a strike. Not everyone knows about that, and it’s actually a little difficult to find out (I only found out because I saw @boatbomber and @Elttob’s InCommand plugin get moved to Cool Creations). So, this should not be a punishable offense.

Thank you for reading this.

5 Likes
7

This reminds me,

A few days back there was literally a post of a game with a while true loop not containing any wait statement, saying it was a resource of how to make a game you can never join.

That was proverbially the most absurd thing I’ve ever seen on the forum.

10 Likes
8

Yes, this should definitely be a must. There is virtually 0 excuse for re-offenders. If anything if the infraction was as obvious and of the same severity I would go as far of saying this should be worth potentially multiple strikes if its within a small timeframe.

3 Likes
9

If PA can’t handle resources, then new members point blank shouldn’t be able to post there. This has reached the level where it is hindering all reasonable usage of the category.

13 Likes
10

Up to this point I’ve been strongly against this solution, for reasons I’ve already outlined, mainly that its unfair on those that properly use the category.

Yet at this point its gone to far and I strongly agree, however its still a shame that a few idiots who don’t read have to take away the privilege from everyone else.

11

Yes, the main problem is that many of them don’t read the category descriptions. They literally just look at the name of the category and assume that it’s for what they think it is. For example, I’ve seen posts that ask for resources in #resources:community-resources, which means they only read the category name and assumed the rest. Even when the category description comes up when choosing a category for a new topic, they still overlook it.

It’s time to enforce some rules around here, please. Constantly archiving/locking posts isn’t doing much or anything at all. This isn’t only happening to resources, but even the #help-and-feedback where they just ask for free scripts and make very vague posts. Imagine what the sacred #lounge would come to if it were opened up (shudders, did someone turn on the AC?).

2 Likes
12

I didn’t bring this up in my post since I thought it would bring controversy and take the conversation off topic but:

I actually think this new system is counterproductive, allowing offenders to see that the majority of the posts are breaking rules. However since, as I’ve said. Half the people offending seem to not be able to read certain pages they don’t agnowledge anymore that it was taken down for breaking rules.

1 Like
13

I definitely agree with this. As someone who’s been fairly new to the forums, I’ve seen some people misusing the forums to say unrelated things. What I’m talking about is those people who try to give out a solution but then contribute nothing to the topic. I’ve gotten flagged once, and I totally understand why. Also, I believe if they post something off topic on a different category, I believe that suspension from posting topics for 1 week will do. If someone does something wrong, punishment must occur. I also believe newer people should still get warning for doing something wrong, because if you spend 3 hours on the forums, read 150 topics, and 1.5k posts, it’s pretty clear they had a lot of time to read the rules. New Members should have the same punishment as regulars, just saying. Other than that, I totally agree with LuaBearyGood on this situation.

2 Likes
14

This must be explored very cautiously. As a new member of the DevForum, I have purposely avoided making posts of my own, and I have only replied to posts in fear of receiving strikes for not knowing what I am doing. To implement this feature, you would need to verify that a user purposely posted in the wrong category, or the user has a history of posting in the wrong category. You don’t want to scare new users from the platform all together.

4 Likes
15

From personal experience, I only learnt to really start to take the rules seriously after my second strike. It may be a controversial teaching technique, however from experience the second a user is at risk of potentially getting permanently kicked out, the second they start actually reading all the rules in depth and all the category guidelines.

A bird only lands on a power line once it burns its feet and realises it hurts, they don’t land on that power line again.

1 Like
16

I think a strike is too far. With this logic we might as well give strikes to people in Help and Feedback.

This happened in discussion. A few “idiots” posted nonsense for discussion but their posts got instantly rejected. You are contradicting yourself here. You want more quality control on Resources yet you go against that with this statement.

I believe at this point if dev rel is reluctant to make it Regular-only we might as well put post approval on it. Sages are locking topics on there anyways so that kinda defeats the whole point of them removing PA for less workload.

17

The reason why I contradict myself is because until this point, it was only the minority of members who post in resources who were making stupid posts, however since I originally started making that statement that its unfair to close it off to all members the circumstance has changed, to the point that such a large amount of members are misusing the catagory, and misusing the catagory knowing what they are doing that I no longer believe it productive to keep it open to members, it just sadens me that there are amazing resource makers that wouldn’t then be able to open source stuff.

18

#help-and-feedback:cool-creations exists. Post Approval was taken off of it a few months ago.

19

I agree on this, I’ve seen many community resource posts having no proper format and just shoves you with a single model full of things, without explaining the full purpose of the resource, and especially how it works.

So many posts this month in #resources ave been closed from the Post Approval team, or the DevRel and DevEng teams, I always want to find some valuable and great explanations in the #resources category, so they can tell and view the user How to do this in a order, and How to use it.

I don’t think strikes aren’t appropriate for the Community Resource when someone doesn’t put it correctly or doesn’t read the “title” of the category, but some say yes while others say no. :eyes:

#resources and #tutorial categories should be P.A approved like for members for Platform Feedback and maybe #discussion? (I don’t think Discussion is P.A.)

2 Likes
20

I completely agree with you. I don’t even bother reading the forums anymore because the quality of posts has drastically declined. It’s gotten so bad, sometimes I send posts to my friends to laugh at because of how low quality they are. Now, the way I think this can be improved is to revert to the old manual approval ways of the developer forums. And while it may be too late to do that, I think that making it a requirement to be a regular to post in more topics could be useful. I’m not even a regular, but I feel as if it needs to happen to raise the quality of posts on the forums, and to ultimately help out with flagging posts becoming more effective. Less bad posts = less flagging, right?

2 Likes