blog/archive/2010/12/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
   4   <head>
   5     <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
   6     <title>Petter Reinholdtsen: entries from December 2010</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="http://www.hungry.com/~pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="http://www.hungry.com/~pere/blog/vim.css" />
   9     <link rel="alternate" title="RSS Feed" href="12.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <!-- XML FEED -->
  13     <div class="title">
  14  <h1>
  15      <a href="http://www.hungry.com/~pere/blog/">Petter Reinholdtsen</a>
  16
  17  </h1>
  18
  19 </div>
  20
  21
  22     <h3>Entries from December 2010.</h3>
  23
  24     <div class="entry">
  25       <div class="title">
  26         <a href="http://www.hungry.com/~pere/blog/What_standards_are_Free_and_Open_as_defined_by_Digistan_.html">What standards are Free and Open as defined by Digistan?</a>
  27       </div>
  28       <div class="date">
  29         30th December 2010
  30       </div>
  31       <div class="body">
  32         <p>After trying to
  33 <a href="http://www.hungry.com/~pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html">compare
  34 Ogg Theora</a> to
  35 <a href="http://www.digistan.org/open-standard:definition">the Digistan
  36 definition</a> of a free and open standard, I concluded that this need
  37 to be done for more standards and started on a framework for doing
  38 this.  As a start, I want to get the status for all the standards in
  39 the Norwegian reference directory, which include UTF-8, HTML, PDF, ODF,
  40 JPEG, PNG, SVG and others.  But to be able to complete this in a
  41 reasonable time frame, I will need help.</p>
  42
  43 <p>If you want to help out with this work, please visit
  44 <a href="http://wiki.nuug.no/grupper/standard/digistan-analyse">the
  45 wiki pages I have set up for this</a>, and let me know that you want
  46 to help out.  The IRC channel #nuug on irc.freenode.net is a good
  47 place to coordinate this for now, as it is the IRC channel for the
  48 NUUG association where I have created the framework (I am the leader
  49 of the Norwegian Unix User Group).</p>
  50
  51 <p>The framework is still forming, and a lot is left to do.  Do not be
  52 scared by the sketchy form of the current pages. :)</p>
  53
  54       </div>
  55       <div class="tags">
  56
  57
  58         Tags: <a href="http://www.hungry.com/~pere/blog/tags/digistan">digistan</a>, <a href="http://www.hungry.com/~pere/blog/tags/english">english</a>, <a href="http://www.hungry.com/~pere/blog/tags/standard">standard</a>.
  59
  60
  61       </div>
  62     </div>
  63     <div class="padding"></div>
  64
  65     <div class="entry">
  66       <div class="title">
  67         <a href="http://www.hungry.com/~pere/blog/The_many_definitions_of_a_open_standard.html">The many definitions of a open standard</a>
  68       </div>
  69       <div class="date">
  70         27th December 2010
  71       </div>
  72       <div class="body">
  73         <p>One of the reasons I like the Digistan definition of
  74 "<a href="http://www.digistan.org/open-standard:definition">Free and
  75 Open Standard</a>" is that this is a new term, and thus the meaning of
  76 the term has been decided by Digistan.  The term "Open Standard" has
  77 become so misunderstood that it is no longer very useful when talking
  78 about standards.  One end up discussing which definition is the best
  79 one and with such frame the only one gaining are the proponents of
  80 de-facto standards and proprietary solutions.</p>
  81
  82 <p>But to give us an idea about the diversity of definitions of open
  83 standards, here are a few that I know about.  This list is not
  84 complete, but can be a starting point for those that want to do a
  85 complete survey.  More definitions are available on the
  86 <a href="http://en.wikipedia.org/wiki/Open_standard">wikipedia
  87 page</a>.</p>
  88
  89 <p>First off is my favourite, the definition from the European
  90 Interoperability Framework version 1.0.  Really sad to notice that BSA
  91 and others has succeeded in getting it removed from version 2.0 of the
  92 framework by stacking the committee drafting the new version with
  93 their own people.  Anyway, the definition is still available and it
  94 include the key properties needed to make sure everyone can use a
  95 specification on equal terms.</p>
  96
  97 <blockquote>
  98
  99 <p>The following are the minimal characteristics that a specification
 100 and its attendant documents must have in order to be considered an
 101 open standard:</p>
 102
 103 <ul>
 104
 105 <li>The standard is adopted and will be maintained by a not-for-profit
 106 organisation, and its ongoing development occurs on the basis of an
 107 open decision-making procedure available to all interested parties
 108 (consensus or majority decision etc.).</li>
 109
 110 <li>The standard has been published and the standard specification
 111 document is available either freely or at a nominal charge. It must be
 112 permissible to all to copy, distribute and use it for no fee or at a
 113 nominal fee.</li>
 114
 115 <li>The intellectual property - i.e. patents possibly present - of
 116 (parts of) the standard is made irrevocably available on a royalty-
 117 free basis.</li>
 118
 119 <li>There are no constraints on the re-use of the standard.</li>
 120
 121 </ul>
 122 </blockquote>
 123
 124 <p>Another one originates from my friends over at
 125 <a href="http://www.dkuug.dk/">DKUUG</a>, who coined and gathered
 126 support for <a href="http://www.aaben-standard.dk/">this
 127 definition</a> in 2004.  It even made it into the Danish parlament as
 128 <a href="http://www.ft.dk/dokumenter/tingdok.aspx?/samling/20051/beslutningsforslag/B103/som_fremsat.htm">their
 129 definition of a open standard</a>.  Another from a different part of
 130 the Danish government is available from the wikipedia page.</p>
 131
 132 <blockquote>
 133
 134 <p>En åben standard opfylder følgende krav:</p>
 135
 136 <ol>
 137
 138 <li>Veldokumenteret med den fuldstændige specifikation offentligt
 139 tilgængelig.</li>
 140
 141 <li>Frit implementerbar uden økonomiske, politiske eller juridiske
 142 begrænsninger på implementation og anvendelse.</li>
 143
 144 <li>Standardiseret og vedligeholdt i et åbent forum (en såkaldt
 145 "standardiseringsorganisation") via en åben proces.</li>
 146
 147 </ol>
 148
 149 </blockquote>
 150
 151 <p>Then there is <a href="http://www.fsfe.org/projects/os/def.html">the
 152 definition</a> from Free Software Foundation Europe.</p>
 153
 154 <blockquote>
 155
 156 <p>An Open Standard refers to a format or protocol that is</p>
 157
 158 <ol>
 159
 160 <li>subject to full public assessment and use without constraints in a
 161 manner equally available to all parties;</li>
 162
 163 <li>without any components or extensions that have dependencies on
 164 formats or protocols that do not meet the definition of an Open
 165 Standard themselves;</li>
 166
 167 <li>free from legal or technical clauses that limit its utilisation by
 168 any party or in any business model;</li>
 169
 170 <li>managed and further developed independently of any single vendor
 171 in a process open to the equal participation of competitors and third
 172 parties;</li>
 173
 174 <li>available in multiple complete implementations by competing
 175 vendors, or as a complete implementation equally available to all
 176 parties.</li>
 177
 178 </ol>
 179
 180 </blockquote>
 181
 182 <p>A long time ago, SUN Microsystems, now bought by Oracle, created
 183 its
 184 <a href="http://blogs.sun.com/dennisding/resource/Open%20Standard%20Definition.pdf">Open
 185 Standards Checklist</a> with a fairly detailed description.</p>
 186
 187 <blockquote>
 188 <p>Creation and Management of an Open Standard
 189
 190 <ul>
 191
 192 <li>Its development and management process must be collaborative and
 193   democratic:
 194
 195          <ul>
 196
 197          <li>Participation must be accessible to all those who wish to
 198             participate and can meet fair and reasonable criteria
 199             imposed by the organization under which it is developed
 200             and managed.</li>
 201
 202          <li>The processes must be documented and, through a known
 203             method, can be changed through input from all
 204             participants.</li>
 205
 206          <li>The process must be based on formal and binding commitments for
 207             the disclosure and licensing of intellectual property rights.</li>
 208
 209          <li>Development and management should strive for consensus,
 210             and an appeals process must be clearly outlined.</li>
 211
 212          <li>The standard specification must be open to extensive
 213             public review at least once in its life-cycle, with
 214             comments duly discussed and acted upon, if required.</li>
 215
 216          </ul>
 217
 218 </li>
 219
 220 </ul>
 221
 222 <p>Use and Licensing of an Open Standard</p>
 223 <ul>
 224
 225 <li>The standard must describe an interface, not an implementation,
 226   and the industry must be capable of creating multiple, competing
 227   implementations to the interface described in the standard without
 228   undue or restrictive constraints.  Interfaces include APIs,
 229   protocols, schemas, data formats and their encoding.</li>
 230
 231 <li> The standard must not contain any proprietary "hooks" that create
 232   a technical or economic barriers</li>
 233
 234 <li>Faithful implementations of the standard must
 235   interoperate. Interoperability means the ability of a computer
 236   program to communicate and exchange information with other computer
 237   programs and mutually to use the information which has been
 238   exchanged. This includes the ability to use, convert, or exchange
 239   file formats, protocols, schemas, interface information or
 240   conventions, so as to permit the computer program to work with other
 241   computer programs and users in all the ways in which they are
 242   intended to function.</li>
 243
 244 <li>It must be permissible for anyone to copy, distribute and read the
 245   standard for a nominal fee, or even no fee. If there is a fee, it
 246   must be low enough to not preclude widespread use.</li>
 247
 248 <li>It must be possible for anyone to obtain free (no royalties or
 249   fees; also known as "royalty free"), worldwide, non-exclusive and
 250   perpetual licenses to all essential patent claims to make, use and
 251   sell products based on the standard.  The only exceptions are
 252   terminations per the reciprocity and defensive suspension terms
 253   outlined below. Essential patent claims include pending, unpublished
 254   patents, published patents, and patent applications. The license is
 255   only for the exact scope of the standard in question.
 256
 257       <ul>
 258
 259       <li> May be conditioned only on reciprocal licenses to any of
 260         licensees' patent claims essential to practice that standard
 261         (also known as a reciprocity clause)</li>
 262
 263       <li> May be terminated as to any licensee who sues the licensor
 264         or any other licensee for infringement of patent claims
 265         essential to practice that standard (also known as a
 266         "defensive suspension" clause)</li>
 267
 268       <li> The same licensing terms are available to every potential
 269         licensor</li>
 270
 271       </ul>
 272 </li>
 273
 274 <li>The licensing terms of an open standards must not preclude
 275   implementations of that standard under open source licensing terms
 276   or restricted licensing terms</li>
 277
 278 </ul>
 279
 280 </blockquote>
 281
 282 <p>It is said that one of the nice things about standards is that
 283 there are so many of them.  As you can see, the same holds true for
 284 open standard definitions.  Most of the definitions have a lot in
 285 common, and it is not really controversial what properties a open
 286 standard should have, but the diversity of definitions have made it
 287 possible for those that want to avoid a level marked field and real
 288 competition to downplay the significance of open standards.  I hope we
 289 can turn this tide by focusing on the advantages of Free and Open
 290 Standards.</p>
 291
 292       </div>
 293       <div class="tags">
 294
 295
 296         Tags: <a href="http://www.hungry.com/~pere/blog/tags/digistan">digistan</a>, <a href="http://www.hungry.com/~pere/blog/tags/english">english</a>, <a href="http://www.hungry.com/~pere/blog/tags/standard">standard</a>.
 297
 298
 299       </div>
 300     </div>
 301     <div class="padding"></div>
 302
 303     <div class="entry">
 304       <div class="title">
 305         <a href="http://www.hungry.com/~pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html">Is Ogg Theora a free and open standard?</a>
 306       </div>
 307       <div class="date">
 308         25th December 2010
 309       </div>
 310       <div class="body">
 311         <p><a href="http://www.digistan.org/open-standard:definition">The
 312 Digistan definition</a> of a free and open standard reads like this:</p>
 313
 314 <blockquote>
 315
 316 <p>The Digital Standards Organization defines free and open standard
 317 as follows:</p>
 318
 319 <ol>
 320
 321 <li>A free and open standard is immune to vendor capture at all stages
 322 in its life-cycle. Immunity from vendor capture makes it possible to
 323 freely use, improve upon, trust, and extend a standard over time.</li>
 324
 325 <li>The standard is adopted and will be maintained by a not-for-profit
 326 organisation, and its ongoing development occurs on the basis of an
 327 open decision-making procedure available to all interested
 328 parties.</li>
 329
 330 <li>The standard has been published and the standard specification
 331 document is available freely. It must be permissible to all to copy,
 332 distribute, and use it freely.</li>
 333
 334 <li>The patents possibly present on (parts of) the standard are made
 335 irrevocably available on a royalty-free basis.</li>
 336
 337 <li>There are no constraints on the re-use of the standard.</li>
 338
 339 </ol>
 340
 341 <p>The economic outcome of a free and open standard, which can be
 342 measured, is that it enables perfect competition between suppliers of
 343 products based on the standard.</p>
 344 </blockquote>
 345
 346 <p>For a while now I have tried to figure out of Ogg Theora is a free
 347 and open standard according to this definition.  Here is a short
 348 writeup of what I have been able to gather so far.  I brought up the
 349 topic on the Xiph advocacy mailing list
 350 <a href="http://lists.xiph.org/pipermail/advocacy/2009-July/001632.html">in
 351 July 2009</a>, for those that want to see some background information.
 352 According to Ivo Emanuel Gonçalves and Monty Montgomery on that list
 353 the Ogg Theora specification fulfils the Digistan definition.</p>
 354
 355 <p><strong>Free from vendor capture?</strong></p>
 356
 357 <p>As far as I can see, there is no single vendor that can control the
 358 Ogg Theora specification.  It can be argued that the
 359 <a href="http://www.xiph.org/">Xiph foundation</A> is such vendor, but
 360 given that it is a non-profit foundation with the expressed goal
 361 making free and open protocols and standards available, it is not
 362 obvious that this is a real risk.  One issue with the Xiph
 363 foundation is that its inner working (as in board member list, or who
 364 control the foundation) are not easily available on the web.  I've
 365 been unable to find out who is in the foundation board, and have not
 366 seen any accounting information documenting how money is handled nor
 367 where is is spent in the foundation.  It is thus not obvious for an
 368 external observer who control The Xiph foundation, and for all I know
 369 it is possible for a single vendor to take control over the
 370 specification.  But it seem unlikely.</p>
 371
 372 <p><strong>Maintained by open not-for-profit organisation?</strong></p>
 373
 374 <p>Assuming that the Xiph foundation is the organisation its web pages
 375 claim it to be, this point is fulfilled.  If Xiph foundation is
 376 controlled by a single vendor, it isn't, but I have not found any
 377 documentation indicating this.</p>
 378
 379 <p>According to
 380 <a href="http://media.hiof.no/diverse/fad/rapport_4.pdf">a report</a>
 381 prepared by Audun Vaaler og Børre Ludvigsen for the Norwegian
 382 government, the Xiph foundation is a non-commercial organisation and
 383 the development process is open, transparent and non-Discrimatory.
 384 Until proven otherwise, I believe it make most sense to believe the
 385 report is correct.</p>
 386
 387 <p><strong>Specification freely available?</strong></p>
 388
 389 <p>The specification for the <a href="http://www.xiph.org/ogg/doc/">Ogg
 390 container format</a> and both the
 391 <a href="http://www.xiph.org/vorbis/doc/">Vorbis</a> and
 392 <a href="http://theora.org/doc/">Theora</a> codeces are available on
 393 the web.  This are the terms in the Vorbis and Theora specification:
 394
 395 <blockquote>
 396
 397 Anyone may freely use and distribute the Ogg and [Vorbis/Theora]
 398 specifications, whether in private, public, or corporate
 399 capacity. However, the Xiph.Org Foundation and the Ogg project reserve
 400 the right to set the Ogg [Vorbis/Theora] specification and certify
 401 specification compliance.
 402
 403 </blockquote>
 404
 405 <p>The Ogg container format is specified in IETF
 406 <a href="http://www.xiph.org/ogg/doc/rfc3533.txt">RFC 3533</a>, and
 407 this is the term:<p>
 408
 409 <blockquote>
 410
 411 <p>This document and translations of it may be copied and furnished to
 412 others, and derivative works that comment on or otherwise explain it
 413 or assist in its implementation may be prepared, copied, published and
 414 distributed, in whole or in part, without restriction of any kind,
 415 provided that the above copyright notice and this paragraph are
 416 included on all such copies and derivative works.  However, this
 417 document itself may not be modified in any way, such as by removing
 418 the copyright notice or references to the Internet Society or other
 419 Internet organizations, except as needed for the purpose of developing
 420 Internet standards in which case the procedures for copyrights defined
 421 in the Internet Standards process must be followed, or as required to
 422 translate it into languages other than English.</p>
 423
 424 <p>The limited permissions granted above are perpetual and will not be
 425 revoked by the Internet Society or its successors or assigns.</p>
 426 </blockquote>
 427
 428 <p>All these terms seem to allow unlimited distribution and use, an
 429 this term seem to be fulfilled.  There might be a problem with the
 430 missing permission to distribute modified versions of the text, and
 431 thus reuse it in other specifications.  Not quite sure if that is a
 432 requirement for the Digistan definition.</p>
 433
 434 <p><strong>Royalty-free?</strong></p>
 435
 436 <p>There are no known patent claims requiring royalties for the Ogg
 437 Theora format.
 438 <a href="http://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=65782">MPEG-LA</a>
 439 and
 440 <a href="http://yro.slashdot.org/story/10/04/30/237238/Steve-Jobs-Hints-At-Theora-Lawsuit">Steve
 441 Jobs</a> in Apple claim to know about some patent claims (submarine
 442 patents) against the Theora format, but no-one else seem to believe
 443 them.  Both Opera Software and the Mozilla Foundation have looked into
 444 this and decided to implement Ogg Theora support in their browsers
 445 without paying any royalties.  For now the claims from MPEG-LA and
 446 Steve Jobs seem more like FUD to scare people to use the H.264 codec
 447 than any real problem with Ogg Theora.</p>
 448
 449 <p><strong>No constraints on re-use?</strong></p>
 450
 451 <p>I am not aware of any constraints on re-use.</p>
 452
 453 <p><strong>Conclusion</strong></p>
 454
 455 <p>3 of 5 requirements seem obviously fulfilled, and the remaining 2
 456 depend on the governing structure of the Xiph foundation.  Given the
 457 background report used by the Norwegian government, I believe it is
 458 safe to assume the last two requirements are fulfilled too, but it
 459 would be nice if the Xiph foundation web site made it easier to verify
 460 this.</p>
 461
 462 <p>It would be nice to see other analysis of other specifications to
 463 see if they are free and open standards.</p>
 464
 465       </div>
 466       <div class="tags">
 467
 468
 469         Tags: <a href="http://www.hungry.com/~pere/blog/tags/digistan">digistan</a>, <a href="http://www.hungry.com/~pere/blog/tags/english">english</a>, <a href="http://www.hungry.com/~pere/blog/tags/h264">h264</a>, <a href="http://www.hungry.com/~pere/blog/tags/standard">standard</a>, <a href="http://www.hungry.com/~pere/blog/tags/video">video</a>.
 470
 471
 472       </div>
 473     </div>
 474     <div class="padding"></div>
 475
 476     <div class="entry">
 477       <div class="title">
 478         <a href="http://www.hungry.com/~pere/blog/The_reply_from_Edgar_Villanueva_to_Microsoft_in_Peru.html">The reply from Edgar Villanueva to Microsoft in Peru</a>
 479       </div>
 480       <div class="date">
 481         25th December 2010
 482       </div>
 483       <div class="body">
 484         <p>A few days ago
 485 <a href="http://www.idg.no/computerworld/article189879.ece">an
 486 article</a> in the Norwegian Computerworld magazine about how version
 487 2.0 of
 488 <a href="http://en.wikipedia.org/wiki/European_Interoperability_Framework">European
 489 Interoperability Framework</a> has been successfully lobbied by the
 490 proprietary software industry to remove the focus on free software.
 491 Nothing very surprising there, given
 492 <a href="http://news.slashdot.org/story/10/03/29/2115235/Open-Source-Open-Standards-Under-Attack-In-Europe">earlier
 493 reports</a> on how Microsoft and others have stacked the committees in
 494 this work.  But I find this very sad.   The definition of
 495 <a href="http://www.nuug.no/dokumenter/standard-presse-def-200506.txt">an
 496 open standard from version 1</a> was very good, and something I
 497 believe should be used also in the future, alongside
 498 <a href="http://www.digistan.org/open-standard:definition">the
 499 definition from Digistan</A>.  Version 2 have removed the open
 500 standard definition from its content.</p>
 501
 502 <p>Anyway, the news reminded me of the great reply sent by Dr. Edgar
 503 Villanueva, congressman in Peru at the time, to Microsoft as a reply
 504 to Microsofts attack on his proposal regarding the use of free software
 505 in the public sector in Peru.  As the text was not available from a
 506 few of the URLs where it used to be available, I copy it here from
 507 <a href="http://gnuwin.epfl.ch/articles/en/reponseperou/villanueva_to_ms.html">my
 508 source</a> to ensure it is available also in the future.  Some
 509 background information about that story is available in
 510 <a href="http://www.linuxjournal.com/article/6099">an article</a> from
 511 Linux Journal in 2002.</p>
 512
 513 <blockquote>
 514 <p>Lima, 8th of April, 2002<br>
 515 To: Señor JUAN ALBERTO GONZÁLEZ<br>
 516 General Manager of Microsoft Perú</p>
 517
 518 <p>Dear Sir:</p>
 519
 520 <p>First of all, I thank you for your letter of March 25, 2002 in which you state the official position of Microsoft relative to Bill Number 1609, Free Software in Public Administration, which is indubitably inspired by the desire for Peru to find a suitable place in the global technological context. In the same spirit, and convinced that we will find the best solutions through an exchange of clear and open ideas, I will take this opportunity to reply to the commentaries included in your letter.</p>
 521
 522 <p>While acknowledging that opinions such as yours constitute a significant contribution, it would have been even more worthwhile for me if, rather than formulating objections of a general nature (which we will analyze in detail later) you had gathered solid arguments for the advantages that proprietary software could bring to the Peruvian State, and to its citizens in general, since this would have allowed a more enlightening exchange in respect of each of our positions.</p>
 523
 524 <p>With the aim of creating an orderly debate, we will assume that what you call "open source software" is what the Bill defines as "free software", since there exists software for which the source code is distributed together with the program, but which does not fall within the definition established by the Bill; and that what you call "commercial software" is what the Bill defines as "proprietary" or "unfree", given that there exists free software which is sold in the market for a price like any other good or service.</p>
 525
 526 <p>It is also necessary to make it clear that the aim of the Bill we are discussing is not directly related to the amount of direct savings that can by made by using free software in state institutions. That is in any case a marginal aggregate value, but in no way is it the chief focus of the Bill. The basic principles which inspire the Bill are linked to the basic guarantees of a state of law, such as:</p>
 527
 528 <p>
 529 <ul>
 530 <li>Free access to public information by the citizen. </li>
 531 <li>Permanence of public data. </li>
 532 <li>Security of the State and citizens.</li>
 533 </ul>
 534 </p>
 535
 536 <p>To guarantee the free access of citizens to public information, it is indispensable that the encoding of data is not tied to a single provider. The use of standard and open formats gives a guarantee of this free access, if necessary through the creation of compatible free software.</p>
 537
 538 <p>To guarantee the permanence of public data, it is necessary that the usability and maintenance of the software does not depend on the goodwill of the suppliers, or on the monopoly conditions imposed by them. For this reason the State needs systems the development of which can be guaranteed due to the availability of the source code.</p>
 539
 540 <p>To guarantee national security or the security of the State, it is indispensable to be able to rely on systems without elements which allow control from a distance or the undesired transmission of information to third parties. Systems with source code freely accessible to the public are required to allow their inspection by the State itself, by the citizens, and by a large number of independent experts throughout the world. Our proposal brings further security, since the knowledge of the source code will eliminate the growing number of programs with *spy code*. </p>
 541
 542 <p>In the same way, our proposal strengthens the security of the citizens, both in their role as legitimate owners of information managed by the state, and in their role as consumers. In this second case, by allowing the growth of a widespread availability of free software not containing *spy code* able to put at risk privacy and individual freedoms.</p>
 543
 544 <p>In this sense, the Bill is limited to establishing the conditions under which the state bodies will obtain software in the future, that is, in a way compatible with these basic principles.</p>
 545
 546
 547 <p>From reading the Bill it will be clear that once passed:<br>
 548 <li>the law does not forbid the production of proprietary software</li>
 549 <li>the law does not forbid the sale of proprietary software</li>
 550 <li>the law does not specify which concrete software to use</li>
 551 <li>the law does not dictate the supplier from whom software will be bought</li>
 552 <li>the law does not limit the terms under which a software product can be licensed.</li>
 553
 554 </p>
 555
 556 <p>What the Bill does express clearly, is that, for software to be acceptable for the state it is not enough that it is technically capable of fulfilling a task, but that further the contractual conditions must satisfy a series of requirements regarding the license, without which the State cannot guarantee the citizen adequate processing of his data, watching over its integrity, confidentiality, and accessibility throughout time, as these are very critical aspects for its normal functioning.</p>
 557
 558 <p>We agree, Mr. Gonzalez, that information and communication technology have a significant impact on the quality of life of the citizens (whether it be positive or negative). We surely also agree that the basic values I have pointed out above are fundamental in a democratic state like Peru. So we are very interested to know of any other way of guaranteeing these principles, other than through the use of free software in the terms defined by the Bill.</p>
 559
 560 <p>As for the observations you have made, we will now go on to analyze them in detail:</p>
 561
 562 <p>Firstly, you point out that: "1. The bill makes it compulsory for all public bodies to use only free software, that is to say open source software, which breaches the principles of equality before the law, that of non-discrimination and the right of free private enterprise, freedom of industry and of contract, protected by the constitution."</p>
 563
 564 <p>This understanding is in error. The Bill in no way affects the rights you list; it limits itself entirely to establishing conditions for the use of software on the part of state institutions, without in any way meddling in private sector transactions. It is a well established principle that the State does not enjoy the wide spectrum of contractual freedom of the private sector, as it is limited in its actions precisely by the requirement for transparency of public acts; and in this sense, the preservation of the greater common interest must prevail when legislating on the matter.</p>
 565
 566 <p>The Bill protects equality under the law, since no natural or legal person is excluded from the right of offering these goods to the State under the conditions defined in the Bill and without more limitations than those established by the Law of State Contracts and Purchasing (T.U.O. by Supreme Decree No. 012-2001-PCM).</p>
 567
 568 <p>The Bill does not introduce any discrimination whatever, since it only establishes *how* the goods have to be provided (which is a state power) and not *who* has to provide them (which would effectively be discriminatory, if restrictions based on national origin, race religion, ideology, sexual preference etc. were imposed). On the contrary, the Bill is decidedly antidiscriminatory. This is so because by defining with no room for doubt the conditions for the provision of software, it prevents state bodies from using software which has a license including discriminatory conditions.</p>
 569
 570 <p>It should be obvious from the preceding two paragraphs that the Bill does not harm free private enterprise, since the latter can always choose under what conditions it will produce software; some of these will be acceptable to the State, and others will not be since they contradict the guarantee of the basic principles listed above. This free initiative is of course compatible with the freedom of industry and freedom of contract (in the limited form in which the State can exercise the latter). Any private subject can produce software under the conditions which the State requires, or can refrain from doing so. Nobody is forced to adopt a model of production, but if they wish to provide software to the State, they must provide the mechanisms which guarantee the basic principles, and which are those described in the Bill.</p>
 571
 572 <p>By way of an example: nothing in the text of the Bill would prevent your company offering the State bodies an office "suite", under the conditions defined in the Bill and setting the price that you consider satisfactory. If you did not, it would not be due to restrictions imposed by the law, but to business decisions relative to the method of commercializing your products, decisions with which the State is not involved.</p>
 573
 574 <p>To continue; you note that:" 2. The bill, by making the use of open source software compulsory, would establish discriminatory and non competitive practices in the contracting and purchasing by public bodies..."</p>
 575
 576 <p>This statement is just a reiteration of the previous one, and so the response can be found above. However, let us concern ourselves for a moment with your comment regarding "non-competitive ... practices."</p>
 577
 578 <p>Of course, in defining any kind of purchase, the buyer sets conditions which relate to the proposed use of the good or service. From the start, this excludes certain manufacturers from the possibility of competing, but does not exclude them "a priori", but rather based on a series of principles determined by the autonomous will of the purchaser, and so the process takes place in conformance with the law. And in the Bill it is established that *no one* is excluded from competing as far as he guarantees the fulfillment of the basic principles.</p>
 579
 580 <p>Furthermore, the Bill *stimulates* competition, since it tends to generate a supply of software with better conditions of usability, and to better existing work, in a model of continuous improvement.</p>
 581
 582 <p>On the other hand, the central aspect of competivity is the chance to provide better choices to the consumer. Now, it is impossible to ignore the fact that marketing does not play a neutral role when the product is offered on the market (since accepting the opposite would lead one to suppose that firms' expenses in marketing lack any sense), and that therefore a significant expense under this heading can influence the decisions of the purchaser. This influence of marketing is in large measure reduced by the bill that we are backing, since the choice within the framework proposed is based on the *technical merits* of the product and not on the effort put into commercialization by the producer; in this sense, competitiveness is increased, since the smallest software producer can compete on equal terms with the most powerful corporations.</p>
 583
 584 <p>It is necessary to stress that there is no position more anti-competitive than that of the big software producers, which frequently abuse their dominant position, since in innumerable cases they propose as a solution to problems raised by users: "update your software to the new version" (at the user's expense, naturally); furthermore, it is common to find arbitrary cessation of technical help for products, which, in the provider's judgment alone, are "old"; and so, to receive any kind of technical assistance, the user finds himself forced to migrate to new versions (with non-trivial costs, especially as changes in hardware platform are often involved). And as the whole infrastructure is based on proprietary data formats, the user stays "trapped" in the need to continue using products from the same supplier, or to make the huge effort to change to another environment (probably also proprietary).</p>
 585
 586 <p>You add: "3. So, by compelling the State to favor a business model based entirely on open source, the bill would only discourage the local and international manufacturing companies, which are the ones which really undertake important expenditures, create a significant number of direct and indirect jobs, as well as contributing to the GNP, as opposed to a model of open source software which tends to have an ever weaker economic impact, since it mainly creates jobs in the service sector."</p>
 587
 588 <p>I do not agree with your statement. Partly because of what you yourself point out in paragraph 6 of your letter, regarding the relative weight of services in the context of software use. This contradiction alone would invalidate your position. The service model, adopted by a large number of companies in the software industry, is much larger in economic terms, and with a tendency to increase, than the licensing of programs.</p>
 589
 590 <p>On the other hand, the private sector of the economy has the widest possible freedom to choose the economic model which best suits its interests, even if this freedom of choice is often obscured subliminally by the disproportionate expenditure on marketing by the producers of proprietary software.</p>
 591
 592 <p>In addition, a reading of your opinion would lead to the conclusion that the State market is crucial and essential for the proprietary software industry, to such a point that the choice made by the State in this bill would completely eliminate the market for these firms. If that is true, we can deduce that the State must be subsidizing the proprietary software industry. In the unlikely event that this were true, the State would have the right to apply the subsidies in the area it considered of greatest social value; it is undeniable, in this improbable hypothesis, that if the State decided to subsidize software, it would have to do so choosing the free over the proprietary, considering its social effect and the rational use of taxpayers money.</p>
 593
 594 <p>In respect of the jobs generated by proprietary software in countries like ours, these mainly concern technical tasks of little aggregate value; at the local level, the technicians who provide support for proprietary software produced by transnational companies do not have the possibility of fixing bugs, not necessarily for lack of technical capability or of talent, but because they do not have access to the source code to fix it. With free software one creates more technically qualified employment and a framework of free competence where success is only tied to the ability to offer good technical support and quality of service, one stimulates the market, and one increases the shared fund of knowledge, opening up alternatives to generate services of greater total value and a higher quality level, to the benefit of all involved: producers, service organizations, and consumers.</p>
 595
 596 <p>It is a common phenomenon in developing countries that local software industries obtain the majority of their takings in the service sector, or in the creation of "ad hoc" software. Therefore, any negative impact that the application of the Bill might have in this sector will be more than compensated by a growth in demand for services (as long as these are carried out to high quality standards). If the transnational software companies decide not to compete under these new rules of the game, it is likely that they will undergo some decrease in takings in terms of payment for licenses; however, considering that these firms continue to allege that much of the software used by the State has been illegally copied, one can see that the impact will not be very serious. Certainly, in any case their fortune will be determined by market laws, changes in which cannot be avoided; many firms traditionally associated with proprietary software have already set out on the road (supported by copious expense) of providing services associated with free software, which shows that the models are not mutually exclusive.</p>
 597
 598 <p>With this bill the State is deciding that it needs to preserve certain fundamental values. And it is deciding this based on its sovereign power, without affecting any of the constitutional guarantees. If these values could be guaranteed without having to choose a particular economic model, the effects of the law would be even more beneficial. In any case, it should be clear that the State does not choose an economic model; if it happens that there only exists one economic model capable of providing software which provides the basic guarantee of these principles, this is because of historical circumstances, not because of an arbitrary choice of a given model.</p>
 599
 600 <p>Your letter continues: "4. The bill imposes the use of open source software without considering the dangers that this can bring from the point of view of security, guarantee, and possible violation of the intellectual property rights of third parties."</p>
 601
 602 <p>Alluding in an abstract way to "the dangers this can bring", without specifically mentioning a single one of these supposed dangers, shows at the least some lack of knowledge of the topic. So, allow me to enlighten you on these points.</p>
 603
 604 <p>On security:</p>
 605
 606 <p>National security has already been mentioned in general terms in the initial discussion of the basic principles of the bill. In more specific terms, relative to the security of the software itself, it is well known that all software (whether proprietary or free) contains errors or "bugs" (in programmers' slang). But it is also well known that the bugs in free software are fewer, and are fixed much more quickly, than in proprietary software. It is not in vain that numerous public bodies responsible for the IT security of state systems in developed countries require the use of free software for the same conditions of security and efficiency.</p>
 607
 608 <p>What is impossible to prove is that proprietary software is more secure than free, without the public and open inspection of the scientific community and users in general. This demonstration is impossible because the model of proprietary software itself prevents this analysis, so that any guarantee of security is based only on promises of good intentions (biased, by any reckoning) made by the producer itself, or its contractors.</p>
 609
 610 <p>It should be remembered that in many cases, the licensing conditions include Non-Disclosure clauses which prevent the user from publicly revealing security flaws found in the licensed proprietary product.</p>
 611
 612 <p>In respect of the guarantee:</p>
 613
 614 <p>As you know perfectly well, or could find out by reading the "End User License Agreement" of the products you license, in the great majority of cases the guarantees are limited to replacement of the storage medium in case of defects, but in no case is compensation given for direct or indirect damages, loss of profits, etc... If as a result of a security bug in one of your products, not fixed in time by yourselves, an attacker managed to compromise crucial State systems, what guarantees, reparations and compensation would your company make in accordance with your licensing conditions? The guarantees of proprietary software, inasmuch as programs are delivered ``AS IS'', that is, in the state in which they are, with no additional responsibility of the provider in respect of function, in no way differ from those normal with free software.</p>
 615
 616 <p>On Intellectual Property:</p>
 617
 618 <p>Questions of intellectual property fall outside the scope of this bill, since they are covered by specific other laws. The model of free software in no way implies ignorance of these laws, and in fact the great majority of free software is covered by copyright. In reality, the inclusion of this question in your observations shows your confusion in respect of the legal framework in which free software is developed. The inclusion of the intellectual property of others in works claimed as one's own is not a practice that has been noted in the free software community; whereas, unfortunately, it has been in the area of proprietary software. As an example, the condemnation by the Commercial Court of Nanterre, France, on 27th September 2001 of Microsoft Corp. to a penalty of 3 million francs in damages and interest, for violation of intellectual property (piracy, to use the unfortunate term that your firm commonly uses in its publicity).</p>
 619
 620 <p>You go on to say that: "The bill uses the concept of open source software incorrectly, since it does not necessarily imply that the software is free or of zero cost, and so arrives at mistaken conclusions regarding State savings, with no cost-benefit analysis to validate its position."</p>
 621
 622 <p>This observation is wrong; in principle, freedom and lack of cost are orthogonal concepts: there is software which is proprietary and charged for (for example, MS Office), software which is proprietary and free of charge (MS Internet Explorer), software which is free and charged for (Red Hat, SuSE etc GNU/Linux distributions), software which is free and not charged for (Apache, Open Office, Mozilla), and even software which can be licensed in a range of combinations (MySQL).</p>
 623
 624 <p>Certainly free software is not necessarily free of charge. And the text of the bill does not state that it has to be so, as you will have noted after reading it. The definitions included in the Bill state clearly *what* should be considered free software, at no point referring to freedom from charges. Although the possibility of savings in payments for proprietary software licenses are mentioned, the foundations of the bill clearly refer to the fundamental guarantees to be preserved and to the stimulus to local technological development. Given that a democratic State must support these principles, it has no other choice than to use software with publicly available source code, and to exchange information only in standard formats.</p>
 625
 626 <p>If the State does not use software with these characteristics, it will be weakening basic republican principles. Luckily, free software also implies lower total costs; however, even given the hypothesis (easily disproved) that it was more expensive than proprietary software, the simple existence of an effective free software tool for a particular IT function would oblige the State to use it; not by command of this Bill, but because of the basic principles we enumerated at the start, and which arise from the very essence of the lawful democratic State.</p>
 627
 628 <p>You continue: "6. It is wrong to think that Open Source Software is free of charge. Research by the Gartner Group (an important investigator of the technological market recognized at world level) has shown that the cost of purchase of software (operating system and applications) is only 8% of the total cost which firms and institutions take on for a rational and truly beneficial use of the technology. The other 92% consists of: installation costs, enabling, support, maintenance, administration, and down-time."</p>
 629
 630 <p>This argument repeats that already given in paragraph 5 and partly contradicts paragraph 3. For the sake of brevity we refer to the comments on those paragraphs. However, allow me to point out that your conclusion is logically false: even if according to Gartner Group the cost of software is on average only 8% of the total cost of use, this does not in any way deny the existence of software which is free of charge, that is, with a licensing cost of zero.</p>
 631
 632 <p>In addition, in this paragraph you correctly point out that the service components and losses due to down-time make up the largest part of the total cost of software use, which, as you will note, contradicts your statement regarding the small value of services suggested in paragraph 3. Now the use of free software contributes significantly to reduce the remaining life-cycle costs. This reduction in the costs of installation, support etc. can be noted in several areas: in the first place, the competitive service model of free software, support and maintenance for which can be freely contracted out to a range of suppliers competing on the grounds of quality and low cost. This is true for installation, enabling, and support, and in large part for maintenance. In the second place, due to the reproductive characteristics of the model, maintenance carried out for an application is easily replicable, without incurring large costs (that is, without paying more than once for the same thing) since modifications, if one wishes, can be incorporated in the common fund of knowledge. Thirdly, the huge costs caused by non-functioning software ("blue screens of death", malicious code such as virus, worms, and trojans, exceptions, general protection faults and other well-known problems) are reduced considerably by using more stable software; and it is well known that one of the most notable virtues of free software is its stability.</p>
 633
 634 <p>You further state that: "7. One of the arguments behind the bill is the supposed freedom from costs of open-source software, compared with the costs of commercial software, without taking into account the fact that there exist types of volume licensing which can be highly advantageous for the State, as has happened in other countries."</p>
 635
 636 <p>I have already pointed out that what is in question is not the cost of the software but the principles of freedom of information, accessibility, and security. These arguments have been covered extensively in the preceding paragraphs to which I would refer you.</p>
 637
 638 <p>On the other hand, there certainly exist types of volume licensing (although unfortunately proprietary software does not satisfy the basic principles). But as you correctly pointed out in the immediately preceding paragraph of your letter, they only manage to reduce the impact of a component which makes up no more than 8% of the total.</p>
 639
 640 <p>You continue: "8. In addition, the alternative adopted by the bill (I) is clearly more expensive, due to the high costs of software migration, and (II) puts at risk compatibility and interoperability of the IT platforms within the State, and between the State and the private sector, given the hundreds of versions of open source software on the market."</p>
 641
 642 <p>Let us analyze your statement in two parts. Your first argument, that migration implies high costs, is in reality an argument in favor of the Bill. Because the more time goes by, the more difficult migration to another technology will become; and at the same time, the security risks associated with proprietary software will continue to increase. In this way, the use of proprietary systems and formats will make the State ever more dependent on specific suppliers. Once a policy of using free software has been established (which certainly, does imply some cost) then on the contrary migration from one system to another becomes very simple, since all data is stored in open formats. On the other hand, migration to an open software context implies no more costs than migration between two different proprietary software contexts, which invalidates your argument completely.</p>
 643
 644 <p>The second argument refers to "problems in interoperability of the IT platforms within the State, and between the State and the private sector" This statement implies a certain lack of knowledge of the way in which free software is built, which does not maximize the dependence of the user on a particular platform, as normally happens in the realm of proprietary software. Even when there are multiple free software distributions, and numerous programs which can be used for the same function, interoperability is guaranteed as much by the use of standard formats, as required by the bill, as by the possibility of creating interoperable software given the availability of the source code.</p>
 645
 646 <p>You then say that: "9. The majority of open source code does not offer adequate levels of service nor the guarantee from recognized manufacturers of high productivity on the part of the users, which has led various public organizations to retract their decision to go with an open source software solution and to use commercial software in its place."</p>
 647
 648 <p>This observation is without foundation. In respect of the guarantee, your argument was rebutted in the response to paragraph 4. In respect of support services, it is possible to use free software without them (just as also happens with proprietary software), but anyone who does need them can obtain support separately, whether from local firms or from international corporations, again just as in the case of proprietary software.</p>
 649
 650 <p>On the other hand, it would contribute greatly to our analysis if you could inform us about free software projects *established* in public bodies which have already been abandoned in favor of proprietary software. We know of a good number of cases where the opposite has taken place, but not know of any where what you describe has taken place.</p>
 651
 652 <p>You continue by observing that: "10. The bill discourages the creativity of the Peruvian software industry, which invoices 40 million US$/year, exports 4 million US$ (10th in ranking among non-traditional exports, more than handicrafts) and is a source of highly qualified employment. With a law that encourages the use of open source, software programmers lose their intellectual property rights and their main source of payment."</p>
 653
 654 <p>It is clear enough that nobody is forced to commercialize their code as free software. The only thing to take into account is that if it is not free software, it cannot be sold to the public sector. This is not in any case the main market for the national software industry. We covered some questions referring to the influence of the Bill on the generation of employment which would be both highly technically qualified and in better conditions for competition above, so it seems unnecessary to insist on this point.</p>
 655
 656 <p>What follows in your statement is incorrect. On the one hand, no author of free software loses his intellectual property rights, unless he expressly wishes to place his work in the public domain. The free software movement has always been very respectful of intellectual property, and has generated widespread public recognition of its authors. Names like those of Richard Stallman, Linus Torvalds, Guido van Rossum, Larry Wall, Miguel de Icaza, Andrew Tridgell, Theo de Raadt, Andrea Arcangeli, Bruce Perens, Darren Reed, Alan Cox, Eric Raymond, and many others, are recognized world-wide for their contributions to the development of software that is used today by millions of people throughout the world. On the other hand, to say that the rewards for authors rights make up the main source of payment of Peruvian programmers is in any case a guess, in particular since there is no proof to this effect, nor a demonstration of how the use of free software by the State would influence these payments.</p>
 657
 658 <p>You go on to say that: "11. Open source software, since it can be distributed without charge, does not allow the generation of income for its developers through exports. In this way, the multiplier effect of the sale of software to other countries is weakened, and so in turn is the growth of the industry, while Government rules ought on the contrary to stimulate local industry."</p>
 659
 660 <p>This statement shows once again complete ignorance of the mechanisms of and market for free software. It tries to claim that the market of sale of non- exclusive rights for use (sale of licenses) is the only possible one for the software industry, when you yourself pointed out several paragraphs above that it is not even the most important one. The incentives that the bill offers for the growth of a supply of better qualified professionals, together with the increase in experience that working on a large scale with free software within the State will bring for Peruvian technicians, will place them in a highly competitive position to offer their services abroad.</p>
 661
 662 <p>You then state that: "12. In the Forum, the use of open source software in education was discussed, without mentioning the complete collapse of this initiative in a country like Mexico, where precisely the State employees who founded the project now state that open source software did not make it possible to offer a learning experience to pupils in the schools, did not take into account the capability at a national level to give adequate support to the platform, and that the software did not and does not allow for the levels of platform integration that now exist in schools."</p>
 663
 664 <p>In fact Mexico has gone into reverse with the Red Escolar (Schools Network) project. This is due precisely to the fact that the driving forces behind the Mexican project used license costs as their main argument, instead of the other reasons specified in our project, which are far more essential. Because of this conceptual mistake, and as a result of the lack of effective support from the SEP (Secretary of State for Public Education), the assumption was made that to implant free software in schools it would be enough to drop their software budget and send them a CD ROM with Gnu/Linux instead. Of course this failed, and it couldn't have been otherwise, just as school laboratories fail when they use proprietary software and have no budget for implementation and maintenance. That's exactly why our bill is not limited to making the use of free software mandatory, but recognizes the need to create a viable migration plan, in which the State undertakes the technical transition in an orderly way in order to then enjoy the advantages of free software.</p>
 665
 666 <p>You end with a rhetorical question: "13. If open source software satisfies all the requirements of State bodies, why do you need a law to adopt it? Shouldn't it be the market which decides freely which products give most benefits or value?"</p>
 667
 668 <p>We agree that in the private sector of the economy, it must be the market that decides which products to use, and no state interference is permissible there. However, in the case of the public sector, the reasoning is not the same: as we have already established, the state archives, handles, and transmits information which does not belong to it, but which is entrusted to it by citizens, who have no alternative under the rule of law. As a counterpart to this legal requirement, the State must take extreme measures to safeguard the integrity, confidentiality, and accessibility of this information. The use of proprietary software raises serious doubts as to whether these requirements can be fulfilled, lacks conclusive evidence in this respect, and so is not suitable for use in the public sector.</p>
 669
 670 <p>The need for a law is based, firstly, on the realization of the fundamental principles listed above in the specific area of software; secondly, on the fact that the State is not an ideal homogeneous entity, but made up of multiple bodies with varying degrees of autonomy in decision making. Given that it is inappropriate to use proprietary software, the fact of establishing these rules in law will prevent the personal discretion of any state employee from putting at risk the information which belongs to citizens. And above all, because it constitutes an up-to-date reaffirmation in relation to the means of management and communication of information used today, it is based on the republican principle of openness to the public.</p>
 671
 672 <p>In conformance with this universally accepted principle, the citizen has the right to know all information held by the State and not covered by well- founded declarations of secrecy based on law. Now, software deals with information and is itself information. Information in a special form, capable of being interpreted by a machine in order to execute actions, but crucial information all the same because the citizen has a legitimate right to know, for example, how his vote is computed or his taxes calculated. And for that he must have free access to the source code and be able to prove to his satisfaction the programs used for electoral computations or calculation of his taxes.</p>
 673
 674 <p>I wish you the greatest respect, and would like to repeat that my office will always be open for you to expound your point of view to whatever level of detail you consider suitable.</p>
 675
 676 <p>Cordially,<br>
 677 DR. EDGAR DAVID VILLANUEVA NUÑEZ<br>
 678 Congressman of the Republic of Perú.</p>
 679 </blockquote>
 680
 681       </div>
 682       <div class="tags">
 683
 684
 685         Tags: <a href="http://www.hungry.com/~pere/blog/tags/digistan">digistan</a>, <a href="http://www.hungry.com/~pere/blog/tags/english">english</a>, <a href="http://www.hungry.com/~pere/blog/tags/standard">standard</a>.
 686
 687
 688       </div>
 689     </div>
 690     <div class="padding"></div>
 691
 692     <div class="entry">
 693       <div class="title">
 694         <a href="http://www.hungry.com/~pere/blog/Officeshots_still_going_strong.html">Officeshots still going strong</a>
 695       </div>
 696       <div class="date">
 697         25th December 2010
 698       </div>
 699       <div class="body">
 700         <p>Half a year ago I
 701 <a href="http://www.hungry.com/~pere/blog/Officeshots_taking_shape.html">wrote
 702 a bit</a> about <a href="http://www.officeshots.org/">OfficeShots</a>,
 703 a web service to allow anyone to test how ODF documents are handled by
 704 the different programs reading and writing the ODF format.</p>
 705
 706 <p>I just had a look at the service, and it seem to be going strong.
 707 Very interesting to see the results reported in the gallery, how
 708 different Office implementations handle different ODF features.  Sad
 709 to see that KOffice was not doing it very well, and happy to see that
 710 LibreOffice has been tested already (but sadly not listed as a option
 711 for OfficeShots users yet).  I am glad to see that the ODF community
 712 got such a great test tool available.</p>
 713
 714       </div>
 715       <div class="tags">
 716
 717
 718         Tags: <a href="http://www.hungry.com/~pere/blog/tags/english">english</a>, <a href="http://www.hungry.com/~pere/blog/tags/standard">standard</a>.
 719
 720
 721       </div>
 722     </div>
 723     <div class="padding"></div>
 724
 725     <div class="entry">
 726       <div class="title">
 727         <a href="http://www.hungry.com/~pere/blog/165_norske_overv_kningskamera_registert_s__langt_i_OpenStreetmap_org.html">165 norske overvåkningskamera registert så langt i OpenStreetmap.org</a>
 728       </div>
 729       <div class="date">
 730         24th December 2010
 731       </div>
 732       <div class="body">
 733         <p>Jeg flikket litt på OpenStreetmap.org i går, og oppdaget ved en
 734 tilfeldighet at det er en rekke noder som representerer
 735 overvåkningskamera som ikke blir med på kartet med overvåkningskamera
 736 i Norge som
 737 <a href="http://www.hungry.com/~pere/blog/Kart_over_overv__kningskamera_i_Norge.html">jeg
 738 laget</a> for snart to år siden.  Fra før tok jeg med noder merket med
 739 man_made=surveillance, mens det er en rekke noder som kun er merket
 740 med highway=speed_camera.  Endret på koden som henter ut kameralisten
 741 fra OSM, og vips er antall kamera økt til 165.</p>
 742
 743 <a href="http://www.hungry.com/~pere/surveillance-norway/">Kartet</a>
 744 er fortsatt ikke komplett, så hvis du ser noen kamera som mangler,
 745 legg inn ved å følge instruksene fra
 746 <a href="http://personvern.no/wiki/index.php/Kameraovervåkning">prosjektsiden</a>.
 747 Hvis du vet om noen flere måter å merke overvåkningskamera i OSM, ta
 748 kontakt slik at jeg kan få med også disse.</p>
 749
 750       </div>
 751       <div class="tags">
 752
 753
 754         Tags: <a href="http://www.hungry.com/~pere/blog/tags/norsk">norsk</a>, <a href="http://www.hungry.com/~pere/blog/tags/personvern">personvern</a>, <a href="http://www.hungry.com/~pere/blog/tags/surveillance">surveillance</a>.
 755
 756
 757       </div>
 758     </div>
 759     <div class="padding"></div>
 760
 761     <div class="entry">
 762       <div class="title">
 763         <a href="http://www.hungry.com/~pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html">How to test if a laptop is working with Linux</a>
 764       </div>
 765       <div class="date">
 766         22nd December 2010
 767       </div>
 768       <div class="body">
 769         <p>The last few days I have spent at work here at the <a
 770 href="http://www.uio.no/">University of Oslo</a> testing if the new
 771 batch of computers will work with Linux.  Every year for the last few
 772 years the university have organised shared bid of a few thousand
 773 computers, and this year HP won the bid.  Two different desktops and
 774 five different laptops are on the list this year.  We in the UNIX
 775 group want to know which one of these computers work well with RHEL
 776 and Ubuntu, the two Linux distributions we currently handle at the
 777 university.</p>
 778
 779 <p>My test method is simple, and I share it here to get feedback and
 780 perhaps inspire others to test hardware as well.  To test, I PXE
 781 install the OS version of choice, and log in as my normal user and run
 782 a few applications and plug in selected pieces of hardware.  When
 783 something fail, I make a note about this in the test matrix and move
 784 on.  If I have some spare time I try to report the bug to the OS
 785 vendor, but as I only have the machines for a short time, I rarely
 786 have the time to do this for all the problems I find.</p>
 787
 788 <p>Anyway, to get to the point of this post.  Here is the simple tests
 789 I perform on a new model.</p>
 790
 791 <ul>
 792
 793 <li>Is PXE installation working?  I'm testing with RHEL6, Ubuntu Lucid
 794 and Ubuntu Maverik at the moment.  If I feel like it, I also test with
 795 RHEL5 and Debian Edu/Squeeze.</li>
 796
 797 <li>Is X.org working?  If the graphical login screen show up after
 798 installation, X.org is working.</li>
 799
 800 <li>Is hardware accelerated OpenGL working?  Running glxgears (in
 801 package mesa-utils on Ubuntu) and writing down the frames per second
 802 reported by the program.</li>
 803
 804 <li>Is sound working?  With Gnome and KDE, a sound is played when
 805 logging in, and if I can hear this the test is successful.  If there
 806 are several audio exits on the machine, I try them all and check if
 807 the Gnome/KDE audio mixer can control where to send the sound.  I
 808 normally test this by playing
 809 <a href="http://www.nuug.no/aktiviteter/20101012-chef/ ">a HTML5
 810 video</a> in Firefox/Iceweasel.</li>
 811
 812 <li>Is the USB subsystem working?  I test this by plugging in a USB
 813 memory stick and see if Gnome/KDE notices this.</li>
 814
 815 <li>Is the CD/DVD player working?  I test this by inserting any CD/DVD
 816 I have lying around, and see if Gnome/KDE notices this.</li>
 817
 818 <li>Is any built in camera working?  Test using cheese, and see if a
 819 picture from the v4l device show up.</li>
 820
 821 <li>Is bluetooth working?  Use the Gnome/KDE browsing tool to see if
 822 any bluetooth devices are discovered.  In my office, I normally see a
 823 few.</li>
 824
 825 <li>For laptops, is the SD or Compaq Flash reader working.  I have
 826 memory modules lying around, and stick them in and see if Gnome/KDE
 827 notice this.</li>
 828
 829 <li>For laptops, is suspend/hibernate working?  I'm testing if the
 830 special button work, and if the laptop continue to work after
 831 resume.</li>
 832
 833 <li>For laptops, is the extra buttons working, like audio level,
 834 adjusting background light, switching on/off external video output,
 835 switching on/off wifi, bluetooth, etc?  The set of buttons differ from
 836 laptop to laptop, so I just write down which are working and which are
 837 not.</li>
 838
 839 <li>Some laptops have smart card readers, finger print readers,
 840 acceleration sensors etc.  I rarely test these, as I do not know how
 841 to quickly test if they are working or not, so I only document their
 842 existence.</li>
 843
 844 </ul>
 845
 846 <p>By now I suspect you are really curious what the test results are
 847 for the HP machines I am testing.  I'm not done yet, so I will report
 848 the test results later.  For now I can report that HP 8100 Elite work
 849 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
 850 and audio fail on RHEL6.  Ubuntu Maverik worked with 8440p.  As you
 851 can see, I have most machines left to test.  One interesting
 852 observation is that Ubuntu Lucid has almost twice the frame rate than
 853 RHEL6 with glxgears.  No idea why.</p>
 854
 855       </div>
 856       <div class="tags">
 857
 858
 859         Tags: <a href="http://www.hungry.com/~pere/blog/tags/debian">debian</a>, <a href="http://www.hungry.com/~pere/blog/tags/debian edu">debian edu</a>, <a href="http://www.hungry.com/~pere/blog/tags/english">english</a>.
 860
 861
 862       </div>
 863     </div>
 864     <div class="padding"></div>
 865
 866     <div class="entry">
 867       <div class="title">
 868         <a href="http://www.hungry.com/~pere/blog/Some_thoughts_on_BitCoins.html">Some thoughts on BitCoins</a>
 869       </div>
 870       <div class="date">
 871         11th December 2010
 872       </div>
 873       <div class="body">
 874         <p>As I continue to explore
 875 <a href="http://www.bitcoin.org/">BitCoin</a>, I've starting to wonder
 876 what properties the system have, and how it will be affected by laws
 877 and regulations here in Norway.  Here are some random notes.</p>
 878
 879 <p>One interesting thing to note is that since the transactions are
 880 verified using a peer to peer network, all details about a transaction
 881 is known to everyone.  This means that if a BitCoin address has been
 882 published like I did with mine in my initial post about BitCoin, it is
 883 possible for everyone to see how many BitCoins have been transfered to
 884 that address.  There is even a web service to look at the details for
 885 all transactions.  There I can see that my address
 886 <a href="http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a>
 887 have received 16.06 Bitcoin, the
 888 <a href="http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3">1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3</a>
 889 address of Simon Phipps have received 181.97 BitCoin and the address
 890 <a href="http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt</A>
 891 of EFF have received 2447.38 BitCoins so far.  Thank you to each and
 892 every one of you that donated bitcoins to support my activity. The
 893 fact that anyone can see how much money was transfered to a given
 894 address make it more obvious why the BitCoin community recommend to
 895 generate and hand out a new address for each transaction.  I'm told
 896 there is no way to track which addresses belong to a given person or
 897 organisation without the person or organisation revealing it
 898 themselves, as Simon, EFF and I have done.</p>
 899
 900 <p>In Norway, and in most other countries, there are laws and
 901 regulations limiting how much money one can transfer across the border
 902 without declaring it.  There are money laundering, tax and accounting
 903 laws and regulations I would expect to apply to the use of BitCoin.
 904 If the Skolelinux foundation
 905 (<a href="http://linuxiskolen.no/slxdebianlabs/donations.html">SLX
 906 Debian Labs</a>) were to accept donations in BitCoin in addition to
 907 normal bank transfers like EFF is doing, how should this be accounted?
 908 Given that it is impossible to know if money can cross the border or
 909 not, should everything or nothing be declared?  What exchange rate
 910 should be used when calculating taxes?  Would receivers have to pay
 911 income tax if the foundation were to pay Skolelinux contributors in
 912 BitCoin?  I have no idea, but it would be interesting to know.</p>
 913
 914 <p>For a currency to be useful and successful, it must be trusted and
 915 accepted by a lot of users.  It must be possible to get easy access to
 916 the currency (as a wage or using currency exchanges), and it must be
 917 easy to spend it.  At the moment BitCoin seem fairly easy to get
 918 access to, but there are very few places to spend it.  I am not really
 919 a regular user of any of the vendor types currently accepting BitCoin,
 920 so I wonder when my kind of shop would start accepting BitCoins.  I
 921 would like to buy electronics, travels and subway tickets, not herbs
 922 and books. :) The currency is young, and this will improve over time
 923 if it become popular, but I suspect regular banks will start to lobby
 924 to get BitCoin declared illegal if it become popular.  I'm sure they
 925 will claim it is helping fund terrorism and money laundering (which
 926 probably would be true, as is any currency in existence), but I
 927 believe the problems should be solved elsewhere and not by blaming
 928 currencies.</p>
 929
 930 <p>The process of creating new BitCoins is called mining, and it is
 931 CPU intensive process that depend on a bit of luck as well (as one is
 932 competing against all the other miners currently spending CPU cycles
 933 to see which one get the next lump of cash).  The "winner" get 50
 934 BitCoin when this happen.  Yesterday I came across the obvious way to
 935 join forces to increase ones changes of getting at least some coins,
 936 by coordinating the work on mining BitCoins across several machines
 937 and people, and sharing the result if one is lucky and get the 50
 938 BitCoins.  Check out
 939 <a href="http://www.bluishcoder.co.nz/bitcoin-pool/">BitCoin Pool</a>
 940 if this sounds interesting.  I have not had time to try to set up a
 941 machine to participate there yet, but have seen that running on ones
 942 own for a few days have not yield any BitCoins througth mining
 943 yet.</p>
 944
 945 <p>Update 2010-12-15: Found an <a
 946 href="http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi">interesting
 947 criticism</a> of bitcoin.  Not quite sure how valid it is, but thought
 948 it was interesting to read.  The arguments presented seem to be
 949 equally valid for gold, which was used as a currency for many years.</p>
 950
 951       </div>
 952       <div class="tags">
 953
 954
 955         Tags: <a href="http://www.hungry.com/~pere/blog/tags/bitcoin">bitcoin</a>, <a href="http://www.hungry.com/~pere/blog/tags/debian">debian</a>, <a href="http://www.hungry.com/~pere/blog/tags/english">english</a>, <a href="http://www.hungry.com/~pere/blog/tags/personvern">personvern</a>, <a href="http://www.hungry.com/~pere/blog/tags/sikkerhet">sikkerhet</a>.
 956
 957
 958       </div>
 959     </div>
 960     <div class="padding"></div>
 961
 962     <div class="entry">
 963       <div class="title">
 964         <a href="http://www.hungry.com/~pere/blog/Pornoskannerne_p__flyplassene_bedrer_visst_ikke_sikkerheten.html">Pornoskannerne på flyplassene bedrer visst ikke sikkerheten</a>
 965       </div>
 966       <div class="date">
 967         11th December 2010
 968       </div>
 969       <div class="body">
 970         <p>Via <a href="http://webmink.com/2010/12/10/links-for-2010-12-10/">en
 971 blogpost fra Simon Phipps i går</a>, fant jeg en referanse til
 972 <a href="http://www.washingtontimes.com/news/2010/dec/9/exposed-tsas-x-rated-scanner-fraud/">en
 973 artikkel i Washington Times</a> som igjen refererer til en artikkel i
 974 det fagfellevurderte tidsskriftet Journal of Transportation Security
 975 med tittelen
 976 "<a href="http://springerlink.com/content/g6620thk08679160/fulltext.html">An
 977 evaluation of airport x-ray backscatter units based on image
 978 characteristics</a>" som enkelt konstaterer at
 979 <a href="http://www.dailysquib.co.uk/?a=2389&c=124">pornoscannerne</a>
 980 som kler av reisende på flyplasser ikke er i stand til å avsløre det
 981 produsenten og amerikanske myndigheter sier de skal avsløre.  Kort
 982 sagt, de bedrer ikke sikkerheten.  Reisende må altså la ansatte på
 983 flyplasser <a href="http://www.thousandsstandingaround.org/">se dem
 984 nakne eller la seg beføle i skrittet</a> uten grunn.  Jeg vil
 985 fortsette å nekte å bruke disse pornoskannerne, unngå flyplasser der
 986 de er tatt i bruk, og reise med andre transportmidler enn fly hvis jeg
 987 kan.</p>
 988
 989       </div>
 990       <div class="tags">
 991
 992
 993         Tags: <a href="http://www.hungry.com/~pere/blog/tags/norsk">norsk</a>, <a href="http://www.hungry.com/~pere/blog/tags/personvern">personvern</a>, <a href="http://www.hungry.com/~pere/blog/tags/sikkerhet">sikkerhet</a>.
 994
 995
 996       </div>
 997     </div>
 998     <div class="padding"></div>
 999
1000     <div class="entry">
1001       <div class="title">
1002         <a href="http://www.hungry.com/~pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html">Now accepting bitcoins - anonymous and distributed p2p crypto-money</a>
1003       </div>
1004       <div class="date">
1005         10th December 2010
1006       </div>
1007       <div class="body">
1008         <p>With this weeks lawless
1009 <a href="http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html">governmental
1010 attacks</a> on Wikileak and
1011 <a href="http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech">free
1012 speech</a>, it has become obvious that PayPal, visa and mastercard can
1013 not be trusted to handle money transactions.
1014 A blog post from
1015 <a href="http://webmink.com/2010/12/06/now-accepting-bitcoin/">Simon
1016 Phipps on bitcoin</a> reminded me about a project that a friend of
1017 mine mentioned earlier.  I decided to follow Simon's example, and get
1018 involved with <a href="http://www.bitcoin.org/">BitCoin</a>.  I got
1019 some help from my friend to get it all running, and he even handed me
1020 some bitcoins to get started.  I even donated a few bitcoins to Simon
1021 for helping me remember BitCoin.</p>
1022
1023 <p>So, what is bitcoins, you probably wonder?  It is a digital
1024 crypto-currency, decentralised and handled using peer-to-peer
1025 networks.  It allows anonymous transactions and prohibits central
1026 control over the transactions, making it impossible for governments
1027 and companies alike to block donations and other transactions.  The
1028 source is free software, and while the key dependency wxWidgets 2.9
1029 for the graphical user interface is missing in Debian, the command
1030 line client builds just fine.  Hopefully Jonas
1031 <a href="http://bugs.debian.org/578157">will get the package into
1032 Debian</a> soon.</p>
1033
1034 <p>Bitcoins can be converted to other currencies, like USD and EUR.
1035 There are <a href="http://www.bitcoin.org/trade">companies accepting
1036 bitcoins</a> when selling services and goods, and there are even
1037 currency "stock" markets where the exchange rate is decided.  There
1038 are not many users so far, but the concept seems promising.  If you
1039 want to get started and lack a friend with any bitcoins to spare,
1040 you can even get
1041 <a href="https://freebitcoins.appspot.com/">some for free</a> (0.05
1042 bitcoin at the time of writing).  Use
1043 <a href="http://www.bitcoinwatch.com/">BitcoinWatch</a> to keep an eye
1044 on the current exchange rates.</p>
1045
1046 <p>As an experiment, I have decided to set up bitcoind on one of my
1047 machines.  If you want to support my activity, please send Bitcoin
1048 donations to the address
1049 <b>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</b>.  Thank you!</p>
1050
1051       </div>
1052       <div class="tags">
1053
1054
1055         Tags: <a href="http://www.hungry.com/~pere/blog/tags/bitcoin">bitcoin</a>, <a href="http://www.hungry.com/~pere/blog/tags/debian">debian</a>, <a href="http://www.hungry.com/~pere/blog/tags/english">english</a>, <a href="http://www.hungry.com/~pere/blog/tags/personvern">personvern</a>, <a href="http://www.hungry.com/~pere/blog/tags/sikkerhet">sikkerhet</a>.
1056
1057
1058       </div>
1059     </div>
1060     <div class="padding"></div>
1061
1062     <div class="entry">
1063       <div class="title">
1064         <a href="http://www.hungry.com/~pere/blog/Martin_Bekkelund__En_stille_b_nn_om_Datalagringsdirektivet.html">Martin Bekkelund: En stille bønn om Datalagringsdirektivet</a>
1065       </div>
1066       <div class="date">
1067          9th December 2010
1068       </div>
1069       <div class="body">
1070         <p><a href="http://www.bekkelund.net/">Martin Bekkelund</a> ved
1071 <a href="http://www.friprog.no/">friprog-senteret</a> har skrevet
1072 følgende
1073 <a href="http://www.bekkelund.net/2010/12/09/en-stille-bonn/">korte
1074 oppsummering</a> rundt datalagringsdirektivet, som jeg videreformidler
1075 her.</p>
1076
1077 <p><blockquote><strong>Det pågår i disse dager en intens diskusjon om
1078 innføring av Datalagringsdirektivet (<acronym
1079 title="Datalagringsdirektivet">DLD</acronym>) i norsk rett. Kanskje
1080 har du gjort deg opp en mening, kanskje er du usikker. I begge
1081 tilfeller ber jeg deg lese videre.</strong></p>
1082
1083 <p>Samtlige fagmiljøer, både i Norge og EU, har konkludert med at
1084 <acronym title="Datalagringsdirektivet">DLD</acronym> ikke bør
1085 innføres på nåværende tidspunkt. Den tekniske kvaliteten på direktivet
1086 er dårlig, det griper uforholdsmessig inn i personvernet, det har
1087 store mangler og viktige spørsmål som hvem som skal ha tilgang og
1088 hvordan data skal lagres er fortsatt uavklart.</p>
1089
1090 <ul>
1091 <li><a href="http://ikt-norge.no/norge-kan-slippe-datalagringsdirektivet/">EU-ekspertene sier</a> at konsekvensene av å benytte vetoretten er minimale</li>
1092 <li><a href="http://www.regjeringen.no/pages/2281080/Deninternasjonalejuristkommisjon.pdf">Juristene påpeker</a> at direktivet er i strid med EMK</li>
1093 <li><a href="http://www.dagbladet.no/2010/12/06/kultur/debatt/kronikk/dld/personvern/14594699/">Datatilsynet sier</a> direktivet får store konsekvenser for personvernet og at direktivet er irreversibelt</li>
1094 <li><a href="http://www.bekkelund.net/?s=dld">Teknologene sier</a> at sikker lagring ikke er mulig, at det er svært enkelt å omgå og mulig å manipulere data og produsere falske beviser</li>
1095 <li><a href="http://www.regjeringen.no/pages/2281080/NJ_247460_1_P.pdf">Pressen sier</a> nei av hensyn til kildevernet</li>
1096 <li>Det er store <a href="http://tetzschner.blogspot.com/2010/03/den-tyske-forfatningsdomstol.html">interne</a> <a href="http://stoppdld.no/2010/03/02/datalagring-stoppet-av-tysk-forfatningsdomstol/">stridigheter</a> i EU. Blant annet har den tyske forfatningsdomstolen funnet at måten <acronym title="Datalagringsdirektivet">DLD</acronym> er innført på er i strid med tysk grunnlov</li>
1097 <li>Alle de store <a href="http://www.bekkelund.net/2010/12/08/lokasjonsdata-og-datalagringsdirektivet/">operatørene og tilbyderne sier nei</a>, av tekniske og personvernmessige årsaker</li>
1098 </ul>
1099
1100 <p>Jeg liker å tro at jeg er en hyggelig fyr. Jeg har et rent
1101 rulleblad, og med unntak av to fartsbøter har jeg aldri vært en byrde
1102 for samfunnet. Det akter jeg å fortsette med. Det er mange som meg,
1103 lovlydige, pliktoppfyllende borgere som aldri vil utgjøre en trussel
1104 mot noe som helst. Vi synes derfor det er trist og sårende at all vår
1105 atferd skal overvåkes døgnkontinuerlig.</p>
1106
1107 <p><strong>Understøttet av faglige vurderinger kan du trygt si nei til
1108 <acronym title="Datalagringsdirektivet">DLD</acronym>.</strong></p>
1109
1110 <p><a href="http://www.bekkelund.net/kontakt/">Ta kontakt med meg</a>
1111 hvis du har spørsmål om <acronym
1112 title="Datalagringsdirektivet">DLD</acronym>, uansett hva det måtte
1113 gjelde.</p>
1114
1115 <p class="info">Denne teksten er å anse som <a
1116 href="http://creativecommons.org/licenses/publicdomain/"><em>Public
1117 Domain</em></a>. Spre den videre til alle som kan ha nytte av
1118 den!</p>
1119 </blockquote></p>
1120
1121 <p>Siste <a href="http://www.nettavisen.no/it/article3043918.ece">melding
1122 fra Nettavisen</a> er at regjeringen planlegger å fremme sitt forslag
1123 til implementering av datalagringsdirektivet i morgen, i ly av
1124 fredprisutdelingen for å få minst mulig pressedekning om saken.  Vi
1125 får snart se om det stemmer.</p>
1126
1127       </div>
1128       <div class="tags">
1129
1130
1131         Tags: <a href="http://www.hungry.com/~pere/blog/tags/dld">dld</a>, <a href="http://www.hungry.com/~pere/blog/tags/norsk">norsk</a>, <a href="http://www.hungry.com/~pere/blog/tags/personvern">personvern</a>.
1132
1133
1134       </div>
1135     </div>
1136     <div class="padding"></div>
1137
1138     <div class="entry">
1139       <div class="title">
1140         <a href="http://www.hungry.com/~pere/blog/Student_group_continue_the_work_on_my_Reprap_3D_printer.html">Student group continue the work on my Reprap 3D printer</a>
1141       </div>
1142       <div class="date">
1143          9th December 2010
1144       </div>
1145       <div class="body">
1146         <p>A few days ago, I was introduces to some students in the robot
1147 student assosiation <a href="http://www.robotica.no/">Robotica
1148 Osloensis</a> at the University of Oslo where I work, who planned to
1149 get their own 3D printer.  They wanted to learn from me based on my
1150 work in the area.  After having a short lunch meeting with them, I
1151 offered them to borrow my reprap kit, as I never had time to complete
1152 the build and this seem unlike to change any time soon.  I look
1153 forward to see how this goes.  This monday their volunteer driver
1154 picked up my kit and drove it to their lab, and tomorrow I am told the
1155 last exam is over so they can start work on getting the 3D printer
1156 operational.</p>
1157
1158 <p>The robotic group have already build several robots on their own,
1159 and seem capable of getting the reprap operational.  I really look
1160 forward to being able to print all the cool 3D designs published on
1161 <a href="http://www.thingiverse.com/">Thingiverse</a>.  I even got
1162 some 3D scans I got made during Dagen@IFI when one of the groups at
1163 the computer science department at the university demonstrated their
1164 very cool 3D scanner.</p>
1165
1166       </div>
1167       <div class="tags">
1168
1169
1170         Tags: <a href="http://www.hungry.com/~pere/blog/tags/3d-printer">3d-printer</a>, <a href="http://www.hungry.com/~pere/blog/tags/english">english</a>, <a href="http://www.hungry.com/~pere/blog/tags/reprap">reprap</a>.
1171
1172
1173       </div>
1174     </div>
1175     <div class="padding"></div>
1176
1177     <p style="text-align: right;"><a href="12.rss"><img src="http://www.hungry.com/~pere/blog/xml.gif" alt="RSS Feed" width="36" height="14" /></a></p>
1178     <div id="sidebar">
1179
1180
1181
1182 <h2>Archive</h2>
1183 <ul>
1184
1185 <li>2025
1186 <ul>
1187
1188 <li><a href="http://www.hungry.com/~pere/blog/archive/2025/01/">January (4)</a></li>
1189
1190 <li><a href="http://www.hungry.com/~pere/blog/archive/2025/02/">February (3)</a></li>
1191
1192 </ul></li>
1193
1194 <li>2024
1195 <ul>
1196
1197 <li><a href="http://www.hungry.com/~pere/blog/archive/2024/01/">January (1)</a></li>
1198
1199 <li><a href="http://www.hungry.com/~pere/blog/archive/2024/02/">February (1)</a></li>
1200
1201 <li><a href="http://www.hungry.com/~pere/blog/archive/2024/03/">March (2)</a></li>
1202
1203 <li><a href="http://www.hungry.com/~pere/blog/archive/2024/04/">April (3)</a></li>
1204
1205 <li><a href="http://www.hungry.com/~pere/blog/archive/2024/05/">May (1)</a></li>
1206
1207 <li><a href="http://www.hungry.com/~pere/blog/archive/2024/06/">June (1)</a></li>
1208
1209 <li><a href="http://www.hungry.com/~pere/blog/archive/2024/07/">July (2)</a></li>
1210
1211 <li><a href="http://www.hungry.com/~pere/blog/archive/2024/12/">December (1)</a></li>
1212
1213 </ul></li>
1214
1215 <li>2023
1216 <ul>
1217
1218 <li><a href="http://www.hungry.com/~pere/blog/archive/2023/01/">January (3)</a></li>
1219
1220 <li><a href="http://www.hungry.com/~pere/blog/archive/2023/02/">February (1)</a></li>
1221
1222 <li><a href="http://www.hungry.com/~pere/blog/archive/2023/04/">April (2)</a></li>
1223
1224 <li><a href="http://www.hungry.com/~pere/blog/archive/2023/05/">May (3)</a></li>
1225
1226 <li><a href="http://www.hungry.com/~pere/blog/archive/2023/06/">June (1)</a></li>
1227
1228 <li><a href="http://www.hungry.com/~pere/blog/archive/2023/08/">August (1)</a></li>
1229
1230 <li><a href="http://www.hungry.com/~pere/blog/archive/2023/09/">September (1)</a></li>
1231
1232 <li><a href="http://www.hungry.com/~pere/blog/archive/2023/10/">October (1)</a></li>
1233
1234 <li><a href="http://www.hungry.com/~pere/blog/archive/2023/11/">November (4)</a></li>
1235
1236 <li><a href="http://www.hungry.com/~pere/blog/archive/2023/12/">December (1)</a></li>
1237
1238 </ul></li>
1239
1240 <li>2022
1241 <ul>
1242
1243 <li><a href="http://www.hungry.com/~pere/blog/archive/2022/02/">February (1)</a></li>
1244
1245 <li><a href="http://www.hungry.com/~pere/blog/archive/2022/03/">March (3)</a></li>
1246
1247 <li><a href="http://www.hungry.com/~pere/blog/archive/2022/04/">April (2)</a></li>
1248
1249 <li><a href="http://www.hungry.com/~pere/blog/archive/2022/06/">June (2)</a></li>
1250
1251 <li><a href="http://www.hungry.com/~pere/blog/archive/2022/07/">July (1)</a></li>
1252
1253 <li><a href="http://www.hungry.com/~pere/blog/archive/2022/09/">September (1)</a></li>
1254
1255 <li><a href="http://www.hungry.com/~pere/blog/archive/2022/10/">October (1)</a></li>
1256
1257 <li><a href="http://www.hungry.com/~pere/blog/archive/2022/12/">December (1)</a></li>
1258
1259 </ul></li>
1260
1261 <li>2021
1262 <ul>
1263
1264 <li><a href="http://www.hungry.com/~pere/blog/archive/2021/01/">January (2)</a></li>
1265
1266 <li><a href="http://www.hungry.com/~pere/blog/archive/2021/02/">February (1)</a></li>
1267
1268 <li><a href="http://www.hungry.com/~pere/blog/archive/2021/05/">May (1)</a></li>
1269
1270 <li><a href="http://www.hungry.com/~pere/blog/archive/2021/06/">June (1)</a></li>
1271
1272 <li><a href="http://www.hungry.com/~pere/blog/archive/2021/07/">July (3)</a></li>
1273
1274 <li><a href="http://www.hungry.com/~pere/blog/archive/2021/08/">August (1)</a></li>
1275
1276 <li><a href="http://www.hungry.com/~pere/blog/archive/2021/09/">September (1)</a></li>
1277
1278 <li><a href="http://www.hungry.com/~pere/blog/archive/2021/10/">October (1)</a></li>
1279
1280 <li><a href="http://www.hungry.com/~pere/blog/archive/2021/12/">December (1)</a></li>
1281
1282 </ul></li>
1283
1284 <li>2020
1285 <ul>
1286
1287 <li><a href="http://www.hungry.com/~pere/blog/archive/2020/02/">February (2)</a></li>
1288
1289 <li><a href="http://www.hungry.com/~pere/blog/archive/2020/03/">March (2)</a></li>
1290
1291 <li><a href="http://www.hungry.com/~pere/blog/archive/2020/04/">April (2)</a></li>
1292
1293 <li><a href="http://www.hungry.com/~pere/blog/archive/2020/05/">May (3)</a></li>
1294
1295 <li><a href="http://www.hungry.com/~pere/blog/archive/2020/06/">June (2)</a></li>
1296
1297 <li><a href="http://www.hungry.com/~pere/blog/archive/2020/07/">July (1)</a></li>
1298
1299 <li><a href="http://www.hungry.com/~pere/blog/archive/2020/09/">September (1)</a></li>
1300
1301 <li><a href="http://www.hungry.com/~pere/blog/archive/2020/10/">October (1)</a></li>
1302
1303 <li><a href="http://www.hungry.com/~pere/blog/archive/2020/11/">November (1)</a></li>
1304
1305 </ul></li>
1306
1307 <li>2019
1308 <ul>
1309
1310 <li><a href="http://www.hungry.com/~pere/blog/archive/2019/01/">January (4)</a></li>
1311
1312 <li><a href="http://www.hungry.com/~pere/blog/archive/2019/02/">February (3)</a></li>
1313
1314 <li><a href="http://www.hungry.com/~pere/blog/archive/2019/03/">March (3)</a></li>
1315
1316 <li><a href="http://www.hungry.com/~pere/blog/archive/2019/05/">May (2)</a></li>
1317
1318 <li><a href="http://www.hungry.com/~pere/blog/archive/2019/06/">June (5)</a></li>
1319
1320 <li><a href="http://www.hungry.com/~pere/blog/archive/2019/07/">July (2)</a></li>
1321
1322 <li><a href="http://www.hungry.com/~pere/blog/archive/2019/08/">August (1)</a></li>
1323
1324 <li><a href="http://www.hungry.com/~pere/blog/archive/2019/09/">September (1)</a></li>
1325
1326 <li><a href="http://www.hungry.com/~pere/blog/archive/2019/11/">November (1)</a></li>
1327
1328 <li><a href="http://www.hungry.com/~pere/blog/archive/2019/12/">December (4)</a></li>
1329
1330 </ul></li>
1331
1332 <li>2018
1333 <ul>
1334
1335 <li><a href="http://www.hungry.com/~pere/blog/archive/2018/01/">January (1)</a></li>
1336
1337 <li><a href="http://www.hungry.com/~pere/blog/archive/2018/02/">February (5)</a></li>
1338
1339 <li><a href="http://www.hungry.com/~pere/blog/archive/2018/03/">March (5)</a></li>
1340
1341 <li><a href="http://www.hungry.com/~pere/blog/archive/2018/04/">April (3)</a></li>
1342
1343 <li><a href="http://www.hungry.com/~pere/blog/archive/2018/06/">June (2)</a></li>
1344
1345 <li><a href="http://www.hungry.com/~pere/blog/archive/2018/07/">July (5)</a></li>
1346
1347 <li><a href="http://www.hungry.com/~pere/blog/archive/2018/08/">August (3)</a></li>
1348
1349 <li><a href="http://www.hungry.com/~pere/blog/archive/2018/09/">September (3)</a></li>
1350
1351 <li><a href="http://www.hungry.com/~pere/blog/archive/2018/10/">October (5)</a></li>
1352
1353 <li><a href="http://www.hungry.com/~pere/blog/archive/2018/11/">November (2)</a></li>
1354
1355 <li><a href="http://www.hungry.com/~pere/blog/archive/2018/12/">December (4)</a></li>
1356
1357 </ul></li>
1358
1359 <li>2017
1360 <ul>
1361
1362 <li><a href="http://www.hungry.com/~pere/blog/archive/2017/01/">January (4)</a></li>
1363
1364 <li><a href="http://www.hungry.com/~pere/blog/archive/2017/02/">February (3)</a></li>
1365
1366 <li><a href="http://www.hungry.com/~pere/blog/archive/2017/03/">March (5)</a></li>
1367
1368 <li><a href="http://www.hungry.com/~pere/blog/archive/2017/04/">April (2)</a></li>
1369
1370 <li><a href="http://www.hungry.com/~pere/blog/archive/2017/06/">June (5)</a></li>
1371
1372 <li><a href="http://www.hungry.com/~pere/blog/archive/2017/07/">July (1)</a></li>
1373
1374 <li><a href="http://www.hungry.com/~pere/blog/archive/2017/08/">August (1)</a></li>
1375
1376 <li><a href="http://www.hungry.com/~pere/blog/archive/2017/09/">September (3)</a></li>
1377
1378 <li><a href="http://www.hungry.com/~pere/blog/archive/2017/10/">October (5)</a></li>
1379
1380 <li><a href="http://www.hungry.com/~pere/blog/archive/2017/11/">November (3)</a></li>
1381
1382 <li><a href="http://www.hungry.com/~pere/blog/archive/2017/12/">December (4)</a></li>
1383
1384 </ul></li>
1385
1386 <li>2016
1387 <ul>
1388
1389 <li><a href="http://www.hungry.com/~pere/blog/archive/2016/01/">January (3)</a></li>
1390
1391 <li><a href="http://www.hungry.com/~pere/blog/archive/2016/02/">February (2)</a></li>
1392
1393 <li><a href="http://www.hungry.com/~pere/blog/archive/2016/03/">March (3)</a></li>
1394
1395 <li><a href="http://www.hungry.com/~pere/blog/archive/2016/04/">April (8)</a></li>
1396
1397 <li><a href="http://www.hungry.com/~pere/blog/archive/2016/05/">May (8)</a></li>
1398
1399 <li><a href="http://www.hungry.com/~pere/blog/archive/2016/06/">June (2)</a></li>
1400
1401 <li><a href="http://www.hungry.com/~pere/blog/archive/2016/07/">July (2)</a></li>
1402
1403 <li><a href="http://www.hungry.com/~pere/blog/archive/2016/08/">August (5)</a></li>
1404
1405 <li><a href="http://www.hungry.com/~pere/blog/archive/2016/09/">September (2)</a></li>
1406
1407 <li><a href="http://www.hungry.com/~pere/blog/archive/2016/10/">October (3)</a></li>
1408
1409 <li><a href="http://www.hungry.com/~pere/blog/archive/2016/11/">November (8)</a></li>
1410
1411 <li><a href="http://www.hungry.com/~pere/blog/archive/2016/12/">December (5)</a></li>
1412
1413 </ul></li>
1414
1415 <li>2015
1416 <ul>
1417
1418 <li><a href="http://www.hungry.com/~pere/blog/archive/2015/01/">January (7)</a></li>
1419
1420 <li><a href="http://www.hungry.com/~pere/blog/archive/2015/02/">February (6)</a></li>
1421
1422 <li><a href="http://www.hungry.com/~pere/blog/archive/2015/03/">March (1)</a></li>
1423
1424 <li><a href="http://www.hungry.com/~pere/blog/archive/2015/04/">April (4)</a></li>
1425
1426 <li><a href="http://www.hungry.com/~pere/blog/archive/2015/05/">May (3)</a></li>
1427
1428 <li><a href="http://www.hungry.com/~pere/blog/archive/2015/06/">June (4)</a></li>
1429
1430 <li><a href="http://www.hungry.com/~pere/blog/archive/2015/07/">July (6)</a></li>
1431
1432 <li><a href="http://www.hungry.com/~pere/blog/archive/2015/08/">August (2)</a></li>
1433
1434 <li><a href="http://www.hungry.com/~pere/blog/archive/2015/09/">September (2)</a></li>
1435
1436 <li><a href="http://www.hungry.com/~pere/blog/archive/2015/10/">October (9)</a></li>
1437
1438 <li><a href="http://www.hungry.com/~pere/blog/archive/2015/11/">November (6)</a></li>
1439
1440 <li><a href="http://www.hungry.com/~pere/blog/archive/2015/12/">December (3)</a></li>
1441
1442 </ul></li>
1443
1444 <li>2014
1445 <ul>
1446
1447 <li><a href="http://www.hungry.com/~pere/blog/archive/2014/01/">January (2)</a></li>
1448
1449 <li><a href="http://www.hungry.com/~pere/blog/archive/2014/02/">February (3)</a></li>
1450
1451 <li><a href="http://www.hungry.com/~pere/blog/archive/2014/03/">March (8)</a></li>
1452
1453 <li><a href="http://www.hungry.com/~pere/blog/archive/2014/04/">April (7)</a></li>
1454
1455 <li><a href="http://www.hungry.com/~pere/blog/archive/2014/05/">May (1)</a></li>
1456
1457 <li><a href="http://www.hungry.com/~pere/blog/archive/2014/06/">June (2)</a></li>
1458
1459 <li><a href="http://www.hungry.com/~pere/blog/archive/2014/07/">July (2)</a></li>
1460
1461 <li><a href="http://www.hungry.com/~pere/blog/archive/2014/08/">August (2)</a></li>
1462
1463 <li><a href="http://www.hungry.com/~pere/blog/archive/2014/09/">September (5)</a></li>
1464
1465 <li><a href="http://www.hungry.com/~pere/blog/archive/2014/10/">October (6)</a></li>
1466
1467 <li><a href="http://www.hungry.com/~pere/blog/archive/2014/11/">November (3)</a></li>
1468
1469 <li><a href="http://www.hungry.com/~pere/blog/archive/2014/12/">December (5)</a></li>
1470
1471 </ul></li>
1472
1473 <li>2013
1474 <ul>
1475
1476 <li><a href="http://www.hungry.com/~pere/blog/archive/2013/01/">January (11)</a></li>
1477
1478 <li><a href="http://www.hungry.com/~pere/blog/archive/2013/02/">February (9)</a></li>
1479
1480 <li><a href="http://www.hungry.com/~pere/blog/archive/2013/03/">March (9)</a></li>
1481
1482 <li><a href="http://www.hungry.com/~pere/blog/archive/2013/04/">April (6)</a></li>
1483
1484 <li><a href="http://www.hungry.com/~pere/blog/archive/2013/05/">May (9)</a></li>
1485
1486 <li><a href="http://www.hungry.com/~pere/blog/archive/2013/06/">June (10)</a></li>
1487
1488 <li><a href="http://www.hungry.com/~pere/blog/archive/2013/07/">July (7)</a></li>
1489
1490 <li><a href="http://www.hungry.com/~pere/blog/archive/2013/08/">August (3)</a></li>
1491
1492 <li><a href="http://www.hungry.com/~pere/blog/archive/2013/09/">September (5)</a></li>
1493
1494 <li><a href="http://www.hungry.com/~pere/blog/archive/2013/10/">October (7)</a></li>
1495
1496 <li><a href="http://www.hungry.com/~pere/blog/archive/2013/11/">November (9)</a></li>
1497
1498 <li><a href="http://www.hungry.com/~pere/blog/archive/2013/12/">December (3)</a></li>
1499
1500 </ul></li>
1501
1502 <li>2012
1503 <ul>
1504
1505 <li><a href="http://www.hungry.com/~pere/blog/archive/2012/01/">January (7)</a></li>
1506
1507 <li><a href="http://www.hungry.com/~pere/blog/archive/2012/02/">February (10)</a></li>
1508
1509 <li><a href="http://www.hungry.com/~pere/blog/archive/2012/03/">March (17)</a></li>
1510
1511 <li><a href="http://www.hungry.com/~pere/blog/archive/2012/04/">April (12)</a></li>
1512
1513 <li><a href="http://www.hungry.com/~pere/blog/archive/2012/05/">May (12)</a></li>
1514
1515 <li><a href="http://www.hungry.com/~pere/blog/archive/2012/06/">June (20)</a></li>
1516
1517 <li><a href="http://www.hungry.com/~pere/blog/archive/2012/07/">July (17)</a></li>
1518
1519 <li><a href="http://www.hungry.com/~pere/blog/archive/2012/08/">August (6)</a></li>
1520
1521 <li><a href="http://www.hungry.com/~pere/blog/archive/2012/09/">September (9)</a></li>
1522
1523 <li><a href="http://www.hungry.com/~pere/blog/archive/2012/10/">October (17)</a></li>
1524
1525 <li><a href="http://www.hungry.com/~pere/blog/archive/2012/11/">November (10)</a></li>
1526
1527 <li><a href="http://www.hungry.com/~pere/blog/archive/2012/12/">December (7)</a></li>
1528
1529 </ul></li>
1530
1531 <li>2011
1532 <ul>
1533
1534 <li><a href="http://www.hungry.com/~pere/blog/archive/2011/01/">January (16)</a></li>
1535
1536 <li><a href="http://www.hungry.com/~pere/blog/archive/2011/02/">February (6)</a></li>
1537
1538 <li><a href="http://www.hungry.com/~pere/blog/archive/2011/03/">March (6)</a></li>
1539
1540 <li><a href="http://www.hungry.com/~pere/blog/archive/2011/04/">April (7)</a></li>
1541
1542 <li><a href="http://www.hungry.com/~pere/blog/archive/2011/05/">May (3)</a></li>
1543
1544 <li><a href="http://www.hungry.com/~pere/blog/archive/2011/06/">June (2)</a></li>
1545
1546 <li><a href="http://www.hungry.com/~pere/blog/archive/2011/07/">July (7)</a></li>
1547
1548 <li><a href="http://www.hungry.com/~pere/blog/archive/2011/08/">August (6)</a></li>
1549
1550 <li><a href="http://www.hungry.com/~pere/blog/archive/2011/09/">September (4)</a></li>
1551
1552 <li><a href="http://www.hungry.com/~pere/blog/archive/2011/10/">October (2)</a></li>
1553
1554 <li><a href="http://www.hungry.com/~pere/blog/archive/2011/11/">November (3)</a></li>
1555
1556 <li><a href="http://www.hungry.com/~pere/blog/archive/2011/12/">December (1)</a></li>
1557
1558 </ul></li>
1559
1560 <li>2010
1561 <ul>
1562
1563 <li><a href="http://www.hungry.com/~pere/blog/archive/2010/01/">January (2)</a></li>
1564
1565 <li><a href="http://www.hungry.com/~pere/blog/archive/2010/02/">February (1)</a></li>
1566
1567 <li><a href="http://www.hungry.com/~pere/blog/archive/2010/03/">March (3)</a></li>
1568
1569 <li><a href="http://www.hungry.com/~pere/blog/archive/2010/04/">April (3)</a></li>
1570
1571 <li><a href="http://www.hungry.com/~pere/blog/archive/2010/05/">May (9)</a></li>
1572
1573 <li><a href="http://www.hungry.com/~pere/blog/archive/2010/06/">June (14)</a></li>
1574
1575 <li><a href="http://www.hungry.com/~pere/blog/archive/2010/07/">July (12)</a></li>
1576
1577 <li><a href="http://www.hungry.com/~pere/blog/archive/2010/08/">August (13)</a></li>
1578
1579 <li><a href="http://www.hungry.com/~pere/blog/archive/2010/09/">September (7)</a></li>
1580
1581 <li><a href="http://www.hungry.com/~pere/blog/archive/2010/10/">October (9)</a></li>
1582
1583 <li><a href="http://www.hungry.com/~pere/blog/archive/2010/11/">November (13)</a></li>
1584
1585 <li><a href="http://www.hungry.com/~pere/blog/archive/2010/12/">December (12)</a></li>
1586
1587 </ul></li>
1588
1589 <li>2009
1590 <ul>
1591
1592 <li><a href="http://www.hungry.com/~pere/blog/archive/2009/01/">January (8)</a></li>
1593
1594 <li><a href="http://www.hungry.com/~pere/blog/archive/2009/02/">February (8)</a></li>
1595
1596 <li><a href="http://www.hungry.com/~pere/blog/archive/2009/03/">March (12)</a></li>
1597
1598 <li><a href="http://www.hungry.com/~pere/blog/archive/2009/04/">April (10)</a></li>
1599
1600 <li><a href="http://www.hungry.com/~pere/blog/archive/2009/05/">May (9)</a></li>
1601
1602 <li><a href="http://www.hungry.com/~pere/blog/archive/2009/06/">June (3)</a></li>
1603
1604 <li><a href="http://www.hungry.com/~pere/blog/archive/2009/07/">July (4)</a></li>
1605
1606 <li><a href="http://www.hungry.com/~pere/blog/archive/2009/08/">August (3)</a></li>
1607
1608 <li><a href="http://www.hungry.com/~pere/blog/archive/2009/09/">September (1)</a></li>
1609
1610 <li><a href="http://www.hungry.com/~pere/blog/archive/2009/10/">October (2)</a></li>
1611
1612 <li><a href="http://www.hungry.com/~pere/blog/archive/2009/11/">November (3)</a></li>
1613
1614 <li><a href="http://www.hungry.com/~pere/blog/archive/2009/12/">December (3)</a></li>
1615
1616 </ul></li>
1617
1618 <li>2008
1619 <ul>
1620
1621 <li><a href="http://www.hungry.com/~pere/blog/archive/2008/11/">November (5)</a></li>
1622
1623 <li><a href="http://www.hungry.com/~pere/blog/archive/2008/12/">December (7)</a></li>
1624
1625 </ul></li>
1626
1627 </ul>
1628
1629
1630
1631 <h2>Tags</h2>
1632 <ul>
1633
1634  <li><a href="http://www.hungry.com/~pere/blog/tags/3d-printer">3d-printer (19)</a></li>
1635
1636  <li><a href="http://www.hungry.com/~pere/blog/tags/amiga">amiga (1)</a></li>
1637
1638  <li><a href="http://www.hungry.com/~pere/blog/tags/aros">aros (1)</a></li>
1639
1640  <li><a href="http://www.hungry.com/~pere/blog/tags/bankid">bankid (4)</a></li>
1641
1642  <li><a href="http://www.hungry.com/~pere/blog/tags/betalkontant">betalkontant (9)</a></li>
1643
1644  <li><a href="http://www.hungry.com/~pere/blog/tags/bitcoin">bitcoin (13)</a></li>
1645
1646  <li><a href="http://www.hungry.com/~pere/blog/tags/bootsystem">bootsystem (17)</a></li>
1647
1648  <li><a href="http://www.hungry.com/~pere/blog/tags/bsa">bsa (2)</a></li>
1649
1650  <li><a href="http://www.hungry.com/~pere/blog/tags/chrpath">chrpath (3)</a></li>
1651
1652  <li><a href="http://www.hungry.com/~pere/blog/tags/debian">debian (209)</a></li>
1653
1654  <li><a href="http://www.hungry.com/~pere/blog/tags/debian edu">debian edu (159)</a></li>
1655
1656  <li><a href="http://www.hungry.com/~pere/blog/tags/debian-handbook">debian-handbook (9)</a></li>
1657
1658  <li><a href="http://www.hungry.com/~pere/blog/tags/digistan">digistan (11)</a></li>
1659
1660  <li><a href="http://www.hungry.com/~pere/blog/tags/dld">dld (18)</a></li>
1661
1662  <li><a href="http://www.hungry.com/~pere/blog/tags/docbook">docbook (33)</a></li>
1663
1664  <li><a href="http://www.hungry.com/~pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1665
1666  <li><a href="http://www.hungry.com/~pere/blog/tags/english">english (471)</a></li>
1667
1668  <li><a href="http://www.hungry.com/~pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
1669
1670  <li><a href="http://www.hungry.com/~pere/blog/tags/fildeling">fildeling (14)</a></li>
1671
1672  <li><a href="http://www.hungry.com/~pere/blog/tags/freeculture">freeculture (34)</a></li>
1673
1674  <li><a href="http://www.hungry.com/~pere/blog/tags/freedombox">freedombox (9)</a></li>
1675
1676  <li><a href="http://www.hungry.com/~pere/blog/tags/frikanalen">frikanalen (20)</a></li>
1677
1678  <li><a href="http://www.hungry.com/~pere/blog/tags/h264">h264 (20)</a></li>
1679
1680  <li><a href="http://www.hungry.com/~pere/blog/tags/intervju">intervju (43)</a></li>
1681
1682  <li><a href="http://www.hungry.com/~pere/blog/tags/isenkram">isenkram (21)</a></li>
1683
1684  <li><a href="http://www.hungry.com/~pere/blog/tags/kart">kart (23)</a></li>
1685
1686  <li><a href="http://www.hungry.com/~pere/blog/tags/kodi">kodi (6)</a></li>
1687
1688  <li><a href="http://www.hungry.com/~pere/blog/tags/ldap">ldap (9)</a></li>
1689
1690  <li><a href="http://www.hungry.com/~pere/blog/tags/lego">lego (5)</a></li>
1691
1692  <li><a href="http://www.hungry.com/~pere/blog/tags/lenker">lenker (8)</a></li>
1693
1694  <li><a href="http://www.hungry.com/~pere/blog/tags/linuxcnc">linuxcnc (8)</a></li>
1695
1696  <li><a href="http://www.hungry.com/~pere/blog/tags/lsdvd">lsdvd (3)</a></li>
1697
1698  <li><a href="http://www.hungry.com/~pere/blog/tags/ltsp">ltsp (1)</a></li>
1699
1700  <li><a href="http://www.hungry.com/~pere/blog/tags/madewithcc">madewithcc (3)</a></li>
1701
1702  <li><a href="http://www.hungry.com/~pere/blog/tags/mesh network">mesh network (8)</a></li>
1703
1704  <li><a href="http://www.hungry.com/~pere/blog/tags/multimedia">multimedia (48)</a></li>
1705
1706  <li><a href="http://www.hungry.com/~pere/blog/tags/nice free software">nice free software (15)</a></li>
1707
1708  <li><a href="http://www.hungry.com/~pere/blog/tags/noark5">noark5 (27)</a></li>
1709
1710  <li><a href="http://www.hungry.com/~pere/blog/tags/norsk">norsk (326)</a></li>
1711
1712  <li><a href="http://www.hungry.com/~pere/blog/tags/nuug">nuug (200)</a></li>
1713
1714  <li><a href="http://www.hungry.com/~pere/blog/tags/offentlig innsyn">offentlig innsyn (42)</a></li>
1715
1716  <li><a href="http://www.hungry.com/~pere/blog/tags/open311">open311 (2)</a></li>
1717
1718  <li><a href="http://www.hungry.com/~pere/blog/tags/opensnitch">opensnitch (4)</a></li>
1719
1720  <li><a href="http://www.hungry.com/~pere/blog/tags/opphavsrett">opphavsrett (76)</a></li>
1721
1722  <li><a href="http://www.hungry.com/~pere/blog/tags/personvern">personvern (114)</a></li>
1723
1724  <li><a href="http://www.hungry.com/~pere/blog/tags/raid">raid (4)</a></li>
1725
1726  <li><a href="http://www.hungry.com/~pere/blog/tags/reactos">reactos (1)</a></li>
1727
1728  <li><a href="http://www.hungry.com/~pere/blog/tags/reprap">reprap (11)</a></li>
1729
1730  <li><a href="http://www.hungry.com/~pere/blog/tags/rfid">rfid (3)</a></li>
1731
1732  <li><a href="http://www.hungry.com/~pere/blog/tags/robot">robot (17)</a></li>
1733
1734  <li><a href="http://www.hungry.com/~pere/blog/tags/rss">rss (1)</a></li>
1735
1736  <li><a href="http://www.hungry.com/~pere/blog/tags/ruter">ruter (7)</a></li>
1737
1738  <li><a href="http://www.hungry.com/~pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1739
1740  <li><a href="http://www.hungry.com/~pere/blog/tags/sikkerhet">sikkerhet (60)</a></li>
1741
1742  <li><a href="http://www.hungry.com/~pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1743
1744  <li><a href="http://www.hungry.com/~pere/blog/tags/skepsis">skepsis (5)</a></li>
1745
1746  <li><a href="http://www.hungry.com/~pere/blog/tags/standard">standard (80)</a></li>
1747
1748  <li><a href="http://www.hungry.com/~pere/blog/tags/stavekontroll">stavekontroll (7)</a></li>
1749
1750  <li><a href="http://www.hungry.com/~pere/blog/tags/stortinget">stortinget (14)</a></li>
1751
1752  <li><a href="http://www.hungry.com/~pere/blog/tags/surveillance">surveillance (65)</a></li>
1753
1754  <li><a href="http://www.hungry.com/~pere/blog/tags/sysadmin">sysadmin (6)</a></li>
1755
1756  <li><a href="http://www.hungry.com/~pere/blog/tags/usenix">usenix (2)</a></li>
1757
1758  <li><a href="http://www.hungry.com/~pere/blog/tags/valg">valg (9)</a></li>
1759
1760  <li><a href="http://www.hungry.com/~pere/blog/tags/verkidetfri">verkidetfri (23)</a></li>
1761
1762  <li><a href="http://www.hungry.com/~pere/blog/tags/video">video (82)</a></li>
1763
1764  <li><a href="http://www.hungry.com/~pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1765
1766  <li><a href="http://www.hungry.com/~pere/blog/tags/web">web (42)</a></li>
1767
1768 </ul>
1769
1770
1771     </div>
1772     <p style="text-align: right">
1773  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1774 </p>
1775
1776   </body>
1777 </html>