Also, real OCR is too expensive to do at the volumes of mail being sent today. Gmail is likely using an OCR-esque technique that has lower precision but is much faster to process a given image.
291 karma · joined April 28, 2007
Also, real OCR is too expensive to do at the volumes of mail being sent today. Gmail is likely using an OCR-esque technique that has lower precision but is much faster to process a given image.
I'd love to only ever have these kinds of bugs.
However, there are a bunch more issues with this. To allow this, they'd have to be able to parse all of the most popular Web server log formats. This, in and of itself, is not that hard until you account for people customizing their logging format via measures like the LogFormat directive in Apache. As well, customizing the log format is a virtual necessity, as GA requires more information than is in the standard log formats of most web servers. Another issue is that the use of a JavaScript snippet on the page prevents non-browser user agents from appearing, clearing GA's logs of spiders and other such cruft that detracts from determining human user behavior (what they are apparently most interested in for the purposes of optimizing AdWords and AdSense).
But the biggest problem for them, I think, is that with this method they are no longer able to set first-party cookies on your user's browsers and thus (more) reliably track individual (read: human) users. So, in effect, they would waste time with this, in that they'd still have to make you put a JS snippet on the page to set cookies that you'd then have to modify your web server logging format to include in every hit. Urchin worked like this back when it was still alive and you could run it on your own servers. So, all in all, it seems like something Google would just be wasting their time in doing given what they want to get out of your data.
"To meet the reliability and scaling needs, Amazon has developed a number of storage technologies, of which the Amazon Simple Storage Service (also available outside of Amazon and known as Amazon S3), is probably the best known. This paper presents the design and implementation of Dynamo, another highly available and scalable distributed data store built for Amazon's platform."
More supporting evidence from section 2.1:
"Dynamo targets applications that need to store objects that are (usually less than 1 MB)."
S3 allows individual objects up to 5GB in size. This in and of itself does not rule out Dynamo being the underlying store for S3 but does certainly lend weight to what Werner and the paper's authors have claimed regarding S3's origin.
http://www.franz.com/products/allegrocache/
I don't know how much it costs, either.