Interpolique: transparently preventing SQL Injection and XSS with base64 encoding, what happened?

What happened is the same thing that happens to many good ideas in the security space: it went nowhere, for reasons outside of the inventor's control. It is a cool idea, but it requires adoption by frameworks and application developers. And, for better or worse, there is not a lot of demand for security solutions like this.

For most developers, security is a secondary consideration. Many application developers don't think they have a problem and don't perceive a need for a solution (most of them are probably fooling themselves, but so it goes). And many of the developers who are aware of XSS, think they can avoid it by just being careful (that's a dubious proposition, as it is too easy to make a single inadvertent mistake that hoses the security of your whole site, but hey, if they don't feel a need for it, they ain't gonna adopt it).

He put up a site for testing, either it failed or it didn't get tested enough and he realized that the place for doing this kind of thing is in the core language -- bolting it on afterword requires user adoption, which generally just doesn't happen. My bet is door number 2.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.