Vad vill Sverigedemokraterna oss?

Efter det tråkiga valresultatet är det frestande att ropa “Hitler kommer!” och raljera över hur dumma medborgarna är, men det är ganska osakligt och tjatigt. Eftersom min underbara fru är nybliven invandrare har jag istället “roat” mig med att läsa Sverigedemokraternas invandringspolitiska program (cache) för att se vad de har att erbjuda oss.

Den härboende personen skall påta sig försörjningsansvar för den anhörige under en femårsperiod och skall dessutom betala en engångssumma, uppgående till ett prisbasbelopp, som ett bidrag till statens utgifter för den anhöriges svenskundervisning och övriga anpassningskostnader.

Jag skulle alltså få betala 42400 kr för min frus uppehållstillstånd, som “ett bidrag” till sfi. I andra sammanhang när vi temporärt belastar samhället – t ex när man skaffar barn eller läser på högskola – så slås den kostnaden ut på den skatt och moms man betalar, varför inte så även här? Det är svårt att se det som något annat än en straffavgift för att jag råkade hitta kärleken utanför Sverige.

Alla uppehållstillstånd som tilldelas nytillkomna utlänningar skall vara tillfälliga. Möjligheten att utfärda permanenta uppehållstillstånd som ett mellansteg mellan temporärt uppehållstillstånd och medborgarskap skall därmed avskaffas. Det tillfälliga uppehållstillståndet gäller för ett år i taget […]

Inget PUT, någonsin. Dessutom så ska vi springa till Migrationsverket en gång om året. Kul! Hur länge ska då detta pågå?

Kraven för att få svenskt medborgarskap skall skärpas kraftigt. Grundläggande krav skall vara att man varit bosatt i landet i minst tio år och att man under denna tid uppvisat en klanderfri vandel.

Tio år! Om några år när vi fått barn så vore det väldigt praktiskt med svenska pass för hela familjen vid utlandsresor, eftersom det ofta är olika visumregler för vietnamesiska och svenska medborgare. SD erbjuder istället mer krångel och spring på ambassader!

Därtill skall man också underteckna en deklaration där man bekräftar sin lojalitet med Sverige och förbinder sig att respektera svenska lagar och övriga samhällsregler.

Att vara lojal mot Sverige är ungefär lika befängt som att vara lojal mot Småland. Det är i bästa fall en löjlig symbolhandling och i värsta fall ett löfte om att alltid sätta Sveriges intressen framför andra länders, alltså motsatsen till internationell solidaritet. Sådant nonsens ska ingen behöva skriva under på.

Den som är svensk medborgare skall inte kunna inneha annat medborgarskap utöver det svenska.

Det här innebär att min fru och mina framtida barn inte kommer att kunna ha vietnamesiska pass och alltså blir tvungna att ansöka om visum när de ska hälsa på mormor och morfar vid Tết (nyår). Det har dock SD löst finurligt genom att förtydliga att vissa nyår är bättre än andra:

Lovdagar i anslutning till religiösa högtider skall endast omfatta traditionella svenska och kristna högtider.

(Förvisso är Tết inte en religiös högtid, men jag betvivlar att det spelar någon roll.)

Sammantaget är det tydligt att ni Sverigedemokrater vill djävlas en hel del med mig och min familj. Ni “tar avstånd från mångkulturalism” och vill inte att min frus kultur “jämställs med, eller värderas högre än,” den svenska. Jag ber er då att dra åt helvete, för vi tänker fortsätta fira okristna högtider och prata olika språk, huller om buller!

När de faktiska politiska programmen är så här patetiska så borde ingen vara orolig för att “ta debatten” med Sverigedemokraterna – citera helt enkelt deras egna åsikter så inser de flesta vilket trams det faktiskt rör sig om.

Sakliga kommentarer välkomnas, andra ej.

SRT research

Discussions in the WHATWG and W3C over several months have led up to the announcement of a new <track> element and the WebSRT format. WebSRT is intended to be mostly compatible with existing SRT content and software, in order to hitch a free ride on the popularity of SRT.

Unfortunately, there was never a proper SRT parsing specification, so all media players implement their own parsers and error handling, much like was the case with HTML before HTML5. If these media players are going to support any of the new features in WebSRT, they will have to do so by modifying existing SRT parsers, as there’s nothing to differentiate SRT and WebSRT. Interoperability would be helped if they were are able to converge towards the same parsing algorithm, but they can only do that if WebSRT handles existing content as good as or better than current algorithms. If we cannot achieve that, it might be better to invent a format that has no legacy compatibility constraints.

There’s been some testing of existing media players, but not much analysis of existing content. I asked OpenSubtitles if they could help out, upon which they very  kindly provided me with the latest 10000 uploaded SRT* files. I wrote a Python script to analyze them, and I think the results are interesting.

First a note on character encoding. Only 666 files were valid UTF-8 and out of those 472 were pure 7-bit ASCII, so deliberate use of UTF-8 doesn’t even reach 2%. Since WebSRT assumes UTF-8, little existing content can be reused as-is.

This is the typical structure of SRT (source):

1
00:00:10,000 --> 00:00:16,000
The Conceited General

2
00:01:08,520 --> 00:01:10,240
The general returns victorious

I’ll use WebSRT terminology: above are 2 cues, each with 3 lines for identifier, timings and the cue text followed by a blank line. Unfortunately, assuming that a blank line separates cues turns out to be unreliable, as 241 files at some point omitted that blank line. In my code, I let a timing line start a new cue even if not preceded by a blank line. I’m not sure what the best general approach is.

The identifier line is mostly useless and has been made optional in WebSRT. I defined any line preceding a timing line as being the identifier. Under this assumption, 571 files had identifiers that didn’t increase by 1 per cue and 55 files had identifiers which weren’t numbers at all. This doesn’t seem to matter to existing players.

The timings are a bit more interesting. No less than 1707 files had overlapping cues. Most existing players handle this by simply showing (only) the next cue when it begins, so such overlap goes unnoticed. However, the WebSRT parser makes no such adjustments, intending that overlapping cues be shown simultaneously. This will quite certainly be a problem if existing content is reused. Also worth noting is that only 4 files consequently used a period (.) to separate seconds and milliseconds, 2 files mixed (apparent typos) and all the rest used only commas (,). Only 1 file used the SubRip X1: … syntax and 38 files had something else trailing the timings. This was mostly trailing punctuation (.,?) or due to a missing newline before the cue text or random typos.

What remains is the cue text itself. Markup, which I defined as anything matching the regular expression ‘<(\w+)>’ or the string ‘<font’, was surprisingly common, occurring in 5525 files. The most common are <i> (5273), <b> (937), <font …> (346) and <u> (71). The WebSRT parser handles italic, bold and ruby markup, ignoring the rest. The fact that markup is so common means that any robust SRT (not just WebSRT) parser must handle it in some way, even if only by ignoring it.

