<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>François Nonnenmacher (EN)</title>
    <icon>http://padawan.info/favicon.png</icon>
    <link rel="alternate" type="text/html" href="http://padawan.info/en/" />
    <link rel="self" type="application/atom+xml" href="http://padawan.info/en/atom.xml" />
    <id>tag:padawan.info,2008-07-23:/en//1</id>
    <updated>2013-01-16T02:21:58Z</updated>
    <subtitle>AKA padawan, founder and webmonkey in chief at Ubiquitic. Web n+1 since 1993.</subtitle>

<entry>
    <title>Steve Jobs</title>
    <link rel="alternate" type="text/html" href="http://padawan.info/en/2011/10/steve-jobs.html" />
    <id>tag:padawan.info,2011:/en//1.4089</id>

    <published>2011-10-08T14:13:01Z</published>
    <updated>2013-01-16T02:21:58Z</updated>

    <summary> &quot;Remembering that I’ll be dead soon is the most important tool I’ve ever encountered to help me make the...</summary>
    <author>
        <name>François Nonnenmacher</name>
        <uri>http://padawan.info/</uri>
    </author>
    
        <category term="Apple" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="apple" label="Apple" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="it" label="IT" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="stevejobs" label="Steve Jobs" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://padawan.info/en/">
        <![CDATA[<p><img alt="Steve Jobs tribute" src="http://padawan.info/fr/images/steve%20jobs.jpg" width="530" height="354" class="mt-image-none" style="" /></p>

<blockquote>"<em>Remembering that I’ll be dead soon is the most important tool I’ve ever encountered to help me make the big choices in life. Because almost everything — all external expectations, all pride, all fear of embarrassment or failure — these things just fall away in the face of death, leaving only what is truly important. Remembering that you are going to die is the best way I know to avoid the trap of thinking you have something to lose. You are already naked. There is no reason not to follow your heart.</em>" - <strong>Steve Jobs</strong></blockquote>

<p>Steve Jobs was stubborn, but less than the statistics on pancreatic cancer. He died at 56, at the pinnacle of an extraordinary and way too short career, after having fought till his last breath.</p>

<p>Through Apple, he marked my professional life more than anybody else in the technology industry. I'm not just an “<a href="http://padawan.info/en/2007/09/apple-fanboy-si.html" hreflang="en">Apple fanboy</a>” since 1985. After I finally could touch and buy a Macintosh in France, I had the chance to know Apple from the inside and share, with extraordinary people, a vision of informatics for humans, for “the rest of us”, that is radically different from the one that was imposed on the business world.</p>

<p>My first contact with Apple predates my love-at-first-sight of the Macintosh. Among our neighbors in Orsay was Giancarlo Zanni, then CEO Apple France. I played with his daughters, my brothers were interns at Apple. At 14 year-old I was hooked by “l'informatique” but I couldn't legally work.</p>

<p>Many years later, in 1997, after a professional reconversion that drove me back to my first technological love affair, I landed an internship at Apple Europe, then got Apple as a client during my first adventure as a freelance. Steve Jobs had just returned to Apple (he was paid by Apple to buy Apple back, as we half joked at the time) and Apple had a product catalog shock-full of 15,000 references. He handsomely turned around a company that was 15 days from bankruptcy, a company the entire IT industry was laughing at. That this industry and many others aren't laughing anymore at Apple now is quite an understatement.</p>

<p>I have had the chance to see Steve Jobs in person on stage at several occasions, in Paris, in Cupertino, in San Francisco; those were even better experiences than seeing him on videos. Some are dismissive of his use of superlatives and his “reality distortion field”, but he really had a larger than life presence and gold in his hands: a vision and the means to make it come true. For one Steve Jobs, how many uncharismatic CEOs are out there bragging about grand ideas that will never see the light because they do not have a fucking clue about what the company they're managing is doing?</p>

<p>Apple's marketing is a wet dream for many marketing folks, who have some difficulty realizing (or admitting) that it's all about good design of good products that sell themselves. The recipe Jobs imposed when he came back in 1997 of not announcing a product before it ships, and especially to only design things that do “just what's needed and just well”, is an absolute departure from the old methods of competitors: empty announcements of vaporware, obese products plagued by plethoric features lists (the strict equivalent of the pissing contest among geeks).</p>

<p>For the past 25 years, all my personal computers have been made by Apple, and I didn't have to depend on IBM or Microsoft. I'm confident this will continue for years to come, considering the recent developments in personal computing and the choices ordinary people make when they're free to chose their own tools. This is the second time Apple has to run without Steve Jobs, definitely this time, but contrary to the Sculley-Amelio era, the company is prepared and stronger than ever.</p>

<p>I've read comments of people who are astonished by the reactions to the death of Steve Jobs. Those public manifestations coming from ordinary people around the world are concrete proofs that he influenced his epoch. Not getting that is just a display of ignorance.</p>

<p>While I am confident on a professional level about what Apple is preparing next, I am personally sad about Steve Jobs' death, sad for his family, and probably a bit nostalgic of a past era, a page that has been turned too suddenly and too soon. I do not ask you to comprehend that, just to respect this sadness.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Your privacy on MOTOBLUR by Motorola</title>
    <link rel="alternate" type="text/html" href="http://padawan.info/en/2011/06/your-privacy-on-motoblur-by-motorola.html" />
    <id>tag:padawan.info,2011:/en//1.4086</id>

    <published>2011-06-21T21:56:04Z</published>
    <updated>2013-05-02T09:02:07Z</updated>

    <summary>After the Nokia Ovi Store carelessness, it&apos;s now Motorola who&apos;s allowing strangers to get access to your private information on...</summary>
    <author>
        <name>François Nonnenmacher</name>
        <uri>http://padawan.info/</uri>
    </author>
    
        <category term="Rants" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="motorola" label="Motorola" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="privacy" label="privacy" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="security" label="security" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://padawan.info/en/">
        <![CDATA[<p>After the <a href="http://padawan.info/en/2011/02/your-privacy-on-nokia-ovi.html">Nokia Ovi Store</a> carelessness, it's now Motorola who's allowing strangers to get access to your private information on their MOTOBLUR portal. Exactly like Nokia, Motorola does not bother to validate the email address you enter on your profile, and sends a welcome message straight to that address:</p>

<blockquote>Bonjour Francois,
Félicitations! Vous avez créé avec succès votre compte MOTOBLURMC! Nous vous écrivons donc pour vous souhaiter la bienvenue dans notre grande famille. Vous êtes maintenant prêt(e) à vous connecter à MOTOBLUR et à profiter d’une vie sociale branchée.</blockquote>
<small><em>(Pardon their French, it's Motorola Canada.)</em></small>

<p>In this case, since it was my own address and it serves as the account ID, I was able to request a password change and access the account:</p>

<p><a href="http://padawan.info/en/assets_c/2011/06/motoblur-132.html" onclick="window.open('http://padawan.info/en/assets_c/2011/06/motoblur-132.html','popup','width=1006,height=776,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://padawan.info/en/assets_c/2011/06/motoblur-thumb-503x388-132.jpg" width="503" height="388" alt="motoblur" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a></p>

<p>An almost complete profile with phone number, phone IMEI, access to contacts, phone location and the ability to wipe the phone remotely!</p>

<p><a href="http://padawan.info/en/assets_c/2011/06/motoblur-wipe-135.html" onclick="window.open('http://padawan.info/en/assets_c/2011/06/motoblur-wipe-135.html','popup','width=710,height=219,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://padawan.info/en/assets_c/2011/06/motoblur-wipe-thumb-503x155-135.jpg" width="503" height="155" alt="motoblur wipe phone" class="mt-image-none" style="" /></a></p>

<p>Since Motorola does not provide any way to delete the account I'm not going to do anything beyond changing the password and opting out from the Motorola marketing spam that's now arriving in my mailbox (thanks Francois!). The poor schmuck might just have made a typo on the email address, and it's Motorola's entire fault to send out the keys to their client's profile without the simple step of verifying it actually belongs to the right person.</p>]]>
        
    </content>
</entry>

<entry>
    <title>How to resume a broken ADC download</title>
    <link rel="alternate" type="text/html" href="http://padawan.info/en/2011/03/how-to-resume-adc-download.html" />
    <id>tag:padawan.info,2011:/en//1.4083</id>

    <published>2011-03-13T02:54:03Z</published>
    <updated>2011-03-23T00:06:16Z</updated>

    <summary>(I&apos;m documenting this trick for myself to remember, but it can be useful for others…) Apple, on its Apple Developer...</summary>
    <author>
        <name>François Nonnenmacher</name>
        <uri>http://padawan.info/</uri>
    </author>
    
        <category term="Apple" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="apple" label="Apple" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://padawan.info/en/">
        <![CDATA[<p><em>(I'm documenting this trick for myself to remember, but it can be useful for others…)</em></p>

<p>Apple, on its <a href="https://developer.apple.com/">Apple Developer Connection</a> site, has a bad habit of not providing small or separate SDK downloads for iOS or Mac OS X development. This means, for example, that I have to download a 4.3GB bundle for Xcode 4 and iOS SDK 4.3 to get one of those. Problem: I'm living on a small island where the local postal-and-telecommunications monopoly is better at finding ways to milk everybody to death rather than providing a fast, stable and affordable internet connection as part of its public service duties, so it's simply impossible to download gigabytes of data without being disconnected at least once. The fact is that I've <em>never</em> been able to download anything on ADC without fail.</p>

<p>Thanks to the Unix roots of Mac OS X, we have <code>curl</code> to the rescue. Here's how to resume a failed download on ADC:</p>

<ol>
	<li>Let's say you have started to download the file <code>xcode_4_and_ios_sdk_4.3__final.dmg</code> but the download has been interrupted. Usually, Safari will happily pretend that the download has completed, but the DMG archive won't load. If you check the file size, it's less than it should be.</li>
	<li>Check the Finder Info for that file and look in the More Info panel where it comes from. There will probably be several URLs (because of redirections), take the first one. For me it's <code>http://adcdownload.apple.com/Developer_Tools/&zwnj;xcode_4_and_ios_sdk_4.3__final/xcode_4_and_ios_sdk_4.3__final.dmg</code></li>
	<li>Connect to ADC to reauthenticate</li>
	<li>In the web inspector on the ADC page, go to Storage then Cookies and note the ADCDownloadAuth cookie and its content. In curl parlance, this will translate into something like: <code>-b "ADCDownloadAuth=&lt;cookie value>;"</code></li>
	<li>And finally, in Terminal — assuming you are in the same path as the download file, get there or give the full path to the <code>-o <em>file</em></code> option — both the <code>-C -</code> and the <code>-o <em>file</em></code> options will tell curl to resume the download exactly where it stopped, and the <code>--retry 100</code> will automatically retry up to 100 times in case it fails again (so it'll work unattended):</li>
</ol>

<p><code>curl -b "ADCDownloadAuth=&lt;cookie value>;" -C - --retry 100 -o xcode_4_and_ios_sdk_4.3__final.dmg http://adcdownload.apple.com/Developer_Tools/&zwnj;xcode_4_and_ios_sdk_4.3__final/xcode_4_and_ios_sdk_4.3__final.dmg</code></p>

<p>Et voilà !</p>

<p>P.S. My CSS overflow rule cuts the long lines above so I've used a zero-width space to force line breaks, but you should get the gist.<br />
P.S. 2: Added the <code>--retry 100</code> option to let curl automatically resume the download in case it fails again.<br />
P.S. 3: Just found <a href="http://atastypixel.com/blog/resuming-adc-downloads-cos-safari-sucks/">this script from Michael Tyson</a> which automates all the manual steps above (won't retry automatically, though it's easy to modify it). Very handy!</p>]]>
        
    </content>
</entry>

<entry>
    <title>WTF is this ‘myEventWatcherDiv’ doing in my web?</title>
    <link rel="alternate" type="text/html" href="http://padawan.info/en/2011/03/wtf-is-this-myeventwatcherdiv-doing-in-my-web.html" />
    <id>tag:padawan.info,2011:/en//1.4082</id>

    <published>2011-03-11T02:39:35Z</published>
    <updated>2013-02-07T15:33:55Z</updated>

    <summary>All of a sudden I started to find the following line in most of the web pages I was browsing,...</summary>
    <author>
        <name>François Nonnenmacher</name>
        <uri>http://padawan.info/</uri>
    </author>
    
        <category term="Web" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://padawan.info/en/">
        <![CDATA[<p>All of a sudden I started to find the following line in most of the web pages I was browsing, including ones I made where I'm sure I didn't place that code:</p>

<p><code>&lt;div id="myEventWatcherDiv" style="display:none;">&lt;/div></code></p>

<p>I googled and binged and yahooed the whole interwebs but couldn't find any explanation. Then I searched my browser plugins directory and found the culprit: <code>wpa.safariextension</code> which is part of the DivX Inc. plugins galore installed with DivX for Mac.</p>

<p>Since these DivX plugins do not bring any value, but on the contrary bring very bad memories from the RealPlayer era of shoddy tactics (“Click here to get a better video experience" my ass!), you can safely trash them and be done with this cruft.</p>

<p>You're welcome.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Your privacy on Nokia Ovi Store</title>
    <link rel="alternate" type="text/html" href="http://padawan.info/en/2011/02/your-privacy-on-nokia-ovi.html" />
    <id>tag:padawan.info,2011:/en//1.4081</id>

    <published>2011-02-25T09:10:13Z</published>
    <updated>2011-02-28T07:24:56Z</updated>

    <summary>My friend Adam Greenfield recently complained about the over-engineering culture at Nokia: I was given an NFC phone, and told...</summary>
    <author>
        <name>François Nonnenmacher</name>
        <uri>http://padawan.info/</uri>
    </author>
    
        <category term="Web" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="design" label="design" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="nokia" label="Nokia" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="privacy" label="privacy" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="security" label="security" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="web" label="web" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://padawan.info/en/">
        <![CDATA[<p>My friend Adam Greenfield recently complained about the <a href="http://speedbird.wordpress.com/2011/02/19/nokia-culture-will-out/">over-engineering culture at Nokia</a>:</p>

<blockquote>I was given an NFC phone, and told to tap it against the item I wanted from the vending machine. This is what happened next: the vending machine teeped, and the phone teeped, and six or seven seconds later a notification popped up on its screen. It was an incoming text message, which had been sent by the vending machine at the moment I tapped my phone against it. I had to respond “Y” to this text to complete the transaction. The experience was clumsy and joyless and not in any conceivable way an improvement over pumping coins into the soda machine just the way I did quarters into Defender at the age of twelve.

<p>It’s not that the NFC-based, phone-to-object interaction didn’t work. Of course it did: it had been <em>engineered</em> perfectly. But what it hadn’t been was <em>designed</em>. Those responsible for imagining the interaction apparently wanted to protect users against the (edge case!) contingency of someone making off with their phones and running up a huge vending-machine tab.<br />
</blockquote></p>

<p>Today, I found out that the Nokia Ovi Store team could actually learn a few things about privacy and security from their engineers.</p>

<p>Yesterday, I received the following email on one of my personal addresses (name changed to protect the guy who used my email address to register):</p>

<p><br />
<blockquote>Date: Thu, 24 Feb 2011 12:18:17 +0000 (UTC)<br />
From: Nokia account <NokiaAccount-no-reply@comms.nokia.com><br />
To: francois_@…<br />
Subject: Welcome to your Nokia account</p>

<p><br />
Hello Francoisxyz, and welcome aboard!</p>

<p>To experience the full suite of Ovi services, all you need to do is visit http://www.ovi.com. Alternatively, if you would like to update your Nokia account details, please visit https://account.nokia.com.</p>

<p>Please verify your email address by clicking the link below:</p>

<p>https://account.nokia.com/acct/verifyEmail?id=_____&lang=en</p>

<p>If clicking the link does not work, copy and paste the URL in a new browser window instead.</p>

<p>Thank you for joining and we hope you enjoy using Nokia services.</p>

<p>All the best,<br />
Your friends at Nokia<br />
http://www.ovi.com</blockquote></p>

<p>Someone had used my email address to register on Ovi. The confirmation email looked quite standard and I ignored it, thinking that the registration wouldn't go through without my confirmation.  (I receive a certain number of similar emails, I guess it's the price to pay for being among the first to grab my first name on popular services.)</p>

<p>Then today, I received this from NokiaMusic-no-reply@nokia.com:</p>

<blockquote>Welcome to Music

<p>Hi Francoisxyz,</p>

<p>Welcome to Ovi, the place to discover and download new music. Make sure you put this email somewhere safe because you'll need it in case you forget your Nokia account username - Francoisxyz. You won't be able to log into Music or any of the other Ovi services without it.</p>

<p>Your music, your way</p>

<p>There are millions of tracks from today's top artists and the legends of yesteryear on Ovi, spanning everything from dance to classical to rock. It's easy to get started - you can search for specific tracks, albums and artists or simply click through the genres, charts and playlists to see what's hot. If you want to know more about exploring music on Ovi, check out our help and troubleshooting page.</p>

<p>We're glad to have you with us.</blockquote></p>

<p>What. The. F…! I immediately requested a password reset, which was nicely delivered to (you guessed it) my email address, and logged in to account.nokia.com to delete this profile. What I discovered at this point is that <strong>the profile was already filled in with the guy's real name, mobile phone number, country of residence, and various other personal information</strong> (I noted he likes being spammed since he authorized Nokia to send him any promotional info by both email and SMS). It took me about 10 seconds to find his Facebook profile and remind him that he should be a bit more careful when (ab)using someone else's email address.</p>

<p>As for Nokia, especially for a platform that <a href="http://www.guardian.co.uk/technology/blog/2009/may/26/nokia-mobilephones">wants to compete with the Apple App Store</a>, <strong>this is appalling</strong>. Anyone who has a vague idea about security and privacy would not design a process where one can complete a registration process with a fake email address or worse, in this case someone else's address with the obvious risk — that I just illustrated — that personal information might be passed to a stranger.</p>

<p>If these examples are typical of the way Nokia designs things nowadays, I'm not betting on the wedding with Microsoft to <a href="http://www.bbc.co.uk/blogs/thereporters/rorycellanjones/2011/02/nokias_burning_platform.html">stop that platform from burning</a>.</p>

<p>Now let's see how long it takes for Nokia, which I'm sure cares about their customers privacy, to fix that security issue in their registration process…</p>

<p>[Update 28 Feb. 2011] I'm not sure whether the Nokia folks really understand the problem. Case in point, <a href="https://twitter.com/nokiahelps/status/42113334908166144">this tweet from @NokiaHelps</a>:</p>

<blockquote>@ubiquitic Account registration is verified either by email or tel. no. depending on selection during account registration. ^JR</blockquote>

<p>I've proved above that <strong>Nokia does <em>NOT</em> verify the email address</strong>, no matter what they say. And verification by phone number does not alleviate the problem if, when the registrant has entered someone else's email address by mistake, the later receives the acknowledgment emails I have received and which allowed me to gain access to — <em>and delete</em> — an account that didn't belong to me.</p>

<p>Let me summarize the problem for short attention-span marketing/support folks:</p>

<p><strong>If someone enters a wrong email address in their Nokia profile, anyone receiving the “confirmation” emails from Nokia will be able to highjack the account.</strong></p>

<p>Is that clearer ?</p>]]>
        
    </content>
</entry>

<entry>
    <title>Internal inconsistency</title>
    <link rel="alternate" type="text/html" href="http://padawan.info/en/2011/02/nsinternaliconsistencyexception.html" />
    <id>tag:padawan.info,2011:/en//1.4079</id>

    <published>2011-02-03T02:22:32Z</published>
    <updated>2011-02-03T02:28:39Z</updated>

    <summary>Seen a minute ago from the Mac App Store, while updating an application: What the heck, Apple? If you are...</summary>
    <author>
        <name>François Nonnenmacher</name>
        <uri>http://padawan.info/</uri>
    </author>
    
        <category term="Apple" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="apple" label="Apple" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="wtf" label="WTF" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://padawan.info/en/">
        <![CDATA[<p>Seen a minute ago from the Mac App Store, while updating an application:</p>

<p><img alt="NSInternalIconsistencyException" src="http://padawan.info/en/images/NSInternalIconsistencyException.jpg" width="500" height="238" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></p>

<p>What the heck, Apple? If you are trying to confuse your users with modal dialogs written by robots à la Microsoft, then yes I do see one internal inconsistency here.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Melody 1.0 Beta 1 is here</title>
    <link rel="alternate" type="text/html" href="http://padawan.info/en/2010/11/melody-10-beta-1-is-here.html" />
    <id>tag:padawan.info,2010:/en//1.4074</id>

    <published>2010-11-02T22:51:31Z</published>
    <updated>2010-11-02T22:52:37Z</updated>

    <summary>The Open Melody Software Group has just released Melody 1.0 for beta testing. If you are using MTOS 4, and/or...</summary>
    <author>
        <name>François Nonnenmacher</name>
        <uri>http://padawan.info/</uri>
    </author>
    
        <category term="Web" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="melody" label="Melody" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="movabletype" label="Movable Type" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://padawan.info/en/">
        <![CDATA[<p>The Open Melody Software Group has just released <a href="http://openmelody.org/blog/2010/11/melody-10-beta-1-is-here">Melody 1.0 for beta testing</a>.</p>

<p>If you are using <abbr title="Movable Type Open Source">MTOS</abbr> 4, and/or MTOS/<abbr title="Movable Type">MT</abbr> 5 do not suit your needs, you should keep an eye on Melody.</p>]]>
        
    </content>
</entry>

<entry>
    <title>101010</title>
    <link rel="alternate" type="text/html" href="http://padawan.info/en/2010/10/101010.html" />
    <id>tag:padawan.info,2010:/en//1.4072</id>

    <published>2010-10-10T19:53:34Z</published>
    <updated>2010-10-11T07:42:11Z</updated>

    <summary>42. (Yes, I know, it&apos;s the geek inside me who forced me.) P.S. And Ubuntu managed to release 10.10 on...</summary>
    <author>
        <name>François Nonnenmacher</name>
        <uri>http://padawan.info/</uri>
    </author>
    
        <category term="Humor" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://padawan.info/en/">
        <![CDATA[<p>42.</p>

<p>(Yes, I know, it's the geek inside me who forced me.)</p>

<p>P.S. And Ubuntu managed to <a href="https://lists.ubuntu.com/archives/ubuntu-announce/2010-October/000139.html">release 10.10 on 10.10.10</a>. No small feat, and with the obligatory compliment to Douglas Adams.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Why Movable Type?</title>
    <link rel="alternate" type="text/html" href="http://padawan.info/en/2010/09/why-movable-type.html" />
    <id>tag:padawan.info,2010:/en//1.4070</id>

    <published>2010-09-30T02:54:53Z</published>
    <updated>2010-09-30T02:59:00Z</updated>

    <summary>On my professional blog I have started a series of articles to explain why Movable Type is an excellent choice...</summary>
    <author>
        <name>François Nonnenmacher</name>
        <uri>http://padawan.info/</uri>
    </author>
    
        <category term="Web" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="cms" label="CMS" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="movabletype" label="Movable Type" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://padawan.info/en/">
        <![CDATA[<p>On my professional blog I have started a series of articles to explain <a href="http://ubiquitic.com/blog/2010/09/why-movable-type.html">why Movable Type is an excellent choice</a> as both a CMS and a blog engine.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Google AdSense pearl</title>
    <link rel="alternate" type="text/html" href="http://padawan.info/en/2010/09/google-adsense-pearl.html" />
    <id>tag:padawan.info,2010:/en//1.4069</id>

    <published>2010-09-30T02:38:28Z</published>
    <updated>2010-09-30T02:42:44Z</updated>

    <summary>The joy of Google AdSense: (As seen on the Angry Drunk feed, no permalink alas.)...</summary>
    <author>
        <name>François Nonnenmacher</name>
        <uri>http://padawan.info/</uri>
    </author>
    
        <category term="Humor" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="google" label="Google" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://padawan.info/en/">
        <![CDATA[<p>The joy of Google AdSense:</p>

<p><img alt="palin-shit.png" src="http://padawan.info/en/images/palin-shit.png" width="480" height="285" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></p>

<p>(As seen on the <a href="http://www.theangrydrunk.com/">Angry Drunk</a> feed, no permalink alas.)</p>]]>
        
    </content>
</entry>

<entry>
    <title>On Apple Safari&apos;s use of justified text in Reader</title>
    <link rel="alternate" type="text/html" href="http://padawan.info/en/2010/06/on-apple-safaris-use-of-justified-text-in-reader.html" />
    <id>tag:padawan.info,2010:/en//1.4052</id>

    <published>2010-06-10T05:44:00Z</published>
    <updated>2010-06-10T05:47:23Z</updated>

    <summary>On my professional blog, a take on Apple Safari&apos;s use of justified text in Reader....</summary>
    <author>
        <name>François Nonnenmacher</name>
        <uri>http://padawan.info/</uri>
    </author>
    
        <category term="Apple" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="apple" label="Apple" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="typography" label="typography" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://padawan.info/en/">
        <![CDATA[<p>On my professional blog, a take <a href="http://ubiquitic.com/blog/2010/06/on-justified-text-in-reader.html">on Apple Safari's use of justified text in Reader</a>.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Curated computing</title>
    <link rel="alternate" type="text/html" href="http://padawan.info/en/2010/05/curated-computing.html" />
    <id>tag:padawan.info,2010:/en//1.4048</id>

    <published>2010-05-20T06:49:24Z</published>
    <updated>2010-05-20T07:49:34Z</updated>

    <summary>Perhaps the most pernicious proposition of the “everything must be open” crusade is the notion that curation is bad and...</summary>
    <author>
        <name>François Nonnenmacher</name>
        <uri>http://padawan.info/</uri>
    </author>
    
        <category term="Apple" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="apple" label="Apple" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="google" label="Google" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="internet" label="internet" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://padawan.info/en/">
        <![CDATA[<blockquote>Perhaps the most pernicious proposition of the “everything must be open” crusade is the notion that curation is bad and anti-freedom. Soldiers of this crusade confuse freedom with competition. Our museums are not football-field sized warehouses where art objects are indiscriminately dumped and our magazines and blogs are not amorphous containers of randomly selected articles. Our classrooms, restaurants, hospitals and indeed all our civilized institutions are firmly reliant on curation of one kind or another. The goal should be for curators to compete, not for curation to be declared illegal and unholy by the “open” zealots.</blockquote>

<p><a href="http://counternotions.com/2010/05/17/curation/">Curated hypocrisy: How Google camouflages its attacks on Apple</a>. A must read.</p>

<p>By the way, <a href="http://www.tbray.org/ongoing/">Tim</a>, what is it when Google, at will and without any explanation, <a href="http://cabinet-arpej.eu/dotclear/index.php/post/2010/04/14/la-technique-le-cambouis-et-google" hreflang="fr">removes the ranking of a web site</a> and, effectively, removes it from search results, if not curation of the web? Google is itself the biggest curating goggles through which a <em>truly huge amount</em> of people see the web.</p>

<p>The problem isn't with Google curating the web (and a big chunk of the online advertisement business). Actually the point is, precisely, that the relevance in search results is a direct product of curation. And to paraphrase Steve Jobs, if Google enjoys up to 90% market dominance in certain countries, it must be doing something right. Right?</p>

<p>The hypocrisy lies in refuting Apple the right to curate its own ecosystem, which by the way isn't anything as public as the web is.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Death by Apple, the obsolescence of Flash</title>
    <link rel="alternate" type="text/html" href="http://padawan.info/en/2010/04/death-by-apple-the-obsolescence-of-flash.html" />
    <id>tag:padawan.info,2010:/en//1.4045</id>

    <published>2010-04-29T21:30:40Z</published>
    <updated>2010-04-29T21:58:22Z</updated>

    <summary>Flash was created during the PC era – for PCs and mice. Flash is a successful business for Adobe, and...</summary>
    <author>
        <name>François Nonnenmacher</name>
        <uri>http://padawan.info/</uri>
    </author>
    
        <category term="Web" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="adobe" label="Adobe" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="apple" label="Apple" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="flash" label="Flash" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="web" label="web" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="webstandards" label="web standards" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://padawan.info/en/">
        <![CDATA[<blockquote>Flash was created during the PC era – for PCs and mice. Flash is a successful business for Adobe, and we can understand why they want to push it beyond PCs. But the mobile era is about low power devices, touch interfaces and open web standards – all areas where Flash falls short.

<p>The avalanche of media outlets offering their content for Apple’s mobile devices demonstrates that Flash is no longer necessary to watch video or consume any kind of web content. And the 200,000 apps on Apple’s App Store proves that Flash isn’t necessary for tens of thousands of developers to create graphically rich applications, including games.</p>

<p>New open standards created in the mobile era, such as HTML5, will win on mobile devices (and PCs too). Perhaps Adobe should focus more on creating great HTML5 tools for the future, and less on criticizing Apple for leaving the past behind.</blockquote></p>

<p>Steve Jobs, <a href="http://www.apple.com/hotnews/thoughts-on-flash/">Thoughts on Flash</a>.</p>

<p>Compare to the <a href="http://daringfireball.net/linked/2010/04/29/wsj-narayen">"weak sauce" from Adobe's CEO</a>.</p>

<p>I believe that Flash will indeed become obsolete, and not just on mobile devices. I like <a href="http://kottke.org/10/04/steve-jobs-thoughts-on-flash">Jason Kottke's thoughts</a> on the matter:</p>

<blockquote>Jobs sort of circles around the main issue which is, from my own perspective as heavy web user and web developer: though Flash may have been necessary in the past to provide functionality in the browser that wasn't possible using JS, HTML, and CSS, that is no longer the case. Those open web technologies have matured (or will in the near future) and can do most or even all of what is possible with Flash. For 95% of all cases, Flash is, or will soon be, obsolete because there is a better way to do it that's more accessible, more open, and more "web-like".</blockquote>]]>
        
    </content>
</entry>

<entry>
    <title>Ogg (and Mozilla) objections</title>
    <link rel="alternate" type="text/html" href="http://padawan.info/en/2010/04/ogg-and-mozilla-objections.html" />
    <id>tag:padawan.info,2010:/en//1.4039</id>

    <published>2010-04-01T03:08:34Z</published>
    <updated>2010-04-01T04:41:49Z</updated>

    <summary>Ogg objections by Måns: When challenged, three types of reaction are characteristic of the Ogg campaigners. On occasion, these people...</summary>
    <author>
        <name>François Nonnenmacher</name>
        <uri>http://padawan.info/</uri>
    </author>
    
        <category term="Web" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="codec" label="codec" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="flash" label="Flash" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="mozilla" label="Mozilla" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="ogg" label="Ogg" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="softwarepatents" label="software patents" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="video" label="video" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="web" label="web" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://padawan.info/en/">
        <![CDATA[<p><a href="http://ffmpeg.org/~mru/hardwarebug.org/2010/03/03/ogg-objections/">Ogg objections</a> by Måns:</p>

<blockquote>When challenged, three types of reaction are characteristic of the Ogg campaigners.

<p>On occasion, these people will assume an apologetic tone, explaining how Ogg was only ever designed for simple audio-only streams (ignoring it is as bad for these as for anything), and this is no doubt true. Why then, I ask again, do they continue to tout Ogg as the one-size-fits-all solution they already admitted it is not?</p>

<p>More commonly, the Ogg proponents will respond with hand-waving arguments best summarised as Ogg isn’t bad, it’s just different. My reply to this assertion is twofold:</p>

<ul><li>Being too different is bad. We live in a world where multimedia files come in many varieties, and a decent media player will need to handle the majority of them. Fortunately, most multimedia file formats share some basic traits, and they can easily be processed in the same general framework, the specifics being taken care of at the input stage. A format deviating too far from the standard model becomes problematic.</li><li>Ogg is bad. When every angle of examination reveals serious flaws, bad is the only fitting description.</li></ul>

<p>The third reaction bypasses all technical analysis: Ogg is patent-free, a claim I am not qualified to directly discuss. Assuming it is true, it still does not alter the fact that Ogg is a bad format. <em>Being free from patents does not magically make Ogg a good choice as file format</em>. If all the standard formats are indeed covered by patents, the only proper solution is to design a new, good format which is not, this time hopefully avoiding the old mistakes.</blockquote></p>

<p>While I do understand, in principle, why Mozilla wants to promote open and free video codecs on the web, its sole reliance on Ogg Theora <em>and</em> its blocade of the most popular H.264 commercial codec even through a plugin (although it allows one like Flash, go figure), make it look fanatical and not the least pragmatical.</p>

<p>As a citizen, I'm totally against software patents. They're an intellectual abomination and  a net burden on society. I do hope Europe will continue to forbid software patents. As a web developer, I'm all for open and free video codecs, <em>provided they are efficient throughout the whole producer-to-consumer chain</em>. I understand and support Mozilla's goals for an open web, but I find that their tactic around the &lt;video> tag is bad and potentially counter-productive.</p>

<p>Good luck to whoever is capable of developing a better (or at least comparable) open and free codec than H.264, but it clearly does not exist yet. Meanwhile, most web videos will continue to be encoded and served using H.264, and the same through Flash for the poor souls browsing with Firefox.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Paris Web 2010 — Call for speakers</title>
    <link rel="alternate" type="text/html" href="http://padawan.info/en/2010/03/paris-web-2010-call-for-speakers.html" />
    <id>tag:padawan.info,2010:/en//1.4035</id>

    <published>2010-03-25T10:24:14Z</published>
    <updated>2010-03-30T22:17:33Z</updated>

    <summary>(Disclaimer: I manage the communication for Paris Web, this is a copy of the official call for speakers.) Hello all,...</summary>
    <author>
        <name>François Nonnenmacher</name>
        <uri>http://padawan.info/</uri>
    </author>
    
        <category term="Web" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="parisweb" label="Paris Web" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="parisweb10" label="parisweb10" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://padawan.info/en/">
        <![CDATA[<p><em>(Disclaimer: I manage the communication for <a href="http://www.paris-web.fr/">Paris Web</a>, this is a copy of the official call for speakers.)</em></p>

<p><img src="http://farm3.static.flickr.com/2583/3997772955_84e87f08a6.jpg" alt="Paris Web 2009 : Day 1 by ~Thanh." title="" width="500" height="333"></p>

<p>Hello all,</p>

<p><a href="http://www.paris-web.fr/">Paris Web</a> is a French conference organised each year and revolving around questions of web accessibility, quality and design. For its fifth edition, the conference wants to broaden its subject base and suggests that you think of this question:&#8220;Improve the user experience through appropriate design and contents&#8221; (non-limiting question).</p>

<p><strong>Paris Web 2010 will take place on the 14-16th of October 2010</strong>, and we invite all the potential speakers to speak out and get in touch with us at <a href="mailto:propositions@paris-web.fr">propositions@paris-web.fr</a>.</p>

<p>You can submit one or more topics under the following formats:<br />
<ol><li>Conference:&nbsp; 50 minutes, Q&amp;A included</li><li>Mini-conference: 15 minutes, without Q&amp;A</li><li>Workshop: 1 hour 30 (or 3 hours for a double-length workshop)</li></ol></p>

<p>Conferences and mini-conferences will take place in amphitheaters on Thursday and Friday. Workshops will take place in 40 to 60 people rooms on Saturday. They are a moment of intense interactivity, and can be either theoretical or practical (rooms with computers will be provided if necessary).</p>

<p><strong>The deadline for proposals is set to the 31st of May 2010.</strong></p>

<p>Ideally, here is the form your proposal should have:<br />
<ol><li><strong>You, in a few lines</strong><br />Who are you? What is your experience? Your specialty?</li><li><strong>Your subject</strong><br />In up to ten lines, a title (doesn't need to be the definitive choice)<br />
and a summary of what you wish to deal with. Please indicate the<br />
estimated level of the audience.</li><li><strong>The form of your intervention</strong><br />According to you, will this be better suited for a conference, a<br />
mini-conference, or a workshop? (We can talk about it.)</li></ol></p>

<p>People who have submitted a subject will be notified personally, whether their subject is selected or not.</p>

<p>If you are selected, you will be able to have your travel expenses and hotel paid. Please bear in mind that videos will be recorded and will be made available for free on the internet (under the CC-By-NC licence).</p>

<p>We can't wait for October!</p>

<p><img src="http://farm4.static.flickr.com/3216/3036532672_0e94a8e9f8.jpg" alt="DSC_1229 by lejoe." title="" width="500" height="334"></p>

<p><em>If you want to have a look at what it's like, there are close to 1,600 <a href="http://www.flickr.com/search/?q=parisweb&l=cc&ss=2&ct=6&mt=photos&w=all&adv=1">pictures of past Paris Web events</a> on Flick.</em></p>]]>
        
    </content>
</entry>

</feed>
