ie. ad- and malware-blocking, user-side script, stylesheet insertion and text, html, xml manipulation (regexes, xpath).
Because then you don’t have to write different scripts for different browsers (in the case of pure filtering). Parsing the stuff ourselves and then forwarding it to the browser (who parses it again) isn’t particularly efficient, but I don’t see how you can circumvent that for proprietary browsers (such as Opera, which I’m primarily using atm).
Should be error-resilient against malformed input (html, xml) and user-specified rules, ie. xpath expressions.
Since imho none of the available proxies quite fit my needs (yet one could possibly chain them, ie. one for ad-filtering, which is available, and the custom stuff ourselves, but I’d rather compile that stuff done into one single binary) there’s the question: When do I do this?
At the moment I have an Opera extension which does what I want, but for reason above this should be extended, possibly with dsl support for rules and optional compilation into state machines for additional speed-up (but which might easily backfire, so benchmarks are in order).