That’s what I could gather from the data I have. If there’s something you want me to check, just leave a comment. Many thanks to OpenSubtitles for providing the data.

*They noted that this regular expression was used to identify SRT files: /^\d\d:\d\d:\d\d[,.]\d\d\d\s*–>\s*\d\d:\d\d:\d\d[,.]\d\d\d\s*(X1:\d+\s+X2:\d+\s+Y1:\d+\s+Y2:\d+)?\s*$/m This means that very broken files won’t have been included.

Ett blocköverskridande hack

Piratpartiet ställer upp i valet och siktar på en vågmästarställning. Som en del i denna strategi tar Piratpartiet inte ställning i några andra frågor än de informationspolitiska och kommer istället att rösta med sina samarbetspartier, vilka det nu blir. Själv hoppas jag verkligen att de lyckas, så att Ask/Bodström inte kan härja fritt i ytterligare en mandatperiod.

Det är populärt att raljera över hur liten skillnaden det är mellan blocken, men likväl så spelar skillnaderna faktiskt roll på valdagen. Om valet blir väldigt jämnt så finns en risk att en del inte vågar rösta på Piratpartiet just för att de står utanför blockpolitiken. Jag själv känner detta dilemma och tror att det finns många som mig på båda sidor blockgränsen. Vore det då inte perfekt om man kunde para ihop tveksamma väljare från båda sidor, så att deras röster tar ut varandra? På så sätt förändras inte vilket block som vinner majoritet, men Piratpartiet får sin vågmästarställning och kan påbörja det hårda arbetet med att vända informationspolitiken på rätt köl.

Hur ska då detta hack fungera? Jag tänker mig en ganska enkel teknisk lösning enligt följande:

  • En webbsida där man får fylla i sin mail-adress och vilket block/parti man stödjer utanför Piratpartiets frågor.
  • Så snart som två väljare från vardera block matchats så skickas ett mail ut till de båda där de presenteras för varandra. De kan sedan välja att utväxla några mail för att stifta bekantskap och försäkra sig om att de är seriösa.

Som en minsta åtgärd mot missbruk kan man se till att samma mail-adress inte registreras flera gånger. Men, ingen teknisk lösning kan i slutändan kontrollera hur man faktiskt röstar på valdagen, så därför är vårt bästa vapen vanlig hederlighet och att folk sätter en gnutta tillit till varandra, för vårt gemensamma bästa.

Tankar?

My father’s wedding speech

As promised, here is the speech my father gave to me and Nga at our wedding, in Swedish, English and Vietnamese. At the wedding, my father spoke in Swedish, while Lan translated into Vietnamese. The English version is a bi-product of the translation process.

Svenska

Nga och Philip – idag är en stor dag – kanske den största i era liv. Det är en ära för oss att få komma hit och att kunna komma hit och delta i denna fantastiska högtid. Jag och Anita är väldigt stolta idag – vi tror det är en stolthet som vi delar med er. Den här dagen kommer ni att minnas för resten av era liv och det är väl ganska naturligt – men vi kan också lova er att nästan varenda svensk också kommer att minnas denna bröllopsdag, för just i detta nu så börjar bröllopet för Sveriges kronprinsessa i Storkyrkan i Stockholm och den största TV-produktionen någonsin pågår just nu med miljoner tittare. När Sveriges blivande drottning valde att gifta sig just idag – ja då måste det vara en bra dag för ett bröllop – måtte hälsa, glädje och tur följa i denna dags spår.

Men jag tänkte börja i en helt annan tid och med helt andra människor.

Det var den 15e oktober 1882 och alltså snart 128 år sedan.

Det var mörkt i den småländska skogen den där höstdagen. Det var 8 grader varmt och regn, en härligt frisk doft av mull och mogna kantareller spreds mellan träden. I det lilla soldattorpet på gården Källeryd i Haurida knastrade det hemtrevligt från elden i järnspisen. Av och an vankade soldaten Sven Lindblad i köket och väntade otåligt på att hans hustru skulle föda. Några timmar senare hördes barnskrik i torpet – en liten gosse hade fötts. Gossens mor hette Inga Sofia Johannesdotter – ja hon hette Inga – det namn i Sverige som är allra mest likt ditt Nga – vi brukar säga till människor som undrar vad du heter att du heter Inga – men utan bokstaven I – och då förstår alla.

Men tillbaka till den lille nyfödde. Han fick namnet David – David Lindblad. Åren gick och David växte upp under mycket knappa förhållanden och när han var något mer än 20 år så träffade han Ester. De blev precis som ni kära i varandra och på luciadagen den 13e december 1906 för 104 år sedan så förlovade de sig och Ester fick en förlovningsring i guld med inskriptionen ”David 13/12 1906”

David och Ester gifte sig och fick 5 döttrar – en av dem var min mamma Kerstin.

När Philip föddes 1984 så var det väl för oss som för alla föräldrar lite olika tankar och förslag om vad du skulle heta – så Philip, du fick också namnet David och du har alltså fått ditt andra namn efter min morfar som jag tyvärr aldrig fick träffa eftersom han dog innan jag själv föddes. Så, Philip och Nga, båda era namn finns alltså sedan tidigt i vår släkt och vi vill att du Nga ska känna att du nu blir en del av vår familj – ännu mera än vad vi hoppas och tror att du redan känt.

Philip, du var väldigt lätt att hantera som liten. Antingen sov du – eller så åt du – nästan fram tills du fyllde 1 år – då öppnade du ögonen och har väl sedan knappast stängt dom. Philip, du hade det nog på ett sätt ganska tufft i dina unga år. Eftersom du alltid var huvudet längre än dina jämnåriga så behandlades du som mycket äldre än du var. De flesta förväntade sig att 4-åringen skulle uppträda lika duktigt som en 6-åring, när du var 6 så kunde du väl läsa, skriva och spela fotboll – det kunde ju de 9-åringar som du var jämnstor med. Philip, du kämpade – du försökte hänga med – du försökte vara duktig och lyckades också med att vara det , ja kanske inte med fotbollen där blev du aldrig särskilt duktig – men du kämpade – du sprang efter bollen – du sparkade efter bollen – men du kom sällan ifatt bollen och sparkarna träffade ganska sällan. Men bortsett från fotbollen, så har du nog lyckats med det mesta du försökt dig på. Det dröjde inte särskilt länge innan jag förstod att du kunde betydligt mer än mig på ganska många områden, din lust till ny kunskap har alltid varit stor – som t.ex. när du plötsligt läste in en kurs i stenografi – inte för att du behövde det eller skulle få nytta av det – utan bara för att du ville veta hur det fungerade. Det är väl just därför du trängt så mycket djupare in bakom datorskärmarna än jag tror någon av oss andra i detta rum och nu arbetar du som ”core programmer” och då vet du ju hur datorns program fungerar, inte ungefär – utan precis. Denna nyfikenhet på hur saker fungerar delar du med din farbror Stig som också vet precis hur saker fungerar – men då mer TV-apparater och bilar, det var många gånger vi åkte hem från Stig med olika gamla trasiga apparater för att du skulle ta hem – skruva isär och se hur de fungerade och var byggda.

