Roll your own google

Google dominates contemporary access to the Internet, having become for many net users virtually synonymous not only with search, but online video (through YouTube), and mobile (through the Android platform).

As the web first developed in the 1990s, websites were sparse isolated islands, tethered together by webrings and a patchwork of amateur link lists and proto-portals. Early search sites balanced between (human) editorially maintained portal sites and a variety of "indexes" based on web crawlers. The Altavista search engine was perhaps the first breakthrough in terms of tackling the ever-growing scale of the online web of documents and shot to an early lead among a field of many, often diversely focused web search engines. Google, however, perfected the formula by taking on not only the scale, but leveraging the link structure of the net itself, via its PageRank algorithm to deliver even better search results, while managing (in fact thriving) on the volume of the web. This algorithm, first patented September 4, 2001, forms the basis of Google's commercial success and the exact mechanisms of their current algorithms to produce search results are closely guarded trade secrets.

This exercise is at once a simple exercise in CGI scripting and an opportunity to critically reflect on the state of the Web and the role of centralized commercial services such as Google.

Exercise

Create a cgi "search engine". It needs to be self-contained, that is contain it's own index based on your own specific crawling of data. Part of the point of doing this is to reflect on the question of data centralization and specificity. What does it mean to create your own index? Your "results" could be "purely" algorithmic, and/or based only on input provided to it (via the search box), and/or using either collected or crawled data you've yourself gathered. It's only fair, that's how Google works too.

STARTER CODE --> DOWNLOAD HERE http://pzwart3.wdka.hro.nl/~mmurtaugh/share/ryog.zip

CGI

• Start with a simple form (HTTP/Post/Submit!)
• Can respond with ANY type (image/audio/...)
• Respond to browser (with audio?)

How search works (according to Google)

• Contemporary (2014) corporate communication about Google about "How Search Works"
• The Anatomy of a Large-Scale Hypertextual Web Search Engine Research paper Google c-founders Sergey Brin and Lawrence (Larry) Page. 1998.

Search circa 1996

http://archive.org/details/ComputerChronicles-SearchEngines_861

Computer Chronicles on Search (1996)

Search circa 1896

• Encyclopedia
• Book as an API

Epub

Emerging standards for electronic books such as epub are interesting in that they bridge web practices and formats with those of tradition publishing.

Alphabets

• Alphabets on Gutenberg
  • ABC Jules Lemaître... Education
  • Anti-Slavery Alphabet... Resistance
  • Typographic/Printing
• De Geuzen Write with Icons
• Martha Rosler Semiology of the Kitchen
• Paul Sharits, Word Movie (Fluxus)
• http://squarevzw.be/ensuite/femkeinterview.htm
• Dictionnaire @ Gutenburg
  • Flaubert's Dictionary of Received Ideas

Alternative Search Engines

• Matthew Fuller's Presentation at Society of the Query #1 Video

In it he uses three alterative search engines:

• Viewzi ("defunct" since 2010)
• Kartoo, also stopped in 2010

oamos

• Oamos by Marc Lee, who also created:

tracenoizer

• Tracenoizer a unique "identity" management solution that allows for tactical scraping to create false "clone" homepages & publish them online

soundbrowser

• While (in part) at PZI Matthias Hurdl developed soundbrowser that searches freesound.org and presents the results as a bank of looping audio players allowing for parallel playing and mixing.

Indexing in Python

• Whoosh is a library for indexing texts written in Python