Find/Replace ON Demand Services (FRONDS) are collaboratively-created blocks (or modules) of Find-Replace combinations for AutoWikiBrowser. The system is still young, and desperately needs contributors in order to further the usefulness of the plugin for other users. Be brave, and take that first step.
The main driver of these developments is WikiProject Check Wikipedia, which lists syntax and other errors, many of which can be easily fixed en-masse using AWB using custom built regular expressions (regexes) which editors add to their find/replace list (see right). Over time, they spend time developing and improving the regexes they need to fix the error in which they are most interested, oblivious to the regexes being used by other editors. Likewise, this is probably the case with other projects, where editing by regular expression is common.
By sharing community lists of regexes, and editor can quickly start work on a new error, working with the most efficient regexes i.e. the ones that will save them the most time. Meanwhile, someone fixing one error can also fix another while they are going along, reducing history clutter and time spent editing that one page.
Firstly, remember that Fronds is still young. For now, one must follow this simple process:
To update your version of the fronds plugin, overwrite your existing Fronds.dll (which should be in the same directory as AutoWikiBrowser.exe) with the latest version (right click, save as).
Due to the nature of Fronds, updates to the main plugin will be few and far between. Therefore, one can safely assume that the update is an important one; it may contain major bugfixes or other improvements. This would suggest that it's advisable to update whenever prompted to do so, especially as the project is now only in its beta phase.
At the end of the day, users of the Fronds system have to install a plugin to get the main interface, but the intention is to make the regexes themselves as easily updatable as possible. (See below for more.)
General fixes are required to have a very low false positive rate, because most editors will assume that AWB has got it right; this is not negligence on the part of the human editor, merely, it is an understandable consequence of performing the same edit over and over again. By opting in, a higher level of care is (hopefully) maintained and false positives more likely to be spotted.
More importantly though is the speed with which updated and fixed regexes can be delivered to the end-user - every time they use AWB, or something similar; this is compared to the several week delay for general fixes that the novice end-user receives. (Bot operators frequently download svn snapshots, but even these are not that frequent.)