Samma nyfikenhet och lust att lära nåt nytt var också det som förde dig samman med Nga. Du bad oss att få ta ett år ”ledigt” från dina universitetsstudier för att åka till Peking och lära dig Mandarin. Det är väl inte det de flesta av oss skulle kalla ”ledigt” men för dig kändes det tydligen så. För att vi skulle släppa iväg dig så ställde Anita och jag 2 villkor ( jag tror inte vi hade kunnat hindra dig hur som helst – och det ville vi ju inte heller) Du hade då ganska politiskt starka åsikter och det första villkoret menade vi väldigt bestämt. När du bor i Peking så FÅR DU INTE kritisera den kinesiska systemet eller samhället – tänk särskilt på att inte göra det på nätet. Det lovade du.

Det andra villkoret som väl inte var så bestämt utan mer en förhoppning att du inte skulle flytta till Kina för alltid. Skaffa inte en kinesisk flickvän.

Jag tror inte det gick mer än ett par veckor efter du åkt till Kina när telefonen ringde och du sa direkt: Jag har hållit båda löftena – ingen kritik mot Kina – och ingen kinesisk flickvän. Men – jag har träffat Nga – hon är inte från Kina – men hon är smart och hon är vacker – och jag är kär. Vi blev givetvis glada för din skull och hoppades vi skulle få möjlighet att träffa denna fantastiska kvinna när vi hälsade på dig i Peking – och det gjorde vi också – men bara på flygplatsen när vårt plan till Stockholm skulle gå – och ditt plan från Hanoi just landat. Vårt första möte blev väldigt märkligt – det var en hög glasvägg mellan oss och vi lyckades bara röra varandras fingertoppar – vi kunde inte prata med varann och kunde bara hälsa med gester. Men sedan dess har vi både fått ha dig som gäst i Sverige och vara din och dina föräldrars gäst här i Hanoi, tack för er varma gästfrihet, och för varje gång vi träffas så förstår vi mer och mer att ni 2 är 1 och vi kan bara hålla med dig Philip – hon är smart och hon är bedårande vacker, bara se på henne – och eftersom du nu kallar oss mamma och pappa (det är inte vad man brukar i Sverige – men förstår att det är er vietnamesiska tradition) så känns det naturligt att välkomna dig som vår ”dotter”.

Som ett bevis och tecken på att du nu inte bara tillhör din vietnamesiska familj utan nu också tillhör och är en del av vår svenska familj och släkt vill jag ge dig denna gåva som jag hoppas du vill bära med dig genom livet. Måtte vi aldrig få några glasväggar mellan oss igen.

Nga öppnar paketet

Detta är alltså den ring som min morfar David gav till sin Ester för 104 år sedan. Vi har låtit göra om den till vad vi tror passar Ngas smak och stil – och tittar du noga inuti så kan du se att det står ”David 13/12 1906”

Ett fyrfaldigt leve för brudparet.

Hurra Hurra Hurra Hurra

English

Nga and Philip – today is a great day – maybe the greatest day of your lives. It is an honor for us to be allowed to come here and be able to participate in this magnificent festivity. My wife Anita and I are very proud today – we believe it is a sense of pride that we share with the two of you. You will definitely remember this day for the rest of your lives and that is rather natural, isn’t it? We can promise you that almost every Swede will also remember this wedding day. At this exact moment the wedding of the Royal Swedish crown princess in the Great Cathedral in Stockholm is beginning, and the largest TV-production ever transmitted is under way with millions of viewers. When the future Swedish Queen chose to get married on this very day – well then it has to be a good day for a wedding – may health, happiness and prosperity follow this day into the future.

But I would like to start this story in a completely different time period, with completely different people.

It was the 15th of October 1882 and 128 years have passed since then.

It was dark in the Swedish forest this autumn day. It was 8 degrees warm and raining, a lovely and fresh smell from mulch and mushrooms spread among the trees. In the tiny little soldier’s cottage on the land of the farm Källeryd in Haurida a fire burnt cosily in the cast iron stove. Every now and again the soldier Sven Lindblad paced around in the kitchen, impatiently waiting for his wife to give birth. A few hours later a screaming child was heard in the cottage – a small baby boy had been born. The name of the newborn’s mother was Inga Sofia Johannesdotter – yes her first name was Inga – the very name in Sweden which most resembles your name, Nga. We explain to people who ask about your name that it is Inga – but without the letter I – and then everybody understands.

But, again back to the little newborn. He was given the name David – David Lindblad. The years went by and David grew up in quite poor circumstances. When he was just over 20 years old he met Ester. They fell in love just like the two of you and on the very day of the St Lucia the 13th of December 1906 (104 years ago) they engaged and Ester was presented with an engagement ring with the inscription ”David 13/12 1906”

David and Ester married and had 5 daughters – one of them was my own mother, Kerstin.

When Philip was born in 1984 Anita and I, like all parents, had some ideas and thoughts about what your name was going to be – so, Philip. You were also given the second name David after my Grandfather, whom I regretfully never got to meet since he died before I was born. So, Philip and Nga, both your names are from early days in our family and we want you Nga to really feel that you are now becoming a part of our family – even more so than we hope and believe you feel already.

Philip, you were very easy to handle as a child. Either you were sleeping – or you were eating – almost until your first birthday – then you opened your eyes and since then I think you have hardly closed them. Philip, you probably had it rather tough in your younger years. You were always head and shoulders taller than everybody your own age. You were often treated as being much older than you were. Most people expected you as a 4-year old to behave just as talented as a 6-year old, and when you were 6 you were expected to read and write, and play football – since all the 9-year olds of your size could. Philip, you struggled – you tried to catch up – you tried to be a good boy and do well and you succeeded too, well maybe not in football you never really became a footballer – but you fought – you ran after the ball – you kicked after the ball – but you rarely caught up with the ball and your kicks rarely hit the ball. Apart from football I think you have succeeded with most things you have tried out. It didn’t take very long before I realized that you knew quite a bit more than myself in many areas, your eagerness to find new knowledge has always been great – for example, when you all of a sudden took on a course to learn shorthand (stenography) – not because you needed it or were to get use of it – but more because you wanted to know how it worked. That lust for knowledge is probably the reason why you have gone deeper behind the computer screens than I would think anybody else in this room and the reason for your current occupation as a Core Programmer and that of course makes you know how a computer program works – not just about – but EXACTLY. This curiosity of how things works you share with your uncle Stig. Stig also knows how things work, exactly – usually more likely to be TV-sets and cars and other electro mechanic things. Many were the times when we left Stig’s place with old broken TVs, toasters and other gadgets because you were taking them home – taking them apart – to see how they worked and how they were built.

