I added the line to my jQuery script, and, *voila!*, WPSC, W3 Total Cache, and Comet Cache are all acting like I want them to. After I use the script, and reload, I get fresh pages.
Placing a post whose content would include a version of the post itself (containing a version of the post itself, and so on) produces a site-crashing “reset overload” (ERR_CONNECTION_RESET). It’s easy to create the danger inadvertently, but also easy to prevent.
A primary use for WP-RUBI will be at sites where administrators have decided to remove images that have been used either without permission or under lapsed or lapsing usage licenses: Proper employment will help to reduce or eliminate legal and actual “exposure” quickly and easily, without harming the site’s search engine rankings and while preserving posts as originally composed, allowing for eventual restoration.
Troll-Stomping and Other Sensible Things: #WordPress Plug-In Beta Test/Preview
It occurred to me the other day or week that it wouldn’t be hard to create a jQuery-enabled ignore button, and it wouldn’t be too hard to add cookies to make the ignoring persistent, and it wouldn’t be too hard to un-ignore, too. While I was at it, and feeling that enabling ignore was kind of negative, how about making it possible to highlight commenters using about the same methods used to ignore them, or particular comments, so they’re easy to pick out in a thread?