(Skip to main content.)

Blogs Quoderat Land and Hold Short

Quoderat

Archive for October, 2008

Banking: blame and beliefs

Tuesday, October 14th, 2008

The world banking meltdown is a lot like the Christian Bible: no matter what your personal beliefs, you can find something there, somewhere, to back them up.

Too little regulation? Lenders were able to use credit derivatives (such as collateralized debt obligations) to keep loans off their books, without any reliable way of assessing their risk (and thus, their actual value).

Too much regulation? Basel II (the regulatory response to previous banking crises) forced banks to reassess their reserves daily at market value — if the market started to fall, banks had to convert stocks to cash quickly to avoid falling below minimum reserve levels, massively magnifying even small stock market movements and encouraging banks to use credit derivatives to keep loans off their books.

Sinners? People (especially in the U.S.) went out and bought homes that they could never afford to pay for, on the assumption that home values would keep rising, then kept taking out more money against their mortgages to finance regular consumer spending.

Victims? Some of the financial instruments available to borrowers in the U.S., like negative amortization mortgages (pay less than the interest for the first few years), were deliberately designed to sucker in buyers who hadn’t quite mastered grade 5 math.

Too much government? By taking over bad loans from the banks, governments around the world have sent out the message that banks get to gain in the good times, but will be spared the pain in bad. Do they have any more incentive to be careful the next time around? Besides, all the government borrowing, especially in the U.S., has hardly helped the situation.

Too little government? Central banks could have stopped the housing bubble in its tracks by raising the prime interest rate (say, to 5 or 6% in the U.S.). Year after year, they passed on the opportunity, keeping interest rates low to keep the stock markets artificially high, and pumping more air in the housing bubble, leading to a bigger explosion this year than we really needed.

So, whether you’re a political candidate or just a Starbucks pundit, pick the statements above that best support what you already believe, and run with them. No matter what, you’ll probably be right.

sorry.google.com

Wednesday, October 1st, 2008

See the update below. I was right: Google’s new bot detection is overly naive, and I’m not the only one having problems.

See also John Cowan’s comment below, for a different (personal) interpretation of Google’s terms of service.

Google Maps won’t show me satellite imagery this morning.

Google has recently set up a system to try to autodetect and block bots scraping their system, and it isn’t working very well — people are getting blocked even from Google Search simply because they have too many (human-generated) queries passing through the same proxy.

This morning, I suddenly discovered a different problem: the satellite view in Google Maps has stopped working for me — I get the “don’t have imagery at this zoom level for this region” error everywhere, at every zoom level. I can still see maps and terrain, but not satellite pics, and I noticed the host sorry.google.com setting a lot of cookies.

Is Google’s satellite imagery down for everyone else this morning, or has their software decided that I’m a bot trying to scrape satellite imagery?

Update

I was right — Google’s software had decided that I was a bot. They have a test link directly to a satellite to see if you’re being blocked:

http://khm0.google.com/kh?v=31&hl=en&x=0&y=0&z=1&s=

It took me to this page. I was able to renable access simply by entering a CAPTCHA.

What happened?

I wrote a couple of months ago about how to detect overzoom in Google Maps. My guess is that the overzoom protection in OurAirports — automatically zooming out every 4 seconds until there were actual satellite tiles available — triggered to bot alert, and I’ve disabled the feature for now.

That’s very bad news for any mashup that uses JavaScript to do more sophisticated things with Google Maps, like, say, panning at regular intervals. Google’s bot detection seems to be extremely naive, and any repeated action at regular intervals will fire it off.