The very same curiosity and eagerness to learn something new was also what brought you together with Nga. You asked us to allow you to take a ‘year off’ your university studies to go to Beijing to study Mandarin. That is not what most of us would call a year off but to you it obviously felt so. In order to let you go, Anita and I put up 2 conditions (I don’t think we could have stopped you anyway – and we really didn’t want to either). At the time you had fairly strong political views and the first condition we really meant strongly. When living in Beijing YOU MAY NOT criticize the Chinese system or society – particularly not on the internet. That you promised.

The second condition was really not very conditional at all but more a mere hope that you wouldn’t move to China forever. Don’t get involved with a Chinese girlfriend.

I don’t think that more than a few weeks had passed after you left for China when the telephone rang and you said directly: I have kept both my promises – no criticism against China – and no Chinese girlfriend. But – I have met Nga, she is not from China – but she is smart and she is beautiful – and I am in love. Of course we were happy for you and hoped to get the opportunity to meet this outstanding woman when we visited you in Beijing – and we did too – but only at the airport when our plane was about to leave to Stockholm – and your flight from Hanoi had just arrived. Our first meeting was very strange. There was a high glass wall between us and we just managed to touch one another’s fingertips – we couldn’t talk to one another and we could just greet one another with gestures. Since then we have had the pleasure to have you as our guest in Sweden and been very warmly welcomed as guests of you and your parents here in Hanoi. Thank you for your warm hospitality. Every time we meet we understand more and more that the 2 of you are really 1 and we can do nothing but agree with you Philip – she is smart and she is gorgeously beautiful – just look at her – and since you now call us mama and papa (that is not what you normally would in Sweden – but we understand it’s your Vietnamese tradition) it feels all natural to welcome you as our ”daughter”.

As evidence of, and a sign and indicator that you now not just belong to your Vietnamese family but are also a part of our Swedish family and relatives I want to give you this gift that I hope you will carry with you through your life. May we never get any glass walls between us ever again.

Nga opens the parcel

This is consequently the very ring that my maternal grandfather David presented to his Ester 104 years ago. We have had it remade into what we believe suits Nga’s taste and style – and if you look carefully inside you will still find the inscription ”David 13/12 1906”

A foursome unison cheer for the bridal couple.

Hurray Hurray Hurray Hurray

Tiếng Việt

Nga và Philip, hôm nay là một ngày trọng đại, có lẽ là ngày trọng đại nhất trong cuộc đời của 2 con. Bố mẹ cảm thấy rất vinh dự khi được tới đây và tham dự ngày lễ tuyệt vời này. Anita và bố cảm thấy vô cùng tự hào, muốn chia sẻ sự tự hào này với 2 con. Chắc chắn rằng hai con sẽ nhớ ngày này mãi mãi, và điều đó cũng tự nhiên thôi, phải ko? Chúng ta có thể chắc rằng người Thụy Điển nào cũng sẽ nhớ ngày cưới này. Chính vào thời điểm này Đám cưới của Công chúa Hoàng gia Thụy Điển tại nhà thờ lớn Stockholm đang bắt đầu, và sự kiện này được truyền hình trực tiếp tới hàng triệu người xem. Khi Hoàng hậu tương lai của Thụy Điển chọn làm đám cưới vào ngày này, thì đó phải là một ngày rất đẹp để cử hành hôn lễ. Sức khỏe, hạnh phúc và sự thịnh vượng sẽ mãi ở lại với ngày này.

Tuy nhiên, tôi muốn kể một câu chuyện vào một thời gian hoàn toàn khác. Đó là ngày 15 tháng 10 năm 1882 và 128 năm đã trôi qua kể từ ngày đó.

Đó là một ngày mùa thu ảm đạm, trong một khu rừng ở Thụy Điển. Trời ấm và có mưa, một mùi hương thanh mát bốc lên từ nấm và củi khô và lan qua các cành cây. Trong ngôi lều dã chiến trên đất của nông trường Källeryd ở Haurida, ngọn lửa bập bùng trong lò gang. Người lính Sven Lindblad bồn chồn bước quanh gian bếp chờ vợ anh đang chuyển dạ. Vài giờ sau, tiếng khóc của một cậu bé vang lên trong căn lều nhỏ. Tên của mẹ cậu bé là Inga Sofia Johannesdotter, vâng, tên của bà là Inga, cái tên Thụy Điển gần giống với tên con nhất Nga ạ. Khi ai đó hỏi về tên của con, bố mẹ đều nói đó là Inga, nhưng ko có chữ I ở đầu, và mọi người đều hiểu.

Quay trở lại với cậu bé con mới được sinh ra. Tên cậu là David – David Lindblad. David dần lớn lên trong hoàn cảnh khó khăn, và khi mới hơn 20 tuổi, cậu gặp Ester. Họ yêu nhau cũng như hai con, và vào chính ngày Thánh Lucia, 13 tháng 12 năm 1906 (104) năm trước, họ đính hôn và Ester được người chồng thân yêu trao cho chiếc nhẫn đính hôn với dòng chữ ”David 13/12 1906”

David và Ester cưới nhau và có 5 con gái, một trong số này là mẹ của bố, Kerstin.

Khi Philip sinh ra vào năm 1984, mẹ Anita và bố, như tất cả những ông bố bà mẹ khác, đã cân nhắc rất nhiều khi đặt cho con cái tên Philip. Tên đệm của con David, được đặt theo tên của ông ngoại của bố, người mà bố đã ko dược gặp mặt vì ông đã mất trước khi bố được sinh ra. Vì thế, Philip và Nga, tên của 2 con đều có từ những ngày đầu tiên của gia đình chúng ta, và bố mẹ muốn Nga cũng thực sự cảm thấy mình giờ đây đã là một thành viên của gia đình mình, hơn thế nữa, bố tin là Nga đã cảm thấy như vậy rồi.

