Another solution is to allow users to see edit history of a reply and when they edited it (if that’s possible). Users could then see which replies were made just to farm likes and flag them accordingly. People who give normal feedback don’t need to be held by the time limit the just to fix a typo.
At the moment it only looks like this is possible if post history is public. I don’t think showing edit history to the public is a good idea…sometimes people accidentally post sensitive information or inappropriate information, by opening edit history to the public, this would allow access to that. Even if it’s per category, there is always that chance that someone posts sensitive information and quickly needs to edit it out.
2 Likes
I feel like this should be added, lately, the latest #updates:announcements from today and earlier this week have had a lot of edits from first or second replies which floods the post entirely, having an edit or simply extending the # of time to reply so this doesn’t happen in the future, it’s honestly annoying.
I’ve also known that you can bypass replying to announcements in a certain way, which seems like it should be patched or noted from staff that runs the forums.
I don’t want useless text and the same text saying “WHOA THIS IS COOL” and more, I want to see honest and valuable questions from members across the forum and responses from staff that I might have struggled with and not flooded replies that are baseless. 
Posting for likes on the forum, not about likes, contributing, and being here for help and asking questions is what I think is priority for people that are here, it needs to stop.
1 Like
In thought it sounds like a good idea, but it can be bad for developers wanting to give real feedback. Possibly only regulars could post replies, or some requirement to be able to reply?
This is addressed. Making it regular-only will only cause a million topics of complaints. Roblox already collects thoughts through surveys using #roblox-surveys – I see no reason for them to not be able to do similar in #updates:announcements.
2 Likes
I agree, but some devs like to have discussion about it in the replies. Maybe just have it as a rule and count those sorts of spam comments as spam, which will hopefully prevent users from doing it.
Anything that isn’t spam is just questions or showing disagreement which only Roblox staff would be able to answer and take action on. I don’t think those need much discussion – the former is just a question, and the latter is an opinion.
It seems like a good solution was reached on this announcement:
Rather than auto-unlocking after 10-15 minutes on a timer, the OP manually locked and unlocked it after about an hour. This prevented people from waiting for the timer to count down so they could spam replies, and gave people who have contributive comments a fair chance to reply when it was opened up a while later.
A more direct solution could be to develop a plugin that limits the number of times a person can post in the first X replies for an announcement, but would probably take too much work to be worthwhile.
Sorry I’m late with the bump, I only remembered this thread recently.
That topic was just technical by nature, the users that might post just for the sake of posting this may not necessarily be very technical people. Closing it for an hour is just going to delay the inevitable.
1 Like
If closing it for an hour is too short, then what about for 24-48 hours after posting? It will open sometime the next day, but no one will know when (aside from the OP). This makes it so that only those who happen to be reading the topic when it opens will get the first chance to reply. Any pressing issues or concerns can be messaged to the OP while the topic is closed. No matter how engaged these users are with growing forum stats, spending 24 hours refreshing an announcement page waiting for it to open is significantly more work than watching a timer count down from 10 minutes.
I have seen this happen several times, especially in #development-discussion.
It is pretty cool to get a couple of likes on a post, but the main purpose of the DevForum is for game development. There are many other websites that are forum-based so if you want to talk about things not related to game development, then go over to one of those websites instead of spamming nonsense here on the DevForums.
For example, #development-discussion is supposed to be about the development of games, and I have seen several topics that discuss current issues on Roblox and misuse the category.
I have also seen way too many topics in #help-and-feedback:scripting-support that are “how do I learn scripting?” and are just designed for people to maximize their stats.
I do think a post cooldown in #updates:announcements will be a good idea, because it will minimize spam and users will not be able to edit their posts for a while.
With the announcement yesterday, there was a slow mode put on the topic, which apparently prevented people from editing their post. I don’t know 100% how slow mode works on Discourse, but I am assuming it works like Discord where individual users are rate-limited, and isn’t a global limit. But it could be the latter as individuals spamming on an announcement usually isn’t a problem, however I can’t confirm since I’ve never replied to a topic with a slow mode. Maybe they can put that, that way the topic doesn’t just explode with 10+ replies of trying to get it to be the first, and you can wait to finish reading one, then another, and so on
3 Likes
I still see certain people rushing to use a feature for the first time to pretend they are a domain expert and then posting some platonic feedback just to get the first post (every time). Not actually convinced just limiting edits is the right solution here anymore.
Ideally I suppose they should just kick these people from the forum or ban them for a long time to disincentivize the behavior. Kinda sucks that their behavior has been entertained for so long.
7 Likes
Decided this is not worth my energy