@Ramhound It's community wiki, so >100 rep doesn't need approval.

@Mokubai Worse, it actually breaks answer #1.

If you do take a screenshot, make sure you quote the text somewhere - whether as image alt/description text or below it. Some people are on connections where images are filtered out (especially because SE hosts them on imgur).

I'd suggest windows-live-tiles or windows-tiles instead... it's not immediately obvious that live-tiles is a Windows thing.

@Twisty IIRC that only happens if the edit is while it's "on hold" (within first week of close)

Making a request like this through meta (like you've done) is one way.

@JourneymanGeek I believe it does. <== anecdotal

If we actually want to do this, content could include weekly highlights from SU - but we'd need more than just that.

See also: Should potentially “Dangerous” answers be flagged/deleted?, Should every answer involving registry edits contain a warning to back up the registry?

@Ramhound Ah, yea. Usually along the vein of "registry cleaners". I mean, if you don't go around deleting random files from C:\Windows\ , why do it from the registry?

@Ramhound I think the proposal here is only for answers that involve manually editing the registry, which is far narrower than "any registry change at all". The manual editing is the case my answer was intended to address.

It's actually much less risky than something like disk resize (complete data loss is worse than failure to boot, in my book) so, if anything, those should have more warnings.

@BenN Yes, every script answer should be accompanied by an explanation of how the script works, when possible. "Here, run this" is usually not a good script answer. On the other hand, it's also alright to pose the answer as a software recommendation (as per our usual guidelines on software rec answers) if the answerer just happens to find the question interesting enough to write a custom solution - in those cases, the question itself is typically just a general question, not one specifically asking for a script.

> Nowadays, the preferred reason is Too Broad, since boatloads of different scripts could accomplish the same thing. -- that argument would equally apply to just about every non-theoretical question here. Of course, there's usually a preferred way of doing something, and that is what we should strive to provide. I'd also recommend not trying to follow Stack Overflow too closely - Super User is purposely different; while SO expects questions to be about specific aspects of code, we accept questions asking how to accomplish a task, which may or may not be answered with a script.