What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 134 Stack Exchange communities.

On Programmers, I just came across a user who was using suggested edits to add Amazon links to many questions. This user was advised to limit the edits to avoid cluttering up the homepage with many edits.

At a practical sense given the current functionality of the home page, I can understand the reasoning. But it seems silly to advise users not to do something helpful on those grounds.

Can we do better?

share|improve this question
2  
    
    
    
    
What do you mean with "Can we do better?" –  kiamlaluno Nov 22 '11 at 18:42
    
@RobertHarvey Thanks for the help with the title -- however -- I'm not suggesting that prevention is the only solution. I'm wondering whether we should change our advice or prevent clutter of the homepage. But, as you commented on the meta.programmers post, I think it's silly to weight the appropriateness of an edit based on how many of them are done. (@kiamlaluno, this should answer your question too) –  NickC Nov 22 '11 at 18:45
3  
Rather than complicating this with yet another Meta post, I'm just going to [feature-request] this one. See my answer below. –  Robert Harvey Nov 22 '11 at 18:51
    
@Robert - fair enough, thanks. –  NickC Nov 22 '11 at 18:52

1 Answer 1

up vote 8 down vote accepted

Bumping posts to the front page when a substantial edit occurs is [by-design]. It allows the community to review the edits to see if they are appropriate.

Perhaps a throttle could be added to suggested edits by an individual user. I suggest a restriction of six suggested edits per hour per user. I think that would solve the problem at hand, and still give editors plenty of leeway to suggest substantial edits.

share|improve this answer
2  
While the number might still be pretty high for low-traffic sites, I definitely think this is a reasonable compromise between trying to keep the front page fresh and allowing low-rep users to help out. –  user149432 Nov 22 '11 at 18:56
    
Just a thought: Should not the limit consider when the post has been created? For example, if I am editing a post created 2 minutes ago, I am not cluttering the front page; vice versa, if I am editing a question asked a month ago, which has already an accepted answer, I am surely doing more "damage." –  kiamlaluno Nov 22 '11 at 19:06
1  
@kiamlaluno: The only people that are likely to hit this limit are editors who are adding Amazon links or deleting the word "hell" from posts, among other similar reasons. It is unlikely that a person doing more substantive editing will hit this limit. –  Robert Harvey Nov 22 '11 at 19:09
    
I understood the reason for restricting the edits; still, it's not cluttering the front page, if I edit a question that has been asked 2 minutes ago. I am not sure the limit would be hit only by who removes the word "hell" from titles; there is also who removes sentences similar to "As this question has been closed here, I asked the same question on […]." –  kiamlaluno Nov 22 '11 at 19:18
3  
The clutter is a symptom of the problem, not the problem itself. The actual problem is finding an acceptable way to edit posts, and then performing that same edit on many, many posts. The rate limit solves both the symptom and the actual underlying problem. It should be a simple rate limiter; I don't want to make the logic too complicated for people to understand, or too onerous for the developers to implement. –  Robert Harvey Nov 22 '11 at 19:23
    
I believe that any edit will cause a bump, not just a substantial edit. I feel that minor edits - adding/removing a link, changing tags, and edits of less than a specific percentage of a post should not cause a bump. It would remedy a lot of problems. Then, the limit could just be applied to substantial edits that cause a post to be bumped. –  Thomas Owens Nov 22 '11 at 20:57

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .