I spent part of the day creating an open-source PowerShell module that makes it easier to create shortcuts. I wrote a detailed explanation showing how it works and included a link to the project, but the post was instantly flagged. Shortening the explanation and removing links didn't help, and even a very brief version was still blocked. The issue turned out not to be links at all: mentioning the Windows scripting automation object commonly written as "WScript.Shell" triggers the automatic filter. Has anyone else run into this, and is there a reliable way to share scripts and technical guidance without setting off the filter?
3 Answers
It may be worth testing the project name and code-hosting link separately, since automatic filters sometimes react to particular domains or phrases. If ordinary project links worked in earlier posts, though, the link itself may not be the problem.
So the module creates shortcut files? That sounds useful. The filtering behavior is frustrating because it blocks a legitimate technical explanation instead of just the problematic phrase.
The trigger appears to be the Windows automation object usually written as “WScript.Shell,” rather than GitHub or other code-hosting links. Posts containing that term can be removed immediately by the automated system, even when the rest of the content is harmless.
That matches what I found. Links were fine; mentioning “WScript.Shell” was what caused the instant removal. I also tested a small code example and saw the same behavior.