Philip, ngay từ hồi nhỏ con đã rất ngoan. Dù đang ăn hay đang ngủ, cho tới khi tròn 1 tuổi, đôi mắt của con luôn mở to mà hiếm khi nhắm lại. Philip, con đã có những năm tháng đầu đời ko mấy dễ dàng. Con luôn cao hơn chúng bạn cả cái đầu. con luôn được mọi người nhìn nhận như một cậu bé già hơn tuổi. khi mới 4 tuổi, Mọi người mong mỏi con phải giỏi như một đứa trẻ 6 tuổi, và khi mới 6 tuổi, mọi người lại mong con đọc, viết và chơi bóng đá giỏi như một cậu bé 9 tuổi rồi. Philip, con đã cố gắng rất nhiều, cố gắng để bắt kịp, cố gắng trở thành một cậu bé ngoan, con đã làm rất tốt, tuy có thể con chơi bóng đá ko được tốt lắm, dù con đã nỗ lực rất nhiều; có lẽ con ko có năng khiếu đá bóng lắm, con cố gắng đuổi theo bóng và sút bóng, nhưng hiếm khi đuổi kịp, và cũng hiếm khi sút trúng đích. Nhưng ngoài việc đó ra, bố nghĩ rằng con đã thành công với phần lớn những việc con làm. Rất nhanh chóng, bố đã nhận ra rằng con biết nhiều hơn bố ở rất nhiều lĩnh vực, con đã rất hăm hở khám phá những điều mới mẻ, ví dụ như con đã theo học một khóa học tốc ký, ko phải vì con cần biết viết tốc ký, mà chỉ để xem người ta viết tốc ký như thế nào.

Sự ham hiểu biết đó có thể là lý do tại sao con học và tìm hiểu sâu hơn về máy tính, có lẽ hơn bất cứ ai trong căn phòng này, và là lý do khiến con muốn làm một nhà lập trình máy tính, sự ham hiểu biết cũng khiến con ko chỉ biết, mà còn hiểu rất chính xác, các chương trình máy tính hoạt động ra sao. Sự tò mò, ham hiểu biết này của con rất giống chú Stig. Stig cũng thích tìm hiểu về nguyên lý hoạt động của máy móc, như TV< ô tô hay những đồ điện tử. Rất nhiều lần khi trở về từ nhà Stig, con mang theo cả đống ti vi, lò nướng hỏng, tháo tung ra và xem chúng hoạt động thế nào.

Sự ham hiểu biết, thích học hỏi này cũng đã mang con tới với Nga. Con đã hỏi bố mẹ về việc nghỉ học một năm ở trường ĐH và sang Bắc Kinh học tiếng Trung. Với phần lớn mọi người, đây ko phải một năm nghỉ ngơi, nhưng với con thì rõ ràng là vậy. bố mẹ đồng ý để con đi, với 2 điều kiện (bố ko nghĩ rằng bố mẹ có thể cản được con, và thực lòng bố mẹ cũng ko muốn vậy). Tại thời điểm đó con có quan điểm chính trị tương đối rõ ràng, và điều kiện đầu tiên mà bố mẹ kiên quyết muốn con làm theo. Đó là khi sống ở BK con không được chỉ trích chế độ chính trị hay XH TQ, đặc biệt là trên internet. Đó là điều con đã hứa với bố mẹ.

Điều kiện thứ hai không phải là bắt buộc, nhưng bố mẹ đã mong rằng con sẽ ko ở lại TQ mãi. Đừng yêu một cô gái Trung Hoa.

Chỉ sau vài tuần khi đến TQ, con đã gọi điện về và tuyên bố: con đã giữ cả 2 lời hứa với bố mẹ, ko chỉ trích TQ, và ko yêu con gái Trung Hoa. Nhưng, con đã gặ Nga, cô ấy không phải người Hoa, nhưng cô ấy rất thông minh và xinh đẹp, và con đang yêu đây. Bố mẹ đã rất vui và hi vọng có cơ hội gặp người con gái tuyệt vời này khi bố mẹ đến thăm con tại BK, và bố mẹ đã có đc cơ hội đó, khi chuyến bay của bố mẹ chuẩn bị cất cánh từ Stockholm thì chuyến bay của con từ Hà nội cũng vừa hạ cánh xuống BK. Cuộc gặp đầu tiên đó thực sự lạ lùng. Có một bức tường vô hình ngăn cách giữa bố mẹ và con, chúng ta chỉ ngại ngùng bắt tay, chưa thể nói chuyện và chỉ chào nhau bằng cử chỉ. Kể từ đó bố mẹ đã có dịp gặp con tại Thụy Điển, và cũng đã tới thăm nhà con tại Hà nội. Cảm ơn con vì những tình cảm nồng ấm của gia đình con. Mỗi khi gặp con, bố mẹ lại hiểu thêm về hai đứa, và bố mẹ phải đồng ý với Philip, rằng Nga thật thông minh và thật đẹp, just look at her, và vì con gọi bố mẹ là bố và mẹ (đây ko phải là truyến thống của Thụy điển, nhưng bố mẹ biết rằng đó là truyền thống của VN), và thật tự nhiên bố mẹ cũng coi con như con gái.

Để chứng tỏ rằng, con giờ đây ko chỉ thuộc về gia đình VN của con, mà còn là một thành viên của gia đình Thụy điển của chúng ta, bố muốn tặng con món quà này, và mong rằng con sẽ giữ nó đến suốt cuộc đời. Sẽ ko còn bức tường trong suốt nào chắn giữa chúng ta nữa.
Đây là chiếc nhẫn là cụ ngoại David đã tặng cho người vợ thân yêu Ester của cụ 104 năm trước. Bố mẹ đã mang đi chỉnh sửa đôi chút để nó hợp với gu và phong cách của con hơn, nhìn kỹ phía trogn chiếc nhẫn, con sẽ thấy dòng chữ ”David 13/12 1906”

Wedding in Hanoi

Last Saturday I and Nga got married here in Hanoi. The temperature was a scorching 42°C, but still 450 guests (8 Swedish) defied the sun and came to share the day with us.

This was the first time I had ever seen Nga wearing make-up, so I was quite worried I might not recognize her. It turned out that I didn’t need to worry at all, doesn’t she look lovely?

The Beautiful Bride

In the meantime, I was struggling to survive in the heat.

The Hot Groom

It was ridiculously hot outside in the sun, but we were able to get a few great pictures despite this.

In the Heat of the Sun

We Look Good Together

Em đẹp lắm!

Our ceremony was neither traditionally Vietnamese nor Swedish, but rather something in between. Unlike in Sweden, the ceremony and dinner is in the same room, with the food already being on the tables before the guests arrive. Somewhat untypically for a Vietnamese wedding, we had a clear theme – purple. The florist did a great job!

Me and Nga's family

Purple Wedding

The ceremony itself consists of three parts: exchange of rings, cutting the cake and pouring the wine.

Exchange of Rings

Cutting of the Cake

Pouring the Wine

At this point one would normally offer the parents on both sides to drink wine, which we eventually did, but first we spliced in a bit of Swedish tradition – my father giving a speech. I hope to be able to post the transcript and Vietnamese translation of that speech later.

My Father Giving a Speech

Once the ceremony on stage was over, we walked to each table to thank the guests for attending, taking plenty of pictures along the way.

Cảm ơn!

For those who have Facebook, more pictures are available in Nga’s wedding album. I leave you with a final picture of the new international family.

