FEED Validator

Congratulations!

This is a valid Atom 1.0 feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

• line 191, column 7279: Two entries with the same value for atom:updated: 2011-12-22T12:43:18Z (92 occurrences) [help]

  ... wsers/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title  ...
                                               ^

• line 276, column 220: Implausible date: 1970-01-01T00:00:00Z (3 occurrences) [help]

  ... rsing/</id><updated>1970-01-01T00:00:00Z</updated></entry><entry><title  ...
                                               ^

Source: http://hsivonen.iki.fi/feed/atom/

1. <?xml version='1.0' encoding='utf-8'?>
2. <feed xmlns="http://www.w3.org/2005/Atom"><title>Henri Sivonen’s pages</title><link href="https://hsivonen.fi/"></link><link href="https://hsivonen.fi/feed/atom/" rel="self"></link><updated>2022-10-19T04:31:51Z</updated><subtitle>Articles and blogish notes</subtitle><rights>Copyright Henri Sivonen</rights><author><name>Henri Sivonen</name><email>hsivonen@hsivonen.fi</email></author><id>http://hsivonen.iki.fi/feed/atom/</id><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Parin vuoden tutkimattomuus</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Comments on the Chancellor of Justice choosing not to investigate the conduct of the Finnish institute for health and welfare. (In Finnish)</div></summary><link href="https://hsivonen.fi/tutkimattomuus/"></link><id>http://hsivonen.iki.fi/tutkimattomuus/</id><updated>2022-10-19T04:26:35Z</updated><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
3.  
4. <p><b>TL;DR:</b> Oikeuskansleri on oma-aloitteiseen tutkintaansa vedoten jättänyt tutkimatta THL:n toimien lainmukaisuutta, vaikkei kantelukysymyksiä käsitelty oma-aloitteisessa tutkinnassa. Oikeuskansleri myös vetosi THL:n mahdollisuuteen reagoida oikeuskanslerin oma-aloitteisen tutkinnan ratkaisuun, vaikka oikeuskanslerilla oli jo tiedossa, ettei THL ollut käyttänyt mahdollisuutta merkityksellisesti.</p>
5.  
6. <hr></hr>
7.  
8. <p><a href="/asiakirjattomuus/">Aiemmin kirjoitin</a> siitä, miten THL oli muuttanut ohjetta, jonka tarkoitus oli ohjata hallintopäätöksiä, perustelematta muutosta kirjallisesti, vaikka hallintopäätökset täytyy perustella. Näin siis hallintopäätösten ohjaus ei ollut samalla perustelun tasolla, kuin mitä hallintopäätöksiltä itseltään edellytetään. Lisäksi muutosta ei oletettavasti ollut tehty päällikkövirastoon kuuluvalla esittelymenettelyllä, koska esittelymenettely olisi tuottanut asiakirjajäljen.</p>
9.  
10. <p><a href="https://hsivonen.fi/tutkimattomuus/~%20OKV_1140_10_2022-OKV-2%20OK_n%20vastaus%20OKV_1140_10_2022%202792295_11_1.pdf">Ratkaisussa kanteluuni OKV/1140/10/2022</a> oikeuskansleri ensin viittasi oma-aloitteiseen tutkintaansa toisessa asiassa luonnehtien sitä näin (kursivointi minun):</p>
11.  
12. <blockquote>
13.  
14. <p>Annoin päätöksen OKV/461/70/2020 ja OKV/458/70/2020, joka koski koronavirusepidemian hoitoa koskevan päätöksenteon avoimuutta. Esitin siinä yleisesti näkemyksiäni
15. vahvistaa yhteiskunnallisen päätöksenteon taustalla olevien tietojen ja perusteiden avoimuutta
16. ja läpinäkyvyyttä, koska katsoin kyseisen avoimuuden olevan merkittävä julkisen vallankäytön
17. lagitiimiyden ja oikeusvaltion osatekijä.</p>
18.  
19. <p><i>THL:n osalta päätöksessäni oli erityisesti kysymys koronavirusepidemian kulkua kuvaavien ja
20. ennustavien mallinnusten tekemisessä käytettyjen taustatietojen julkisuudesta ja avoimuudesta.</i> Kyseisten tietojen avulla tehdyt epidemian kulkua koskevat ennustukset olivat epidemian
21. hoitoa koskevan ja ihmisten oikeuksia ja vapauksia rajoittavan päätöksenteon pohjana, ja tietojen saatavuus ja avoimuus olivat siten merkityksellisiä päätöksenteon ja julkisen vallan käytön
22. arvioitavuuden kannalta.</p>
23. </blockquote>
24.  
25. <p>Ja totesi sitten käsillä olleeseen asiaan:</p>
26.  
27. <blockquote>
28.  
29. <p>En edellä mainitussa päätöksessäni ottanut kantaa suoranaisesti kantelussanne esittämiinne
30. kysymyksiin, jotka koskevat suositusten ja ohjeiden taustalla olevan harkinnan ja arvioinnin perusteiden kirjaamista. Kantelussa arvostelemanne menettelyt kuitenkin koskevat THL:n menettelyä ja toimenpiteitä ennen kuin annoin edellä mainitun päätökseni ja esitin näkemykseni koronavirusepidemian hoitoa koskevan päätöksenteon läpinäkyvyydestä ja päätöksenteon taustalla olevan tiedon avoimuudesta. Laitos ei siten tuolloin ollut vielä voinut ryhtyä toimenpiteisiin
31. päätöksessäni tarkoittamani avoimuuden lisäämiseksi. Sen vuoksi en pidä tässä vaiheessa aiheellisena ryhtyä kantelussa tarkoittamallanne tavalla selvittämään esille tuomienne suositusten ja ohjeen perusteiden dokumentointia ja kirjaamista koskevaa asiaa.</p>
32.  
33. </blockquote>
34.  
35. <p>Mielestäni oikeuskanslerin esittämä perustelu asian tutkimatta jättämiselle on huono jo itsessään. <a href="https://oikeuskansleri.fi/documents/1428954/107303574/ratkaisu_koronavirusepidemian_hoitoa_koskevan_paatoksenteon_avoimuus_+OKV_461_70_2020.pdf/f08cd602-c06e-7d5f-5241-30b2bc2c1196/ratkaisu_koronavirusepidemian_hoitoa_koskevan_paatoksenteon_avoimuus_+OKV_461_70_2020.pdf">Oikeuskanslerin oma-aloitteisesti tutkima asia</a> koski eri tekoa eikä siinä käsitelty ohjauksen suhdetta hallintolain perusteluvaatimukseen (<a href="https://finlex.fi/fi/laki/ajantasa/2003/20030434#O2L7P45">45 §</a>; oma-aloitteisesti viitattu pykäliin 6 ja 10) eikä päällikköviraston esittelymenettelyn käyttämiseen. Miksi valvottavan pitäisi saada toimia kyseenalaisesti monella tapaa samaan pakettiin siksi, että yhtä asiaa on tutkittu?</p>
36.  
37. <p>Oikeuskanslerin perustelu näyttää kuitenkin vielä huonommalta kun otetaan huomioon mitä oikeuskansleri minulle vastatessaan jo tiesi THL:n ilmoituksesta.</p>
38.  
39. <p>Oikeuskansleri antoi päätöksensä mallinnusavoimuusasiassa 21.12.2021. THL:n piti ilmoittaa 30.4.2022 mennessä, mihin toimenpiteisiin se on ryhtynyt oikeuskanslerin näkemysten johdosta. Lisäaikaa annottuaan <a href="https://hsivonen.fi/tutkimattomuus/Ilmoitus%20kehitt%C3%A4mistoimista%20THL-2470-4.00.00-2020%20,%20OKV-461-70-2020.pdf">THL vastasi 6.5.2022</a>.</p>
40.  
41. <p>THL:n ilmoittamissa toimenpiteissä ei ollut mukana ohjeiden ja ohjemuutosten perustelujen kirjallinen dokumentointi, vaan perustelemiseen oli vain pyritty kiinnittämään huomiota.</p>
42.  
43. <p>19.5.2022 THL:ssä aiemmin työskennellyt henkilö kirjoitti oikeuskanslerille asiassa OKV/1470/10/2022 (kursivointi minun):</p>
44.  
45. <blockquote>
46.  
47. <p>THL toimitti vastineensa (THL/2470/4.00.00/2020) viikon myöhässä 6.5.2022. Siinä laitos kertoi ryhtyneensä seuraaviin toimiin.</p>
48.  
49. <ol>
50. <li>THL on pitänyt kaikiille avoimia webimaareja epidemiamallinnuksesta.</li>
51. <li>THL julkaisee vertaisarvioituja tieteellisiä artikkeleita, raportteja ja pitää kursseja
52. yliopistossa.</li>
53. <li>THL on toimittanut mallinnuskoodeja julkisuuslain mukaisen tietopyynnön tehneille.</li>
54. <li>THL on selvittänyt koodin avoimuuden mahdollistavien järjestelmien käyttöönottoon
55. liittyviä seikkoja.</li>
56. <li>THL on kommunikoinut asiantuntijakantaansa lausunnoissa.</li>
57. <li>THL on pyrkinyt julkaisemaan tieteelliset artikkelinsa maksumuurittomissa
58. preprint-palveluissa.</li>
59. <li>THL:n asiantuntijat ovat pitäneet esityksiä esim. kansallisessa rokoteasiantuntijaryhmässä, ja esitysdiat on jaettu verkossa.</li>
60. <li>THL on tehnyt tiedotteita ja järjestänyt tiedotustilaisuuksia ja avoimia kansalaistilaisuuksia.</li>
61. <li>THL:n asiantuntijat ovat olleet laajasti median käytettävissä.</li>
62. <li>THL on julkaissut tuottamaansa tietoa myös avoimena datana.</li>
63. <li>THL on selvittänyt tutkittavien suostumuksen pyytämiseen liittyviä käytäntöjä ja
64. immateriaalioikeuskysymyksiä tiedon avaamisen edistämiseksi.</li>
65. </ol>
66.  
67. <p>Ensimmäinen huomio toimenpidelistasta on, että <i>THL:n lausunnosta löytyvät 11 toimenpidettä ovat kaikki olleet meneillään jo oikeuskanslerin kirjoittaessa lausuntoaan. THL siis vaikenee itse pääkysymyksestä eli siitä, mihin toimiin on ryhdytty oikeuskanslerin moitteiden takia hänen huomaamiensa puutteiden korjaamiseksi.</i></p>
68.  
69. <p>Mahdollisesti kohtiin 4 ja 11 liittyen on toimintaa tehostettu, joskaan lausunnosta ei tällaista ilmene. Sen sijaan muiden toimien osalta THL on useassa yhteydessä viestinyt toimivansa suorituskykynsä äärirajoilla, joten niissä tuskin on tapahtunut merkittävää muutosta oikeuskanslerin moitteiden jälkeen. Jos olisi, THL olisi varmasti lausunnossaan kertonut lisänneensä resursseja johonkin tiettyyn asiaan.</p>
70. </blockquote>
71.  
72. <p>(Resursoinnin osalta käsiteltiin myös sitä, miten apu ei ole kelvannut, mutta se ei kuulu tämän kirjoituksen aiheeseen.)</p>
73.  
74. <p>Tähän <a href="https://hsivonen.fi/tutkimattomuus/OKV_1470_10_2022-OKV-2%20OK_n%20vastaus%20OKV_1470_10_2022%202771056_4_1.pdf">oikeuskansleri oli 27.6.2022 vastannut</a>: ”Esittämänne näkemykset ovat kuitenkin kantelunne johdosta tulleet tietooni.”</p>
75.  
76. <p>Samassa vastauksessaan oikeuskansleri totesi: ”Ette pyydä tutkimaan mitään tiettyä THL:n menettelyä tai laiminlyöntiä ettekä kirjoituksessanne tuo esille, että laitos olisi missään yksilöidyssä tilanteessa menetellyt lainvastaisesti.” ja sitten ”Kantelustanne ilmenevän perusteella minulla ei ole aihetta epäillä edellä mainitussa lainkohdassa tarkoitettua laillisuusvalvonnallisesti arvosteltavaa menettelyä enkä sen vuoksi ole ryhtynyt kanteluanne tutkimaan.”</p>
77.  
78. <p>On aivan oikein sanoa, ettei kantelussa pyydetty tutkimaan mitään yksilöityä asiaa, vaan vain tuotiin oikeuskanslerin tietoon asioita, mutta kuitenkin mielestäni kummallista, ettei oikeuskansleri ryhtynyt kerrotun pohjalta toimiin. <b>Nyt näyttää siltä, että oikeuskansleri antaa THL:n vetää itseään nenästä.</b> Kunnollisessa valvonta-asetelmassa luulisi, että valvojan tietoisuus siitä, että valvottava on ilmoituksessaan vaiennut siitä, mitä piti ilmoittaa, ja kertonut sen sijaan muita asioita aiheen ympäriltä, aiheuttaisi jatkotoimia valvottavaa kohtaan.</p>
79.  
80. <p>Kun oikeuskansleri 17.8.2022 kirjoitti minulle ”Laitos ei siten tuolloin ollut vielä voinut ryhtyä toimenpiteisiin päätöksessäni tarkoittamani avoimuuden lisäämiseksi.”, hänellä oli siis jo tiedossa, ettei THL ollut ryhtynyt hänen näkemystensä vuoksi uusiin toimenpiteisiin.</p>
81.  
82. <p>Tämä ei edes ollut ensimmäinen kerta kun oikeuskansleri jätti tuon saman oma-aloitteisen tutkinnan perusteella tutkimatta sellaista, mitä olin pyytänyt tutkimaan. 30.6.2020 oikeuskanslerinviraston esittelijäneuvos <a href="https://hsivonen.fi/tutkimattomuus/OKV_832_10_2020-OKV-2%20Vastaus%20OKV_832_10_2020%20937916_3_3.pdf">kirjoitti minulle asiassa OKV/832/10/2020 seuraavasti</a>:</p>
83.  
84. <blockquote>
85.  
86. <p>Arvostelette oikeuskanslerille 18.5.2020 osoittamassanne kantelussa Terveyden- ja hyvinvoinnin laitoksen (THL) ja sen johtajan Mika Salmisen sekä sosiaali- ja terveysministeriön menettelyä covid-19-epidemian hoitamisessa. Pyydätte oikeuskansleria tutkimaan, ovatko Salminen, THL tai ministeriö neuvoneet hallitusta ryhtymään toimiin, joiden tarkoituksena on nopeuttaa epidemian etenemistä. Mikäli näin on tapahtunut, pyydätte oikeuskansleria ottamaan kantaa siihen, onko epidemian etenemisen nopeuttamista tavoitteleva toiminta tai sellaisen suositteleminen vastoin tartuntatautilain 6 §:ssä viranomaisille säädettyjä tartuntatautien torjuntatyöhön kuuluvia velvollisuuksia. Pyydätte, että oikeuskansleri ryhtyy tarvittaessa toimenpiteisiin lainvastaisen toiminnan estämiseksi.</p>
87.  
88. <p>Kantelussanne tutkittavaksi tarkoittamanne asia liittyy oikeuskanslerin omasta aloitteestaan tutkittavaksi ottamaan asiaan (OKV/461/70/2020), jossa on kysymys covid-19-epidemian hoitoa koskevan päätöksenteon perusteiden ja erityisesti siinä käytetyn tietoperustan avoimuudesta ja objektiivisuudesta siitä näkökulmasta, kuinka epidemian hoitoa koskevassa päätöksenteossa ja ohjauksessa toteutuvat perustuslaista, julkisuuslaista ja tartuntatautilaista johtuvat oikeudet ja velvoitteet. Asian taustalla oli muun muassa julkisuudessa esiintyneet tiedot, joista saattoi saada käsityksen, että valtioneuvoston 6.5.2020 covid-19-epidemian hoitamisesta tekemän periaatepäätöksen (ns. hybridistrategia) taustalla oli muunlaisia näkemyksiä, kuin päätöksen perusteena oli esitetty. Asiassa on pyydetty sosiaali- ja terveysministeriön selvitys ja asiassa tullaan aikanaan antamaan päätös.
89. Asianne esiteltiin oikeuskansleri Tuomas Pöystille. Hänen ratkaisunsa oli, ettei kanteluanne ryhdytä tutkimaan, koska asia on jo tutkittavana edellä mainitulla tavalla.</p>
90.  
91. </blockquote>
92.  
93. <p>Sama esittelijäneuvos <a href="https://hsivonen.fi/tutkimattomuus/OKV_431_10_2020-OKV-1%20Vastaus%20OKV_431_10_2020%20(935_1_2020)%20863615_9_3.pdf">vastasi</a> 29.5.2020 samansuuntaisesti toiselle kantelijalle, joka oli kannellut samansuuntaisesti sekä laajemmin asiassa OKV/431/10/2020.</p>
94.  
95. <p>(Muistin virkistykseksi esim. <a href="https://www.mtvuutiset.fi/artikkeli/tallaisiin-arvioihin-paatos-koulujen-avaamisesta-perustuu-asiantuntijat-suosittivat-koronaepidemian-kiihdyttamista-muutoin-voi-syntya-ruutitynnyri/7807298">MTV Uutiset kirjoitti tuohon aikaan ingressiinsä</a>: ”Koronavirusepidemia etenee Suomessa sosiaali- ja terveysministeriön (STM) ja Terveyden ja hyvinvoinnin laitoksen (THL) asiantuntijoiden mukaan liian hitaasti ja liian matalalla tasolla.”)</p>
96.  
97. <p>Oma-aloitteisen tutkinnan valmistuttua pyysin oikeuskansleria arvioimaan asian OKV/832/10/2020 tutkimattomuuspäätöstä uudestaan, koska kantelun keskeisiä kysymyksiä ei ollutkaan käsitelty oma-aloitteisessa tutkinnassa. <a href="https://hsivonen.fi/tutkimattomuus/OKV_249_10_2022-OKV-2Vastaus%20OKV249102022.pdf">Oikeuskansleri ei ottanut asiaa käsittelyyn uudelleen pyytämällä.</a></p>
98.  
99. <p><b>Tehokkaan valvonnan sijaan tästä tulee sellainen mielikuva, että THL oli vapautettu sellaisten asioiden, jotka voidaan jollakin tapaa muotoilla tietopohjan avoimuuteen liittyviksi, tutkinnasta toukokuusta 2020 toukukuuhun 2022</b> (jos lasketaan THL:n ilmoitukseen asti), <b>vaikka näin sivuutetaan muita kysymyksiä esim. tavoitteen laillisuudesta, hallintopäätösten perusteluketjusta tai ohjeita tuottavan prosessin dokumentoinnista</b>. Näinkö julkisen vallankäytön legitimiteetti ja oikeusvaltio edistyvät?</p>
100.  
101. <p>Oikeuskanslerinviraston ja THL:n suhde on erässä toisessakin asiassa näyttäytynyt kulmakarvoja nostattavasti, kun ajatellaan maallikon odotuksia valvojan ja valvottavan suhteesta. Asiassa OKV/1336/10/2022 apulaisoikeuskansleri siirsi THL:ää koskevan kantelun <a href="https://hsivonen.fi/tutkimattomuus/~%20OKV_2196_80_2022-SAAP-1%20Julkinen%20versio.%20THLn%20ilmoitus%20apulaisoikeuskanslerille.%20THLn%20men.pdf">vastattavaksi</a> THL:lle itselleen. Kyseessä todellakin oli asian <a href="https://hsivonen.fi/tutkimattomuus/OKV%201336%2010%202022%20julkinen%20versio.%20Ilmoitus%20asian%20siirrosta.pdf">siirto</a> eikä se, että kantelu kohteelta olisi pyydetty selvitys asiassa, joka olisi kuitenkin jäänyt muodollisesti apulaisoikeuskanslerin ratkaistavaksi. Maallikkona kuvittelisi, että siirtomomentin tarkoitus olisi se, että vaikkapa terveydenhuollon ammattilaista koskevan kantelun voisi siirtää oikeuskanslerinvirastosta Valviralle. Kummeksun kantelun siirtoa kantelun kohteelle itselleen.</p>
102.  
103. <p><b>Yllä kerrottu herättää myös kysymyksen siitä, onko oikeuskanslerin oma-aloitteinen tutkinta valvontaa parantava vai huonontava toimi, kun oma-aloitteisuuden perusteella kanteluita jätetään tutkimatta.</b> <a href="https://oikeuskansleri.fi/documents/1428954/107303577/ratkaisu_terveysturvallisuusohjeiden_noudattaminen_ja_+seuranta_kouluissa_koronavirusepidemian_aikana_+OKV_2733_70_2021.pdf/39f7c141-d711-84cd-67ff-b02d44b2ce35/ratkaisu_terveysturvallisuusohjeiden_noudattaminen_ja_+seuranta_kouluissa_koronavirusepidemian_aikana_+OKV_2733_70_2021.pdf">Asian OKV/2733/70/2021 ratkaisussa</a> oikeuskansleri kirjoitti vireilletulosta (kursivointi minun):</p>
104.  
105. <blockquote>
106. <p><i>Oikeuskanslerille
107.    alkusyksyllä 2021
108.    tehdyissä
109.    kanteluissa</i> ja kansalaiskirjoituksissa on tuotu
110.    esiin huoli siitä, ovatko opetuksen ja koulutuksen järjestäjille koronavirustartuntojen estämiseksi
111.    annetut
112.    ohjeet
113.    ja
114.    suositukset
115.    (jäljempänä
116.    myös
117.    terveysturvallisuusohjeet)
118.    riittäviä
119.    ja
120.    ajantasaisia muuttuvassa epidemiatilanteessa. Huolta kannettiin erityisesti siitä, miten ohjeet ja
121.    suositukset
122.    oppilaitosten
123.    arjessa toteutuvat ja miten
124.    terveysturvallisuustoimien
125.    toteuttamista
126.    valvotaan käytännössä.</p>
127. </blockquote>
128.  
129. <p>Ja sitten:</p>
130.  
131. <blockquote>
132. <p>Päätin
133.    omasta
134.    aloitteestani
135.    terveysturvallisuustoimia
136.    selvittää,
137.    koskevien
138.    onko perusopetuksen ja toisen
139.    asteen
140.    ohjeidenja suositusten toimivuuden
141.    koulutuksen
142.    ja vaikuttavuuden
143.    seuranta järjestetty lapsen oikeuksien toteutumisen edellyttämällä tavalla.</p>
144. </blockquote>
145.  
146. <p><a href="https://mobile.twitter.com/hsivonen/status/1565576229213929472">Kysyin</a> oikeuskanslerilta Twitterissä vastauksena <a href="https://mobile.twitter.com/thpoysti/status/1554524474766147584">twiittiin, jossa hän toi tuon tutkinnan esille</a>:</p>
147.  
148. <blockquote>
149.  
150. <p>Tuossa kerrotaan, että asia otettiin oma-aloitteisesti tutkintaan, kun oli tullut kanteluja. Miksei tällaisessa tapauksessa yhdistetä kanteluita ja tutkita niitä? Eikö tällaisessa kantelun jälkeisessä oma-aloitteisuudessa ole riskinä, että kantelukysymyksiä sivuutetaan?</p>
151. </blockquote>
152.  
153. <p>En saanut vastausta.</p>
154. </div></content></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">encoding_rs</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A Web-Compatible Character Encoding Library in Rust. (Used in Firefox.)</div></summary><link href="https://crates.io/crates/encoding_rs"></link><id>https://crates.io/crates/encoding_rs</id><updated>2022-10-13T21:27:26Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Asiakirjatonta toimintaa</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Document requests to the Finnish institute for health and welfare and to Ministry of Education and Culture. (In Finnish)</div></summary><link href="https://hsivonen.fi/asiakirjattomuus/"></link><id>http://hsivonen.iki.fi/asiakirjattomuus/</id><updated>2022-07-26T15:07:54Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">It’s Not Wrong that <code>"🤦🏼‍♂️".length == 7</code></div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">From time to time, someone shows that in JavaScript the <code>.length</code> of a string containing an emoji results in a number greater than 1 (typically 2) and then proceeds to the conclusion that haha JavaScript is so broken. In this post, I will try to convince you that ridiculing JavaScript for this is less insightful than it first appears.</div></summary><link href="https://hsivonen.fi/string-length/"></link><id>http://hsivonen.iki.fi/string-length/</id><updated>2022-05-28T11:58:38Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Koulutartuntojen tilastointimenettely</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Document requests to the City of Helsinki and to University of Eastern Finland. (In Finnish)</div></summary><link href="https://hsivonen.fi/koulutartunnat/"></link><id>http://hsivonen.iki.fi/koulutartunnat/</id><updated>2022-01-23T13:46:37Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Perusteasiakirjoja hallussapitämättä ikärajoitettu</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A document request to the Finnish institute for health and welfare. (In Finnish)</div></summary><link href="https://hsivonen.fi/k-15-maskit/"></link><id>http://hsivonen.iki.fi/k-15-maskit/</id><updated>2021-10-16T18:44:11Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Asiantuntijat ja nukkuva vallan vahtikoira</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">My wishlist for Finnish journalists when interviewing experts. (In Finnish)</div></summary><link href="https://hsivonen.fi/asiantuntijat/"></link><id>http://hsivonen.iki.fi/asiantuntijat/</id><updated>2021-10-09T17:21:51Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Koronapassilausunto</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A document request to the Finnish institute for health and welfare. (In Finnish)</div></summary><link href="https://hsivonen.fi/koronapassi/"></link><id>http://hsivonen.iki.fi/koronapassi/</id><updated>2021-09-24T09:54:06Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Suppealla tietopohjalla ohimeneväksi väitetty</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A document request to the Ministry of Social Affairs and Health. (In Finnish)</div></summary><link href="https://hsivonen.fi/ohimenevyys/"></link><id>http://hsivonen.iki.fi/ohimenevyys/</id><updated>2021-09-24T09:31:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Text Encoding Menu in 2021</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">This post is about a UI feature that I wish no one would have to use. Happily, it is indeed <i>almost</i> unused. Still, I made it more usable in the case when it <i>is</i> used.</div></summary><link href="https://hsivonen.fi/encoding-menu-2021/"></link><id>http://hsivonen.iki.fi/encoding-menu-2021/</id><updated>2021-08-24T14:12:16Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The Text Encoding Submenu Is Gone</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Firefox 91 is the first release that does not have a Text Encoding submenu and instead has a single menu item called Repair Text Encoding.</div></summary><link href="https://hsivonen.fi/no-encoding-menu/"></link><id>http://hsivonen.iki.fi/no-encoding-menu/</id><updated>2021-08-24T13:53:33Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">An HTML5 Conformance Checker</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">My master’s thesis</div></summary><link href="https://hsivonen.fi/thesis/"></link><id>http://hsivonen.iki.fi/thesis/</id><updated>2021-06-14T19:02:28Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Not Part of the Technology Stack</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">At XTech 2006, I got a W3C brochure entitled <cite>Leading the Web
155. to its Full Potential</cite> that had a diagram visualizing the W3C
156. technology stack(s).</div></summary><link href="https://hsivonen.fi/technology-stack/"></link><id>http://hsivonen.iki.fi/technology-stack/</id><updated>2021-06-14T11:59:57Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Browser Technology Stack</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I took a quick attempt at drawing a stack for Web browsing.</div></summary><link href="https://hsivonen.fi/web-stack/"></link><id>http://hsivonen.iki.fi/web-stack/</id><updated>2021-06-14T11:56:06Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Bogo-XML Declaration Returns to Gecko</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Firefox 89 was released today. This release (again!) honors a character encoding declaration made via syntax that looks like an XML declaration used in <code>text/html</code> (if there are no other character encoding declarations).</div></summary><link href="https://hsivonen.fi/xml-decl/"></link><id>http://hsivonen.iki.fi/xml-decl/</id><updated>2021-06-02T07:36:32Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A Look at Encoding Detection and Encoding Menu Telemetry from Firefox 86</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Concluding that chardetng should tolerate Big5 byte sequences that the Encoding Standard treats as unmapped.</div></summary><link href="https://hsivonen.fi/encoding-telemetry/"></link><id>http://hsivonen.iki.fi/encoding-telemetry/</id><updated>2021-03-31T15:06:05Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Why Supporting Unlabeled UTF-8 in HTML on the Web Would Be Problematic</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">UTF-8 has won. Yet, Web authors have to opt in to having browsers treat HTML as UTF-8 instead of the browsers Just Doing the Right Thing by default. Why?</div></summary><link href="https://hsivonen.fi/utf-8-detection/"></link><id>http://hsivonen.iki.fi/utf-8-detection/</id><updated>2021-03-11T08:57:20Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Rust Target Names Aren’t Passed to LLVM</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Rust’s <code>i686-unknown-linux-gnu</code> target requires SSE2 and, therefore, does not mean the same as GCC’s <code>-march=i686</code>. It is the responsibility of Linux distributions to use a target configuration that matches what they intend to support.</div></summary><link href="https://hsivonen.fi/i686/"></link><id>http://hsivonen.iki.fi/i686/</id><updated>2021-03-01T10:31:27Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Toimintamalli</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A document request to the city of Helsinki. (In Finnish)</div></summary><link href="https://hsivonen.fi/toimintamalli/"></link><id>http://hsivonen.iki.fi/toimintamalli/</id><updated>2021-02-22T08:29:35Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Activating Browser Modes with Doctype</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A document about the essentials of the layout modes of newer browsers.</div></summary><link href="https://hsivonen.fi/doctype/"></link><id>http://hsivonen.iki.fi/doctype/</id><updated>2021-02-07T16:56:56Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Johtopäätöksiä mallin rakenteesta</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Observations made by reading the source code of the epidemiological model used by the Finnish institute for health and welfare. (In Finnish)</div></summary><link href="https://hsivonen.fi/mallin-rakenteesta/"></link><id>http://hsivonen.iki.fi/mallin-rakenteesta/</id><updated>2021-01-31T20:56:48Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Tehtävänmäärittelyä kirjoittamatta ja kuolemia laskematta laumasuojamallinnettu</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Document requests to the Finnish institute for health and welfare. (In Finnish)</div></summary><link href="https://hsivonen.fi/laumasuojamallinnus/"></link><id>http://hsivonen.iki.fi/laumasuojamallinnus/</id><updated>2021-01-27T19:45:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Character Encoding Menu in 2014</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">This post is about a UI feature that I wish no one would have to use. Happily, it is indeed <i>almost</i> unused. Still, I made it more usable in the case when it <i>is</i> used. (The change was more driven by code removal than usability, though.)</div></summary><link href="https://hsivonen.fi/encoding-menu/"></link><id>http://hsivonen.iki.fi/encoding-menu/</id><updated>2021-01-18T07:54:59Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Erillissuosituksen tarpeettomuudesta yleissuosituksen poikkeukseksi?</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A document request to the city of Helsinki. (In Finnish)</div></summary><link href="https://hsivonen.fi/tyopaikkamaskipoikkeus/"></link><id>http://hsivonen.iki.fi/tyopaikkamaskipoikkeus/</id><updated>2020-12-23T11:27:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">STM:n maskiaikajana</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A document request to the Ministry of Social Affairs and Health. (In Finnish)</div></summary><link href="https://hsivonen.fi/maskiaikajana/"></link><id>http://hsivonen.iki.fi/maskiaikajana/</id><updated>2020-11-04T16:32:27Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Rust 2021</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">It is again the time of year when the Rust team is <a href="https://blog.rust-lang.org/2020/09/03/Planning-2021-Roadmap.html">calling</a> for blog post as input to the next annual roadmap. This is my contribution.</div></summary><link href="https://hsivonen.fi/rust2021/"></link><id>http://hsivonen.iki.fi/rust2021/</id><updated>2020-09-13T17:45:43Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Oma-aloitteisesti mallinnettu</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A document request to the Finnish institute for health and welfare. (In Finnish)</div></summary><link href="https://hsivonen.fi/thl-talous/"></link><id>http://hsivonen.iki.fi/thl-talous/</id><updated>2020-06-24T19:16:52Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Kokopinovaatimuksin kilpailutettu</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A document request to the Finnish institute for health and welfare. (In Finnish)</div></summary><link href="https://hsivonen.fi/thl-sovelluskilpailutus/"></link><id>http://hsivonen.iki.fi/thl-sovelluskilpailutus/</id><updated>2020-06-17T06:17:39Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">chardetng: A More Compact Character Encoding Detector for the Legacy Web</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><a href="https://crates.io/crates/chardetng">chardetng</a> is a new small-binary-footprint character encoding detector for Firefox written in Rust.</div></summary><link href="https://hsivonen.fi/chardetng/"></link><id>http://hsivonen.iki.fi/chardetng/</id><updated>2020-06-08T16:23:51Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Varauksia paisutellen tiedotettu</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A document request to the Finnish institute for health and welfare. (In Finnish)</div></summary><link href="https://hsivonen.fi/maskittomuus-thl/"></link><id>http://hsivonen.iki.fi/maskittomuus-thl/</id><updated>2020-05-30T13:05:13Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Perusteasiakirjoitta tiedotettu</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A document request to the Ministry of Social Affairs and Health. (In Finnish)</div></summary><link href="https://hsivonen.fi/maskittomuus/"></link><id>http://hsivonen.iki.fi/maskittomuus/</id><updated>2020-05-30T12:26:31Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Always Use UTF-8 &amp; Always Label Your HTML Saying So</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">To avoid having to deal with escapes (other than for &lt;, &gt;, &amp;, and "), to avoid data loss in form submission, to avoid XSS when serving user-provided content, and <a href="https://html.spec.whatwg.org/multipage/semantics.html#charset">to comply with the HTML Standard</a>, always encode your HTML as UTF-8. Furthermore, in order to let browsers know that the document is UTF-8-encoded, always label it as such.</div></summary><link href="https://hsivonen.fi/label-utf-8/"></link><id>http://hsivonen.iki.fi/label-utf-8/</id><updated>2020-03-03T09:18:38Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">IME Smoke Testing</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">In early 2019, I found myself in a situation where I needed to check that I hadn’t broken IME integration code. Later in 2019, I needed to do it again and now I'm testing this again in 2020, so I’m writing this down.</div></summary><link href="https://hsivonen.fi/ime/"></link><id>http://hsivonen.iki.fi/ime/</id><updated>2020-02-14T09:16:44Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The Validator.nu HTML Parser</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">An implementation of the HTML5 parsing algorithm in Java. (Used in Firefox by the means of automated translation to C++.)</div></summary><link href="https://about.validator.nu/htmlparser/"></link><id>https://about.validator.nu/htmlparser/</id><updated>2020-02-11T13:44:04Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">About the Hiragino Fonts with CSS</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A short document about a couple of observations on using the Hiragino fonts with CSS. (The Hiragino fonts come with Mac OS X.)</div></summary><link href="https://hsivonen.fi/hiragino/"></link><id>http://hsivonen.iki.fi/hiragino/</id><updated>2020-01-12T17:21:59Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">It’s Time to Stop Adding New Features for Non-Unicode Execution Encodings in C++</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I think the C++ standard should adopt the approach of “Unicode-only internally” for <i>new</i> text processing facilities and should not support non-Unicode execution encodings in newly-introduced features. This allows new features to have less abstraction obfuscation for Unicode usage, avoids digging legacy applications deeper into non-Unicode commitment, and avoids the specification and implementation effort of adapting new features to make sense for non-Unicode execution encodings.</div></summary><link href="https://hsivonen.fi/non-unicode-in-cpp/"></link><id>http://hsivonen.iki.fi/non-unicode-in-cpp/</id><updated>2020-01-08T08:39:09Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Rust 2020</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">It’s again the time of year when the Rust Core Team calls for blog posts for input into the next year’s roadmap. This is my contribution.</div></summary><link href="https://hsivonen.fi/rust2020/"></link><id>http://hsivonen.iki.fi/rust2020/</id><updated>2019-11-06T14:13:53Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The Last of the Parsing Quirks</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I implemented a single quirk for HTML5 parsing yesterday.</div></summary><link href="https://hsivonen.fi/last-html-quirk/"></link><id>http://hsivonen.iki.fi/last-html-quirk/</id><updated>2019-10-24T18:33:42Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">About <code>about:blank</code></div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><code><a href="about:blank">about:blank</a></code>
157. is probably the hardest Web page to load. In fact, it is so hard that
158. in order to turn the HTML5 parser on by default in Firefox last year,
159. we decided to special-case <code>about:blank</code>
160. to use the old parser in Firefox 4.</div></summary><link href="https://hsivonen.fi/about-blank/"></link><id>http://hsivonen.iki.fi/about-blank/</id><updated>2019-09-19T13:06:53Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Rust 2019</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The Rust team <a href="https://blog.rust-lang.org/2018/12/06/call-for-rust-2019-roadmap-blogposts.html">encouraged</a> people to write blog posts reflecting on Rust in 2018 and proposing goals and directions for 2019. Here’s mine.</div></summary><link href="https://hsivonen.fi/rust2019/"></link><id>http://hsivonen.iki.fi/rust2019/</id><updated>2018-12-15T19:36:20Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">encoding_rs: a Web-Compatible Character Encoding Library in Rust</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><a href="https://crates.io/crates/encoding_rs">encoding_rs</a> is a high-decode-performance, low-legacy-encode-footprint and high-correctness implementation of the WHATWG <a href="https://encoding.spec.whatwg.org/">Encoding Standard</a> written in Rust.</div></summary><link href="https://hsivonen.fi/encoding_rs/"></link><id>http://hsivonen.iki.fi/encoding_rs/</id><updated>2018-12-05T11:22:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">How I Wrote a Modern C++ Library in Rust</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Patterns that I used to make <a href="https://crates.io/crates/encoding_rs">encoding_rs</a> appear as a modern C++ library to C++ code.</div></summary><link href="https://hsivonen.fi/modern-cpp-in-rust/"></link><id>http://hsivonen.iki.fi/modern-cpp-in-rust/</id><updated>2018-12-05T11:20:42Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Using cargo-fuzz to Transfer Code Review of Simple Safe Code to Complex Code that Uses <code>unsafe</code></div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><a href="rust2018/">#Rust2018</a></div></summary><link href="https://hsivonen.fi/cargo-fuzz/"></link><id>http://hsivonen.iki.fi/cargo-fuzz/</id><updated>2018-12-03T09:42:34Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A Rust Crate that
161. Also Quacks Like
162. a Modern C++ Library</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">My RustFest Paris 2018 talk. (Slides about pointers in zero-length slices have been edited after RustFest to avoid spreading out-of-date information.) <a href="https://media.ccc.de/v/rustfest18-5-a_rust_crate_that_also_quacks_like_a_modern_c_library">Video is available</a>.</div></summary><link href="https://hsivonen.fi/rustfest2018/"></link><id>http://hsivonen.iki.fi/rustfest2018/</id><updated>2018-06-04T10:28:16Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">#Rust2018</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The Rust team <a href="https://blog.rust-lang.org/2018/01/03/new-years-rust-a-call-for-community-blogposts.html">encouraged</a> people to write blog posts reflecting on Rust in 2017 and proposing goals and directions for 2018. Here’s mine.</div></summary><link href="https://hsivonen.fi/rust2018/"></link><id>http://hsivonen.iki.fi/rust2018/</id><updated>2018-01-11T18:44:27Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">No Namespaces in JSON, Please</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I think that experience from Namespaces in XML should lead to the conclusion not to repeat the same (or almost same) thing with JSON. I think the developer community as a whole should not pay the cost of the use cases of the part of the developer community that believes (out of the scope of this post if rightly or wrongly) that identifiers in data formats should fit into a global naming scheme and, more specifically, that naming scheme should make every identifier into a URI. Instead,  I think that the part of the developer community that believes that it needs to be able merge data thanks to identifiers being URIs should bear the cost of doing whatever name mangling it needs to do upon data ingest given the information of which format a given ingested piece of JSON was in.</div></summary><link href="https://hsivonen.fi/no-json-ns/"></link><id>http://hsivonen.iki.fi/no-json-ns/</id><updated>2017-05-31T07:14:40Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A Lecture about HTML5</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I was invited to give a lecture about HTML5 on a course titled <a href="https://noppa.tkk.fi/noppa/kurssi/t-111.5360/">WWW Applications</a> at the Department of Media Technology of Helsinki University of Technology.</div></summary><link href="https://hsivonen.fi/html5-lecture/"></link><id>http://hsivonen.iki.fi/html5-lecture/</id><updated>2016-07-26T16:32:45Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Julkisesti luotettu varmenne ikidomainille TLS:ää (SSL:ää) varten</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Aiemmin <a href="https://ikiwiki.iki.fi/faq/ikidomain">ikidomainille</a>,
163. kuten <code>hsivonen.iki.fi</code>, on ollut vaikeaa saada julkisesti
164. luotettua TLS-varmennetta. Uusi voittoa tavoittelematon varmentaja <a href="https://letsencrypt.org/">Let’s Encrypt</a> tarkistaa
165. isäntänimen (hostname) hallinnan ja mahdollistaa näin julkisesti luotetun varmenteen saamisen ikidomaineille. <span>(<i>English summary:</i> Previously it was
166. impractical to get a publicly trusted TLS certificate for an iki domain (e.g.
167. <code>hsivonen.iki.fi</code>). Thanks to Let’s Encrypt performing validation
168. on a per-hostname basis, it’s now practical to get a publicly trusted
169. certificate for an iki domain.)</span></div></summary><link href="https://hsivonen.fi/iki-cert/"></link><id>http://hsivonen.iki.fi/iki-cert/</id><updated>2016-04-02T12:20:12Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">-webkit-HTML5</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Apple took some of their Safari Technology Demos from their
170. developer site and published them at <a href="http://www.apple.com/html5/">http://www.apple.com/html5/</a>
171. as an “HTML5 Showcase”. <a href="http://www.0xdeadbeef.com/weblog/2010/06/intellectual-honesty-and-html5/">Christopher
172. Blizzard's blog post</a> about the subject says almost everything I'd
173. have to say, so please read Blizzard's post. I'm posting just my
174. diffs here.</div></summary><link href="https://hsivonen.fi/-webkit-html5/"></link><id>http://hsivonen.iki.fi/-webkit-html5/</id><updated>2015-07-14T11:26:36Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Lists in Attribute Values</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Whitespace-separation is good.</div></summary><link href="https://hsivonen.fi/lists-in-attributes/"></link><id>http://hsivonen.iki.fi/lists-in-attributes/</id><updated>2015-07-14T11:25:29Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The Sad Story of PNG Gamma “Correction”</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Why you might not want to use PNG images when you want image colors and CSS colors to match.</div></summary><link href="https://hsivonen.fi/png-gamma/"></link><id>http://hsivonen.iki.fi/png-gamma/</id><updated>2015-07-14T11:23:23Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">If You Want Software Freedom on Phones, You Should Work on Firefox OS, Custom Hardware and Web App Self-Hostablility</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">To achieve full-stack Software Freedom on mobile phones, I think it makes sense to focus on Firefox OS, commission custom hardware and develop self-hostable Free Software Web apps and an easy deployment platform for them.</div></summary><link href="https://hsivonen.fi/phone-freedom/"></link><id>http://hsivonen.iki.fi/phone-freedom/</id><updated>2015-01-24T10:04:16Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">HTML5 Parser Improvements</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">As <a href="test-html5-parsing/">mentioned</a> <a href="speculative-html5-parsing/">earlier</a>, there is an ongoing project for replacing Gecko’s old HTML parser with an <a href="https://www.whatwg.org/specs/web-apps/current-work/">HTML5</a> parser. Significant improvements have landed lately, so if you’ve previously tried the HTML5 parser and turned it off due to crashiness or Web compatibility issues, now is a good time to turn it back on.</div></summary><link href="https://hsivonen.fi/html5-parser-improvements/"></link><id>http://hsivonen.iki.fi/html5-parser-improvements/</id><updated>2014-11-21T09:44:53Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">ARIA in HTML5 Integration: Document Conformance (Draft, Take Two)</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Now a runnable suggestion.</div></summary><link href="https://hsivonen.fi/aria-html5-bis/"></link><id>http://hsivonen.iki.fi/aria-html5-bis/</id><updated>2014-11-21T09:37:07Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Schema.org and Pre-Existing Communities</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I have been reading tweets and blog posts expressing various
175. levels of disappointment and unhappiness about schema.org not using
176. RDFa, not using Microformats or not having been developed in the open
177. with the community. Since other people’s perspectives differ from
178. mine, I feel <a href="http://xkcd.com/386/">compelled</a> to write
179. down my take.</div></summary><link href="https://hsivonen.fi/schema-org-and-communities/"></link><id>http://hsivonen.iki.fi/schema-org-and-communities/</id><updated>2014-11-21T09:34:49Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Lowering memory requirements by replacing Schematron</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">For long time, <a href="thesis/html5-conformance-checker#opt-schematron">I’ve said</a> is that the Schematron schema in the <a href="https://html5.validator.nu/">HTML5 facet of Validator.nu</a> was merely a rapid prototype that should be replaced with custom Java code.</div></summary><link href="https://hsivonen.fi/schematron-ram/"></link><id>http://hsivonen.iki.fi/schematron-ram/</id><updated>2014-11-21T09:17:14Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">HTML5 Parsing in Gecko: A Build</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The effort of putting an <a href="https://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html">HTML5
180. parser</a> inside Gecko takes a step out of the vaporware land.</div></summary><link href="https://hsivonen.fi/html5-gecko-build/"></link><id>http://hsivonen.iki.fi/html5-gecko-build/</id><updated>2014-11-21T09:16:00Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Introducing SAX Tree</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I chose to write yet another XML tree package.</div></summary><link href="https://hsivonen.fi/introducing-sax-tree/"></link><id>http://hsivonen.iki.fi/introducing-sax-tree/</id><updated>2014-11-21T09:13:33Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">NVDL Support in Validator.nu</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I enabled NVDL today.</div></summary><link href="https://hsivonen.fi/nvdl/"></link><id>http://hsivonen.iki.fi/nvdl/</id><updated>2014-11-21T09:11:12Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">HOWTO Avoid Being Called a Bozo When Producing XML</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Dos and don’ts about producing XML programmatically.</div></summary><link href="https://hsivonen.fi/producing-xml/"></link><id>http://hsivonen.iki.fi/producing-xml/</id><updated>2014-11-21T09:08:37Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">An Unofficial Q&amp;A about the Discontinuation of the XHTML2 WG</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Many of the comments on Zeldman’s
181. post indicate that there are people who are badly misinformed about
182. the matters surrounding this announcement. To help remedy that,
183. here’s some quick Q&amp;A for getting informed.</div></summary><link href="https://hsivonen.fi/xhtml2-html5-q-and-a/"></link><id>http://hsivonen.iki.fi/xhtml2-html5-q-and-a/</id><updated>2014-11-21T09:03:57Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Thoughts on HTML5 Becoming a W3C Recommendation</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Since I’ve participated in the development of HTML5 for a decade now (since before it was commonly called “HTML5”), I’ve been asked for my thoughts about HTML5 becoming a W3C Recommendation. Hence, I figured I’d post something here.</div></summary><link href="https://hsivonen.fi/html5-rec/"></link><id>http://hsivonen.iki.fi/html5-rec/</id><updated>2014-10-26T19:45:55Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Four Finnish Banks Training Users to Give Banking Credentials to Another Site</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A person who turns to me for technical advice was logging in to government service using banking for a bank called Handelsbanken. However, the page that was asking for the Handelsbanken login credentials was not served from <code>https://*.handelsbanken.fi/</code>!  After investigating what was going on, I decided to review how other banks  in Finland handle this. Here are my findings.</div></summary><link href="https://hsivonen.fi/bank-idp/"></link><id>http://hsivonen.iki.fi/bank-idp/</id><updated>2013-12-16T06:55:31Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Unimpressed by Leopard</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Sadly, Leopard is not a clear improvement over Tiger.</div></summary><link href="https://hsivonen.fi/leopard/"></link><id>http://hsivonen.iki.fi/leopard/</id><updated>2013-11-23T14:13:19Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Sergeant Semantics</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">So the W3C launched a <a href="http://www.w3.org/html/logo/">logo for HTML5</a>. And not just for <a href="http://www.w3.org/TR/html5/">HTML5-the-spec</a> but <a href="http://www.webstandards.org/2011/01/18/regarding-the-html5-logo/">for HTML5-the-buzzword</a>. Regardless of the logo itself or what it stands for, I find the choice of the ancillary visual elements weird.</div></summary><link href="https://hsivonen.fi/sergeant-semantics/"></link><id>http://hsivonen.iki.fi/sergeant-semantics/</id><updated>2013-11-23T14:11:28Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The Content Sink Inheritance Diagram – 2006-06-30</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I have discovered that my <a href="../content-sink/">previous diagram</a> showed only a part of the inheritance graph below <code>nsIContentSink</code>. There is more.</div></summary><link href="https://hsivonen.fi/kesakoodi/content-sink-diagram/"></link><id>http://hsivonen.iki.fi/kesakoodi/content-sink-diagram/</id><updated>2013-11-23T14:08:21Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">What is EME?</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">It was suggested at the Mozilla Summit that there isn’t good information around about what <a href="https://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/encrypted-media.html">Encrypted Media Extensions</a> (EME) actually is. Since I’m on the HTML working group and have been reading the email threads about EME there, I thought that I could provide an introduction that explains things that may not be apparent from the specification itself.</div></summary><link href="https://hsivonen.fi/eme/"></link><id>http://hsivonen.iki.fi/eme/</id><updated>2013-10-16T13:47:00Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">About Points and Pixels as Units</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A document about points being often mistakenly though as pixel units. Points are not pixel units. Defining the font size in points on Web pages is considered harmful. <strong>This document needs to be updated.</strong></div></summary><link href="https://hsivonen.fi/units/"></link><id>http://hsivonen.iki.fi/units/</id><updated>2012-10-02T12:56:58Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The Performance Cost of the HTML Tree Builder</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I’ve been thinking about the performance gap between the
184. Validator.nu HTML Parser and Xerces. What can be attributed to the
185. “extra fix-ups” that an HTML parser has to do and what can be
186. attributed to my code being worse than the Xerces code?</div></summary><link href="https://hsivonen.fi/cost-of-html/"></link><id>http://hsivonen.iki.fi/cost-of-html/</id><updated>2012-09-17T12:24:57Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Social Media Impression Management</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I asked if they had researched the
187. image formation of social media sites. They hadn’t.</div></summary><link href="https://hsivonen.fi/social-media-impression-management/"></link><id>http://hsivonen.iki.fi/social-media-impression-management/</id><updated>2012-09-17T12:24:26Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The <code>spacer</code> Element Is Gone</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Today, I landed a <a href="https://hg.mozilla.org/mozilla-central/rev/bc15c280c430">patch</a>
188. that made the HTML5 parser in Gecko unaware of the HTML <code>spacer</code>
189. element.</div></summary><link href="https://hsivonen.fi/spacer/"></link><id>http://hsivonen.iki.fi/spacer/</id><updated>2012-09-17T12:22:30Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Openmind 2006</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I attended <a href="http://www.openmind.fi/">Openmind</a> 2006
190. last week. Here are some notes.</div></summary><link href="https://hsivonen.fi/openmind-2006/"></link><id>http://hsivonen.iki.fi/openmind-2006/</id><updated>2012-09-17T12:19:16Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Performance Mistake</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">In the spirit of documenting one’s mistakes…</div></summary><link href="https://hsivonen.fi/performance-mistake/"></link><id>http://hsivonen.iki.fi/performance-mistake/</id><updated>2012-09-17T12:17:14Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">XHTML and Mobile Devices</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><a href="https://simon.html5.org/articles/mobile-results">Simon
191. Pieters’ mobile XHTML test results</a> need more publicity.</div></summary><link href="https://hsivonen.fi/zcorpan-xhtml/"></link><id>http://hsivonen.iki.fi/zcorpan-xhtml/</id><updated>2012-09-17T12:16:32Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">WebM-Enabled Browser Usage Share Exceeds H.264-Enabled Browser Usage Share on Desktop (in StatCounter Numbers)</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Looking at StatCounter stats, it occurred to me that they might not match the common narrative about H.264 market share. I decide to run some numbers using StatCounter stats.</div></summary><link href="https://hsivonen.fi/webm-share/"></link><id>http://hsivonen.iki.fi/webm-share/</id><updated>2012-09-17T12:15:57Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">HTML5 Parser-Based View Source Syntax Highlighting</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A new implementation of the View Source HTML and XML syntax highlighting has landed in Firefox.</div></summary><link href="https://hsivonen.fi/view-source/"></link><id>http://hsivonen.iki.fi/view-source/</id><updated>2012-03-14T16:10:01Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Vendor Prefixes Are Hurting the Web</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I think vendor prefixes are hurting the Web. I think we (people developing browsers and Web standards) should stop hurting the Web.</div></summary><link href="https://hsivonen.fi/vendor-prefixes/"></link><id>http://hsivonen.iki.fi/vendor-prefixes/</id><updated>2012-02-10T13:15:55Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><code>Accept-Charset</code> Is No More</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Now that Firefox 10 has been released, <del>none of the major browsers send</del> <ins>only Chrome sends</ins> the <code>Accept-Charset</code> HTTP header.</div></summary><link href="https://hsivonen.fi/accept-charset/"></link><id>http://hsivonen.iki.fi/accept-charset/</id><updated>2012-02-07T06:56:01Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Dualroids</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A two-player asteroid shooting network game written in Java.</div></summary><link href="https://hsivonen.fi/dualroids/"></link><id>http://hsivonen.iki.fi/dualroids/</id><updated>2011-12-22T13:27:39Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Writing Structural Stylable Documents in Mozilla Editor</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The Mozilla Editor is designed around HTML 4 Transitional. If special steps aren’t taken, it is easy to produce presentational documents that lack stylable structure. This document describes some basic good authoring practices for the purpose of writing structural and stylable documents.</div></summary><link href="https://hsivonen.fi/moz-editor/"></link><id>http://hsivonen.iki.fi/moz-editor/</id><updated>2011-12-22T13:22:32Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">ISO-8859-15 on haitallinen</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">UTF-8 is the way to go. (In Finnish.)</div></summary><link href="https://hsivonen.fi/iso-8859-15/"></link><id>http://hsivonen.iki.fi/iso-8859-15/</id><updated>2011-12-22T13:18:09Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Hourglass</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Yet another ray tracing gallery page.</div></summary><link href="https://hsivonen.fi/hourglass/"></link><id>http://hsivonen.iki.fi/hourglass/</id><updated>2011-12-22T13:16:08Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The Scientific Method According to Hixie</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Quote of the week from the topic of #developers on irc.mozilla.org</div></summary><link href="https://hsivonen.fi/scientific-method-according-to-hixie/"></link><id>http://hsivonen.iki.fi/scientific-method-according-to-hixie/</id><updated>2011-12-22T12:57:52Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Maemo Source Code</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">To save others the trouble of requesting the source, here are the contents of the package called “2.2006.39-14-srcs”.</div></summary><link href="https://hsivonen.fi/maemo-src/"></link><id>http://hsivonen.iki.fi/maemo-src/</id><updated>2011-12-22T12:57:07Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Karpelan lukkovertaus ontuu</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Anti-circumvention legislation does not make sense, and it is fallacious to compare circumventing DRM to breaking into an apartment. (In Finnish)</div></summary><link href="https://hsivonen.fi/lukkovertaus/"></link><id>http://hsivonen.iki.fi/lukkovertaus/</id><updated>2011-12-22T12:56:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Digitaalisesta arkistoinnista</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Documents about archiving digital documents (in Finnish)</div></summary><link href="https://hsivonen.fi/arkistointi/"></link><id>http://hsivonen.iki.fi/arkistointi/</id><updated>2011-12-22T12:51:35Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">ARIA in HTML5 Integration: Document Conformance (Draft)</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">This is not a spec and has not been endorsed by anyone.</div></summary><link href="https://hsivonen.fi/aria-html5/"></link><id>http://hsivonen.iki.fi/aria-html5/</id><updated>2011-12-22T12:50:37Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">XHTML—What’s the Point? (Draft, incomplete)</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">This document is incomplete, but I put it on the Web in order to avoid retyping the same thing over and over again in newsgroup discussions.</div></summary><link href="https://hsivonen.fi/xhtml-the-point/"></link><id>http://hsivonen.iki.fi/xhtml-the-point/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Mac OS X Browser Comparison</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">This document is a rough yes/no feature comparison of the Web browsers that run natively on Mac OS X. It does not cover browsers that run on the Classic VM or require an implementation of the X11 windowing system. <strong>Severely out of date. For historical reference only!</strong></div></summary><link href="https://hsivonen.fi/os-x-browsers/"></link><id>http://hsivonen.iki.fi/os-x-browsers/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">HOWTO Spot a Wannabe Web Standards Advocate</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I have seen this too often. (<a href="wannabe/fr/">Aussi disponible en français</a>;
192. <a href="wannabe/de/">Auch vorhanden auf Deutsch</a>; <a href="wannabe/pl/">jest dostępny po polsku</a>)</div></summary><link href="https://hsivonen.fi/wannabe/"></link><id>http://hsivonen.iki.fi/wannabe/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">An Idea About Intermediate Language Trees and Web UI Generation</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">An idea about Web UI generation I had when I was studying compiler technology.</div></summary><link href="https://hsivonen.fi/web-ui-trees/"></link><id>http://hsivonen.iki.fi/web-ui-trees/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Thoughts on Using SSL/TLS Certificates as the Solution to Phishing</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Comments on <a href="http://www.gerv.net/security/stay-safe/"><cite>Staying Safe From
193. Phishing With Firefox</cite></a>.</div></summary><link href="https://hsivonen.fi/phishing-certs/"></link><id>http://hsivonen.iki.fi/phishing-certs/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Bureaucracy Meets the Web</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Three things from the past week happened to be related to bureaucracy and the Web…</div></summary><link href="https://hsivonen.fi/bureaucracy-meets-the-web/"></link><id>http://hsivonen.iki.fi/bureaucracy-meets-the-web/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Europe Day</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Tuesday 2006-05-09 was the Europe Day. I traveled to Tampere for a show debate.</div></summary><link href="https://hsivonen.fi/europe-day/"></link><id>http://hsivonen.iki.fi/europe-day/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">HOWTO Establish a 100% Literacy Rate</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">This is one of my favorite pieces of West
194. Wing script writing.</div></summary><link href="https://hsivonen.fi/literacy/"></link><id>http://hsivonen.iki.fi/literacy/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">What to Do with All These Photos?</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I have a lot of photos that aren’t shared properly, which makes
195. them less useful than they could be. Considering that it has been
196. possible to publish photos on the Web for over a decade, I find it
197. interesting and annoying how many unsolved problems there still are.</div></summary><link href="https://hsivonen.fi/online-photos/"></link><id>http://hsivonen.iki.fi/online-photos/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Charmod Norm Checking</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><a href="http://www.w3.org/TR/charmod-norm/">Charmod Norm</a> is
198. still in the Working Draft state, but if it were to become a
199. normative part of (X)HTML5, it would belong to the area of the
200. conformance checking service that I am working on now, so I
201. prototyped Charmod Norm enforcement as well.</div></summary><link href="https://hsivonen.fi/charmod-norm-checking/"></link><id>http://hsivonen.iki.fi/charmod-norm-checking/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Validator Web Service Interface Ideas</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I am just writing this down so I don’t forget it.</div></summary><link href="https://hsivonen.fi/validator-ws-ideas/"></link><id>http://hsivonen.iki.fi/validator-ws-ideas/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">DTDs Don’t Work on the Web</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Last weekend, Slashdot <a href="http://slashdot.org/article.pl?sid=07/01/14/1359213">linked</a>
202. to an <a href="http://www.deviceforge.com/news/NS9169645513.html">article</a>
203. that observed that Netscape had removed the <a href="http://my.netscape.com/publish/formats/rss-0.91.dtd">RSS
204. 0.91 DTD</a>. I hope this episode has a silver
205. lining and helps in making people realize that DTDs don’t belong on
206. the Web.</div></summary><link href="https://hsivonen.fi/no-dtd/"></link><id>http://hsivonen.iki.fi/no-dtd/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">EFFI’s Day in Court</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><a href="bureaucracy-meets-the-web/">As
207. mentioned earlier</a>, <a href="https://www.effi.org/">Electronic
208. Frontier Finland</a> (EFFI) was suspected of illegal fundraising. The
209. case was tried today. I went to the court house to observe the
210. proceedings.</div></summary><link href="https://hsivonen.fi/effi-court/"></link><id>http://hsivonen.iki.fi/effi-court/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Speaking at XTech</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I’ll be speaking at <a href="http://2007.xtech.org/public/schedule/grid">XTech</a>.</div></summary><link href="https://hsivonen.fi/speaking-at-xtech/"></link><id>http://hsivonen.iki.fi/speaking-at-xtech/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Security Quote of the Day</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Cluelessness and incompetence of epic proportions.</div></summary><link href="https://hsivonen.fi/sampo-epic-multifail/"></link><id>http://hsivonen.iki.fi/sampo-epic-multifail/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Out of Context</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Last week on W3C mailing lists.</div></summary><link href="https://hsivonen.fi/out-of-context/"></link><id>http://hsivonen.iki.fi/out-of-context/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The <code>html5.parser.enable</code> Pref is Gone</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Just a quick note to Firefox nightly testers and bug triagers: I pushed
211. a patch that makes Firefox no longer honor the <code>html5.parser.enable</code> pref.</div></summary><link href="https://hsivonen.fi/old-parser-pref/"></link><id>http://hsivonen.iki.fi/old-parser-pref/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Miscellaneous Java Code</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Utility code.</div></summary><link href="https://hsivonen.fi/code/"></link><id>http://hsivonen.iki.fi/code/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Autozoom Extension for Firefox®</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">When Autozoom is activated, the current document is analyzed for the
212. dominant font size and the view is zoomed by the factor that makes
213. the dominant size match your font size preference.</div></summary><link href="https://hsivonen.fi/autozoom/"></link><id>http://hsivonen.iki.fi/autozoom/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Älä käytä Creative Commons 1.0 -lisenssejä
214. – käytä 2.5-sarjaa</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The Finland version of the Creative Commons
215. suite of licenses is still at 1.0. The 1.0 series of CC licenses has
216. three serious known bugs (in Finnish)</div></summary><link href="https://hsivonen.fi/ei-cc-1.0/"></link><id>http://hsivonen.iki.fi/ei-cc-1.0/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Tag Soup: How Mac IE 5 and Safari handle &lt;x&gt; &lt;y&gt; &lt;/x&gt;
217. &lt;/y&gt;</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">What happens with the DOM in Safari and Mac IE 5 when the nesting of the markup is broken?</div></summary><link href="https://hsivonen.fi/soup-dom/"></link><id>http://hsivonen.iki.fi/soup-dom/</id><updated>2011-12-22T12:43:18Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Mustaa valkoisella</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A document request to the Ministry of Education. (In Finnish)</div></summary><link href="https://hsivonen.fi/mustaa-valkoisella/"></link><id>http://hsivonen.iki.fi/mustaa-valkoisella/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Is Atom What We Really Need?</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Atom (formerly known as Pie, Echo and Necho) has been created as a cleaner and better-defined alternative to RSS 2.0, which is underspecified. But is a reformulated version of RSS 2.0 really what we need?</div></summary><link href="https://hsivonen.fi/need-atom/"></link><id>http://hsivonen.iki.fi/need-atom/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">10 Safari 1.0 issues</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Hyatt requested lists like this.</div></summary><link href="https://hsivonen.fi/safari-issues/"></link><id>http://hsivonen.iki.fi/safari-issues/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Names of Browser Engines</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A table of browser names, engine names and script engine names.</div></summary><link href="https://hsivonen.fi/engines/"></link><id>http://hsivonen.iki.fi/engines/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Natural Hazards: NA</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Thoughts about nuclear power plants in stormy situations.</div></summary><link href="https://hsivonen.fi/natural-hazards/"></link><id>http://hsivonen.iki.fi/natural-hazards/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Who knows prefixed XHTML from a hole in the ground?</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Remember to test prefixed XHTML as well.</div></summary><link href="https://hsivonen.fi/atom-xhtml/"></link><id>http://hsivonen.iki.fi/atom-xhtml/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Aula 2006</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Yesterday, I went to listen to the public speeches that were part
218. of <a href="http://aula.org/">Aula 2006 – Movement</a>.</div></summary><link href="https://hsivonen.fi/aula-2006/"></link><id>http://hsivonen.iki.fi/aula-2006/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Charmod Checking</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Here’s how I have addressed the requirements of Charmod that
219. apply to content (marked as [C] is Charmod).</div></summary><link href="https://hsivonen.fi/charmod-checking/"></link><id>http://hsivonen.iki.fi/charmod-checking/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Printing Web Apps 1.0</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">This is a quick guide for getting a dead-tree version of the Web
220. Applications 1.0 spec.</div></summary><link href="https://hsivonen.fi/printing-wa10/"></link><id>http://hsivonen.iki.fi/printing-wa10/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Validator.nu Gets Out of the Java Trap</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">This week, I upgraded the operating system on the <a href="http://www.xen.org/">Xen</a>
221. virtual machine that powers <code><a href="https://validator.nu/">validator.nu</a></code>
222. and <code><a href="https://html5.validator.nu/">html5.validator.nu</a></code>
223. to <a href="http://www.ubuntu.com/">Ubuntu</a> <a href="https://wiki.ubuntu.com/HardyHeron">Hardy</a>.</div></summary><link href="https://hsivonen.fi/out-of-java-trap/"></link><id>http://hsivonen.iki.fi/out-of-java-trap/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Thou Shalt Not Spec a Feature that Might Inadvertently Compete with RDF when Used Contrary to How It Is Designed to Be Used</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">From the minutes of the TAG meeting on November 2<sup>nd</sup> 2009.</div></summary><link href="https://hsivonen.fi/rdf-competition/"></link><id>http://hsivonen.iki.fi/rdf-competition/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">SVG and MathML in <code>text/html</code> in Firefox and Validator.nu</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I enabled SVG and MathML-related stuff recently on both
224. mozilla-central and on Validator.nu.</div></summary><link href="https://hsivonen.fi/svg-and-mathml-in-html5/"></link><id>http://hsivonen.iki.fi/svg-and-mathml-in-html5/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">What Could Microsoft Do about IE6?</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Microsoft has started a <a href="http://ie6countdown.com/">campaign
225. to drive down the market share of IE6</a>. Getting rid of IE6 is a
226. righteous goal. Microsoft’s proposed solution isn’t righteous, though.</div></summary><link href="https://hsivonen.fi/ie6/"></link><id>http://hsivonen.iki.fi/ie6/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">UTF-8 to Code Point Array Converter in PHP</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">This package contains a PHP include file which provides two functions for converting between UTF-8 strings and arrays of ints representing Unicode code points.</div></summary><link href="https://hsivonen.fi/php-utf8/"></link><id>http://hsivonen.iki.fi/php-utf8/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">HTML Syntax Checker in PHP</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">An HTML linter written in PHP.</div></summary><link href="https://hsivonen.fi/html-syntax-checker/"></link><id>http://hsivonen.iki.fi/html-syntax-checker/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">SaxCompiler</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">SaxCompiler is a tool for recording SAX <a href="http://www.saxproject.org/apidoc/org/xml/sax/ContentHandler.html"><code>ContentHandler</code></a>
227. events as Java code that can play back the events without parsing
228. XML.</div></summary><link href="https://hsivonen.fi/saxcompiler/"></link><id>http://hsivonen.iki.fi/saxcompiler/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Photo Group Feed</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><a href="http://flickr.com/">Flickr</a> doesn’t provide feeds
229. for private groups. It doesn’t provide feeds for comments on photos
230. in a group, either. It is reasonable to want such feeds, so here’s
231. a script that generates them on your HTTP server.</div></summary><link href="https://hsivonen.fi/group-feed/"></link><id>http://hsivonen.iki.fi/group-feed/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Photo and <em>Metadata</em> Backup for Flickr</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">This is a photo and <em>metadata</em> backup utility for Flickr
232. written as a <em>self-contained</em> Java command line tool. The
233. metadata is written is an XML file whose format is an aggregation of
234. the response data from the Flickr API.</div></summary><link href="https://hsivonen.fi/photobackup/"></link><id>http://hsivonen.iki.fi/photobackup/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Thoughts About a Print <abbr title="User Interface">UI</abbr> for Mozilla</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Some thoughts about printing from a Web browser.</div></summary><link href="https://hsivonen.fi/print-ui/"></link><id>http://hsivonen.iki.fi/print-ui/</id><updated>2011-12-22T12:43:17Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Oops! I broke MathML – 2006-07-05</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Or, well, one could argue that it was already broken but my
235. content sink changes and a suitably crafted test case just exposed
236. the layout issues that were already there.</div></summary><link href="https://hsivonen.fi/kesakoodi/mathml-oops/"></link><id>http://hsivonen.iki.fi/kesakoodi/mathml-oops/</id><updated>2011-12-22T12:43:16Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Week 35</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The weekly report for week 35.</div></summary><link href="https://hsivonen.fi/kesakoodi/week35/"></link><id>http://hsivonen.iki.fi/kesakoodi/week35/</id><updated>2011-12-22T12:43:16Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Natural Hazards Again</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Looking across the street, I can see that there’s something
237. extra in the air between where I sit and the house on the other side
238. of the street.</div></summary><link href="https://hsivonen.fi/natural-hazards-again/"></link><id>http://hsivonen.iki.fi/natural-hazards-again/</id><updated>2011-12-22T12:43:16Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">CMS Stuff</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Papers and code related to a CMS project.</div></summary><link href="https://hsivonen.fi/cms/"></link><id>http://hsivonen.iki.fi/cms/</id><updated>2011-12-22T12:43:16Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Assembling Web Pages Using Document Trees</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A paper about a template engine that operates on XML document trees. (<a href="cms/">Source code available.</a>)</div></summary><link href="https://hsivonen.fi/cms/te/"></link><id>http://hsivonen.iki.fi/cms/te/</id><updated>2011-12-22T12:43:16Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Kesäkoodi Starting – 2006-05-23</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">So what’s this <a href="http://www.coss.fi/kesakoodi">Kesäkoodi</a>
239. thing about?</div></summary><link href="https://hsivonen.fi/kesakoodi/start/"></link><id>http://hsivonen.iki.fi/kesakoodi/start/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">DOM Traversal Performance – 2006-05-26</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">But there is a problem. My JavaScript implementation is slow.</div></summary><link href="https://hsivonen.fi/kesakoodi/dom-performance/"></link><id>http://hsivonen.iki.fi/kesakoodi/dom-performance/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Week 21</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The weekly report for week 21.</div></summary><link href="https://hsivonen.fi/kesakoodi/week21/"></link><id>http://hsivonen.iki.fi/kesakoodi/week21/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Week 22</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The weekly report for week 22.</div></summary><link href="https://hsivonen.fi/kesakoodi/week22/"></link><id>http://hsivonen.iki.fi/kesakoodi/week22/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Planning the XML Content Sink Incrementalization Work – 2006-06-10</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I’ve been researching the problem area of <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=18333">bug
240. 18333</a>.</div></summary><link href="https://hsivonen.fi/kesakoodi/content-sink/"></link><id>http://hsivonen.iki.fi/kesakoodi/content-sink/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Week 23</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The weekly report for week 23.</div></summary><link href="https://hsivonen.fi/kesakoodi/week23/"></link><id>http://hsivonen.iki.fi/kesakoodi/week23/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Week 24</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The weekly report for week 24.</div></summary><link href="https://hsivonen.fi/kesakoodi/week24/"></link><id>http://hsivonen.iki.fi/kesakoodi/week24/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Week 25</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The weekly report for week 25.</div></summary><link href="https://hsivonen.fi/kesakoodi/week25/"></link><id>http://hsivonen.iki.fi/kesakoodi/week25/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Eclipse CDT – 2006-06-27</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">After working in TextWrangler (and a bit in XCode) for a couple of
241. weeks, I really started to miss Eclipse. </div></summary><link href="https://hsivonen.fi/kesakoodi/eclipse-cdt/"></link><id>http://hsivonen.iki.fi/kesakoodi/eclipse-cdt/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Week 26</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The weekly report for week 26.</div></summary><link href="https://hsivonen.fi/kesakoodi/week26/"></link><id>http://hsivonen.iki.fi/kesakoodi/week26/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Builds! – 2006-07-06</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Now there is something to test. I am providing builds with my
242. preliminary patches for four target platforms.</div></summary><link href="https://hsivonen.fi/kesakoodi/builds/"></link><id>http://hsivonen.iki.fi/kesakoodi/builds/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Builds, Take Two – 2006-07-07</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The <a href="http://hsivonen.iki.fi/test/bug18333/builds/">builds</a>
243. have been respun with fixes for interrupting Expat properly.</div></summary><link href="https://hsivonen.fi/kesakoodi/builds-take-two/"></link><id>http://hsivonen.iki.fi/kesakoodi/builds-take-two/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Week 27</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The weekly report for week 27.</div></summary><link href="https://hsivonen.fi/kesakoodi/week27/"></link><id>http://hsivonen.iki.fi/kesakoodi/week27/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Week 30</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The weekly report for week 30.</div></summary><link href="https://hsivonen.fi/kesakoodi/week30/"></link><id>http://hsivonen.iki.fi/kesakoodi/week30/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Week 31</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The weekly report for week 31.</div></summary><link href="https://hsivonen.fi/kesakoodi/week31/"></link><id>http://hsivonen.iki.fi/kesakoodi/week31/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Week 32</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The weekly report for week 32.</div></summary><link href="https://hsivonen.fi/kesakoodi/week32/"></link><id>http://hsivonen.iki.fi/kesakoodi/week32/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Week 33</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The weekly report for week 33.</div></summary><link href="https://hsivonen.fi/kesakoodi/week33/"></link><id>http://hsivonen.iki.fi/kesakoodi/week33/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Speaking Gig – 2006-08-28</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I have been booked to speak at the Openbyte pre-conference of the
244. <a href="http://www.openmind.fi/">Openmind 2006</a> event in Tampere
245. Hall on 2006-10-24. </div></summary><link href="https://hsivonen.fi/kesakoodi/speaking-gig/"></link><id>http://hsivonen.iki.fi/kesakoodi/speaking-gig/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Week 34</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The weekly report for week 34.</div></summary><link href="https://hsivonen.fi/kesakoodi/week34/"></link><id>http://hsivonen.iki.fi/kesakoodi/week34/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">On Clipboard Formats – 2006-09-15</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">This stuff is so underdocumented that it isn’t even funny. This
246. document is written so that others might find something when they
247. search the Web.</div></summary><link href="https://hsivonen.fi/kesakoodi/clipboard/"></link><id>http://hsivonen.iki.fi/kesakoodi/clipboard/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Kesäkoodi Wrap-Up – 2006-09-19</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The last week of Kesäkoodi stretched to two sparse weeks.</div></summary><link href="https://hsivonen.fi/kesakoodi/wrap-up/"></link><id>http://hsivonen.iki.fi/kesakoodi/wrap-up/</id><updated>2011-12-22T12:43:15Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Outlining the “Ultimate” Blogging Server</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I’ve been thinking what a really
248. good blogging system or a news site content management system would
249. be like. Here’s my attempt at outlining the “ultimate”
250. blogging server.</div></summary><link href="https://hsivonen.fi/blog-server/"></link><id>http://hsivonen.iki.fi/blog-server/</id><updated>2011-12-22T12:43:14Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">How Not to Advertise an Election Candidate</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">On Sunday and Monday elections were held at the local congregation in order to select a new vicar. I didn’t like the campaigning.</div></summary><link href="https://hsivonen.fi/election-ads/"></link><id>http://hsivonen.iki.fi/election-ads/</id><updated>2011-12-22T12:43:14Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Unused Icons</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Unhelpful Microsoft wizardiness</div></summary><link href="https://hsivonen.fi/unused-icons/"></link><id>http://hsivonen.iki.fi/unused-icons/</id><updated>2011-12-22T12:43:14Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Comedy is the Real News</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">An observation I made last year when watching TV in the U.S.</div></summary><link href="https://hsivonen.fi/real-news/"></link><id>http://hsivonen.iki.fi/real-news/</id><updated>2011-12-22T12:43:14Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Need a Taxi at a Taxi Station? You Lose!</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A taxi station is the worst place to be in Helsinki when you need a taxi (unless there’s one already there).</div></summary><link href="https://hsivonen.fi/taxi/"></link><id>http://hsivonen.iki.fi/taxi/</id><updated>2011-12-22T12:43:14Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Reality Distortion Fields</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Where Joel Spolsky’s analysis of the IE version targeting issue goes wrong.</div></summary><link href="https://hsivonen.fi/rdf/"></link><id>http://hsivonen.iki.fi/rdf/</id><updated>2011-12-22T12:43:14Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">XTech 2006</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I went to the <a href="http://xtech06.usefulinc.com/">XTech 2006</a>
251. conference last week.</div></summary><link href="https://hsivonen.fi/xtech-2006/"></link><id>http://hsivonen.iki.fi/xtech-2006/</id><updated>2011-12-22T12:43:13Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Built-in Accessibility Roles in HTML5</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A quick table of <a href="http://www.w3.org/TR/aria-role/">WAI-ARIA</a> roles and what <a href="http://www.whatwg.org/specs/web-apps/current-work/">HTML 5</a> provides natively for each role as of July 2007.</div></summary><link href="https://hsivonen.fi/html5-roles/"></link><id>http://hsivonen.iki.fi/html5-roles/</id><updated>2011-12-22T12:43:13Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Validator.nu Downtime</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Validator.nu was down last week.</div></summary><link href="https://hsivonen.fi/downtime/"></link><id>http://hsivonen.iki.fi/downtime/</id><updated>2011-12-22T12:43:13Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I Want an Affordable Snapshot-Saving Crypto-Backupping RAID NAS</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">This week, I lost over one potential work day to HFS+. And it
252. wasn’t the first time I’ve lost time to HFS+. I want to
253. make arrangements to avoid losing time to HFS+ in the future.</div></summary><link href="https://hsivonen.fi/nas/"></link><id>http://hsivonen.iki.fi/nas/</id><updated>2011-12-22T12:43:13Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">SVG Filter Effects in HTML without External References</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The project of putting an <a href="html5-gecko-build/">HTML5
254. parser inside Gecko</a> has progressed. I merged in code from the
255. trunk in order to experiment with cool new stuff such as <a href="http://weblogs.mozillazine.org/roc/archives/2008/06/applying_svg_ef.html">SVG
256. filter effects for HTML</a>.</div></summary><link href="https://hsivonen.fi/svg-filters-html5/"></link><id>http://hsivonen.iki.fi/svg-filters-html5/</id><updated>2011-12-22T12:43:13Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">HTML5 Script Execution Changes in Firefox 4 Beta 7</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">In Firefox 4 beta 7, script execution changed to be more
257. HTML5-compliant than before. This means that in some cases sites that
258. sniff for Firefox or Gecko may break. <i>If your site/app works
259. cross-browser without browser sniffing, you don’t need to read
260. further.</i> (However, if you triage bugs on bugzilla.mozilla.org, you might still want to read on.)</div></summary><link href="https://hsivonen.fi/script-execution/"></link><id>http://hsivonen.iki.fi/script-execution/</id><updated>2011-12-22T12:43:13Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Vihreiden tekijänoikeuslinja ja teosten tekijöiden eläketurva</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Vihreät julkaisivat äskettäin <a href="http://www.vihreat.fi/tekijanoikeuslinjat">tekijänoikeuslinjapaperin</a>.
261. On positiivista, että puolue kiinnittää huomiota aihepiiriin niin
262. paljon, että siitä julkaistaan erillinen linjapaperi. Minua
263. kuitenkin häiritsee paperissa suhtautuminen teosten tekijöiden
264. eläketurvaan. <span>(<i>English summary:</i> I’m unhappy that the newly
265. released copyright policy paper of the Finnish Green Party suggests
266. that authors of copyrighted works should get royalties for the
267. commercial use of the works they have created long after the creation
268. of the work in order to get money in the pensioner age.)</span></div></summary><link href="https://hsivonen.fi/rojalti-ja-elake/"></link><id>http://hsivonen.iki.fi/rojalti-ja-elake/</id><updated>2011-12-22T12:43:13Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Windows 8 App Support Matrix</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Over the last few days, there’s been quite a bit of speculation about whether Windows 8 on ARM will ship the desktop environment and allow recompiled code written to the legacy Win32 APIs run.</div></summary><link href="https://hsivonen.fi/windows8/"></link><id>http://hsivonen.iki.fi/windows8/</id><updated>2011-12-22T12:43:13Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Regular Expressions, Computer Science and Practice</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Disregard of computer science can crash your app.</div></summary><link href="https://hsivonen.fi/regexp/"></link><id>http://hsivonen.iki.fi/regexp/</id><updated>2011-12-22T12:43:12Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Almost Precedent</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Why the Gecko Almost Standards Mode shouldn’t be used to justify IE engine version targeting.</div></summary><link href="https://hsivonen.fi/almost-precedent/"></link><id>http://hsivonen.iki.fi/almost-precedent/</id><updated>2011-12-22T12:43:12Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Access Blocked</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I followed a link from a message to a spec in the <a href="http://www.w3.org/TR/">/TR/</a>
269. space on <a href="http://www.w3.org/">www.w3.org</a>.</div></summary><link href="https://hsivonen.fi/access-blocked/"></link><id>http://hsivonen.iki.fi/access-blocked/</id><updated>2011-12-22T12:43:12Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Extended Uncertainty</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I use <a href="https://myvidoop.com/">myvidoop</a> as my OpenID
270. delegate. They used to have an <a href="https://en.wikipedia.org/wiki/Extended_Validation_Certificate">EV
271. certificate</a>. Yesterday, they didn’t.</div></summary><link href="https://hsivonen.fi/extended-uncertainty/"></link><id>http://hsivonen.iki.fi/extended-uncertainty/</id><updated>2011-12-22T12:43:12Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">View Originl Bookmarklet</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">It takes way too many clicks to get from a Flickr photo page to the original JPEG file. I wrote a bookmarklet that does it with just one click.</div></summary><link href="https://hsivonen.fi/view-originl/"></link><id>http://hsivonen.iki.fi/view-originl/</id><updated>2011-12-22T12:43:12Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Things to Take into Account When Moving to Standards-Compliant HTML and CSS Authoring</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">This is a mixed collection of a few issues that are worth taking into account when writing Web pages according to the W3C Recommendations.</div></summary><link href="https://hsivonen.fi/standards/"></link><id>http://hsivonen.iki.fi/standards/</id><updated>2011-12-22T12:43:11Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Makasiinit</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">So the <span>Makasiinit</span> burned today.</div></summary><link href="https://hsivonen.fi/makasiinit/"></link><id>http://hsivonen.iki.fi/makasiinit/</id><updated>2011-12-22T12:43:11Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Imitating Reflective Caustics in POV-Ray</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">A tutorial on imitating reflective caustics in the official distribution of POV-Ray</div></summary><link href="https://hsivonen.fi/refl-light/"></link><id>http://hsivonen.iki.fi/refl-light/</id><updated>2011-12-22T12:43:10Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">RFC 2119 Key Words in Management Textbooks</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Just a random observation about the vocabulary of management textbooks.</div></summary><link href="https://hsivonen.fi/rfc2119-management/"></link><id>http://hsivonen.iki.fi/rfc2119-management/</id><updated>2011-12-22T12:43:10Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Atom Feed</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I now have an Atom 1.0 feed.</div></summary><link href="https://hsivonen.fi/atom-feed/"></link><id>http://hsivonen.iki.fi/atom-feed/</id><updated>2011-12-22T12:43:10Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">ISO Opens Up a Little</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">It turns out that ISO now has some standards on the Web. That’s
272. good, but putting all of them there in a Web-friendly format would be
273. even better.</div></summary><link href="https://hsivonen.fi/iso-web/"></link><id>http://hsivonen.iki.fi/iso-web/</id><updated>2011-12-22T12:43:10Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Table Integrity Checker</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The first non-schema checker prototype is a table integrity checker.</div></summary><link href="https://hsivonen.fi/table-integrity-checker/"></link><id>http://hsivonen.iki.fi/table-integrity-checker/</id><updated>2011-12-22T12:43:10Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Three Styles</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Well, four styles if you count the original.</div></summary><link href="https://hsivonen.fi/three-styles/"></link><id>http://hsivonen.iki.fi/three-styles/</id><updated>2011-12-22T12:43:10Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Thesis Defense on XForms</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">On Friday 2007-01-12, I went to listen to the thesis defense of
274. <a href="http://users.tkk.fi/~honkkis/">Mikko Honkala</a>.</div></summary><link href="https://hsivonen.fi/honkala-xforms/"></link><id>http://hsivonen.iki.fi/honkala-xforms/</id><updated>2011-12-22T12:43:10Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">IM Logs</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Quote of the week.</div></summary><link href="https://hsivonen.fi/im-logs/"></link><id>http://hsivonen.iki.fi/im-logs/</id><updated>2011-12-22T12:43:10Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Browser Sniffing History in the Chrome UA String</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><a href="https://www.google.com/chrome/">Google Chrome</a> has the following cruft in the HTTP <code>User-Agent</code> header.</div></summary><link href="https://hsivonen.fi/chrome-ua/"></link><id>http://hsivonen.iki.fi/chrome-ua/</id><updated>2011-12-22T12:43:10Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Speculative HTML5 Parsing Landed</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">As mentioned earlier, there is an ongoing project for replacing Gecko’s old HTML parser with an HTML5 parser. Today, a significant milestone landed: off-the-main-thread speculative HTML5 parsing.</div></summary><link href="https://hsivonen.fi/speculative-html5-parsing/"></link><id>http://hsivonen.iki.fi/speculative-html5-parsing/</id><updated>2011-12-22T12:43:10Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The Old HTML Fragment Parser is Gone</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Just a quick note to Firefox nightly testers and bug triagers.</div></summary><link href="https://hsivonen.fi/old-fragment/"></link><id>http://hsivonen.iki.fi/old-fragment/</id><updated>2011-12-22T12:43:10Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Big Brother EU</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">On Tuesday 2005-11-22, I went to a public discussion event titled “Big Brother EU”.</div></summary><link href="https://hsivonen.fi/big-brother-eu/"></link><id>http://hsivonen.iki.fi/big-brother-eu/</id><updated>2011-12-22T12:43:09Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Can Anti-DRM Clauses in Content Licenses be Free?</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Are anti-DRM clauses a good idea? Are the current clauses merely badly drafted and an anti-DRM clause in general could be free? Or is any anti-DRM clause inherently non-free?</div></summary><link href="https://hsivonen.fi/free-anti-drm/"></link><id>http://hsivonen.iki.fi/free-anti-drm/</id><updated>2011-12-22T12:43:09Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">An Introduction to Unicode</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">PDF slides about Unicode.</div></summary><link href="https://hsivonen.fi/Unicode.pdf"></link><id>http://hsivonen.iki.fi/Unicode.pdf</id><updated>2005-07-27T17:07:37Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">W3C DOM -esittely</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">An introduction to the W3C DOM (in Finnish).</div></summary><link href="https://hsivonen.fi/dom-presentaatio/"></link><id>http://hsivonen.iki.fi/dom-presentaatio/</id><updated>2002-06-28T17:59:02Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Testing HTML5 Parsing</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">I have been using a browser with an HTML5 parser for both my work
275. and leisure browsing for a bit over a week now. I think in-browser
276. HTML5 parsing is now ready to be tested by others as well.</div></summary><link href="https://hsivonen.fi/testing-html5-parsing/"></link><id>http://hsivonen.iki.fi/testing-html5-parsing/</id><updated>1970-01-01T00:00:00Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Help Test HTML5 Parsing in Gecko</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">The HTML5 parsing algorithm is meant to demystify HTML parsing and
277. make it uniform across implementations in a backwards-compatible way.
278. The algorithm has had “in the lab” testing, but so far it hasn’t
279. been tested inside a browser by a large number of people. <em>You</em>
280. can help change that now!</div></summary><link href="https://hsivonen.fi/test-html5-parsing/"></link><id>http://hsivonen.iki.fi/test-html5-parsing/</id><updated>1970-01-01T00:00:00Z</updated></entry><entry><title type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Validator.nu</div></title><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Validation 2.0.</div></summary><link href="https://validator.nu/"></link><id>https://validator.nu/</id><updated>1970-01-01T00:00:00Z</updated></entry></feed>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

1. Download the "valid Atom 1.0" banner.

2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

3. Add this HTML to your page (change the image src attribute if necessary):

   <a href="http://www.feedvalidator.org/check.cgi?url=http%3A//hsivonen.iki.fi/feed/atom/"><img src="valid-atom.png" alt="[Valid Atom 1.0]" title="Validate my Atom 1.0 feed" /></a>

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//hsivonen.iki.fi/feed/atom/

Home · About · News · Docs · Terms