<?xml version="1.0" encoding="iso-8859-15" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" >
 <channel rdf:about="http://www.open-search.net/Blog/WebRss">
  <title>TWiki Blog (combined)</title>
  <link>http://www.open-search.net/Blog</link>
  <description>The open-search blog</description>
<image rdf:resource="" />
  <dc:language>en-us</dc:language>
  <dc:rights>Copyright &#169; 2010 by contributing authors</dc:rights>
  <dc:publisher>TWiki Administrator [webmaster@open-search.net]</dc:publisher>
  <dc:creator>TWiki Administrator [webmaster@open-search.net]</dc:creator>
  <dc:source>TWiki</dc:source>
  <items>
    <rdf:Seq>
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry25" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry24" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry23" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry22" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry21" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry20" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry19" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry18" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry17" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry12" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry16" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry7" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry4" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry5" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry8" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry3" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry2" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/WebHome" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry9" />
  <rdf:li rdf:resource="http://www.open-search.net/Blog/BlogEntry10" />
    </rdf:Seq>
  </items>
</channel>
<image rdf:about="">
  <title>TWiki/NatSkin</title>
  <link>http://www.open-search.net/Blog</link>
  <url></url>
</image>
<item rdf:about="http://www.open-search.net/Blog/BlogEntry25">
 <title>Report on the Forum on Quaero</title>
 <link>http://www.open-search.net/Blog/BlogEntry25</link>
 <description> &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.open-search.org&#34;&#62;Open-Search&#60;/a&#62; was invited to participate in the &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.janvaneyck.nl/0&#95;2&#95;3&#95;events&#95;info/arc&#95;07&#95;quaero&#95;thinktank.html&#34;&#62;Forum on Quaero&#60;/a&#62; at the Jan van Eyck Acadamie in Maastricht, September 29 and 30, 2007. The purpose of the forum was to question and investigate the European intentions to build a search engine and, broader, to investigate the cultural, political, and philosophical issues related to information search and access.  It turned out to be a critique on centralized search engines and a plea for systems like Open-Search: decentralized, open and privacy respecting.  Following is an elaborate report and my impression of the two day forum on Quaero.&#60;p /&#62;&#60;div class&#61;&#34;twikiToc&#34;&#62; &#60;ul&#62; &#60;li&#62; &#60;a href&#61;&#34;#Quaero&#34;&#62; Quaero&#60;/a&#62; &#60;/li&#62; &#60;li&#62; &#60;a href&#61;&#34;#Eight&#95;privacy&#95;protecting&#95;demands&#34;&#62; Eight privacy protecting demands&#60;/a&#62; &#60;/li&#62; &#60;li&#62; &#60;a href&#61;&#34;#The&#95;absence&#95;of&#95;Quaero&#34;&#62; The absence of Quaero&#60;/a&#62; &#60;/li&#62; &#60;li&#62; &#60;a href&#61;&#34;#Search&#95;engines&#95;their&#95;borders&#95;and&#34;&#62; Search engines, their borders, and appropriation of the image&#60;/a&#62; &#60;/li&#62; &#60;li&#62; &#60;a href&#61;&#34;#Quaero&#95;Uncorporate&#95;Virtual&#95;Terri&#34;&#62; Quaero Uncorporate &#38;amp; Virtual Territories, Real Borders&#60;/a&#62; &#60;/li&#62; &#60;li&#62; &#60;a href&#61;&#34;#Political&#95;Algorithms&#95;Value&#95;Sensi&#34;&#62; Political Algorithms: Value-Sensitive Design&#60;/a&#62; &#60;/li&#62; &#60;li&#62; &#60;a href&#61;&#34;#So&#95;what&#95;is&#95;a&#95;crawl&#95;scrape&#95;index&#34;&#62; So what is a crawl / scrape / index?&#60;/a&#62; &#60;/li&#62; &#60;li&#62; &#60;a href&#61;&#34;#Maps&#34;&#62; Maps&#60;/a&#62; &#60;/li&#62; &#60;li&#62; &#60;a href&#61;&#34;#Blogging&#95;and&#95;searching&#95;as&#95;Self&#95;M&#34;&#62; Blogging and searching as Self-Management under Communicative Capitalism&#60;/a&#62; &#60;/li&#62; &#60;li&#62; &#60;a href&#61;&#34;#Do&#95;engines&#95;have&#95;politics&#95;Do&#95;poli&#34;&#62; Do engines have politics?  Do politics have engines?&#60;/a&#62; &#60;/li&#62; &#60;li&#62; &#60;a href&#61;&#34;#The&#95;semantic&#95;web&#95;with&#95;the&#95;use&#95;of&#34;&#62; The semantic web with the use of a universal ontology or a folksonomy?&#60;/a&#62; &#60;/li&#62; &#60;li&#62; &#60;a href&#61;&#34;#Open&#95;Search&#34;&#62; Open-Search&#60;/a&#62; &#60;/li&#62; &#60;li&#62; &#60;a href&#61;&#34;#Freedom&#95;of&#95;Expression&#95;and&#95;Search&#34;&#62; Freedom of Expression and Search Engines&#60;/a&#62; &#60;/li&#62; &#60;li&#62; &#60;a href&#61;&#34;#The&#95;final&#95;discussion&#34;&#62; The final discussion&#60;/a&#62; &#60;/li&#62;&#60;/ul&#62;  &#60;/div&#62; &#60;p /&#62; &#60;h2&#62;&#60;a name&#61;&#34;Quaero&#34;&#62;&#60;/a&#62; Quaero &#60;/h2&#62; &#60;p /&#62; Quaero is a &#91;...] research and development program which has the goal of developing multimedia and multilingual indexing and management tools for professional and general public applications (such as search engines) (&#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.aii.fr/upload/flb/90/Dossier&#95;de&#95;presse&#95;1146047080747.pdf&#34;&#62;1&#60;/a&#62;).  Initiated by the French ,Quaero aimed to be a European backed project but in 2006 Hartmut Schauerte, a state secretary within the &#91;German] Ministry for Economics and Labour, announced during the IT-Gipfel summit in Potsdam that a German consortium has put together a semantic search project called Theseus that will be distinct from Quaero (&#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.heise.de/newsticker/meldung/82708/from/rss09&#34;&#62;2&#60;/a&#62;).  The main source of disagreement was the format of the search engine, with German engineers favoring a text-based search engine and the French engineers favoring a multimedia search engine. Many German engineers also balked at what they thought was becoming too much of an anti-Google project, rather than a project driven by its own ideals (&#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.iht.com/articles/2007/01/02/business/search.php&#34;&#62;3&#60;/a&#62;). &#60;p /&#62; &#60;h2&#62;&#60;a name&#61;&#34;Eight&#95;privacy&#95;protecting&#95;demands&#34;&#62;&#60;/a&#62; Eight privacy protecting demands &#60;/h2&#62; &#60;p /&#62; The first presentation at the public forum on Quaero was by Michael Zimmer, who did his Phd on &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.michaelzimmer.org/dissertation&#34;&#62;The Quest for the Perfect Search Engine: Values, Technical Design, and the Flow of Personal Information in Spheres of Mobility&#60;/a&#62;.  In his talk Michael  explained the goals of Google by using some of their quotes: &#34;process and understand all the information in the world&#34; and &#34;understand exactly what you mean and give back what exactly what you want&#34;.  In search engine talk this would be called &#39;perfect reach&#39; for the former and &#39;perfect recall&#39; for the latter.  Google summarizes this when they state that they want to be &#34;like the mind of God&#34;.  Michael went on to say that personal data which was previously obscure is now searchable, and that Google collects as much information as possible about the searcher through server logs, cookies and user accounts.  However, Google does not only have a search engine but also a plenitude of other product and services, of which the information is of course combinable with that gathered by offering search.  The perfect search thus promises breadth, depth, efficiency, and relevancy but you lose &#39;security via obscurity&#39; and it involves the widespread capture of personal and intellectual information.  Michael Zimmer calls this the &#39;Faustian Bargain&#39;.  Quaero&#39;s perfect search would involve and combine sound, image and video search.  To show one of the dangers of perfect multimedia search, Michael showed a series of pictures with automagically identified faces.  The most salient of those was the one where protesters of a surveillance protest were algorithmically identified.  After showing us a lot of threats of perfect search, Michael Zimmer argued for value-conscious design and stated &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://michaelzimmer.org/2007/09/29/privacy-and-quaeros-quest-for-the-perfect-search-engine-threats-and-opportunities/&#34;&#62;eight privacy protecting demands&#60;/a&#62;. (&#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://michaelzimmer.org/files/Zimmer&#37;20Quaero&#37;20slides.pdf&#34;&#62;4&#60;/a&#62;)  He called upon all people from Quaero in the audience to really think about this.  Unfortunately nobody from Quaero attended the conference &#8230; &#60;p /&#62; &#60;h2&#62;&#60;a name&#61;&#34;The&#95;absence&#95;of&#95;Quaero&#34;&#62;&#60;/a&#62; The absence of Quaero &#60;/h2&#62; &#60;p /&#62; In the conference booklet was an email discussion between the organization and the director of the French Quaero&#174; program.  The director tried to convince the organization not to use the name Quaero because &#39;The event announced by Jan van Eyck mentions the Quaero program and uses the Quaero name without endorsement by the Quaero program partners&#39;.  &#39;Quaero aims &#8211; just &#8211; at a series of industrial and technological objectives&#39;, and therefor he was also not interested in the forum because he has &#39;no authority on cultural, political and philosophical aspects of search engines&#39;.  He would &#39;rather leave these aspects to the people with strong convictions in these areas&#39;.  And that was a pity because according to the organization &#39;One could see this Forum as the democratic counterpart to a strategy session&#39; and for a democracy to work you have to hear different opinions. &#60;p /&#62; &#60;h2&#62;&#60;a name&#61;&#34;Search&#95;engines&#95;their&#95;borders&#95;and&#34;&#62;&#60;/a&#62; Search engines, their borders, and appropriation of the image &#60;/h2&#62; &#60;p /&#62; Although the industrial and technological actors in Quaero were absent, we continued our democratic obligation to investigate the politics of search engines with a presentation by &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.debalie.nl/persoon.jsp?personid&#61;17941&#34;&#62;Florian Schneider&#60;/a&#62; (no, not the guy from Kraftwerk).  Florian had a very interesting though difficult talk.  In the following paragraphs I tried to reproduce Florian&#39;s arguments from my notes.  I hope the idea gets through  &#60;p /&#62; Florian investigated the circularity between knowledge and power and analyzed the correspondences between migration machines (border control or management), as an ongoing attempt to control freedom of movement on the one hand, and how it corresponds to management and emergence of new information regimes on the other.   &#60;p /&#62; Florian sees search engine technology as an attempt to image knowledge.  In the digital world an image is understood as an exact replication of any kind of information.  A search engine however is not a backup but a snapshot / image of some of the information.  The question then is who decides when, how, and what kind of information is stored.   &#60;p /&#62; When using a search engine we experience it as something that produces an image.  The result of a query is a meta design.  The results are reduced to a matter of graphical design; it needs to be functional and aesthetic at the same time.  The search engine has a clearly defined purpose with a manufacturing process that is hidden to the user.  The crucial point is the algorithm (the manufacturing), which is hidden to user and consists of the management of the algorithm. &#60;p /&#62; The search engine is sort of an interface for what one would call a mirror by e.g. googling yourself or search engine optimization.  This constitutes the paradigm of imaginary order, a subject is permanently captured and formed by its own image.  Search engines thus deal in imaginary property.  But what does it mean to &#39;own&#39; such an image?  The question is not so much who is owning the image but what it &#39;means&#39; to own an image.  This actually addresses privacy to theoretical reconsiderations of what an image is in an area of digital reproduction.  In a purely Kantian sense: it&#39;s a matter of imagination.   &#60;p /&#62; The manufacturing (the algorithm) is involved in an act of determining space and time, as a rule of production.  It is defined by the way in which the search engine is built and installed, and forms the objects that are supposed to be spidered, crawled, and stored.  Search engines then appropriate this image as their property.  The conservation of this image is subject to invariant operations &#8211; of the algorithm.  The images might be results of structures for imaginations.  Images then manage the violations rather than prevent them from the environment.  The question of ownership has turned into executions in real-time.  It&#39;s not only facial recognition &#8211; solutions are executed in real time.   &#60;p /&#62; A question which pops up is then: Who has the right to read write and access this image / property.  Google claims ownership but is not owning up.  Now there is a quite dramatic shift in the concept of property.   &#60;p /&#62; As the migrant new economy was build on illegalized migrants, according to Florian Schneider, web 2.0 is based on the imaginary revenue.  This also means legalizing content.  Valorization is built on immediate appropriation of content and building imaginary content from it.  The arrival of search engines clearly corresponds with the migrant wave in the 20th century.   The post-modern border machine appears as a system of control with constant modulation of rights that are transformed in a set of permissions.  The border thus becomes a matter of performance.   &#60;p /&#62; The function of post-modern border management is to illegalize migration.  Migrants are allowed in as long as it is &#39;useful labor force&#39;.  When translated to search engines, they operate in corresponding vain.  The question is about imaginary property and it&#39;s valorization.   It is important to see their borders, e.g. Google only indexes 10 to 15&#37; of the &#39;surface web&#39;.  But how can you border the WWW?  The question what is included / excluded remains.  Is the WWW in principle limitless or do you want to border the territory so you can assure information is found?  Behind the surface web there is a deep web, and before a query happens there is a certain quadrage of imaginary that defines territory or maps it out.  Every search engine has to manage what is on and what is of.  Censorship appears as a constant modulation in real time; this ranges from China to ignoring everything that is not text. &#60;p /&#62; Searching thus is an act of imagination.  Finding is not the opposite of missing.  We rewrite imagination in the same way as we rewrite the future &#8211; when you actually find something.  There is a delicate relationship between searching and measuring.  Searching needs a measurement on what is accessible and therefor &#60;em&#62;could&#60;/em&#62; be found.  &#34;I am not searching what i know that i need to find.  I am searching for what i do not yet know that i want to find.&#34;  The success of a search engine can be explained as an abstract machine which processes and colonizes (our power to) imagination. &#60;p /&#62; We need to form new forms of autonomy in new forms of society of control.  Search engines are misfunctional, success is build on misuse, search is appropriating the right to misuse.  p2p access to cultural heritage is already available and re-appropriated by the mass.  The problem of Europe and the European search engine is controlling and managing of what can be imagined as European.   &#60;p /&#62; Clearly, Florian Schneider&#39;s notion of border, the indexable, and the imaginary are very important concepts in an attempt to understand the politics of search engines. &#60;p /&#62; Richard Rogers asked how this image could be described.  You got the original, the copy, and &#8230; the third object?  How does one think about and deals with this &#39;third object&#39;?  How can you justify the ownership of it? &#60;p /&#62; &#60;h2&#62;&#60;a name&#61;&#34;Quaero&#95;Uncorporate&#95;Virtual&#95;Terri&#34;&#62;&#60;/a&#62; Quaero Uncorporate &#38;amp; Virtual Territories, Real Borders &#60;/h2&#62; &#60;p /&#62; &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.metahaven.net&#34;&#62;Metahaven&#60;/a&#62;, designers by origin, showed various newly designed logos for Quaero,  thereby wondering what the characteristics of a good search engine should be.     The second part of the presentation was about a sketch of a layered 3D interface that visualized the isolation within search results.  Unfortunately I was very tired and I did not pick up much from their presentation.  My apologies.   &#60;p /&#62; &#60;h2&#62;&#60;a name&#61;&#34;Political&#95;Algorithms&#95;Value&#95;Sensi&#34;&#62;&#60;/a&#62; Political Algorithms: Value-Sensitive Design &#60;/h2&#62; &#60;p /&#62; Tsila Hassine showed us the Image Tracer and Schmoogle.   &#60;p /&#62; The &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.geuzen.org/tracer/&#34;&#62;Image Tracer&#60;/a&#62; is a collaborative project between Tsila Hassine and &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.geuzen.org&#34;&#62;De Geuzen&#60;/a&#62;. It evolved out of their interests in media images and the way their significance and presence fluctuate in the ecology of the world wide web.  It is built on top of Google Images and grabs images each day for a particular query.  Image density builds and wanes through time, reflecting how long or little, a jpeg, gif or png has been online and how its rank shifts over time. Opacity denotes the consistent presence and position of an image through multiple searches, while more transparent or murky images have appeared for less time or moved in rank.  (&#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.geuzen.org/?page&#95;id&#61;89&#34;&#62;5&#60;/a&#62;) &#60;p /&#62; &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.geuzen.org/cgi-bin/shmoogle/shmoogle&#95;form.cgi&#34;&#62;Schmoogle&#60;/a&#62; also lives on top of Google.  For each query it fetches all 1000 results which are returned by Google.  Instead of displaying it in the order (with the rank) Google gives them, they randomly reorder the results.  This way they question and critique the ranking algorithm of Google.  What &#39;if the result you were looking for was hiding in page 53?&#39; &#60;p /&#62; &#60;h2&#62;&#60;a name&#61;&#34;So&#95;what&#95;is&#95;a&#95;crawl&#95;scrape&#95;index&#34;&#62;&#60;/a&#62;&#60;a name&#61;&#34;So&#95;what&#95;is&#95;a&#95;crawl&#95;scrape&#95;index&#95;&#34;&#62;&#60;/a&#62; So what is a crawl / scrape / index? &#60;/h2&#62; &#60;p /&#62; At the end of the first day Ingmar Weber did some hands on demonstrations of various aspects of building a search engine.  By using the free software program &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.httrack.com/&#34;&#62;HTTrack&#60;/a&#62; Ingmar started to crawl some websites, excluding the tld .org.  This way he showed us the importance of starting-points, the design decisions of how and what to crawl (depth, outdegree, inclusion/exclusion), the resulting found websites and how a reversed index is built &#8211; everybody has encountered it as the word/concept index in a book.  Ingmar then went on to demonstrate other kinds of search engines such as the p2p search engine yacy and the human search engine chacha.com.  The latter was very funny, as Joris van Hoboken told us that most of the operators actually use Google to find information. &#60;p /&#62; &#60;h2&#62;&#60;a name&#61;&#34;Maps&#34;&#62;&#60;/a&#62; Maps &#60;/h2&#62; &#60;p /&#62; The next day started of with &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://utangente.free.fr/index2.html&#34;&#62;Bureau d&#39;etudes&#60;/a&#62; who presented a beautiful map on Quaero.  Unfortunately the map is not online (yet?) so I will not discuss it now, as it would not make any sense. &#60;p /&#62; &#60;h2&#62;&#60;a name&#61;&#34;Blogging&#95;and&#95;searching&#95;as&#95;Self&#95;M&#34;&#62;&#60;/a&#62; Blogging and searching as Self-Management under Communicative Capitalism &#60;/h2&#62; &#60;p /&#62; On &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://netzmedium.de/2007/10/02/questioning-quaero/&#34;&#62;netzmedium.de&#60;/a&#62; a good summary of Jodi Deans&#39; presentation has been written, so I will quote it here:   &#60;p /&#62; &#60;blockquote&#62; &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://jdeanicite.typepad.com/&#34;&#62;Jodi Dean&#60;/a&#62; presented an interesting comparison between blogs and search engines. From a psychoanalytical perspective, she interpreted both phenomena as an answer to anxieties associated with a chaotic and unstructured information space. Based on algorithmic ranking, search engines promise an objective ordering of this space and introduce an element of purity and immaculacy. Blogs, on the other hand, act as guides in the information space by presenting a strictly individual view. Dean portrays them as &#38;#8220;technologies for managing distributed subjectivities&#38;#8221;. &#60;/blockquote&#62; &#60;p /&#62; &#60;h2&#62;&#60;a name&#61;&#34;Do&#95;engines&#95;have&#95;politics&#95;Do&#95;poli&#34;&#62;&#60;/a&#62; Do engines have politics?  Do politics have engines? &#60;/h2&#62; &#60;p /&#62; Next up was &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.govcom.org&#34;&#62;Richard Rogers&#60;/a&#62;.  He had 4 case studies at hand.   &#60;p /&#62; First was the demise of the expert libraries.  Using the &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.waybackmachine.org&#34;&#62;wayback machine&#60;/a&#62; Richard found out that the directory disappeared from the web.  Google, in its early days, had one accessible on the front page.  Through the years however you had to click through more and more until it finally disappeared. &#60;p /&#62; Second was the &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://mastersofmedia.hum.uva.nl/2007/09/28/911truthorg-dissappears-from-google/&#34;&#62;disappearance of 911truth.org from Google&#39;s result page for the query &#39;9/11&#39;&#60;/a&#62;, while it used to have a prominent place in the top 5 in the months before.  Although there is no clear reason about the disappearance (is it a result of manual censorship? Is it a violation of Google&#39;s term and conditions by e.g. SEO?), it does not make it less disturbing.   Because Google&#39;s ranking is a secret, there is no way of finding out why it happened &#8211; which is one of the most problematic aspects of the current search engines in an era where access to information is largely controlled by one company. &#60;p /&#62; After giving us an insight into the politics of search engines, Richard Rogers turned to the question whether politics have engines.  To illustrate this he showed two examples, researched by the &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://dmi.mediastudies.nl&#34;&#62;Digital Methods Initiative&#60;/a&#62;.  Quoting from their &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://wiki2.issuecrawler.net/twiki/bin/view/Dmi/MethodsByTheme#Source&#95;Distance&#34;&#62;source distance project&#60;/a&#62;: &#60;blockquote&#62;The focus here is on the prominence of particular sources in different spheres (e.g. blogosphere, news sphere, images), according to different devices (e.g. Google, Technorati, del.icio.us). For example, how far are climate change skeptics from the top of the news? For comparison sake, how far are they from the top of search engine returns? The answer to this and similar &#39;cross-spherical&#39; inquiries goes a way towards answering the question about the quality of old versus new media.&#60;/blockquote&#62; &#60;p /&#62; By searching climate change skeptics in the top 100 Google sites for the query &#39;Climate Change&#39;,  Richard Rogers noted that &#34;There is distance between the skeptics and the top of the search engine returns. &#91;...] few skeptics appear on the Websites of the top ten results in Google. When they do appear (Patrick Michaels, Steven Milloy) their resonance is not particularly resounding.  &#91;...] From the visualization one is able to see the &#39;skeptic-friendly&#39; sources, realclimate.org and, to a lesser extent, climatescience.gov stand out as skeptic-friendly. Sourcewatch also is prominent, albeit as a progressive watchdog group &#39;exposing&#39; the skeptics.  Remarkably, news sites, generally speaking, do not mention the climate change skeptics by name. Whilst news watchers and listeners may have the impression that &#39;uncertainty&#39; in the climate change &#39;debate&#39; continues in a general sense (as opposed to, say, in more specific, scientific sub-discussions), &#39;uncertainty&#39; appears to be discussed without resort to the well-known, or identified, skeptics.&#34; (&#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://wiki2.issuecrawler.net/twiki/bin/view/Dmi/ClimateChangeSkeptics#Findings&#34;&#62;6&#60;/a&#62;) &#60;p /&#62; His last example concerned which animals associated with climate change, &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://wiki2.issuecrawler.net/twiki/bin/view/Dmi/IssueImageAnalysis&#34;&#62;issue animals&#60;/a&#62;, were represented in different spheres.  It turned out Google, Google News, and Technorati present a whole different &#39;image&#39; about which animals are referred to a lot in the climate change debate. &#60;p /&#62; &#60;h2&#62;&#60;a name&#61;&#34;The&#95;semantic&#95;web&#95;with&#95;the&#95;use&#95;of&#34;&#62;&#60;/a&#62; The semantic web with the use of a universal ontology or a folksonomy? &#60;/h2&#62; &#60;p /&#62; Florian Cramer declared all attempts at creating universal classification schemes (ontologies) futile. To say rephrase his arguments in the words of Theodor Nelson, who coined the term Hypertext: &#60;blockquote&#62;Last week&#39;s categories, perhaps last night&#39;s field, may be gone today. &#91;...] &#60;em&#62;The&#60;/em&#62; categories are chimerical (or temporal) and our categorization systems must evolve as they do.  Information systems must have &#60;em&#62;built in&#60;/em&#62; the capacity to accept the new categorization systems as they evolve from, or outside, the framework of the old. (&#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://portal.acm.org/citation.cfm?id&#61;800197.806036&#34;&#62;7&#60;/a&#62;), emphasis by the author. &#60;/blockquote&#62;  &#60;p /&#62; Florian illustrated this with historical material, but his real target was the German &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://theseus-programm.de&#34;&#62;Theseus initiative&#60;/a&#62;, which seeks to develop AI-like tools for &#38;#8220;automated logical deduction&#38;#8221;.  Florian sees folksonomies as more promising then ontologies.   &#60;p /&#62; &#60;h2&#62;&#60;a name&#61;&#34;Open&#95;Search&#34;&#62;&#60;/a&#62; Open-Search &#60;/h2&#62; &#60;p /&#62; My presentation can be found on &#60;a href&#61;&#34;http://www.open-search.net/Opensearch/QuaeroTalk&#34; target&#61;&#34;&#95;top&#34;&#62;http://www.open-search.net/Opensearch/QuaeroTalk&#60;/a&#62;  In this talk I explained what the problem with the current search engines is, according to Open-Search: because the control over information is central and nobody can look into their algorithms or decisions, it is susceptible to censorship, manipulation and profiling.  Getting out the central part and making it open would solve a lot of problems.  We believe this is possible through an open source p2p project.  Of course there are a lot of challenges as well: spam, efficient query propagation, etcetera, but most of all we haven&#39;t had time to build a community and we do not have the time nor money to put a lot of continued effort in the development of Open-Search. &#60;p /&#62; Richard Rogers had some constructive comments for Open-Search. &#60;p /&#62; &#60;strong&#62;Manipulation vs. spam&#60;/strong&#62; &#60;p /&#62; &#60;em&#62;Normally search engine companies argue that their logics are closed and not transparent, because if they were open, the search would be open to spamming and manipulation. In the presentation, you have that you strive to be open about the logics, but have no answer yet for spam. search engine companies already have an answer. Yours?&#60;/em&#62; &#60;p /&#62; My first answer would be the one from &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://wiki.apache.org/nutch/FAQ#head-58c08bdc65a929eb4ba2688827938685963a817c&#34;&#62;Nutch&#60;/a&#62;:  &#60;blockquote&#62;Search engines work hard to construct ranking algorithms that are immune to manipulation. Search engine optimizers still manage to reverse-engineer the ranking algorithms used by search engines, and improve the ranking of their pages. For example, many sites use link farms to manipulate search engines&#39; link-based ranking algorithms, and search engines retaliate by improving their link-based algorithms to neutralize the effect of link farms.   &#60;p /&#62; With an open-source search engine, this will still happen, just out in the open. This is analagous to encryption and virus protection software. In the long term, making such algorithms open source makes them stronger, as more people can examine the source code to find flaws and suggest improvements. Thus we believe that an open source search engine has the potential to better resist manipulation of its rankings.&#60;/blockquote&#62; &#60;p /&#62; A second answer would be that because people can devise their own ranking plug-in&#39;s with different ranking schemes,  it would be harder to manipulate and spam them. &#60;p /&#62; &#60;strong&#62;Personalization vs. tribalism&#60;/strong&#62; &#60;p /&#62; &#60;em&#62;With plug-in&#39;s people can choose their own ranking algorithm, and thus can personalize results. Classically, there is the idea that shared media experiences (people seeing similar things) make society &#8212; i.e., commonality in exposure but different views about what it all means (cf. community, which is different). Personalization, however, creates tribes, hate groups privileging other hate sites and their results, dictatorial regimes privileging &#39;official&#39; sites. Search engines claim a kind of egalitarianism (indexing the &#39;whole web&#39;), but then ranking according to authority. Yours?&#60;/em&#62; &#60;p /&#62; Search engines might claim a kind of egalitarianism but this is not because of indexing the whole web.  &#60;a href&#61;&#34;http://www.open-search.net/Blog/BlogEntry25#Search&#95;engines&#95;their&#95;borders&#95;and&#34; class&#61;&#34;twikiAnchorLink&#34;&#62;Florian Schneider&#39;s presentation&#60;/a&#62; for example has questioned the &#39;borders&#39; of the database and index of a search engine.  There is also the tendency of search engines to localize and personalize, e.g. iGoogle serving results which are specifically tailered to you (recall also perfect recall from &#60;a href&#61;&#34;http://www.open-search.net/Blog/BlogEntry25#Eight&#95;privacy&#95;protecting&#95;demands&#34; class&#61;&#34;twikiAnchorLink&#34;&#62;Michael Zimmer&#39;s talk&#60;/a&#62;), or a specific country version of a particular search engine.    One might also be tempted to talk about an &#39;objective&#39; ordering but there are enough &#60;a href&#61;&#34;http://www.open-search.net/Opensearch/WhyOpenSearch&#34; target&#61;&#34;&#95;top&#34;&#62;examples&#60;/a&#62; that prove the current ranking schemes of the big search engines are not that objective at all.  &#60;p /&#62; The shared media experience that makes society is already diffusing by the broading offer of information channels via internet and interactive television.  Of course personalization of the current engines also adds to the decline of the shared media experience.   &#60;p /&#62; One might think a p2p engine like Open-Search has the danger of tribalism and segregation because your peers might not &#39;know&#39; as much as somebody else&#39;s peers.  At the level of the search engine however, there are no peers. To the open-search engine, the p2p layer is an abstraction of a generic storage device, a database. It is assumed that each peer will have access to the entire database at all times, regardless of which peers connect to which peers. We are not using a flooding model, as does e.g. Soulseek. &#60;p /&#62; &#60;h2&#62;&#60;a name&#61;&#34;Freedom&#95;of&#95;Expression&#95;and&#95;Search&#34;&#62;&#60;/a&#62; Freedom of Expression and Search Engines &#60;/h2&#62; &#60;p /&#62; &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.jorisvanhoboken.nl/&#34;&#62;Joris van Hoboken&#60;/a&#62; has been interested in Open-Search from the beginning.  I invited him to do a presentation with me.  Joris is a Phd student whose research concerns regulation problems in search engines.  On the public forum on Quaero he gave a short presentation on the implications for freedom of expression for search engine law and government involvement in particular.  There are three actors on which you can focus regarding freedom of expression and search engines: the search engine, the information provider, and the user.  From the user&#39;s perspective &#34;Freedom of expression in the context of Internet search implies that a search engine has to make its index and ranking machinery openly available for its end users of various kinds to support free (not as in gratis) access to information.  (user becomes the real search engine editor).&#34; &#60;p /&#62; &#60;h2&#62;&#60;a name&#61;&#34;The&#95;final&#95;discussion&#34;&#62;&#60;/a&#62; The final discussion &#60;/h2&#62; &#60;p /&#62; Two days of conference raised a lot of critique on privately owned centralized search engines.  Questions about the borders of indexed information, access to and control over information, objectivity in ranking, and concerns about privacy led the participants to favor a system like Open-Search.  Open-Search and similar systems however, are in its infancy &#8211; a lot of problems still need to be solved technically and politically. &#60;p /&#62; Jodi dean has a &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://jdeanicite.typepad.com/i&#95;cite/2007/09/still-more-quae.html&#34;&#62;great post&#60;/a&#62; about the final discussion, which I quote here: &#60;p /&#62; &#60;blockquote&#62; The conference closed on a shockingly optimistic and unified note &#91;...] Why such a great note? Likely because of three crucial interventions that resulted in the sense of a politics around P2P/open search, a politics that would assert the failures and limits of a search (foregoing the knowledge claims of a god/subject supposed to know and thus attempting to divert transferential investments into authority) engine. This could seem counter-intuitive. Who wants a search engine that doesn&#39;t claim to be reliable, thorough, and objective? Perhaps those who recognize that there is no such search engine and take responsibility for this limited, partial, and shared knowledge. The three interventions: &#60;p /&#62; Florian Schneider directly politicized open search. It had been implicit in the discussion, but he made it explicit and political. He also used the term exodus as a kind of movement constitutive of the political. &#60;p /&#62; Daniel van der Velden rendered exodus as more of a decision, and thus as requiring a kind of awareness or even consciousness (which makes the projects demonstrating the failures and interventions of google--which doesn&#39;t live up to its anti-evil ideals--all the more important). &#60;p /&#62; For me, these two ideas seemed to conflict. There is hardly an exodus from google, rather the opposite--the problem is the way people flock to it, rely on it--like Wal-Mart and McDonalds. &#60;p /&#62; But Florian Cramer traversed this dilemma, refused the false choice--and gave a rousing speech that all agreed marked an appropriate end point for this phase of the conversation. So, he said that exodus is a metaphor, with limits, and that exodus can&#39;t mean here anything like a kind of neo-luddite movement/moment. And, he refused the demand for an image. More specifically, he said that the very question of &#39;what would a European search engine look like&#39; should be eliminated (for good techie reasons involved API, available public interface). There isn&#39;t one answer, one image, one model. &#60;p /&#62; This fits well with the theme of the imaginary that I took from the conference. It accepts neither the imaginary, nor calls for a symbolic (name, authority, law). It traverses these with a different kind of accountability (clearly not quite ready for release, but maybe soon in beta). Maybe this is something like an act in information politics. &#60;p /&#62; And, if information is value and search engines add, create, and arrange value, what sort of value would P2P search engines create? &#60;/blockquote&#62; &#60;p /&#62; To me it was a great forum.  A lot of interesting intellectuals shared their thoughts and theories about search engines.  It gave me a lot of inspiration and deepened my conceptualization about the politics of search engines.  I hope that this group of researchers goes on with the problematique and that follow-up conferences are organized.  Further discussion of the pitfalls and benefits of a system like Open-Search is encouraged to take place in the comments and on the &#60;a href&#61;&#34;http://www.open-search.net/Opensearch/MailingLists&#34; target&#61;&#34;&#95;top&#34;&#62;mailing lists&#60;/a&#62;. &#60;p /&#62; &#60;p /&#62;&#60;b&#62;Tags&#60;/b&#62;: &#60;a href&#61;&#34;http://www.open-search.net/Blog/BlogArchive?mode&#61;tag&#38;amp;search&#61;quaero, information politics, search, google&#34; rel&#61;&#34;tag&#34;&#62;quaero, information politics, search, google&#60;/a&#62; </description>
 <dc:creator>ErikBorra</dc:creator>
 <dc:date>2007-10-03T13:38:00Z</dc:date>
 <dc:subject>UsersChat</dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/ErikBorra">
 <rdf:value>ErikBorra</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry24">
 <title>Google censors 911truth.org</title>
 <link>http://www.open-search.net/Blog/BlogEntry24</link>
 <description> In a well documented case of censorship, google again shows its true meaning of &#34;don&#39;t be evil&#34;.&#60;p /&#62;In a university blog, open-search suspect Erik Borra &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://mastersofmedia.hum.uva.nl/2007/09/28/911truthorg-dissappears-from-google/&#34;&#62;writes about the decline and final demise of 911truth.org&#60;/a&#62;. in google search results. On 911truth.org, it has become apparent that &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.911truth.org/article.php?story&#61;2007092200814732&#34;&#62;several readers have noticed the disappearance of 911truth.org from google&#60;/a&#62;. &#60;p /&#62; Google attracted more bad press, with &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://it.slashdot.org/it/07/09/27/167249.shtml&#34;&#62;the recent gmail vulnerabilities&#60;/a&#62; also posing a serious threat to users of google services.&#60;p /&#62;&#60;b&#62;Tags&#60;/b&#62;: &#60;a href&#61;&#34;http://www.open-search.net/Blog/BlogArchive?mode&#61;tag&#38;amp;search&#61;google,news&#34; rel&#61;&#34;tag&#34;&#62;google,news&#60;/a&#62; </description>
 <dc:creator>KoenMartens</dc:creator>
 <dc:date>2007-09-28T12:58:00Z</dc:date>
 <dc:subject>UsersChat</dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/ErikBorra">
 <rdf:value>ErikBorra</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry23">
 <title>Open-search to participate in Forum On QuaerO</title>
 <link>http://www.open-search.net/Blog/BlogEntry23</link>
 <description> Open-search is asked to participate in a public think tank on the politics of the search engine. The forum is brought together by Quaero, a consortium of technology firms and research labs working together on multimedia and web search projects.&#60;p /&#62;From the &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.janvaneyck.nl/0&#95;2&#95;3&#95;events&#95;info/arc&#95;07&#95;quaero&#95;thinktank.html&#34;&#62;flyer&#60;/a&#62;: &#60;p /&#62; &#34;QUAERO: isn&#39;t that the search engine that former French president Jacques CHIRAC declared to  be the EUROPEAN challenge to Google? A pub-lic alternative to Silicon Valley-born commercial  search engines, funded by the French state, in service of the PUBLIC GOOD, in the true tradition of the GRAND PROJET? An INFORMATION MACHINE capable of reclaiming European LANGUAGE and intellectual HERITAGE in the age of GLOBALIZATION? &#60;p /&#62; NO. Quaero is the name of a CONSORTIUM of technology firms and RESEARCH LABS working  together  on  multimedia  and  WEB  SEARCH PROJECTS.  It  is  a  STATE-SPONSORED  effort  to  stimulate  PRIVATE  French  technological competitiveness. &#60;p /&#62; According to Franc,ois BOURDONCLE, one of its participating developers, `Quaero is definitely  not a project to build a web search engine, it is a project to make significant advances  on the handling and indexing of multimedia content. It is completely out of the question  to build a new, state-owned, state-operated, or even state-funded search engine. Only the  R&#38;amp;D around these cutting-edge multimedia indexing technologies are in the scope of the  project.&#39; &#60;p /&#62; But still, the issues that the idea of Quaero has  raised &#8211; since its public launch by the former French  president  &#8211;  constitute  a  formidable  challenge. Internet search engines are political projects proper if only because they  give  and  take power; they represent science, technology, (trans)national politics, private enterprise, culture, territoriality and language in ever different combinations. They are also social spaces. Internet search, the indispensable public tool that allows one to survey the ever increasing web,   is currently in the hands of only a few global players, to whose private interests its setup corresponds.&#34; </description>
 <dc:creator>KoenMartens</dc:creator>
 <dc:date>2007-09-14T10:26:00Z</dc:date>
 <dc:subject>Project</dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/KoenMartens">
 <rdf:value>KoenMartens</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry22">
 <title>Presentations and Articles</title>
 <link>http://www.open-search.net/Blog/BlogEntry22</link>
 <description> Koen&#39;s has written an article about Google as the Microsoft of the 21st century.  It can be found &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.livre.nl/achtergronden/internet/google-is-de-microsoft-van-de-21ste-eeuw-24052007.html&#34;&#62;here&#60;/a&#62; (in Dutch).  Another interesting (Dutch) article about Google, by Michiel Leenaars from gridnet.nl is &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.webwereld.nl/articles/46452/google-s-verklikkernetwerk.html&#34;&#62;Google&#39;s verklikkernetwerk&#60;/a&#62;. &#60;p /&#62; Apart from developing (see our previous post) we are also very busy giving presentations about open-search.  Last week at &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.versgeperst.info&#34;&#62;versgeperst.info&#60;/a&#62;  Tomorrow at &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.isoc.nl/activ/2007-ALV-juni.htm&#34;&#62;ISOC.nl&#60;/a&#62; and Monday at the &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.hosc.nl/&#34;&#62;Holland Open Source Conference&#60;/a&#62;.  &#60;p /&#62; </description>
 <dc:creator>ErikBorra</dc:creator>
 <dc:date>2007-06-05T16:00:00Z</dc:date>
 <dc:subject>UsersChat</dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/ErikBorra">
 <rdf:value>ErikBorra</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry21">
 <title>some technical details</title>
 <link>http://www.open-search.net/Blog/BlogEntry21</link>
 <description> closing in on the holland open.&#60;p /&#62;Here&#39;s some technical details that we&#39;re gonna reveal in a prototype at the open-holland conference: &#60;p /&#62; &#60;ul&#62; &#60;li&#62; the &#60;em&#62;oscar&#60;/em&#62; peer to peer layer uses a &#60;em&#62;gossip-engine&#60;/em&#62; to multiplex traffic over a single TCP port. &#8211; it also allows to tunnel traffic eg. via HTTP to circumvent firewall, without much performance penalty. &#60;/li&#62;&#60;/ul&#62;  &#60;p /&#62; &#60;ul&#62; &#60;li&#62; in this prototype the data-signing is not part of open-search, but the P2P layer: Every p2p-packet sent or received contains a RSA-SHA; (yielding ~35&#37; overhead at the moment) &#8211; the signature will identify the host responsible for providing the information (not the ID of the Source of the Information ie. crawler or user) &#60;/li&#62;&#60;/ul&#62;  &#60;p /&#62; &#60;ul&#62; &#60;li&#62; only &#34;bad clients&#34; not &#34;annoying users&#34; can be &#60;em&#62;banned&#60;/em&#62; and the ban affect the local open-search-client only, not the whole network. &#60;/li&#62;&#60;/ul&#62;  &#60;p /&#62; &#60;p /&#62; &#60;ul&#62; &#60;li&#62; we&#39;re testing &#38;amp; debugging a crawler with a local perl::DBD database (currently sqlite) &#8211; The SQL interface can be replaced with a p2p layer and is currently used to develop and debug the latter at the moment. &#60;/li&#62;&#60;/ul&#62;  &#60;p /&#62; &#60;p /&#62; &#60;ul&#62; &#60;li&#62;  privacy can be archived as an additional Feature. A user can select &#60;/li&#62;&#60;/ul&#62;  any content of the p2p-network using it&#39;s identifier and checksum to sign it&#39;s content with a private key. A user&#39;s signed content can be referenced ,like any other content in the p2p-network (you can search for it) and it&#39;s up to the end-user-application to make use of it. &#60;p /&#62; &#60;p /&#62;&#60;b&#62;Tags&#60;/b&#62;: &#60;a href&#61;&#34;http://www.open-search.net/Blog/BlogArchive?mode&#61;tag&#38;amp;search&#61;Development&#34; rel&#61;&#34;tag&#34;&#62;Development&#60;/a&#62; </description>
 <dc:creator>RobinGareus</dc:creator>
 <dc:date>2007-06-05T13:50:00Z</dc:date>
 <dc:subject>Development</dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/RobinGareus">
 <rdf:value>RobinGareus</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry20">
 <title>p2p interface</title>
 <link>http://www.open-search.net/Blog/BlogEntry20</link>
 <description> &#60;p /&#62;with the current endeavor to plug a distribted hash table below the open-search-client, here is the protocol used to for communication between the open-search core and the p2p-layer. &#60;p /&#62; the p2p engine will run as separate process, and communication is done via a local TCP socket. for testing and develpment we use two simple perl-scripts (contrib/hatsim) and it will act as a p2p-db simulator. &#60;p /&#62; the protocol is yet rather simple: &#60;p /&#62; we use &#34;++&#34; as separator for ASCII-text encoded arguments. the format is &#60;code&#62;COMMAND&#60;/code&#62; ++ &#60;code&#62;opt-args&#60;/code&#62; ++ &#60;code&#62;HASHED-KEY&#60;/code&#62; ++ &#60;code&#62;XML-VALUE&#60;/code&#62; ++ &#60;p /&#62; example perl-printf&#39;s: &#60;pre&#62; &#34;STORE&#34;.&#34;++&#34;.&#34;&#38;lt;p2p-opt-args&#38;gt;&#34;.&#34;++&#34;.&#34;&#38;lt;HASH&#95;FOR&#95;KEYWORD:&#38;gt;&#34;.&#34;++&#34;.&#34;&#38;lt;XML-LIST-OF-URL&#95;HASH&#38;gt;&#34;.&#34;++&#34;; &#34;STORE&#34;.&#34;++&#34;.&#34;&#38;lt;p2p-opt-args&#38;gt;&#34;.&#34;++&#34;.&#34;&#38;lt;HASH&#95;FOR&#95;URL&#38;gt;&#34;.&#34;++&#34;.&#34;&#38;lt;XML-DATA&#95;FOR-URLS&#38;gt;&#34;.&#34;++&#34;; &#34;LOOKUP&#34;.&#34;++&#34;.&#34;&#38;lt;p2p-opt-args&#38;gt;&#34;.&#34;++&#34;.&#34;&#38;lt;HASH&#38;gt;&#34;  # &#38;rarr; returns either &#38;lt;XML-LIST-OF-URL&#95;HASH&#38;gt; or &#38;lt;XML-DATA&#95;FOR-URLS&#38;gt;  &#60;/pre&#62; &#60;p /&#62; this very simple protocol will be enough for a protptype test implementation. &#8211; the &#38;lt;p2p-opt-args&#38;gt; are yet unused but we forsee a couple of features that would need to pass extra information to the p2p-engine.. &#60;p /&#62; currently packets are gpg signed when they pass tru the p2p layer, using a host-key rather than individual crawler signature. &#8211; also the format of the xml-data is yet unknown to the the p2p layer.  once search-filtering is optimized and parts of it can be done at network-layer, there&#39;ll be a new command &#60;code&#62;STORE&#95;IDX&#60;/code&#62; and a separate LOOKUP functions for different return types. &#8211; it remains to be discussed whether priotity-tags are implemented as optinal-argument or separate command. &#60;p /&#62; &#60;p /&#62; </description>
 <dc:creator>RobinGareus</dc:creator>
 <dc:date>2007-05-23T13:36:00Z</dc:date>
 <dc:subject>BlogDev, Development</dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/RobinGareus">
 <rdf:value>RobinGareus</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry19">
 <title>open-search collaboration</title>
 <link>http://www.open-search.net/Blog/BlogEntry19</link>
 <description> peer to peer to peer&#60;p /&#62;Teased by our 2nd Workshop, Marco Fiscato has jumped aboard our team of developers. His expertise in peer to peer networks and his implementation of a chord based p2p layer will be of great help for prototyping p2p open-search. &#60;p /&#62; This weeks Todo includes a simulator that implements the distributed-database query interface: the simulator (dubbed hatsim) allows to &#34;replay/simulate&#34; crawler &#38;amp; user activity for the P2P software and emulates a dummy p2p to be used for client development. &#60;p /&#62; &#60;p /&#62;&#60;b&#62;Tags&#60;/b&#62;: &#60;a href&#61;&#34;http://www.open-search.net/Blog/BlogArchive?mode&#61;tag&#38;amp;search&#61;blog development news&#34; rel&#61;&#34;tag&#34;&#62;blog development news&#60;/a&#62; </description>
 <dc:creator>RobinGareus</dc:creator>
 <dc:date>2007-05-18T11:50:00Z</dc:date>
 <dc:subject>BlogDev, Project</dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/RobinGareus">
 <rdf:value>RobinGareus</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry18">
 <title>Visiting the enemy camp</title>
 <link>http://www.open-search.net/Blog/BlogEntry18</link>
 <description> So, last friday I had to visit google NL hq for business related matters. It is located near station Amsterdam Zuid, in one of the new buildings in the area that is to become the &#39;south axis&#39;. On ground level, shadow reigned. High-rise buildings obscure the sky, and i doubt the sun will ever reach down to the entrance of the building. At the 15th floor, i was greeted by a NDA that wanted to be signed. After doing so i was allowed to enter the realm of google NL.&#60;p /&#62;It was not very impressing, although the facilities sure are nice and the skippy balls looked inviting. However, as I later learned there are no engineers in this branch of google, just sales and marketing people. &#60;p /&#62; Putting the google bashing aside for a moment, their motto does sound noble: &#8220;organize the worlds&#39; information and make it universally available&#39;&#39;. And when they say information they mean &#60;strong&#62;all&#60;/strong&#62; information. They started out with web indexing, but have moved far beyond that. Google Earth, although scarry, also is a wealth of geographical information. For example, I can just look up the layout of tramway depots in my city, or check out railyard layouts around the world. With just a few clicks and drags. &#60;p /&#62; Their move into the audio-visual world is also an example of making information available to the world. The internet was once, long before youtube, touted as the replacement for traditional broadcasting models. Everyone could now send out their information. But it wasn&#39;t before sites like youtube that indeed everyone did publish their videos. Now, with google video, youtube and the likes, putting your own video online has become so easy that the masses are jumping on it. And google stores and streams this information, free of charge, no strings attached (or are there?). &#60;p /&#62; The problem with all this is that not only do they collect this information, and make it available. They also collect information about who uses what information when (and if possible, with what purpose). Basically, they do this to to improve their services. Let us assume that this is indeed the case. Then there still is a big privacy issue here. Once google has these databases that they can use to build detailed profiles of your interests and behavioural traits, its use can be extended. For example, the US government could claim this database for &#39;homeland security&#39;. Or (remember the AOL debacle), the database or a part thereof could accidentally leak and become available on the internet. Or hackers could gain access to the system and extract information about you. Perhaps to create a false identity, abusing your profile. &#60;p /&#62; Their move into online applications, such as &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://docs.google.com&#34;&#62;google docs &#38;amp; spreadsheet&#60;/a&#62; is especially notable in this respect. Although at first sight, it sounds nice. You don&#39;t need openoffice.org or microsoft office on your computer, you just use your browser to do all your document editting. Store your documents on googles servers and be able to access them from any computer where you can browse the net. &#60;p /&#62; But several problems are apparent: first of all, what happens when your data gets lost? That this is not far-fetched has become apparent recently with the iGoogle mess, where users data was lost. Apparently, they were able to recover the data after-all. But all the same, it could have been lost forever. Imagine this happening to your documents! &#60;p /&#62; But of course, once your documents are on googles servers, they can use them to build an even more detailed profile on you. They can scan these documents, maybe these are letters you write to your insurance company, maybe these are letters to friends or your financial administration in a spreadsheet. All this is then open to the same dangers mentioned before: abuse by governments, identity-theft by criminals and what more. &#60;p /&#62; And if you are unfazed by all this, because you think the government wouldn&#39;t do such things, or that you have nothing to hide, consider what would happen when in 10 years there is a different government, with different priorities. Then you might all of a sudden be the &#39;criminal&#39; they are looking for, and your online profile comes back to bite you!&#60;p /&#62;&#60;b&#62;Tags&#60;/b&#62;: &#60;a href&#61;&#34;http://www.open-search.net/Blog/BlogArchive?mode&#61;tag&#38;amp;search&#61;google&#34; rel&#61;&#34;tag&#34;&#62;google&#60;/a&#62; </description>
 <dc:creator>KoenMartens</dc:creator>
 <dc:date>2007-05-06T19:45:00Z</dc:date>
 <dc:subject></dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/KoenMartens">
 <rdf:value>KoenMartens</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry17">
 <title>post workshop</title>
 <link>http://www.open-search.net/Blog/BlogEntry17</link>
 <description> &#60;p /&#62;first of all: thanks to everyone participating in the open-search workshop! &#60;p /&#62; it&#39;s been less fruitful than expected but a very blooming workshop! Though we did produce some code fragments the major contributions were in discussion and the community building process. &#60;p /&#62; We made contacts with coders outside open-search, in particular we&#39;ve found a candidate from the vrije universiteit to plug a P2P layer in the open-search client. We compiled and tested a first windows version at the workshop, though there is no package yet.  &#60;p /&#62; We&#39;ve received comments from designers &#38;amp; layouters, and also some hands-on design experiments and brainstorm about the user-interface that are to be followed up&#8230; &#60;p /&#62; the road is still long, but the open-search path is on the verge to become a street! stay tuned. &#60;p /&#62; </description>
 <dc:creator>RobinGareus</dc:creator>
 <dc:date>2007-05-01T13:08:00Z</dc:date>
 <dc:subject>Project</dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/RobinGareus">
 <rdf:value>RobinGareus</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry12">
 <title>Second workshop: new contacts, more structure</title>
 <link>http://www.open-search.net/Blog/BlogEntry12</link>
 <description> With the second workshop, we released the alpha version of &#60;a href&#61;&#34;http://www.open-search.net/Software/WebHome&#34; class&#61;&#34;twikiLink&#34;&#62;our search client&#60;/a&#62;. Not much of the projected functionality is present, but it does provide the general framework that will be extended with various plugins. The &#60;a href&#61;&#34;http://www.open-search.net/Opensearch/SecondWorkshop&#34; class&#61;&#34;twikiLink&#34;&#62;second workshop&#60;/a&#62;, next to being the official release event of the client, is also the starting point of more community involvement.&#60;p /&#62;Because that is what we need right now: people who care about the project and want to help out in making it a reality. Our paid developer Robin Gareus will be leaving in one or two months (unless we manage to secure further funding before that time), so the project will have to be able to sustain itself. &#60;p /&#62; Although we do need programmers, there are a lot of other tasks where we could use your help. If you are wondering where you can help out, check out the &#60;a href&#61;&#34;http://www.open-search.net/Opensearch/TechnicalTodo&#34; class&#61;&#34;twikiLink&#34;&#62;TechnicalTodo&#60;/a&#62; and &#60;a href&#61;&#34;http://www.open-search.net/Opensearch/TheoreticalTodo&#34; class&#61;&#34;twikiLink&#34;&#62;TheoreticalTodo&#60;/a&#62;. Also, make sure to subscribe to our discussion mailing list to keep up to date with current efforts. &#60;p /&#62; All in all, the workshop was a succes, despite the low attendance. It was almost a 30 degrees celsius in Amsterdam, not the best weather to sit inside behind a laptop screen. Thanks to all who did come regardless! </description>
 <dc:creator>KoenMartens</dc:creator>
 <dc:date>2007-04-28T14:55:00Z</dc:date>
 <dc:subject>Project</dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/KoenMartens">
 <rdf:value>KoenMartens</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry16">
 <title>workshop ahead.</title>
 <link>http://www.open-search.net/Blog/BlogEntry16</link>
 <description> &#60;p /&#62;we&#39;re currently preparing the talk and topic &#38;amp; slides for the workshop&#8230; &#60;p /&#62; after the keynote it&#39;s gonna be a 3track workshop: &#60;ul&#62; &#60;li&#62; open software philosophy  (legal issues; end-user participation; editing) &#60;/li&#62; &#60;li&#62; web-development (open-search look &#38;amp; feel and desktop integration) &#60;/li&#62; &#60;li&#62; core-development (p2p bindings, search&#38;amp;page ranking) &#60;/li&#62;&#60;/ul&#62;  &#60;p /&#62; we&#39;ll provide a framework to &#34;plug in&#34; code-prototypes that runs on osX and Linux. &#60;p /&#62; It should compile under windows with CYGWin but we do not have access to a MS operating system. Maybe also sth to try at/after the workshop. &#8211; we&#39;ll provide bootable gnu/Linux CDs for participants with a PC. &#60;p /&#62; more later..&#60;p /&#62;&#60;b&#62;Tags&#60;/b&#62;: &#60;a href&#61;&#34;http://www.open-search.net/Blog/BlogArchive?mode&#61;tag&#38;amp;search&#61;news workshop&#34; rel&#61;&#34;tag&#34;&#62;news workshop&#60;/a&#62; </description>
 <dc:creator>Main.RobinGareus</dc:creator>
 <dc:date>2007-04-17T18:00:00Z</dc:date>
 <dc:subject>Project</dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/ErikBorra">
 <rdf:value>ErikBorra</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry7">
 <title>late easter egg</title>
 <link>http://www.open-search.net/Blog/BlogEntry7</link>
 <description> &#60;p /&#62;In the wake of easter we are heading towards the 2nd workshop.. with no public software client it&#39;s gonna be a close call, but after the attached screen-shot we hope to announce an alpha version a week before the workshop. probably already April 19 2007. &#60;p /&#62; Last week has been rather distracting (installing python on our web-server, re-furbishing php and installing mantis on bug.open-search.net) &#8211; and the easter weekend turned out rather sunny which did not aid open-search development after all. &#8211; so without furter ado.. &#60;p /&#62; &#60;div id&#61;&#34;&#34; class&#61;&#34;imageFloat imageFloat&#95;right &#34; &#62;&#60;a href&#61;&#34;/pub/Blog/BlogImages/os-sshot1.png&#34; class&#61;&#34;imageHref&#34; title&#61;&#34;os-sshot1.png&#34;&#62;&#60;img border&#61;&#34;0&#34; align&#61;&#34;middle&#34; src&#61;&#34;/pub/Blog/BlogImages/&#95;250&#95;&#95;&#95;os-sshot1.png&#34; alt&#61;&#34;os-sshot1.png&#34; width&#61;&#34;250&#34; height&#61;&#34;192&#34; longdesc&#61;&#34;os-sshot1.png&#34;  /&#62;&#60;/a&#62;&#60;/div&#62; &#60;p /&#62; &#60;ul&#62; &#60;li&#62; local-webserver: check &#60;/li&#62; &#60;li&#62; cgi-interface: check &#60;/li&#62; &#60;li&#62; AJAX-engine: partly  &#60;/li&#62; &#60;li&#62; design, layout &#38;amp; language support: preliminary. &#60;/li&#62; &#60;li&#62; serach-backend: faked local. &#60;/li&#62; &#60;li&#62; crawler: independant (preliminary perl AND/OR python) &#60;/li&#62; &#60;li&#62; P2P-lib: none  &#8211; exeriments and simulations. (planning to use gnutella for the workshop) &#60;/li&#62;&#60;/ul&#62;  &#60;p /&#62; &#60;p /&#62; current ToDo:  debug and document AJAX api (javascript, xslt);  code a P2P API-wrapper (c, py-bindings) , renice twiki-blog (hammer). &#60;p /&#62; &#60;p /&#62;&#60;b&#62;Tags&#60;/b&#62;: &#60;a href&#61;&#34;http://www.open-search.net/Blog/BlogArchive?mode&#61;tag&#38;amp;search&#61;blog news&#34; rel&#61;&#34;tag&#34;&#62;blog news&#60;/a&#62; </description>
 <dc:creator>RobinGareus</dc:creator>
 <dc:date>2007-04-10T16:00:00Z</dc:date>
 <dc:subject>BlogDev</dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/RobinGareus">
 <rdf:value>RobinGareus</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry4">
 <title>Four months into the project, where are we now?</title>
 <link>http://www.open-search.net/Blog/BlogEntry4</link>
 <description> It has been about four months ago that we started this project off with the support of digital pioneers. So it is time to look back a bit, and look forward.&#60;p /&#62;To start with, we underestimated the amount of work, as our current developer Robin already mentioned in &#60;a href&#61;&#34;http://www.open-search.net/Blog/BlogEntry3&#34; class&#61;&#34;twikiLink&#34;&#62;his blogpost&#60;/a&#62;. We planned on having a beta product ready by the end of april, but that seems unrealistic now. The next days a new planning will be determined, but the goal will still be to present a working product (albeit beta) by the end of our digital pioneers funding. &#60;p /&#62; Another thing we underestimated was the amount of time the volunteers (mainly Erik and me) have to put in to this project to make it a succes. We now finally have something of a project architecture coming together though, as this weblog exemplifies. This weblog also marks the shift of focus from setting up the internal structures to facing outward and getting the community interested.  &#60;p /&#62; Another important step is the registration of the &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://sourceforge.net/projects/open-search/&#34;&#62;sourceforge project space&#60;/a&#62;, where we will shortly be putting online the first snippets of code. &#60;p /&#62; Financially, things are still on budget. That is, if we only look at the original budget. It has become clear that more paid development might very well be necessary. There is not enough of a community yet to take over the project after Robin&#39;s term ends. We therefore need to look into further funding (suggestions are welcome of course). &#60;p /&#62; So, summarizing. We have done a great deal of research and have invested in a solid project infrastructure. Next up is community building and securing continued funding.&#60;p /&#62;&#60;b&#62;Tags&#60;/b&#62;: &#60;a href&#61;&#34;http://www.open-search.net/Blog/BlogArchive?mode&#61;tag&#38;amp;search&#61;progress finance board&#34; rel&#61;&#34;tag&#34;&#62;progress finance board&#60;/a&#62; </description>
 <dc:creator>KoenMartens</dc:creator>
 <dc:date>2007-04-05T14:01:00Z</dc:date>
 <dc:subject>Project</dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/KoenMartens">
 <rdf:value>KoenMartens</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry5">
 <title>We are currently implementing the alpha version of open-search.</title>
 <link>http://www.open-search.net/Blog/BlogEntry5</link>
 <description> We&#39;ll have a blog with more info soon.&#60;p /&#62; </description>
 <dc:creator>ErikBorra</dc:creator>
 <dc:date>2007-04-01T12:00:00Z</dc:date>
 <dc:subject>Project</dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/ErikBorra">
 <rdf:value>ErikBorra</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry8">
 <title>panel on (cyber)dissidents and restrictions at the impakt festival</title>
 <link>http://www.open-search.net/Blog/BlogEntry8</link>
 <description> On March 31 2007, we were part of a panel on (cyber)dissidents and restrictions at the &#60;a href&#61;&#34;http://www.open-search.net/Opensearch/ImpaktPanel&#34; target&#61;&#34;&#95;top&#34;&#62;impakt festival&#60;/a&#62;.&#60;p /&#62;You can find our presentation and extra links and maps in &#60;a href&#61;&#34;http://www.open-search.net/Opensearch/ImpaktPanel&#34; target&#61;&#34;&#95;top&#34;&#62;ImpaktPanel&#60;/a&#62;.  Also Nicholas Dearden&#39;s presentation from irrepressible.info can be found there. </description>
 <dc:creator>ErikBorra</dc:creator>
 <dc:date>2007-04-01T09:47:00Z</dc:date>
 <dc:subject>Project</dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/ErikBorra">
 <rdf:value>ErikBorra</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry3">
 <title>open-search today.</title>
 <link>http://www.open-search.net/Blog/BlogEntry3</link>
 <description> &#60;p /&#62; Besides our enthusiastic kick-off, we slowly gain a more realistic but not pessimistic view on peer-to-peer web-indexing and searching: The upcoming year(s) will bring various PhD theses on that subject, addressing shortcomings of pioneer work, and providing a fundament for next-generation P2P applications. &#60;p /&#62; open-search.net is aiming towards a tightrope walk between academic and real-world appliance.  &#91;NPO, open-source, free -&#38;gt; distinct from software-industry !] &#8211; For the time being,  we feel that we can best provide valuable solutions for issues that are not addressed at University, while refraining from actual research on Peer-to-Peer and resort to existing P2P-implementations. &#60;p /&#62; open-search.net will wrap one or more p2p lib/app and provide a open-source framework to aid development, prototyping, testing and distribution a p2p search-engine. &#60;p /&#62; We split the project into 2 major task-forces: &#60;p /&#62; &#60;ul&#62; &#60;li&#62; (A) API + back-end devel &#60;/li&#62; &#60;li&#62; (B) Community  + front-end &#60;/li&#62;&#60;/ul&#62;  &#60;p /&#62; &#60;p /&#62; &#60;h1&#62;&#60;a name&#61;&#34;A&#34;&#62;&#60;/a&#62;&#60;a name&#61;&#34;&#95;A&#95;&#34;&#62;&#60;/a&#62; (A) &#60;/h1&#62; It is still one of our goals to povide the core in POSIX-C but it feels much more realistic to glue P2P libraries and search cores via local sockets and provide an API to bind crawlers, P2P-storage and data-processing to other programming languages. &#60;p /&#62; (using java itself introduces latencies which are an order of magnitude larger that a local-socket API. Python, perl or haskell bindings might come in handy.) &#60;p /&#62; The framework comprises a simple HTTP server, open-search configuration and session management, and API abstration to manage search-requests/results wrapped in a installable package. &#60;p /&#62; The database to store the index, will evolve from static-file, via a dynamic query interface (forward queries to other search-engines) to a P2P example implementation (eg. using gnutella &#38;amp; existing torrents). well use the opensearch and other XML based import/export mechanisms. &#60;p /&#62; p2p is not yet ready for a commercial grade search engine: thus flexibility and rapid prototyping are to be focused on! &#60;p /&#62; &#60;p /&#62; &#60;h1&#62;&#60;a name&#61;&#34;B&#34;&#62;&#60;/a&#62;&#60;a name&#61;&#34;&#95;B&#95;&#34;&#62;&#60;/a&#62; (B) &#60;/h1&#62; different audiences: &#60;ul&#62; &#60;li&#62; devels (core + framework) &#60;/li&#62; &#60;li&#62; devels (serach + p2p) &#60;/li&#62; &#60;li&#62; desigeners + front-end devels &#60;/li&#62; &#60;li&#62; testers and users &#60;/li&#62; &#60;li&#62; privacy &#8211; part of the open-search frameworks API. &#60;/li&#62; &#60;li&#62; anonymity &#8211; separate layer (eg. TOR) &#8211; check p2p lib. support &#60;/li&#62;&#60;/ul&#62;  &#60;p /&#62;&#60;b&#62;Tags&#60;/b&#62;: &#60;a href&#61;&#34;http://www.open-search.net/Blog/BlogArchive?mode&#61;tag&#38;amp;search&#61;blog development news&#34; rel&#61;&#34;tag&#34;&#62;blog development news&#60;/a&#62; </description>
 <dc:creator>RobinGareus</dc:creator>
 <dc:date>2007-03-13T10:54:00Z</dc:date>
 <dc:subject></dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/RobinGareus">
 <rdf:value>RobinGareus</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry2">
 <title>missing feb 29 this year!</title>
 <link>http://www.open-search.net/Blog/BlogEntry2</link>
 <description> open-search development is slightly behind schedule!&#60;p /&#62;I eventually received the book &#34;Peer-to-Peer-Systems and Applications&#34; and there&#39;s no doubt that priorities will shift a little over the next days.  &#60;p /&#62; we should have read that before writing our proposal, but it was worth the learning experience&#8230; &#60;p /&#62; good thing is: we made our March 1st deadline to install the blog plugin! &#60;p /&#62; cheers, robin&#60;p /&#62;&#60;b&#62;Tags&#60;/b&#62;: &#60;a href&#61;&#34;http://www.open-search.net/Blog/BlogArchive?mode&#61;tag&#38;amp;search&#61;news, development blog&#34; rel&#61;&#34;tag&#34;&#62;news, development blog&#60;/a&#62; </description>
 <dc:creator>RobinGareus</dc:creator>
 <dc:date>2007-02-28T16:19:00Z</dc:date>
 <dc:subject>Development, UsersChat</dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/RobinGareus">
 <rdf:value>RobinGareus</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry9">
 <title>We made a new face for the website.</title>
 <link>http://www.open-search.net/Blog/BlogEntry9</link>
 <description> The credits and idea can be found &#60;a href&#61;&#34;http://www.open-search.net/Opensearch/OpensearchDesign&#34; target&#61;&#34;&#95;top&#34;&#62;here&#60;/a&#62;&#60;p /&#62; </description>
 <dc:creator>ErikBorra</dc:creator>
 <dc:date>2007-02-14T10:19:00Z</dc:date>
 <dc:subject>Project</dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/ErikBorra">
 <rdf:value>ErikBorra</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry10">
 <title>The current design document is available for discussion.</title>
 <link>http://www.open-search.net/Blog/BlogEntry10</link>
 <description> You can read and comment on it &#64; &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://doc.open-search.net&#34;&#62;http://doc.open-search.net&#60;/a&#62;&#60;p /&#62; </description>
 <dc:creator>ErikBorra</dc:creator>
 <dc:date>2007-02-04T10:30:00Z</dc:date>
 <dc:subject>Development</dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/ErikBorra">
 <rdf:value>ErikBorra</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> 
<item rdf:about="http://www.open-search.net/Blog/BlogEntry11">
 <title>Currently visiting congresses and workshops</title>
 <link>http://www.open-search.net/Blog/BlogEntry11</link>
 <description> We are currently visiting congresses and workshops like &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://events.ccc.de/congress/2006/Fahrplan/events/1752.en.html&#34;&#62;23c3&#60;/a&#62; and &#60;a class&#61;&#34;natExternalLink&#34; target&#61;&#34;&#95;blank&#34; href&#61;&#34;http://www.fosdem.org/2007/&#34;&#62;FOSDEM &#39;07&#60;/a&#62; to gather extra input and build a community of volunteers.&#60;p /&#62; </description>
 <dc:creator>ErikBorra</dc:creator>
 <dc:date>2007-01-05T10:33:00Z</dc:date>
 <dc:subject></dc:subject> <dc:contributor>
 <rdf:Description link="http://www.open-search.net/Main/ErikBorra">
 <rdf:value>ErikBorra</rdf:value>
 </rdf:Description>
 </dc:contributor>
 </item> </rdf:RDF>