One Big Family

VP8 has landed

Today, WebM/VP8 was announced at Google IO. The last month I have been working on adding support for Opera and we have now released labs builds for Windows, Mac and Linux. We have also published an article for web developers who want to start using WebM <video>. Here’s what it looks like, the Sintel trailer on YouTube playing in Opera with WebM <video>. No Flash!

Previously I’ve posted on Opera Core Concerns, but this time I want to share some personal reflections. (In other words: any views expressed are my own, not those of Opera Software.) What follows is the (quite geeky) history of me and the various codecs and organizations I’ve come into contact with over the past 8 years.

Back in gymnasiet I was a compulsive MP3 collector and was very picky about my bitrates. 128 kbps sounded (still sounds) horrible and it pained me, so when I learned about the Vorbis audio codec I was very excited. Not only was it technically superior, it was also completely free. I re-ripped all of my CDs as Vorbis, told all my friends to do the same and started listening to Machinae Supremacy simply because they offered Ogg downloads. I was a fanboy.

In June 2002 On2 released VP3 to the world. It was my summer holidays and I spent most days inside on an extra slow dial-up connection. I clearly remember that upon reading the news I literally bounced out of my chair and threw my hands in the air out of joy. (Remember, I was 17.) The first thing I did when there was code I could compile and run (packaged by Xiph I believe) was to encode and watch Star Trek: First Contact. The example decoder could neither pause or play in fullscreen, so instead I changed my screen resolution and just watched.

At the time I couldn’t do much to help out, but I wanted to be part of this cool community. One of the first pieces of C code I ever wrote was oggsplit, a not-so-useful tool for splitting multiplexed Ogg streams into separate files. I never used it much, but was quite proud to see it in Xiph’s ogg-tools package.

Fast foward. In the summer of 2006 I began working as a summer intern at Opera Software in Linköping, where I wrote an example plugin for video playback on Opera Devices SDK. I picked GStreamer as the backend and by the time I was done I must have watched A New Computer ~1000 times.

In February 2007 Opera proposed <video> and released a proof-of concept Ogg Vorbis+Theora build. I had no part in this, so it came as somewhat of a surprise. Initially thought that they had used my plugin, but that turned out to not be the case – it was libogg, libvorbis and libtheora integrated directly into the browser. The most exciting part was the strong stance for open standards, something that I obviously agree with.

What happened after that is pretty well known: the <video> tag makes obvious sense, so it quickly got implemented in other browsers. When I joined Opera’s core department (part time) in the summer of 2008, <video> hadn’t been touched much for over a year, so I was tasked with bringing it back to life. Loving both audio/video and the web, it would be hard to find a more suitable and fun job. I ended up porting my then 2-year old plugin and thus Opera is now using GStreamer internally. The Codec Wars™ were always a pain, but we did finally release Opera 10.50 with support for Ogg Vorbis+Theora.

After Google announced that they were buying On2 there was lots of speculation that they would release VP8. I have certainly hoped it would happen, but it seemed a bit too good to be true. Therefore, my reaction when it was confirmed was similar to when VP3 was released – bouncing like a 17-year old. That Vorbis is the chosen audio codec for WebM only makes things better. How lucky I am, that this time I get to actually be part of the release event. It’s been immensely fun working on this, in secrecy, then seeing everything happen in a maelstrom of releases, tweets and blog posts today. Håkon is at Google IO running my code on stage, but just a few weeks ago he was in Opera’s Beijing office, watching sunflowers in one of the first Opera VP8 builds:

While not yet 100% bug-free, VP8 in Opera is well on its way and will be in an official release soon. Today is a good day for open video and the open web. Many thanks to everyone who have worked to make this possible. Live long and prosper, WebM!

I’m getting married! 我订婚了!

The 9th of December was Nga’s 25th birthday, so to celebrate we went on a trip to Hong Kong. We stayed at the very fancy Mira Hotel, which was a very pleasant experience. It is a tradition in my family to serve cake in bed on birthdays. Ideally it should be a hand made cake, but this time we had to make do with what the hotel could provide. 宝贝请原谅我,下次我一定亲手给你做蛋糕!

Of course there were also 25 red roses. Actually Nga likes pink roses better, but I thought I’d be a bit traditional.  对不起美女,下次我会买粉色的哦! The writing on the cake is also in traditional Chinese, because it looks better…

I had originally planned to propose while dangling from a hot air balloon with fireworks exploding all across Hong Kong island, or something similarly extreme. However, this was a bit difficult to arrange and wouldn’t really have surprised Nga anyway because I am a bit crazy (ask about her 22nd birthday). Instead, I opted to propose in the hotel room in the morning, guessing that at least she wouldn’t expect that. Having helped Nga eat some cake I hid in the bathroom for a very long time to put on my very special proposal outfit that I had prepared in Sweden.

这么帅! I’d marry me! While Nga was getting ready I prepared the ring, which I had ordered online from the US and picked up at a local FedEx office the day before. So then we sat together in this green chair and I gave a rather long and mostly improvised speech which ended with 我爱你。生日快乐。嫁给我吧! (I love you. Happy birthday. Marry me!) and a ring. I’ve already given away the ending in the title, but it looked a bit like this:

Clearly this is a reinactment as I’m wearing the wrong clothes. Also, Nga should have some tears of joy in her eyes and I should look a lot more nervous. Quite to my surprise, Nga said she had a condition. Asking me to close my eyes she pulled out a ring of her own from the very drawer you see in the picture. Apparently, she was planning to propose herself should I have failed to do so. Apart from being a very pleasant surprise (I said yes) it was also very convenient, because I hadn’t bought a ring for myself (which is otherwise common in Sweden). I don’t have very good pictures of the rings, but I do have a very good picture of us.

The wedding is in Hanoi on the 19th of June 2010.

Microformats vs RDFa vs Microdata

Warning: The microdata syntax has changed (e.g. item="foo" is now itemscope itemtype="foo") since this blog post was written. Don’t copy the examples.

I spent last weekend with my good friend Emil sketching a REST-style interface for his graph database Neo4j. One of the output formats we wanted was plain HTML for easy debugging via the browser. Wanting to enable JavaScript-based enhancements of these pages we needed a way to annotate the data to make it available to scripts. (Use by clients of the REST API should be possible, but unlikely if XML or JSON output is available.)

The three candidates were microformats, microdata and RDFa. We began with plain HTML:

<p>
  I'm Philip Jägenstedt at
  <a href="http://foolip.org/">foolip.org</a>.
</p>

The simple task at hand is to make my name and homepage machine-readable using each of these formats. What follows is a more elaborate version of the reasoning we went through while evaluating the strengths and weaknesses of each alternative.

Microformats

<p class="vcard">
 I'm <span class="fn">Philip Jägenstedt</span> at   <a class="url" href="http://foolip.org/">foolip.org</a>.
