markfilipak wrote:What do surrogates do?
It's just a way to run custom pieces of JS through NoScript to help un-break pages and/or make them more user/friendly to NoScript users.
markfilipak wrote:Oh, I get it. The 'replacement' script is returned as though it was fetched from the URL. Yes, that's what I need to do.
Yep, in the case of no prefix.
markfilipak wrote:What's "!@"?
It means to run the surrogate script on DOMContentLoaded, if a web page's address matches the regexp defined by the rest of the pref value
markfilipak wrote:Shouldn't this: "^https?://[^/]+google\..*/" be "/^https?:\/\/[^\/]+google\..*/"?
No, it's fine. the regexp is constructed with
which does not take enclosing / nor do / need to be excaped
markfilipak wrote:What's "search" doing at the end of the (somewhat strangly constructed) regexp?
What you said:
markfilipak wrote:(...or is "/search" part of the URL?)
markfilipak wrote:OMG. Are you saying that I will have to craft a suitable replacement based on minified JS that, in many cases, will be provisioning event listeners that are dynamically bound to <div>-elements? Ugh! I can't spend the rest of my life analyzing minified DOM-code just to make someone's web site work.
Yeah, basically...
markfilipak wrote:What if I simply roll a VM whenever I want to go to the net (and I go to the net "naked", so-to-speak), going through an anonymizer, and tear the VM down when I'm finished? Anyone doing that?
I also use a disposable VM for that kind of thing but I don't use an anonymizer/proxy because I have no way to be sure it's trustworthy.
markfilipak wrote:Does surrogate processing involve GET headers? How?
I don't know that much details about it.