comment
Lots of Power Shell questions, low answers; none on first page
I think the distinction is SO is probably better for language questions, where you want to know how some aspect of the language works, while SU is better for task questions, where you want to know how to perform some task (of small scope, not "write a program for me").
awarded
revised
TrickleEdit test question 2
add tag
Loading…
awarded
comment
TrickleEdit: Queuing edits to prevent flooding
@KamilMaciorowski Unfortunately, that would have to be a SE change. And it will never happen: all edits must bump so vandalism can be detected. At least, that was the reasoning the last few times this was brought up. So, the only solution to edit flooding is to do it slowly, in batches. The idea of this extension is to make it easier to time those slow batches.
revised
TrickleEdit test question 2
added 16 characters in body
Loading…
revised
TrickleEdit: Queuing edits to prevent flooding
added 123 characters in body
Loading…
revised
TrickleEdit test question 2
added 14 characters in body; added 2 characters in body; deleted 2 characters in body
Loading…
revised
TrickleEdit: Queuing edits to prevent flooding
added 74 characters in body
Loading…
Loading…
Loading…
comment
TrickleEdit: Queuing edits to prevent flooding
@allquixotic Eventually, yea. I'll probably copy this over to StackApps at some point. But it's easier to start (testing) in a small-ish community, I think.
revised
TrickleEdit: Queuing edits to prevent flooding
added 54 characters in body
Loading…
revised
TrickleEdit: Queuing edits to prevent flooding
edited title
Loading…
revised
TrickleEdit: Queuing edits to prevent flooding
added 12 characters in body
Loading…
revised
TrickleEdit: Queuing edits to prevent flooding
added 140 characters in body
Loading…
revised
TrickleEdit: Queuing edits to prevent flooding
added 181 characters in body
Loading…
revised
TrickleEdit: Queuing edits to prevent flooding
added 181 characters in body
Loading…
Loading…
comment
Editing answers to closed questions?
@Mokubai Yup, I've manually fixed that one.