</p>

Microformats are “a set of simple, open data formats”, i.e. predefined vocabularies under centralized control. In this example I’ve used the hCard microformat. One “feature” of microformats is that it is valid HTML 4.01/XHTML 1.0, which is why the class attribute is used in novel ways. Although HTML 4.01 mentions that class may be used “for general purpose processing by user agents” it’s normally only used “as a style sheet selector”, i.e. for CSS. What this means is that we are working in a single global namespace which is already polluted with all the CSS class names ever used.

The only thing that distinguishes microformats from random CSS classes is the tree structure. This structure is quite a limitation though, because it means that you have to find or make a common ancestor element to all of the data in a single hCard. For a data interchange format, it all seems insane and simply too brittle. Emil put it rather bluntly when he tweeted:

Microformats. Pile of shite that just increases our systematic technical debt.

Still, I have great respect for some of the people behind microformats and the down-to-earth philosophy. They openly state that microformats aren’t “infinitely extensible and open-ended” or “a panacea for all taxonomies, ontologies, and other such abstractions”. As microformats was never intended to solve our use case it is no surprise that it really doesn’t.

Certainly anyone can use class="foo" to mean anything they like without going through the microformats process – such data formats are cleverly called poshformats (Plain Old Semantic HTML). All things considered though, the whole approach seems outdated and I hope it won’t still be around 5 years from now. Microformats has shown the need for HTML-embedded machine-readable data, now let’s find a better solution.

RDFa

To understand RDFa you first need some understanding of RDF. The RDF model is basically a somewhat roundabout way of describing graphs using subject-predicate-object triples. An example is the best way to illustrate:

RDF graph of me, my name and my homepage

This graph represents me, my name, my homepage and the relationships between them. I’m using the FOAF vocabulary because it already has the concepts of “name” and “homepage”. In N3 syntax this corresponds to these two triples:

@prefix foaf: <http://xmlns.com/foaf/0.1/> .
<#me> <foaf:name> "Philip Jägenstedt" .
<#me> <foaf:homepage> <http://foolip.org> .

Everything in <brackets> is a URI and because URIs tend be long prefixes are used: <foaf:name> actually means <http://xmlns.com/foaf/0.1/name>. I’ve used #me to represent myself, but this should really be resolved to a full URI.

As you can see, the subject is #me in both statements. The relationships in the graph are the predicates, i.e. foaf:name and foaf:homepage. The object is either another URI or a string literal. Adding RDF triples equates to adding more nodes and relationships to the graph. This is general enough that you can model almost anything you want with it.

Back to RDFa. The “a” refers to how attributes in XHTML are used to serialize RDF:

<p xmlns:foaf="http://xmlns.com/foaf/0.1/" about="#me">
 I'm <span property="foaf:name">Philip Jägenstedt</span> at
  <a rel="foaf:homepage" href="http://foolip.org/">foolip.org</a>.
</p>

The use of XML namespaces here is a bit odd. Prefixes in XML are used on element and attribute names, but here it’s only used in the attribute value. These are actually CURIEs, another URL shortening scheme. Jeni Tennison recently wrote an excellent post about the use of prefixes in RDFa which I encourage everyone to read. I also chatted briefly with Henri Sivonen about the problems with xmlns and would recommend reading his mails on those issues.

If we return to RDFa syntax for a bit, notice how property, rel and rev are used for the exact same purpose (setting the predicate) in different contexts. The intention was probably to mimic existing practices such as rel=”next”, but the net result is just more room for confusion. While I won’t claim that it’s just too hard I certainly think it could have been simpler without loosing much expressive power.

RDFa began in the now discontinued XHTML2 WG and seems strongly rooted in the Semantic Web (now Linked Data) community and that stack of technologies and tools. It was later made into a module for XHTML 1.1, but there is no W3C-sanctioned way of embedding RDFa in plain HTML. Getting into HTML5 would guarantee RDFa’s survival in the web ecosystem, so its proponents approached the WHATWG/HTML WG suggesting that RDFa be included. There was much heated discussion, the drama of which was my sole source of entertainment for weeks at a time. I’ll again refer to Jeni’s summary of the clash of priorities and “fruitless discussion”. I particularly want to emphasize this conclusion:

It’s just not going to happen for HTML5

I don’t hate RDF(a). I can certainly see the appeal of the RDF model after taking the time to understand it. It may just be a very verbose way of describing graphs, but as a data interchange format it seems to do a good job. However, being able to express arbitrary RDF in HTML in a compact way is not an actual use case for most web developers. If it’s possible without added complexity that’s fine, but HTML is not a triplestore.

Microdata

As a result of gathering use cases and other input from the big RDFa discussion, suddenly one day HTML5 microdata section sprung into existence along with a very long announcement to the WHATWG list from Ian Hickson (our editor). Within 3 hours there was a demo and not long after another. This is it:

<p item="vcard"> I'm <span itemprop="fn">Philip Jägenstedt</span> at
  <a itemprop="url" href="http://foolip.org/">foolip.org</a>.
</p>

This looks very similar to the microformats example, but the new item and itemprop attributes are used instead of class. The model used is nested groups of name-value pairs, where the name-value pairs are given by the elements with itemprop attributes. In other words, it is quite similar to a DOM tree or a JavaScript object.

