diff --git a/blog/Avisene_i_endring.html b/blog/Avisene_i_endring.html
index 78f3f2ed79..0648ca1468 100644
--- a/blog/Avisene_i_endring.html
+++ b/blog/Avisene_i_endring.html
@@ -49,7 +49,7 @@ eksisterer. Det blir spennende å se hva vi ender opp med.
diff --git a/blog/FAD_lanserer_reiseregningsskjema_som_fri_programvare.html b/blog/FAD_lanserer_reiseregningsskjema_som_fri_programvare.html
index f3d30b9e14..1918a2aa95 100644
--- a/blog/FAD_lanserer_reiseregningsskjema_som_fri_programvare.html
+++ b/blog/FAD_lanserer_reiseregningsskjema_som_fri_programvare.html
@@ -120,7 +120,7 @@ gjorde det litt vanskeligere for brukeren.
diff --git a/blog/Fiksgatami_begynner____ta_form.html b/blog/Fiksgatami_begynner____ta_form.html
index 8534e5549a..5083a622d3 100644
--- a/blog/Fiksgatami_begynner____ta_form.html
+++ b/blog/Fiksgatami_begynner____ta_form.html
@@ -61,7 +61,7 @@ med dem. Dette blir bra.
diff --git a/blog/Frikanalen_og_jul_i_studentr__det.html b/blog/Frikanalen_og_jul_i_studentr__det.html
index bfd24ab8e8..4bdbe166ab 100644
--- a/blog/Frikanalen_og_jul_i_studentr__det.html
+++ b/blog/Frikanalen_og_jul_i_studentr__det.html
@@ -82,7 +82,7 @@ NUUG lykkes med å få ut sine opptak med like stor suksess.
diff --git a/blog/Hva_er_egentlig_en___pen_standard_.html b/blog/Hva_er_egentlig_en___pen_standard_.html
index 4a5862ffa7..7e647fd765 100644
--- a/blog/Hva_er_egentlig_en___pen_standard_.html
+++ b/blog/Hva_er_egentlig_en___pen_standard_.html
@@ -141,7 +141,7 @@ av en standard for at en standard skal kunne kalles fri og åpen.
diff --git a/blog/Norge_trenger_en_personvernforening.html b/blog/Norge_trenger_en_personvernforening.html
index e69483207f..29e8c1055f 100644
--- a/blog/Norge_trenger_en_personvernforening.html
+++ b/blog/Norge_trenger_en_personvernforening.html
@@ -56,7 +56,7 @@ nå får vi se om noen er enig.
diff --git a/blog/Reprap_pakke_tapt_i_posten.html b/blog/Reprap_pakke_tapt_i_posten.html
index 2ddf6d77f8..6e017af854 100644
--- a/blog/Reprap_pakke_tapt_i_posten.html
+++ b/blog/Reprap_pakke_tapt_i_posten.html
@@ -52,7 +52,7 @@ lenge alt er klart til Go Open
Standardize on protocols and formats, not vendors and applications
+
2009-03-30 11:50
+
+
Where I work at the University of Oslo, one decision stand out as a
+very good one to form a long lived computer infrastructure. It is the
+simple one, lost by many in todays computer industry: Standardize on
+open network protocols and open exchange/storage formats, not applications.
+Applications come and go, while protocols and files tend to stay, and
+thus one want to make it easy to change application and vendor, while
+avoiding conversion costs and locking users to a specific platform or
+application.
+
+
This approach make it possible to replace the client applications
+independently of the server applications. One can even allow users to
+use several different applications as long as they handle the selected
+protocol and format. In the normal case, only one client application
+is recommended and users only get help if they choose to use this
+application, but those that want to deviate from the easy path are not
+blocked from doing so.
+
+
It also allow us to replace the server side without forcing the
+users to replace their applications, and thus allow us to select the
+best server implementation at any moment, when scale and resouce
+requirements change.
+
+
I strongly recommend standardizing - on open network protocols and
+open formats, but I would never recommend standardizing on a single
+application that do not use open network protocol or open formats.
diff --git a/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html b/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
index bb0700aef6..fedcfc895c 100644
--- a/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
+++ b/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
@@ -61,7 +61,7 @@ be the only one fitting our needs. :/
diff --git a/blog/Vitenskapens_dogmer___.html b/blog/Vitenskapens_dogmer___.html
index a969beec2d..5a23a94a6a 100644
--- a/blog/Vitenskapens_dogmer___.html
+++ b/blog/Vitenskapens_dogmer___.html
@@ -111,7 +111,7 @@ skyskrapere. Takke meg til en tur til månen.
diff --git a/blog/When_web_browser_developers_make_a_video_player___.html b/blog/When_web_browser_developers_make_a_video_player___.html
index 0a155deffe..296b7a67d4 100644
--- a/blog/When_web_browser_developers_make_a_video_player___.html
+++ b/blog/When_web_browser_developers_make_a_video_player___.html
@@ -85,7 +85,7 @@ sure hope it was using the announced Ogg Theora support. :)
diff --git a/blog/archive/2008/11/index.html b/blog/archive/2008/11/index.html
index cabc69d575..a38faa431b 100644
--- a/blog/archive/2008/11/index.html
+++ b/blog/archive/2008/11/index.html
@@ -206,7 +206,7 @@ lenge alt er klart til Go Open
diff --git a/blog/archive/2009/03/03.rss b/blog/archive/2009/03/03.rss
index 3366171903..fb3ed32434 100644
--- a/blog/archive/2009/03/03.rss
+++ b/blog/archive/2009/03/03.rss
@@ -486,5 +486,39 @@ now. :)</p>
+
+ Standardize on protocols and formats, not vendors and applications
+ ../../../Standardize_on_protocols_and_formats__not_vendors_and_applications.html
+ ../../../Standardize_on_protocols_and_formats__not_vendors_and_applications.html
+ Mon, 30 Mar 2009 11:50:00 +0200
+
+<p>Where I work at the University of Oslo, one decision stand out as a
+very good one to form a long lived computer infrastructure. It is the
+simple one, lost by many in todays computer industry: Standardize on
+open network protocols and open exchange/storage formats, not applications.
+Applications come and go, while protocols and files tend to stay, and
+thus one want to make it easy to change application and vendor, while
+avoiding conversion costs and locking users to a specific platform or
+application.</p>
+
+<p>This approach make it possible to replace the client applications
+independently of the server applications. One can even allow users to
+use several different applications as long as they handle the selected
+protocol and format. In the normal case, only one client application
+is recommended and users only get help if they choose to use this
+application, but those that want to deviate from the easy path are not
+blocked from doing so.</p>
+
+<p>It also allow us to replace the server side without forcing the
+users to replace their applications, and thus allow us to select the
+best server implementation at any moment, when scale and resouce
+requirements change.</p>
+
+<p>I strongly recommend standardizing - on open network protocols and
+open formats, but I would never recommend standardizing on a single
+application that do not use open network protocol or open formats.</p>
+
+
+
diff --git a/blog/archive/2009/03/index.html b/blog/archive/2009/03/index.html
index 50f6d01d29..f2a427c80f 100644
--- a/blog/archive/2009/03/index.html
+++ b/blog/archive/2009/03/index.html
@@ -643,6 +643,53 @@ now. :)
+
Where I work at the University of Oslo, one decision stand out as a
+very good one to form a long lived computer infrastructure. It is the
+simple one, lost by many in todays computer industry: Standardize on
+open network protocols and open exchange/storage formats, not applications.
+Applications come and go, while protocols and files tend to stay, and
+thus one want to make it easy to change application and vendor, while
+avoiding conversion costs and locking users to a specific platform or
+application.
+
+
This approach make it possible to replace the client applications
+independently of the server applications. One can even allow users to
+use several different applications as long as they handle the selected
+protocol and format. In the normal case, only one client application
+is recommended and users only get help if they choose to use this
+application, but those that want to deviate from the easy path are not
+blocked from doing so.
+
+
It also allow us to replace the server side without forcing the
+users to replace their applications, and thus allow us to select the
+best server implementation at any moment, when scale and resouce
+requirements change.
+
+
I strongly recommend standardizing - on open network protocols and
+open formats, but I would never recommend standardizing on a single
+application that do not use open network protocol or open formats.
Where I work at the University of Oslo, one decision stand out as a
+very good one to form a long lived computer infrastructure. It is the
+simple one, lost by many in todays computer industry: Standardize on
+open network protocols and open exchange/storage formats, not applications.
+Applications come and go, while protocols and files tend to stay, and
+thus one want to make it easy to change application and vendor, while
+avoiding conversion costs and locking users to a specific platform or
+application.
+
+
This approach make it possible to replace the client applications
+independently of the server applications. One can even allow users to
+use several different applications as long as they handle the selected
+protocol and format. In the normal case, only one client application
+is recommended and users only get help if they choose to use this
+application, but those that want to deviate from the easy path are not
+blocked from doing so.
+
+
It also allow us to replace the server side without forcing the
+users to replace their applications, and thus allow us to select the
+best server implementation at any moment, when scale and resouce
+requirements change.
+
+
I strongly recommend standardizing - on open network protocols and
+open formats, but I would never recommend standardizing on a single
+application that do not use open network protocol or open formats.
Etter mange års meditasjon over temaet, har NUUG endelig klart å
-bestemme seg for hvilken lisens vi skal bruke på videoopptakene som
-gjøres av NUUGs videogruppe. Ole Kristian har annonsert at lisensen
-blir Creative
-Commons Navngivelse-Del på samme vilkår 3.0 Norge. Jeg er veldig
-glad for at denne saken endelig er landet. Lisensen for opptaket til
-Stallman-foredraget ble en annen pga. at lisensvalget ikke var avklart
-på forhånd og IFI og PING ønsket CC-BY-ND, og må ses på som et unntak
-i denne sammenhengen.
diff --git a/blog/index.rss b/blog/index.rss
index d2d00b244d..7ef97cf9d2 100644
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -6,6 +6,40 @@
+
+ Standardize on protocols and formats, not vendors and applications
+ Standardize_on_protocols_and_formats__not_vendors_and_applications.html
+ Standardize_on_protocols_and_formats__not_vendors_and_applications.html
+ Mon, 30 Mar 2009 11:50:00 +0200
+
+<p>Where I work at the University of Oslo, one decision stand out as a
+very good one to form a long lived computer infrastructure. It is the
+simple one, lost by many in todays computer industry: Standardize on
+open network protocols and open exchange/storage formats, not applications.
+Applications come and go, while protocols and files tend to stay, and
+thus one want to make it easy to change application and vendor, while
+avoiding conversion costs and locking users to a specific platform or
+application.</p>
+
+<p>This approach make it possible to replace the client applications
+independently of the server applications. One can even allow users to
+use several different applications as long as they handle the selected
+protocol and format. In the normal case, only one client application
+is recommended and users only get help if they choose to use this
+application, but those that want to deviate from the easy path are not
+blocked from doing so.</p>
+
+<p>It also allow us to replace the server side without forcing the
+users to replace their applications, and thus allow us to select the
+best server implementation at any moment, when scale and resouce
+requirements change.</p>
+
+<p>I strongly recommend standardizing - on open network protocols and
+open formats, but I would never recommend standardizing on a single
+application that do not use open network protocol or open formats.</p>
+
+
+
Returning from Skolelinux developer gathering
Returning_from_Skolelinux_developer_gathering.html
@@ -431,23 +465,5 @@ NUUG lykkes med å få ut sine opptak med like stor suksess.</p>
-
- Lisensvalg for NUUG-opptakene endelig på plass
- Lisensvalg_for_NUUG_opptakene_endelig_p___plass.html
- Lisensvalg_for_NUUG_opptakene_endelig_p___plass.html
- Fri, 6 Mar 2009 21:20:00 +0100
-
-<p>Etter mange års meditasjon over temaet, har NUUG endelig klart å
-bestemme seg for hvilken lisens vi skal bruke på videoopptakene som
-gjøres av NUUGs videogruppe. Ole Kristian har annonsert at lisensen
-blir <a href="http://creativecommons.org/licenses/by-sa/3.0/no/">Creative
-Commons Navngivelse-Del på samme vilkår 3.0 Norge</a>. Jeg er veldig
-glad for at denne saken endelig er landet. Lisensen for opptaket til
-Stallman-foredraget ble en annen pga. at lisensvalget ikke var avklart
-på forhånd og IFI og PING ønsket CC-BY-ND, og må ses på som et unntak
-i denne sammenhengen.</p>
-
-
-
diff --git a/blog/tags/3d-printer/index.html b/blog/tags/3d-printer/index.html
index ea3f6f81af..a8c25ca5a6 100644
--- a/blog/tags/3d-printer/index.html
+++ b/blog/tags/3d-printer/index.html
@@ -440,7 +440,7 @@ limet egentlig heter, så det er vanskelig å søke på nett.
diff --git a/blog/tags/debian/debian.rss b/blog/tags/debian/debian.rss
index 6b640375d8..12a2002b8b 100644
--- a/blog/tags/debian/debian.rss
+++ b/blog/tags/debian/debian.rss
@@ -142,5 +142,39 @@ now. :)</p>
+
+ Standardize on protocols and formats, not vendors and applications
+ ../../Standardize_on_protocols_and_formats__not_vendors_and_applications.html
+ ../../Standardize_on_protocols_and_formats__not_vendors_and_applications.html
+ Mon, 30 Mar 2009 11:50:00 +0200
+
+<p>Where I work at the University of Oslo, one decision stand out as a
+very good one to form a long lived computer infrastructure. It is the
+simple one, lost by many in todays computer industry: Standardize on
+open network protocols and open exchange/storage formats, not applications.
+Applications come and go, while protocols and files tend to stay, and
+thus one want to make it easy to change application and vendor, while
+avoiding conversion costs and locking users to a specific platform or
+application.</p>
+
+<p>This approach make it possible to replace the client applications
+independently of the server applications. One can even allow users to
+use several different applications as long as they handle the selected
+protocol and format. In the normal case, only one client application
+is recommended and users only get help if they choose to use this
+application, but those that want to deviate from the easy path are not
+blocked from doing so.</p>
+
+<p>It also allow us to replace the server side without forcing the
+users to replace their applications, and thus allow us to select the
+best server implementation at any moment, when scale and resouce
+requirements change.</p>
+
+<p>I strongly recommend standardizing - on open network protocols and
+open formats, but I would never recommend standardizing on a single
+application that do not use open network protocol or open formats.</p>
+
+
+
diff --git a/blog/tags/debian/index.html b/blog/tags/debian/index.html
index 1c7ef62c01..1b0eafad09 100644
--- a/blog/tags/debian/index.html
+++ b/blog/tags/debian/index.html
@@ -220,6 +220,53 @@ now. :)
Where I work at the University of Oslo, one decision stand out as a
+very good one to form a long lived computer infrastructure. It is the
+simple one, lost by many in todays computer industry: Standardize on
+open network protocols and open exchange/storage formats, not applications.
+Applications come and go, while protocols and files tend to stay, and
+thus one want to make it easy to change application and vendor, while
+avoiding conversion costs and locking users to a specific platform or
+application.
+
+
This approach make it possible to replace the client applications
+independently of the server applications. One can even allow users to
+use several different applications as long as they handle the selected
+protocol and format. In the normal case, only one client application
+is recommended and users only get help if they choose to use this
+application, but those that want to deviate from the easy path are not
+blocked from doing so.
+
+
It also allow us to replace the server side without forcing the
+users to replace their applications, and thus allow us to select the
+best server implementation at any moment, when scale and resouce
+requirements change.
+
+
I strongly recommend standardizing - on open network protocols and
+open formats, but I would never recommend standardizing on a single
+application that do not use open network protocol or open formats.
diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss
index fa8e711a9f..5a118a3c24 100644
--- a/blog/tags/english/english.rss
+++ b/blog/tags/english/english.rss
@@ -424,5 +424,39 @@ now. :)</p>
+
+ Standardize on protocols and formats, not vendors and applications
+ ../../Standardize_on_protocols_and_formats__not_vendors_and_applications.html
+ ../../Standardize_on_protocols_and_formats__not_vendors_and_applications.html
+ Mon, 30 Mar 2009 11:50:00 +0200
+
+<p>Where I work at the University of Oslo, one decision stand out as a
+very good one to form a long lived computer infrastructure. It is the
+simple one, lost by many in todays computer industry: Standardize on
+open network protocols and open exchange/storage formats, not applications.
+Applications come and go, while protocols and files tend to stay, and
+thus one want to make it easy to change application and vendor, while
+avoiding conversion costs and locking users to a specific platform or
+application.</p>
+
+<p>This approach make it possible to replace the client applications
+independently of the server applications. One can even allow users to
+use several different applications as long as they handle the selected
+protocol and format. In the normal case, only one client application
+is recommended and users only get help if they choose to use this
+application, but those that want to deviate from the easy path are not
+blocked from doing so.</p>
+
+<p>It also allow us to replace the server side without forcing the
+users to replace their applications, and thus allow us to select the
+best server implementation at any moment, when scale and resouce
+requirements change.</p>
+
+<p>I strongly recommend standardizing - on open network protocols and
+open formats, but I would never recommend standardizing on a single
+application that do not use open network protocol or open formats.</p>
+
+
+
diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html
index 02168c647d..d232b6cf9b 100644
--- a/blog/tags/english/index.html
+++ b/blog/tags/english/index.html
@@ -541,6 +541,53 @@ now. :)
+
+
+
Where I work at the University of Oslo, one decision stand out as a
+very good one to form a long lived computer infrastructure. It is the
+simple one, lost by many in todays computer industry: Standardize on
+open network protocols and open exchange/storage formats, not applications.
+Applications come and go, while protocols and files tend to stay, and
+thus one want to make it easy to change application and vendor, while
+avoiding conversion costs and locking users to a specific platform or
+application.
+
+
This approach make it possible to replace the client applications
+independently of the server applications. One can even allow users to
+use several different applications as long as they handle the selected
+protocol and format. In the normal case, only one client application
+is recommended and users only get help if they choose to use this
+application, but those that want to deviate from the easy path are not
+blocked from doing so.
+
+
It also allow us to replace the server side without forcing the
+users to replace their applications, and thus allow us to select the
+best server implementation at any moment, when scale and resouce
+requirements change.
+
+
I strongly recommend standardizing - on open network protocols and
+open formats, but I would never recommend standardizing on a single
+application that do not use open network protocol or open formats.
diff --git a/blog/tags/fiksgatami/index.html b/blog/tags/fiksgatami/index.html
index 3df53ca0c1..31b40bdc6b 100644
--- a/blog/tags/fiksgatami/index.html
+++ b/blog/tags/fiksgatami/index.html
@@ -78,7 +78,7 @@ med dem. Dette blir bra.
diff --git a/blog/tags/multimedia/index.html b/blog/tags/multimedia/index.html
index 862e6808b9..43f16b8900 100644
--- a/blog/tags/multimedia/index.html
+++ b/blog/tags/multimedia/index.html
@@ -142,7 +142,7 @@ sure hope it was using the announced Ogg Theora support. :)
diff --git a/blog/tags/norsk/index.html b/blog/tags/norsk/index.html
index e6ab1849ee..8a4d0e5963 100644
--- a/blog/tags/norsk/index.html
+++ b/blog/tags/norsk/index.html
@@ -1627,7 +1627,7 @@ av en standard for at en standard skal kunne kalles fri og åpen.
Where I work at the University of Oslo, one decision stand out as a
+very good one to form a long lived computer infrastructure. It is the
+simple one, lost by many in todays computer industry: Standardize on
+open network protocols and open exchange/storage formats, not applications.
+Applications come and go, while protocols and files tend to stay, and
+thus one want to make it easy to change application and vendor, while
+avoiding conversion costs and locking users to a specific platform or
+application.
+
+
This approach make it possible to replace the client applications
+independently of the server applications. One can even allow users to
+use several different applications as long as they handle the selected
+protocol and format. In the normal case, only one client application
+is recommended and users only get help if they choose to use this
+application, but those that want to deviate from the easy path are not
+blocked from doing so.
+
+
It also allow us to replace the server side without forcing the
+users to replace their applications, and thus allow us to select the
+best server implementation at any moment, when scale and resouce
+requirements change.
+
+
I strongly recommend standardizing - on open network protocols and
+open formats, but I would never recommend standardizing on a single
+application that do not use open network protocol or open formats.
diff --git a/blog/tags/nuug/nuug.rss b/blog/tags/nuug/nuug.rss
index 5bb8673c49..2761ec8524 100644
--- a/blog/tags/nuug/nuug.rss
+++ b/blog/tags/nuug/nuug.rss
@@ -1278,5 +1278,39 @@ now. :)</p>
+
+ Standardize on protocols and formats, not vendors and applications
+ ../../Standardize_on_protocols_and_formats__not_vendors_and_applications.html
+ ../../Standardize_on_protocols_and_formats__not_vendors_and_applications.html
+ Mon, 30 Mar 2009 11:50:00 +0200
+
+<p>Where I work at the University of Oslo, one decision stand out as a
+very good one to form a long lived computer infrastructure. It is the
+simple one, lost by many in todays computer industry: Standardize on
+open network protocols and open exchange/storage formats, not applications.
+Applications come and go, while protocols and files tend to stay, and
+thus one want to make it easy to change application and vendor, while
+avoiding conversion costs and locking users to a specific platform or
+application.</p>
+
+<p>This approach make it possible to replace the client applications
+independently of the server applications. One can even allow users to
+use several different applications as long as they handle the selected
+protocol and format. In the normal case, only one client application
+is recommended and users only get help if they choose to use this
+application, but those that want to deviate from the easy path are not
+blocked from doing so.</p>
+
+<p>It also allow us to replace the server side without forcing the
+users to replace their applications, and thus allow us to select the
+best server implementation at any moment, when scale and resouce
+requirements change.</p>
+
+<p>I strongly recommend standardizing - on open network protocols and
+open formats, but I would never recommend standardizing on a single
+application that do not use open network protocol or open formats.</p>
+
+
+
diff --git a/blog/tags/personvern/index.html b/blog/tags/personvern/index.html
index 1070370ff1..fe981c44d0 100644
--- a/blog/tags/personvern/index.html
+++ b/blog/tags/personvern/index.html
@@ -184,7 +184,7 @@ automatisk over i spesialkartet.
diff --git a/blog/tags/standard/index.html b/blog/tags/standard/index.html
index 4ef07cc3a9..996c712f92 100644
--- a/blog/tags/standard/index.html
+++ b/blog/tags/standard/index.html
@@ -139,6 +139,53 @@ av en standard for at en standard skal kunne kalles fri og åpen.
+
+
+
Where I work at the University of Oslo, one decision stand out as a
+very good one to form a long lived computer infrastructure. It is the
+simple one, lost by many in todays computer industry: Standardize on
+open network protocols and open exchange/storage formats, not applications.
+Applications come and go, while protocols and files tend to stay, and
+thus one want to make it easy to change application and vendor, while
+avoiding conversion costs and locking users to a specific platform or
+application.
+
+
This approach make it possible to replace the client applications
+independently of the server applications. One can even allow users to
+use several different applications as long as they handle the selected
+protocol and format. In the normal case, only one client application
+is recommended and users only get help if they choose to use this
+application, but those that want to deviate from the easy path are not
+blocked from doing so.
+
+
It also allow us to replace the server side without forcing the
+users to replace their applications, and thus allow us to select the
+best server implementation at any moment, when scale and resouce
+requirements change.
+
+
I strongly recommend standardizing - on open network protocols and
+open formats, but I would never recommend standardizing on a single
+application that do not use open network protocol or open formats.
diff --git a/blog/tags/standard/standard.rss b/blog/tags/standard/standard.rss
index 2250532187..f95f8af708 100644
--- a/blog/tags/standard/standard.rss
+++ b/blog/tags/standard/standard.rss
@@ -113,5 +113,39 @@ av en standard for at en standard skal kunne kalles fri og åpen.</p>
+
+ Standardize on protocols and formats, not vendors and applications
+ ../../Standardize_on_protocols_and_formats__not_vendors_and_applications.html
+ ../../Standardize_on_protocols_and_formats__not_vendors_and_applications.html
+ Mon, 30 Mar 2009 11:50:00 +0200
+
+<p>Where I work at the University of Oslo, one decision stand out as a
+very good one to form a long lived computer infrastructure. It is the
+simple one, lost by many in todays computer industry: Standardize on
+open network protocols and open exchange/storage formats, not applications.
+Applications come and go, while protocols and files tend to stay, and
+thus one want to make it easy to change application and vendor, while
+avoiding conversion costs and locking users to a specific platform or
+application.</p>
+
+<p>This approach make it possible to replace the client applications
+independently of the server applications. One can even allow users to
+use several different applications as long as they handle the selected
+protocol and format. In the normal case, only one client application
+is recommended and users only get help if they choose to use this
+application, but those that want to deviate from the easy path are not
+blocked from doing so.</p>
+
+<p>It also allow us to replace the server side without forcing the
+users to replace their applications, and thus allow us to select the
+best server implementation at any moment, when scale and resouce
+requirements change.</p>
+
+<p>I strongly recommend standardizing - on open network protocols and
+open formats, but I would never recommend standardizing on a single
+application that do not use open network protocol or open formats.</p>
+
+
+
diff --git a/blog/tags/stavekontroll/index.html b/blog/tags/stavekontroll/index.html
index b7cbe13867..03cd1bea79 100644
--- a/blog/tags/stavekontroll/index.html
+++ b/blog/tags/stavekontroll/index.html
@@ -83,7 +83,7 @@ stavekontrollen.
diff --git a/blog/tags/video/index.html b/blog/tags/video/index.html
index 553e275f29..f1d59b16f3 100644
--- a/blog/tags/video/index.html
+++ b/blog/tags/video/index.html
@@ -272,7 +272,7 @@ NUUG lykkes med å få ut sine opptak med like stor suksess.
diff --git a/blog/tags/vitenskap/index.html b/blog/tags/vitenskap/index.html
index 494c139842..bda2dba6e2 100644
--- a/blog/tags/vitenskap/index.html
+++ b/blog/tags/vitenskap/index.html
@@ -128,7 +128,7 @@ skyskrapere. Takke meg til en tur til månen.
diff --git a/blog/tags/web/index.html b/blog/tags/web/index.html
index 86a6d320b9..4b5a9e65cd 100644
--- a/blog/tags/web/index.html
+++ b/blog/tags/web/index.html
@@ -142,7 +142,7 @@ sure hope it was using the announced Ogg Theora support. :)