3 ms·

OP said: "How much business did I lose? I have no idea how many potential customers tried to buy our JavaScript Performance ebook through Google Checkout and

OP said: "How much business did I lose? I have no idea how many potential customers tried to buy our JavaScript Performance ebook through Google Checkout and saw a message that our account was disabled." The irony of this whole issue is the complaint is resultant from the site attempting to sell an eBook on JavaScript. What possibly happened is that this particular "technical error" was resultant from some kind of conflict between the eBook's syntactically sketchy JavaScript references (perhaps there are code examples within the eBook) and the way that Google Checkout wants to handle JavaScript. I would think somebody touting and attempting to _sell_ the "performance" virtues of JavaScript would also be aware of the potential evil that JavaScript can do. "Don't get me wrong: I don't hate Google or people inside Google . . . rather, the way Google's abstract, corporate algorithms have treated me." It's probably a very good thing that this "technical error" was indeed preemptively caught by the "abstract, corporate algorithm." After all, JavaScript can be evil. I would say. . . score one for Google Checkout. Sometimes better safe than sorry.

ahoyhere 18y ago
You make a very bad conspiracy theorist. Or comedian. The language isn't slow, implementations of it are. Regardless, you can still maximize the performance of something slow, even if that local maximum is not extremely fast in the absolute sense. We cover the whole range of techniques, from better architecture, DOM tweaking, and the maximization of specific bits of code. The contents of the book never touch Google Checkout, even in their zipped form. I wasn't aware publically boasting of ignorance was cool after junior high.
- indiejade 18y ago
  I never said the language was slow. I said it can be used to do evil things. Your translation was that Google is somehow "evil" for not implicitly allowing your profit-making motives upon potentially evil exploits. So you got chastised by some security check for a technical error. Technical errors happen all the time. Get over it. BTW where, exactly, in this eBook do you do you cover security issues related to JavaScript? The contents of the book never touch Google Checkout Specifically, where do you cover what "touching" means, in a network's mind? . See: http://neil.fraser.name/news/2005/07/16/ http://neil.fraser.name/news/2005/07/16/ Also, this: http://message.worldbank.org/isp_403.html http://message.worldbank.org/isp_403.html (Part-time comedian, part time FBI agent)
  - ahoyhere 18y ago
    Um? How do you think that the topic of the book I'm selling and the Google Checkout saga correlate at all? I'm really curious, because there's not even the tiniest link in the chain between the two totally disparate and unrelated things. I didn't get "chastised" by a "security check." They closed my account, disrupted my business, and stole my money. With no warning, communication, notice or appeal. They give no way to contact them and they tell you the money is gone for good. I got my account back only through this publicity campaign, which is, in my opinion, a good example of how Google's "Don't be evil" motto has been abandoned.
    - indiejade 18y ago
      Remember that you've garnered a lot of attention for this attack on Google in your "publicity campaign". Anybody who buys your book would be either a dolt or a schmutz, IMHO. Show us some links for your supposed JavaScript foo, and we can talk. Not third party links, dearie; let's see them on your server.
    - indiejade 18y ago
      One more thing: You're seeking "paid validation" as a writer through Google. Welcome to the club. Want to compare AdSense revenue? How much money do you really think you "lost" as a result of this error? How many people do you picture were lined up to purchase your book? Can't be much. You seem to intrinsically overvalue your self-input. True hackers hack for free. Anything that comes of it is icing on the cake. Even pennies are enormously welcome. Whining loudly is lame. You should really try to remember to keep a sense of humor when dealing with certain types of code like JavaScript. P.S. Thanks, Neil!

ahoyhere 18y ago

You make a very bad conspiracy theorist. Or comedian. The language isn't slow, implementations of it are. Regardless, you can still maximize the performance of something slow, even if that local maximum is not extremely fast in the absolute sense. We cover the whole range of techniques, from better architecture, DOM tweaking, and the maximization of specific bits of code. The contents of the book never touch Google Checkout, even in their zipped form. I wasn't aware publically boasting of ignorance was cool after junior high.

indiejade 18y ago
I never said the language was slow. I said it can be used to do evil things. Your translation was that Google is somehow "evil" for not implicitly allowing your profit-making motives upon potentially evil exploits. So you got chastised by some security check for a technical error. Technical errors happen all the time. Get over it. BTW where, exactly, in this eBook do you do you cover security issues related to JavaScript? The contents of the book never touch Google Checkout Specifically, where do you cover what "touching" means, in a network's mind? . See: http://neil.fraser.name/news/2005/07/16/ http://neil.fraser.name/news/2005/07/16/ Also, this: http://message.worldbank.org/isp_403.html http://message.worldbank.org/isp_403.html (Part-time comedian, part time FBI agent)
- ahoyhere 18y ago
  Um? How do you think that the topic of the book I'm selling and the Google Checkout saga correlate at all? I'm really curious, because there's not even the tiniest link in the chain between the two totally disparate and unrelated things. I didn't get "chastised" by a "security check." They closed my account, disrupted my business, and stole my money. With no warning, communication, notice or appeal. They give no way to contact them and they tell you the money is gone for good. I got my account back only through this publicity campaign, which is, in my opinion, a good example of how Google's "Don't be evil" motto has been abandoned.
  - indiejade 18y ago
    Remember that you've garnered a lot of attention for this attack on Google in your "publicity campaign". Anybody who buys your book would be either a dolt or a schmutz, IMHO. Show us some links for your supposed JavaScript foo, and we can talk. Not third party links, dearie; let's see them on your server.
  - indiejade 18y ago
    One more thing: You're seeking "paid validation" as a writer through Google. Welcome to the club. Want to compare AdSense revenue? How much money do you really think you "lost" as a result of this error? How many people do you picture were lined up to purchase your book? Can't be much. You seem to intrinsically overvalue your self-input. True hackers hack for free. Anything that comes of it is icing on the cake. Even pennies are enormously welcome. Whining loudly is lame. You should really try to remember to keep a sense of humor when dealing with certain types of code like JavaScript. P.S. Thanks, Neil!