Til Norge til jul

Fra http://styrheim.com/kontakt.no.html#ferie:

Fra 20.desember 2005 ? 4.januar 2006 er vi p ferie i Norge
Jan Egils GSM/SMS i Norge: +47 9383 6447
Anna Sofas GSM/SMS i Norge: +47 4528 8564
Kongsberg: +47 32733863
Sandefjord: +47 33472613

Se ogs upcoming.org.

Technorati claim


ge Utnes told me to look at the workings of http://af/ in various browsers. The results will probably vary with user configurations, but here are the results for my account on this PC:


Does not find the host af, and does no HTTP request at all. Surprisingly clean behaviour for a Microsoft application, but that is because I have configured IE not to search from the address line. Even an ayatollah like me could accept a silent retry at http://www.af/.

Even with address line search enabled, IE will not search when http: is specified. Good!

Firefox 1.0.7

Firefox 1.0.7 used Google to figure out that AF means Arbejdsformidlingen.

I'm pretty sure I disabled that once, but I can't remember where to do it.

On another machine, I ended at the U.S. Air Force, which has a certain perverted relevance.

Opera 8.5

The slightly outdated Opera 8.5 makes a guess at www.af.com, without warning me. I think http://www.af/ would be a much safer guess, because the host www.af is under the authority of the domain af

Yes, I said safer guess, having a browser silently going to another place than the one I asked for, is a security issue. But in general, substituting www.[domain] for [domain] should be safe, if the administration of the domain is doing its part.

What does http: mean?

Unlike IE, both Opera 8.5 and Firefox 1.0.7 will search, even when I explicitly type http:.

Even worse, they start searching silently on the link to http://af/, that is incredibly stupid. If I want to link to a Google search, I do so.

In this respect, Internet Explorer is clearly the serious browser. Maybe too serious, in not suggesting http://www.af/ as an alternative to http://af/.


Vernesonen og Haagdomstolen

Norge taper hvis vernesonen rundt Svalbard kommer opp for Haagdomstolen. Men det gjr den neppe, fordi de andre vil tape nesten like mye.

Det er to mulige utfall i Haag, og begge er drlige, srlig for Norge og Russland, men neppe gode for noen.

Vernesonen oppheves

Hvis vernesonen oppheves, blir det uregulert fiske der. I beste fall blir havet fiska svart, i vrste fall blir omrdet forsynt med ny fisk fra norske og russiske soner, men i s fall vi vi fiske vre egne soner svarte.

Vernesonen underlegges Svalbardtraktaten

S kan Norge regulere fisket, men ingen kan fordele kvotene. Det blir for eksempel fastsatt en totalkvote, og s blir fisket stoppet nr kvoten er ndd. Det er ikke en effektiv mte fiske.

Den uformelle lsningen er best

Jeg tror alle parter er enig om at norsk forvaltning er det beste, konfliktene er om fordeling av kvotene, der Haag-domstolen er en slags selvmordsbombe av et forhandlingkort. Hvis ikke vi fr ei rimelig kvote, s skal vi nok delegge fisket for alle sammen

Grsonen er en del av den prisen Norge betaler Russland i en hestehandel for f praktisk russisk aksept av vernesonen. akseptere vernesonen formelt ville vre idioti, s spiller man fra seg Haagdomstolen som forhandlingskort.

(Men jeg er ikke pragmatiker nok til unng kvalmen nr jeg hrer norske talsmenn uttale seg som om vernesonen er norskere enn Svalbard.)



P✪ppK✪rn - a more unique tag

With a rather generic name like PoppKorn, I wonder if an esoteric tag like is more useful than PoppKorn?

Cleaning up my 10MB corner of the world

Two useful tools to find the blubber at my web site:

Daylight savings time: Not that easy

The W3C working group note Working with Time Zones correctly identifes the problem that local time in a time zone with "daylight savings time" part of the year can not be specified by offset from UTC, because that offset is not constant. So the time zone must be identified by a TZID.

They suggest that two <datetime, TZID> pair can be compared, by computing the offsets on that date and at those times, using the TZ database.

It is not that easy. Each spring there is an hour that does not exist (and all trains are suddenly one hour late). That is not a computational problem, because a datetime is still unique within its time zone.

But each fall there is an hour that appears twice (causing all the trains to be one hour delayed). No time zone database can possibly tell if a datetime falling within that hour is the first or the second appearance of that datetime.

So I see no other solution than this: Don't mess with time (leave that to Hermione Granger) but keep the offset from UTC constant in each time zone. If daylight savings time must be used, use it all year round. Anyone suggesting other solutions, should provide a computational method to convert local time to UTC.

If rational arguments are not enough, let me remind you that daylight savings time was introduced in Norway during World War II by Vidkun Quisling.


Flash and SVG

Adobe SVG Adobe buys Macromedia. What does that mean for and ? Maybe Flash will use the open SVG format? Maybe Adobe will kill its SVG support?

RSS 0.91