There are some predefined item types (used above), but it’s possible to use either URLs (http://foolip.org/footype) or reversed DNS identifiers (org.foolip.footype) to define your own types without any risk of namespace pollution. Note however that there are no prefixes or other URL shortening schemes. I don’t think I’m crazy to suggest that services like bit.ly and tr.im have shown a way out of the “long URL” problem. If microdata gains any traction, I think communities will create vocabularies with clever shorthands like http://link.to/the/past, mr.burns or ht.ml5.

Finally, the subject attribute can be used to avoid the “common ancestor” problem we had with microformats by simply referring to the item element by id:

<p item="vcard" id="me">
   I'm <span itemprop="fn">Philip Jägenstedt</span>.
</p>
<!-- stuff -->
<a itemprop="url" subject="me"   href="http://foolip.org/">foolip.org</a>.

Microdata is quite straightforward and feels much more native to HTML than RDFa. As Jeni explains, microdata can’t express RDF triples using datatypes or XML literals. I’ll also add that using a blank node as object isn’t possible. Other than that, RDF triples can be expressed by using the about type to give the subject of the name-value (predicate-object) pair. Here’s my FOAF example from earlier:

<p item>
  <a itemprop="about" href="#me"></a>
  I'm <span itemprop="http://xmlns.com/foaf/0.1/name">
    Philip Jägenstedt</span> at
  <a itemprop="http://xmlns.com/foaf/0.1/homepage"
    href="http://foolip.org/">foolip.org</a>.
</p>

It is quite ugly, so if there’s any way to make it simpler I’m sure such suggestions are welcome. In general though, it seems like a better idea to use simple microdata structures and map that against a RDF vocabulary if possible. In fact, the spec already defines how to extract some RDF (and JSON) from microdata so I’m sure it’s not difficult to do.

Returning to the “browsable web” (the one I normally work with), microdata has a DOM API that browsers can implement. The prospect of JavaScript having access to the microdata on a page is so exciting that I didn’t want to wait, so I hacked up MicrodataJS to try it out. You can access my name and email in the vcard example as such:

var props = document.getItems("vcard")[0].properties;
var fn = props.namedItem("fn")[0].content;
var url = props.namedItem("url")[0].content;
alert("Name: " + fn + "; URL: " + url);

Unsurprisingly there are some issues with the API which I’ve sent feedback on and expect to be fixed to my satisfaction eventually, but the basic functionality is sound. I imagine scripts making dynamic pie charts from tables, providing page-specific autocomplete suggestions and making shiny animated SVG visualizations of the RDF graphs hidden in the tag soup…

Google is now offering to do usability testing of the microdata syntax to see if it can be improved, so if you have any suggestions be sure to bring those to the WHATWG now.

Summary

The examples I’ve used are overly simplistic and may utterly fail to show the strengths and weaknesses of each syntax. Still, this is my best effort to make sense of the issues at hand and I haven’t intentionally misrepresented any technology or community. I assume that there is much more debate to come before the dust settles on this issue and perhaps I’ll even change my mind after experimenting more with real-world implementation. I leave you with this unambiguous summary of my views:

  • Microformats, you’re a class attribute kludge
  • RDFa, HTML is not your triplestore
  • Microdata, I like you but you need more review

Updates

  • Shelley Powers wrote about RDFa and HTML5’s microdata from the perspective of the RDFa/Semantic Web community. It’s quite a different view from mine, so read that before believing my propaganda.
  • Following James Graham’s suggestion, I have registered mantic.se for fun reverse DNS identifiers like se.mantic.banana. Mostly for fun, don’t take it too seriously…
  • I misunderstood Jeni’s post about expressing RDF in microdata and have fixed that section to be more accurate.

Disclaimer: this post is the result of excess spare time and not part of my work at Opera Software. I know nothing about Opera’s plans (or lack thereof) for microformats, RDFa or microdata.

Det är inte svårt att konkurrera med gratis

Dagens ledare i DN är ett mycket märkligt stycke som inspirerat till viss ilska med nyckelord som katastrofsmörja och dum i huvudet. Jag tar tillfället i akt att skriva om något som ofta stör mig. DN skriver:

Oavsett vad den slutgiltiga domen blir kommer den olagliga fildelningen att fortsätta så länge det inte finns bra lagliga alternativ – och så länge lättillgängliga, men olagliga, servrar finns kvar runt om i världen. Att konkurrera mot gratis nedladdning är inte särskilt lätt.

Den som tror att “gratis nedladdning” via t ex The Pirate Bay är så bra att den inte går att konkurrera med kan inte ha provat på det själv i någon större omfattning. Att försäljningen av CD-skivor sjunker beror inte på att fildelning är oöverträffbart utan på att CD-skivor är ett så föråldrat och klumpigt medium i jämförelse. Fildelning i allmänhet och BitTorrent i synnerhet lider av bland annat följande:

  • Det tar allt för lång tid att hitta det man söker. I naiva tv-reportage brukar reportern göra en sökning på någon bioaktuell film och imponeras av de många resultaten, men att hitta något längre ut på den långa svansen är sannerligen inte lika lätt.
  • Osäker tillgänglighet. Även om man hittat det man söker så finns det inga garantier för att man kommer lyckas ladda ner det inom rimlig tid.

Det finns även punkter där fildelning rent av är sämre (!) än CD-skivor:

  • Förvisso gör nätet det möjligt bredda sitt musiklyssnande och hitta sådant som man aldrig skulle ha hittat i en skivaffär på 90-talet, men fortfarande finns det mycket som går att köpa på CD som man inte hittar på nätet. Klassisk musik är typiskt svårt att fildela, men även många kända popartisters singlar (med b-spår) är svåra att hitta annat än på plastskiva.
  • I regel så är ljudkvaliteten sämre än på en CD-skiva (undantag: FLAC/Log/Cue). Det duger helt enkelt inte för en digital musiksamlare som vill ersätta CD-skivor och inte bara ha något flyktigt MP3-brus i sin iPod.
  • Den mest grundläggande metadata som artist- och låtnamn är ofta felstavad eller inkonsekvent. Komposition, arrangemang och annan information som brukar finnas i CD-häftet finns i stort sett inte i digital form, oavsett källa.

Jag köper fortfarande motvilligt CD-skivor då och då av alla ovanstående orsaker. Det krävs inte mycket fantasi för att se hur man skulle kunna konkurrera med både dessa CD-köp och “gratis” (pengar, inte tid) fildelning. Om någon skulle erbjuda bara en del av nedanstående skulle jag stå på kö med plånboken i högsta hugg.

  • Digitalisera artisters komplett diskografier i ett format som är bättre än CD, inte sämre. 320 kbps MP3 är inte OK, det ska vara arkivkvalitet (t ex FLAC) och varför inte högre samplingsfrekvens/bitdjup än CD?
  • Digitalisera all den metadata som normalt finns i CD-häftet och gör den sökbar. För en musiknörd vore det guld värt att kunna få svar på frågor som “vilka skivor har gitarristen i band X gjort gästspel på?”. Tänk MusicBrainz fast bättre.
  • Gör allt tillgängligt som en riktig webbtjänst där man kan hitta det man söker snabbt med garanterad tillgänglighet.

Kort sagt gäller det att själv erbjuda den mest kompletta samlingen med den högsta kvaliteten på det enklaste sättet. Som av en händelse så är upphovsrättsinnehavaren den enda som skulle kunna erbjuda det idag, då fildelning till sin natur är flyktig och opålitlig. Däremot tror jag inte på något centralarkiv som har allt utan snarare på tusentals webbtjänster och intelligenta sökmotorer för att knyta samman det hela. Det är nya tider nu och det kräver nya tekniska lösningar, men det är faktiskt inte rocket science. “Det går inte konkurrera med gratis” låter mest som en uppgiven suck från en bransch som helst skulle velat stannat kvar på det dåliga 90-talet.

Brand name collision

This morning I discovered that I’ve gotten competition for my personal “brand” foolip. I can’t image why anyone would think that foolip is a good name for any commercial endeavor, but anything is possible on the interwebs. I sure hope this is going nowhere or the googleability of myself could be in jeopardy. As a counter-measure I’ve registered the domains foolip.net and foolip.se, maybe I can do something fun with them…