<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Martin @ Blog &#187; Google</title>
	<atom:link href="http://www.wolkje.net/category/internet/google/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wolkje.net</link>
	<description>software development and life.</description>
	<lastBuildDate>Sun, 10 Jan 2010 11:18:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Paper about Google with interesting quote</title>
		<link>http://www.wolkje.net/2007/01/24/paper-about-google-with-interesting-quote/</link>
		<comments>http://www.wolkje.net/2007/01/24/paper-about-google-with-interesting-quote/#comments</comments>
		<pubDate>Wed, 24 Jan 2007 16:10:24 +0000</pubDate>
		<dc:creator>Martin Sturm</dc:creator>
				<category><![CDATA[English]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[Science]]></category>

		<guid isPermaLink="false">http://blog.wolkje.net/?p=141</guid>
		<description><![CDATA[Today, I read a paper (PDF) written by the founders of Google about the first versions of their search engines. Probably, this is already noted by a large number of other webloggers, but I came across the following quote about &#8216;other commercial search engines&#8217;: 
Currently, the predominant business model for commercial search engines is advertising. [...]]]></description>
			<content:encoded><![CDATA[<p>Today, I read a <a href="http://www-db.deis.unibo.it/courses/SI-LS/papers/BP98.pdf">paper (PDF)</a> written by the founders of Google about the first versions of their search engines. Probably, this is already noted by a large number of other webloggers, but I came across the following quote about &#8216;other commercial search engines&#8217;: </p>
<blockquote><p>Currently, the predominant business model for commercial search engines is advertising. The goals of<br />
the advertising business model do not always correspond to providing quality search to users. For<br />
example, in our prototype search engine one of the top results for cellular phone is &#8220;The Effect of<br />
Cellular Phone Use Upon Driver Attention&#8221;, a study which explains in great detail the distractions and<br />
risk associated with conversing on a cell phone while driving. This search result came up first because<br />
of its high importance as judged by the PageRank algorithm, an approximation of citation importance on<br />
the web [Page, 98]. It is clear that a search engine which was taking money for showing cellular phone<br />
ads would have difficulty justifying the page that our system returned to its paying advertisers. For this<br />
type of reason and historical experience with other media [Bagdikian 83], we expect that advertising<br />
funded search engines will be inherently biased towards the advertisers and away from the needs of the<br />
consumers.
</p></blockquote>
<p>Considering the fact that Google generates most of its revenues by putting advertisements in its search results, it makes one wonder whether Google did not made the same mistakes as its predecessors. In the current version of Google, a search on <a href="http://www.google.nl/search?q=cellular+phone&#038;ie=utf-8&#038;oe=utf-8&#038;rls=com.ubuntu:nl:official&#038;client=firefox-a">Cellular phone</a> does return only information about where one can buy the cheapest cell phones, but no results about a study on the dangers of using cell phones while driving a car. I think it is at least interesting, and maybe even an example of the risk of &#8216;allowing&#8217; advertisements everywhere (of course, Google may decide for itself if it put advertisements in its search results). I also wonder how Page and Brin (the authors of the paper, but also the fouders of Google and now both billionairs) currently think about this topic. I guess they have a different vision on it now, then they had nine years ago&#8230; </p>
]]></content:encoded>
			<wfw:commentRss>http://www.wolkje.net/2007/01/24/paper-about-google-with-interesting-quote/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Reader</title>
		<link>http://www.wolkje.net/2006/10/24/google-reader/</link>
		<comments>http://www.wolkje.net/2006/10/24/google-reader/#comments</comments>
		<pubDate>Tue, 24 Oct 2006 08:08:25 +0000</pubDate>
		<dc:creator>Martin Sturm</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Internet]]></category>

		<guid isPermaLink="false">http://blog.wolkje.net/?p=117</guid>
		<description><![CDATA[Today I came across a weblog entry of Jorge O. Castro
(whiprush) on Planet Gnome which mentions Google Reader. While I didn&#8217;t know this service of Google, I decided to give it a try. I must say, it is a very nice AJAX-based webapplication for following various websites. There are several &#8216;packages&#8217; available, such as photography [...]]]></description>
			<content:encoded><![CDATA[<p>Today I came across a weblog entry of <a href="http://www.whiprush.org/2006/10/laptop_bags_and.html">Jorge O. Castro<br />
(whiprush)</a> on <a href="http://planet.gnome.org">Planet Gnome</a> which mentions Google Reader. While I didn&#8217;t know this service of Google, I decided to give it a try. I must say, it is a very nice <abbr title="Asynchronous JavaScript and XML">AJAX</abbr>-based webapplication for following various websites. There are several &#8216;packages&#8217; available, such as photography (see screenshot below) and Technology (which consits of sites such as Slashdot, Digg, Wired, etc.). It is possible to add other RSS-feeds to the list as well, and you even don&#8217;t have to look them up yourself, because you can easily search for them using Google. Even the Tweakers.net RSS-feeds are known by Google. I think this may be the first RSS-reader I will use regularly in the feature because of the ease of use (and also because of the nice pre-package feed-packages).</p>
<p><img id="image116" src="http://blog.wolkje.net/wp-content/uploads/2006/10/Google%20reader.png" alt="Google Reader" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.wolkje.net/2006/10/24/google-reader/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Codesearch: a potential hackers paradise</title>
		<link>http://www.wolkje.net/2006/10/11/google-codesearch-a-potential-hackers-paradise/</link>
		<comments>http://www.wolkje.net/2006/10/11/google-codesearch-a-potential-hackers-paradise/#comments</comments>
		<pubDate>Wed, 11 Oct 2006 08:12:25 +0000</pubDate>
		<dc:creator>Martin Sturm</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Internet]]></category>

		<guid isPermaLink="false">http://blog.wolkje.net/?p=114</guid>
		<description><![CDATA[Google recently introduced Google Codesearch, a search engine for programming code. While Google was already a valuable source of information for hackers (it could be used to find passwords, usernames and so on), Codesearch enables even more possibilities. Obviously, it is quite easy to find patterns of potential vulnerable code, like buffer overflows, backdoor passwords [...]]]></description>
			<content:encoded><![CDATA[<p>Google recently introduced <a href="http://www.google.com/codesearch">Google Codesearch</a>, a search engine for programming code. While Google was already a valuable source of information for hackers (it could be used to find passwords, usernames and so on), Codesearch enables even more possibilities. Obviously, it is quite easy to find patterns of potential vulnerable code, like buffer overflows, backdoor passwords and even proprietary code which is unintentionally published on public accessible websites. </p>
<p>One can think this is &#8216;bad&#8217; or something, but I think it is very good that flaws in programs are easy to find and exposed to the entire  world. This is the only way to prevent companies and individuals from relying on &#8217;security by obscurity&#8217;. And it is good for &#8216;closed source&#8217; companies to realise that even while there program sources are not widely available, it is very hard to prevent people from getting it anyway. As some people say: &#8216;there are no secrets, only information you do not have yet&#8217;.</p>
<p>A nice list of stuff which can be found using Google Codesearch can be found on a weblog called <a href="http://www.kottke.org/06/10/google-code-search">kottke.org</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.wolkje.net/2006/10/11/google-codesearch-a-potential-hackers-paradise/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
