<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Baldur Bjarnason on Medium]]></title>
        <description><![CDATA[Stories by Baldur Bjarnason on Medium]]></description>
        <link>https://medium.com/@fakebaldur?source=rss-ec8c474ec577------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*uIDJ-Hx04C32eFgs.png</url>
            <title>Stories by Baldur Bjarnason on Medium</title>
            <link>https://medium.com/@fakebaldur?source=rss-ec8c474ec577------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 06:25:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fakebaldur/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Colophon Cards User Survey]]></title>
            <link>https://medium.com/@fakebaldur/the-colophon-cards-user-survey-e3f6d8d22e8a?source=rss-ec8c474ec577------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3f6d8d22e8a</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Baldur Bjarnason]]></dc:creator>
            <pubDate>Wed, 02 Feb 2022 12:56:06 GMT</pubDate>
            <atom:updated>2022-02-03T15:46:37.303Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9bvlePsYrWaa5kJT.jpg" /></figure><p>I need your help to create a user-friendly web app for note-taking!</p><p>Notes, notebooks, stickies-physical or digital-have become a big part of our professional and personal lives.</p><p>Whether we’re using Apple’s built-in Notes app, a physical notebook or deck of index cards, or something more involved like Notion or Roam, most of us have tools that we use to make notes-ephemeral or permanent-to help us organise our lives.</p><p>I’m <a href="https://www.baldurbjarnason.com/">Baldur Bjarnason</a>. I’ve been working in web development, digital publishing, and digital reading for over twenty years. I’m working on a prototype for a note-taking web app called Colophon Cards.</p><p>(You can follow my progress on the project over at the <a href="https://www.colophon.cards/">Colophon Cards</a> website.)</p><p>My Colophon Cards project is an effort to build a note-taking tool that stakes out the otherwise sparsely populated middle ground in the Personal Knowledge Management (PKM) space:</p><ul><li>As straightforward to use as is sensible</li><li>A bit more visually oriented than the high-end apps</li><li>Have the hypertextual or organisational features from the high-end that don’t make the app too complicated to use</li><li>Have at least basic support for our digital reading needs</li></ul><p>To accomplish this, I need your help!</p><p>I need to know what <em>you</em> are doing-how <em>you</em> take notes.</p><p>Ideally, I would also need to know how some of my in-progress ideas and designs work for you.</p><p>The first step towards this is a short survey you can take to help me see the lay of the note-taking land. It should only take you about five minutes to finish. More importantly, it ends with a question where you can volunteer to be a tester for the project.</p><p>Which I would find very helpful 🙂.</p><p>Feel free to share a link to this post or the survey with anybody you think might be interested in this space.</p><p><a href="https://bit.ly/3AXOXhL">Colophon Cards: Note-taking User Research</a></p><p><em>The Colophon Cards prototype project is funded by The Icelandic Centre for Research’s Technology Development Fund</em></p><p><em>Originally published at </em><a href="https://www.baldurbjarnason.com/2022/colophon-cards-user-survey/"><em>https://www.baldurbjarnason.com</em></a><em> on February 2, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3f6d8d22e8a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Notes on debating for the web development community]]></title>
            <link>https://medium.com/@fakebaldur/notes-on-debating-for-the-web-development-community-fcaccdc27dcc?source=rss-ec8c474ec577------2</link>
            <guid isPermaLink="false">https://medium.com/p/fcaccdc27dcc</guid>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Baldur Bjarnason]]></dc:creator>
            <pubDate>Mon, 17 Oct 2016 00:00:00 GMT</pubDate>
            <atom:updated>2016-10-17T12:54:38.980Z</atom:updated>
            <content:encoded><![CDATA[<p>Don’t. Just don’t debate. Especially if the issue is an important one.</p><p>It took me decades to figure this out, despite clear evidence from several fields (like psychology), and being backed by substantial research. I’ve always been an argumentative bastard, but arguing and debating people just doesn’t change their minds. It does the opposite: the exercise of having to come up with explanations and rationalisations for their point of view makes their conviction in their point of view stronger.</p><p>Debating people lowers the odds of them changing their minds and directly undermines your own position. The best thing to do — I’m I’m still trying to get into the habit of doing this properly — is to:</p><ul><li>Simply state your position in a manner that does not force others to defend theirs. People are social beings so — all else being equal — the fact that others hold an opinion makes them more open to considering it.</li><li>You <em>can</em> outline reasons why you hold your opinion as long as you don’t use your reasons as a weapon to club others into your position. “I believe in X because of Y and Z, and those matter to me.”</li><li><em>Do</em> present information and facts without forcing people into a particular interpretation of what those facts mean <em>to them</em>. “I found this helpful in making up my own mind.”</li></ul><p>Unless you <em>want</em> to undermine your own position and force others to strengthen their resolve:</p><ul><li><em>Do not</em> call people out by name or affiliation for having a position. Doing so indirectly is often just as bad as doing so directly to their face.</li><li><em>Do not</em> exaggerate their opinion. Instead of forcing them to reconsider, exaggerating their beliefs only increases the odds of them <em>adopting</em> that exaggerated position.</li><li><em>Do not</em> demonise their position as that forces people to either deliberately avoid you or vociferously defend themselves by attacking back.</li></ul><p>I managed to reach middle age without learning this lesson and it’s a lesson I’m still struggling to heed. My tendency to argue and debate has done nothing but undermine the positions that I hold and the values that matter to me.</p><p>My advice to the web developer and javascript communities: don’t make the same mistake I’ve kept making for decades. Debate doesn’t change minds. Exchanging information and explaining your context — empathy — is the only thing that works.</p><p><em>Originally published at </em><a href="https://www.baldurbjarnason.com/notes/debating-web-development/"><em>www.baldurbjarnason.com</em></a><em> on October 17, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fcaccdc27dcc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A thought to consider]]></title>
            <link>https://medium.com/@fakebaldur/a-thought-to-consider-a7128846871?source=rss-ec8c474ec577------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7128846871</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[publishing]]></category>
            <dc:creator><![CDATA[Baldur Bjarnason]]></dc:creator>
            <pubDate>Mon, 23 May 2016 15:41:18 GMT</pubDate>
            <atom:updated>2016-05-23T15:53:45.737Z</atom:updated>
            <content:encoded><![CDATA[<p>What if the market for the services offered by publishers and agents is an <a href="https://en.wikipedia.org/wiki/The_Market_for_Lemons">Akerlof-style market for lemons</a>?</p><p>As in, the information necessary for the author to judge the value of the services offered (i.e. honesty, dishonesty, median title performance, editorial resources, design resources) is only available to those already in the publishing industry network or to those with the financial resources to buy that information (such as hiring a specialised lawyer).</p><p>If your average new author doesn’t have access to the resources necessary to tell an honest publisher or agent from a dishonest one (just to name one information asymmetry) without personal recommendation, if the market for the service offered by publishers is indeed a market for lemons, then the perceived economic value of those services to authors outside of the publishing industry network will trend towards zero.</p><p>(Those inside the network can get trustworthy personal recommendations and so will be able to assess the true economic value of each offer.)</p><p>If this dynamic applies, then the situation would be even more stark for minority authors because they can’t rely on the recommendations of their non-minority network contacts.</p><p>This dynamic would have been sort of sustainable when authors had no alternatives except to either deal with the market for lemons (i.e. be overcharged for publishing services) or leave their chosen profession. That is no longer the case.</p><p>(<em>Aside:</em> You could view self-publishing services as alternate markets that have decreased the information asymmetry of buying publishing services by unbundling them and forcing them to use fixed prices, and have decreased the risk of purchasing those services by preventing publishers from claiming any rights. These markets can be unfair in other ways, of course. They just manage to avoid this particular dynamic.)</p><p>If the market for publishing services is a market for lemons, that would mean that it is structurally impossible for the industry to diversify its author base economically, geographically, or in terms of minorities and class.</p><p>Reforming a market for lemons is generally impossible without regulation since well-meaning sellers (i.e. individual publishers) are usually driven out by the less than well-meaning. And, yes, how fair your standard contract is plays a big part in whether you’d be considered well-meaning or not as far as the economics of the market are concerned.</p><p>New publishers who don’t have a pre-existing stable of proven authors—authors who are already in the network and who don’t suffer from the information asymmetry—would have to compete by lowering their prices directly or indirectly: shorter contract terms, higher royalties, more personal (and more costly) services. Over time, their lower margins would reduce the sustainability of smaller publishers and they’d be driven out of the market.</p><p>Ergo, if this applies, the perceived economic value of the services offered by publishers and agents will trend towards zero for authors who don’t have pre-existing connections in the publishing industry and for authors who are members of one or more minority.</p><p>Insiders (rich, well-educated white people) will opt for signing up with a publisher.</p><p>Outsiders and minorities will switch wholesale to self-publishing and similar markets.</p><p>Just a thought.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7128846871" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Link compilation, final thoughts, and compromises]]></title>
            <link>https://medium.com/@fakebaldur/link-compilation-final-thoughts-and-compromises-c561630f4691?source=rss-ec8c474ec577------2</link>
            <guid isPermaLink="false">https://medium.com/p/c561630f4691</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[web-standards]]></category>
            <dc:creator><![CDATA[Baldur Bjarnason]]></dc:creator>
            <pubDate>Wed, 18 May 2016 22:54:46 GMT</pubDate>
            <atom:updated>2016-05-18T23:03:06.507Z</atom:updated>
            <content:encoded><![CDATA[<p>The preamble:</p><p>It started with the announcement of a proposed merger between the IDPF and the W3C but the debate really began with <a href="https://medium.com/u/185ce758ca9f">Peter Brantley</a>’s post where he came out in favour of the idea:</p><p><a href="https://medium.com/@naypinya/books-in-a-browser-375df76207ce#.h4ui939di">Books, in a browser</a></p><p>The thing to read after that is probably my blog post which compiles some of my Medium posts and the discussion after that:</p><p><a href="https://www.baldurbjarnason.com/notes/thoughts-on-standardisation/">A few thoughts on standardisation, W3C, and the IDPF</a></p><p><a href="https://medium.com/u/e977a1aba66a">Dave Cramer</a> responded to this post in detail:</p><p><a href="https://medium.com/@dauwhe/w3c-and-idpf-better-together-c92988674444#.e1ck8y8s9">W3C and IDPF: Better Together?</a></p><p>My response was to highlight the two different philosophies that are at play <em>within</em> the W3C.</p><p><a href="https://medium.com/@fakebaldur/my-first-short-response-to-you-on-this-idpf-w3c-thing-a53a028fafd#.5kqn3muva">My first, short, response to you on this IDPF/W3C thing</a></p><p>One thing that got a bit lost in the discussion here is that this <em>isn’t</em> a criticism of the W3C. Nor is it intended to be a slight against the publishing industry. I was trying to suggest that there are other pathways and tactics <em>within</em> the W3C to pursue if you want to maximise the odds of book-related specifications being implemented by browser vendors. This isn’t a question of me trying to reform the W3C but of making sure that reading <em>on the web</em> is improved using processes that the W3C <em>already has</em>.</p><p>If you don’t care about browser implementation or browser-based reading, <strong><em>nothing</em></strong> I’ve written in this debate applies to you. I am solely interested in what I can make happen within the browser. If you aren’t interested in browser-implementation, the venn diagram of our interests is two non-overlapping circles.</p><p>I followed the above post up with a couple of Medium posts that were largely references and talking points for Twitter discussions all of whom are already a part of one of the posts above but benefited from being emphasised separately. These links got a bit lost in the mix in the essays and I think a lot of people missed them when reading (my fault, apologies).</p><p>These links specifically:</p><blockquote><a href="https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/PJ_E04kcFb8">The blink-dev email announcing blink’s incubation first policy.</a></blockquote><blockquote><a href="https://medium.com/@fakebaldur/a-few-tweets-by-alex-russell-on-diversity-and-standardisation-f5b50af2736b#.fy53vjtiw">A few tweets by Alex Russell on some of his motivation for playing a part in the policy.</a></blockquote><blockquote><a href="https://thinkpurpose.com/2016/05/17/i-turned-down-a-40-pay-rise-heres-why/">This blog post outlines some of the issues with the expert-led approach in general.</a> Does a really good job of it too.</blockquote><blockquote><a href="http://blog.newsystemsthinking.com/the-955-rule/">Deming’s 95/5 rule is a nice and simple model for why I think change is needed.</a></blockquote><p>The last Medium post was a few lines on why mergers are risky in general which is why I don’t think the merger is a good idea:</p><p><a href="https://medium.com/@fakebaldur/mergers-are-inherently-risky-70b9efecea98#.t818cmi3o">Mergers are inherently risky</a></p><p>After that discussion on Twitter I feel that I have made my case regarding the merger and arguing it further serves no purpose other than to make noise. If people of the IDPF and the W3C, being aware of other people’s concerns and after having assessed them, decide that the merger is the right thing to do, who am I to argue against that?</p><p>With regards to the community-led approach, there is no need to try and force a wholesale shift. Forcing anybody to do anything goes against the spirit and the soul of the community-led approach, which would make such a move hypocritical and counter-productive.</p><p>If pointing out the incubation processes that the W3C is rolling out leads to people testing that approach for publication-related specs, and if I have the freedom to choose the process <em>within the W3C </em>that I think has the lowest risk when I do get involved, then that is already more than I have any right to ask for.</p><p>From my perspective, this entire debate is about how processes have different risk profiles depending on the problems they are tackling. Processes that are low risk for one context are high risk in others. None of this is about certainties. No one approach, no one strategy, is certain to succeed or fail. Odds vary; nothing is certain.</p><p>My argument is solely that the <em>clear</em> failure of prior ebook-related specifications should give us more than enough cause to investigate other processes. And, as it happens, the W3C is rolling out another process that is community-led and has a different risk profile. It seems logical to try it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c561630f4691" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mergers are inherently risky]]></title>
            <link>https://medium.com/@fakebaldur/mergers-are-inherently-risky-70b9efecea98?source=rss-ec8c474ec577------2</link>
            <guid isPermaLink="false">https://medium.com/p/70b9efecea98</guid>
            <category><![CDATA[web-standards]]></category>
            <category><![CDATA[mergers-and-acquisitions]]></category>
            <dc:creator><![CDATA[Baldur Bjarnason]]></dc:creator>
            <pubDate>Wed, 18 May 2016 12:52:57 GMT</pubDate>
            <atom:updated>2016-05-18T12:52:57.270Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a very common theme in economics. So common that it’s a frequent topic in both <a href="https://encrypted.google.com/search?hl=en&amp;q=why%20do%20mergers%20fail">business commentary</a> and academic research.</p><p>The reasons for why mergers are so risky are twofold:</p><ol><li>The benefits are overstated.</li><li>The cost of the merger is understated.</li></ol><p>In terms of the benefits, most of the proposed benefits do not pan out post-merger.</p><p>Shared resources and better processes don’t save as much as claimed because resources, processes, and systems are a function of the intended <em>output</em>. So unless the merged organisation intends to do substantially <em>less</em> than the old organisations, the savings will not be meaningful.</p><p>This is why, long term, most merged companies resort to product cancellations, layoffs, and other cutbacks to deliver on the cost savings they promise prior to the merger.</p><p>In fact, judging by most organisational literature mergers should <em>increase</em> cost because a larger, more complicated, organisation has higher coordination and transaction costs.</p><p>To make a long story short:</p><p><strong><em>A merged IDPF/W3C is likely to have to raise its fees in the future, not lower them.</em></strong></p><p>Community in turn is a function of the systems in each organisationand you can’t just jack up the input in a system to get an increase in community participation. Communities don’t work that way There is no reliable way of taking two communities and merging them without incurring substantial risk of collateral damage.</p><p>So the only way the merged IDPF/W3C will be more effective than the separate organisations is if it deliberately does less.</p><p>On the merger cost:</p><p>Merging the command structures of two organisations is hard. It takes a lot of work. There is an inherent integration cost to mergers that cannot be avoided. This cost comes at a cost of the two organisations’ resources which means they will have fewer resources for their other processes until the merger is complete. This causes delays and reduces each project’s ability to respond to changing circumstances. Which in turn increases the risk of project failure <em>throughout the organisation.</em></p><p>Mergers are inherently risky. They are, barring very unusual circumstances, <em>a last resort</em>. The fact that mergers are getting more an more common in the publishing industry should give you an indication of the health of the industry.</p><p>If the IDPF and the W3C have no other option than to merge, then these two organisations are in bigger trouble than I had hoped.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70b9efecea98" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[(This is a reply to Tzviya Siegman’s question on Twitter, posted here due to Twitter’s length…]]></title>
            <link>https://medium.com/@fakebaldur/this-is-a-reply-to-tzviya-siegmans-question-on-twitter-posted-here-due-to-twitter-s-length-942d5f6332e?source=rss-ec8c474ec577------2</link>
            <guid isPermaLink="false">https://medium.com/p/942d5f6332e</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[web-standards]]></category>
            <dc:creator><![CDATA[Baldur Bjarnason]]></dc:creator>
            <pubDate>Wed, 18 May 2016 11:17:01 GMT</pubDate>
            <atom:updated>2016-05-18T11:17:01.925Z</atom:updated>
            <content:encoded><![CDATA[<p>(This is a reply to Tzviya Siegman’s question on Twitter, posted here due to Twitter’s length constraints.)</p><h3>Tzviya Siegman on Twitter</h3><p>@fakebaldur how do you envision the community getting to a standard?I truly don&#39;t understand your proposal cc @dauwhe</p><p>I’m not envisioning anything. Not really. I’m suggesting that since the publishing IG has a number of features intended for browser vendors to implement, you’ll have a much higher chance of success using a community process <em>they themselves have already set up at the W3C. </em>Namely the <a href="https://www.w3.org/community/wicg/">Web Platform Incubator Community Group</a>. You can read <a href="http://wicg.github.io/admin/charter.html">their charter for more detail.</a></p><p>An added benefit of using this group is that publishers of all sizes, industry freelancers, and small design outfits can all participate and give feedback without having to be invited experts or pay high fees.</p><p>The more woolly aspect of my proposal is the idea of starting something similar for specs that aren’t relevant to browser vendors, one that would basically be a publishing industry specific copy of the WPIC. That’s more woolly mainly because I’m not sure how many publication-related specs there are that <em>aren’t</em> intented for browser implementation.</p><p>Again, I’m not asking anybody to build anything new nor am I inventing anything myself. I’m suggesting that the W3C already has specific pathways that are more likely to succeed than what people have been doing so far when it comes to publishing industry specifications.</p><h4>Further reading:</h4><p><a href="https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/PJ_E04kcFb8">The blink-dev email announcing blink’s incubation first policy.</a></p><p><a href="https://medium.com/@fakebaldur/a-few-tweets-by-alex-russell-on-diversity-and-standardisation-f5b50af2736b#.fy53vjtiw">A few tweets by Alex Russell on some of his motivation for playing a part in the policy.</a></p><p><a href="https://thinkpurpose.com/2016/05/17/i-turned-down-a-40-pay-rise-heres-why/">This blog post outlines some of the issues with the expert-led approach in general.</a> Does a really good job of it too.</p><p><a href="http://blog.newsystemsthinking.com/the-955-rule/">Deming’s 95/5 rule is a nice and simple model for why I think change is needed.</a> If the system’s output is regularly flawed or fails, odds are that the system is at fault and not any of its participants. The fact that the merger is being proposed shows that people already realise this, I just think that it doesn’t actually change any of the processes involved. (That post actually simplifies Deming’s point a bit but is close enough for jazz.)</p><p>And since I’ve pointed towards Deming, I might as well end with a quote of his:</p><blockquote>“It is not necessary to change. Survival is not mandatory.”</blockquote><blockquote>~ W. Edwards Deming</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=942d5f6332e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A few tweets by Alex Russell on diversity and standardisation]]></title>
            <link>https://medium.com/@fakebaldur/a-few-tweets-by-alex-russell-on-diversity-and-standardisation-f5b50af2736b?source=rss-ec8c474ec577------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5b50af2736b</guid>
            <category><![CDATA[web-standards]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Baldur Bjarnason]]></dc:creator>
            <pubDate>Tue, 17 May 2016 22:10:05 GMT</pubDate>
            <atom:updated>2016-05-17T22:10:05.629Z</atom:updated>
            <content:encoded><![CDATA[<p>Because I wanted to have a place where I could link to these.</p><p>For context: <a href="https://infrequently.org/">Alex Russel</a> is a…</p><blockquote>developer working on Chrome, <a href="http://www.chromium.org/blink">Blink</a>, and the Web Platform at Google.</blockquote><p>And he has been very involved in web standards.</p><p>Also, excellent blogger when he finds the time.</p><h3>Alex Russell on Twitter</h3><p>Thing that bugs me: the moment in a standards meeting when I realize 100% of the folks in the conversation are (self-identified) dudes.</p><h3>Alex Russell on Twitter</h3><p>Hot tip!: building a platform for the entire world that excludes 50% of it (however unintentionally) from the debate is BS.</p><h3>Alex Russell on Twitter</h3><p>For folks following earlier tweets: this is part of the reason for the incubation-first policy in Blink/Chrome. I&#39;m sick of powerful people.</p><h3>Alex Russell on Twitter</h3><p>Powerful people make environments that are comfortable to them _because they can_. Not evil, just human nature. But we need to re-litigate.</p><h3>Alex Russell on Twitter</h3><p>The terms of each feature should be set by the constituency that every designer can cobble together, not the (exclusionary) status-quo.</p><h3>Alex Russell on Twitter</h3><p>This, BTW, is also good for the designers: the other way leads to groupthink (see: CSS, HTML5, etc.) which causes &quot;regretted features&quot;</p><p>The relevance of the above to the debate surrounding the IDPF/W3C merger should be obvious.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5b50af2736b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Different economics require different standards processes]]></title>
            <link>https://medium.com/@fakebaldur/different-economics-require-different-standards-processes-9eb0f98e6332?source=rss-ec8c474ec577------2</link>
            <guid isPermaLink="false">https://medium.com/p/9eb0f98e6332</guid>
            <category><![CDATA[web-standards]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[publishing]]></category>
            <dc:creator><![CDATA[Baldur Bjarnason]]></dc:creator>
            <pubDate>Sun, 15 May 2016 20:26:09 GMT</pubDate>
            <atom:updated>2016-05-15T20:26:09.267Z</atom:updated>
            <content:encoded><![CDATA[<h3>Dave Cramer on Twitter</h3><p>@fakebaldur I think of the w3c process as the great advantage over idpf process-requiring multiple implementations before a spec is final</p><p>This is utterly true. Procedurally, the W3C process favours implementation. But it also doesn’t present the whole picture.</p><p>First off, the W3C is usually dealing with specifications that have very particular economic dynamics.</p><p>Second, the W3C has, off the top of my head, three different processes, two of which have evolved explicitly because the standard W3C process <em>wasn’t working well.</em></p><h4>1. The economics</h4><p>Historically, the W3C has tried to solve two different problems.</p><p>The first is to harmonise the implementation of a particular feature of the web stack across vendors. E.g. several browser vendors see the value in addressing a particular problem area and need to make sure that the solution is compatible across browsers. This has sort of worked because browser vendors realised that incompatible APIs and features reduced the value of their browser to pretty much everybody. Compatibility maximises adoption and value because they share a platform.</p><p>The key here is that you already have more than one browser vendor who has figured that the marginal profit (marginal value added minus marginal cost of implementing) of a feature is high enough to be worthwhile.</p><p>The second problem the W3C has tried to solve is when it sees the web stack as incomplete in some way or tries to push it in a particular ideological direction. These tend to be efforts that are high on ideology and low on economic rationale. Examples being early flavours of RDF, various flavours of XHTML, XHTML2 (a big enough flop to mention on its own) and similar messes.</p><p>It is generally much less successful at solving the second type of problem than it has been at the first (they often end up being utter disasters). The reasons should become clear when you look at the processes.</p><h4>2. The processes</h4><p>The W3C’s <a href="http://www.w3.org/2004/02/Process-20040205/tr.html">normal specification process</a> in broad strokes: a committee of interested vendors assign editors they trust to write a specification, that specification then becomes a firmer and firmer recommendation as more and more vendors implement it and hash out incompatibilities.</p><p>This works well when the economic picture is clear: the value of the feature is obvious to all participants and there’s no particular economic advantage for any one of them to hold the others back.</p><p>The process <em>doesn’t</em> work well under a few circumstances:</p><ol><li>The marginal profit of a feature is unclear, i.e. browser vendors either aren’t sure if the web community will value the feature or aren’t certain about how hard it will be to implement.</li><li>The feature clearly has no near term marginal profit but the W3C (or somebody else) is driving the feature because they firmly believe in some long term picture.</li><li>Vendors are divided because the marginal profit of the feature varies a lot from vendor to vendor. For example, Apple often doesn’t have the same economic dynamic as Google, and Mozilla’s values tend to differ considerably from the rest.</li></ol><p>The second process at the W3C came because of tensions between vendors and the W3C. The consortium pushed for XHTML2 while vendors wanted a more pragmatic approach. (This is simplifying a complex situation <em>a lot</em>, I know.) This led to the WHATWG and its set of specs followed by a reconciliation and harmonisation process of sorts. The end result is a complicated mess that is extremely confusing to outsiders. Obviously HTML5 walked its own walk when it came to W3C specification processes.</p><p>Reusing the WHATWG/W3C hybrid process for other specs is clearly inadvisable but it’s evidence to the fact that there has been in the past considerable dissatisfaction with how W3C has done things.</p><p>The third process is, in my view, a consequence of two realisations:</p><ol><li>The W3C is institutionally a really bad judge of what’s a good idea.</li><li>The marginal profit for a lot of potential web features is very hard to gauge at the outset. I.e. the ‘is it worth implementing?’ question is hard to answer.</li></ol><p>This has led to an increase in a community-oriented standards process where a community incubates and debates a feature before it graduates to a standards track at the W3C. <a href="http://indiewebcamp.com/">IndieWebCamp</a> has done this with <a href="http://webmention.net/">Web Mentions</a> and <a href="http://micropub.net/">Micropub</a>. And it has been done in informal ways with several specs that have been developed in ad hoc outside communities before they are brought to the W3C. Chromium/Blink has formalised this as its preferred specification path by adopting an <a href="https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/PJ_E04kcFb8">incubation-first standards policy</a>, directing participants to take proposed web specs through <a href="https://www.w3.org/community/wicg/">Web Platform Incubator Community Group</a>. It should be noted that since this is a community group, participation is open to all, unlike what you see in the W3C’s standard working group format.</p><p>The community incubation process is a quick, iterative way for developers and vendors discover exactly how hard a feature is to implement, what design for the feature is the most viable, and gauge the value it would add to the platform: it allows for a dramatically simpler discovery of a feature’s marginal profit than the other processes do.</p><h4>My suggestion</h4><p>As my <a href="https://medium.com/@fakebaldur/rhetorical-questions-about-standards-f3458f50343c#.bhyco0cek">prior series of posts and tweets</a> should make abundantly obvious, I think that a merger of the IDPF and the W3C is a bad idea and I’m sceptical of the direction that the specs driven by the publishing industry at the W3C are taking.</p><p>The digital side of publishing suffers from a very hazy economic picture. Layoffs have been abundant in the past year. A lot of its digital talent, including people with standardisation expertise are now unemployed. Sales have been going down. Amazon’s dominance makes the ROI on tech investment unclear. Publishing industry processes aren’t particularly compatible with web industry processes. We don’t know if any of these issues can be addressed by new specifications at all. We don’t know if the various publishing industries will adopt new specifications even if they get specified. We don’t know if any vendor will implement them. We don’t know if publishers will use them even if they do get implemented. The marginal profit of new specifications is utterly unknown. Not acknowledging these uncertainties and the risk they pose to tech specification is irrational.</p><p>The W3C’s standard process is <em>not going to work </em>under these circumstances. Adding the IDPF and its cluster-mess of a format into the mix will not improve the odds one bit.</p><p>The only viable process under these circumstances is the community incubation model. Take the features that the publishing industry needs but might interest browser vendors through the Web Incubator Community Group. In parallel, the W3C should set up an Publication Incubator Community Group, structured in the same way, for specifications that are less interesting to browser vendors but are publishing industry specific and relevant to non-browser vendors.</p><p>Going the community route is more democratic, more transparent (which has been lacking in publishing industry standards work), better suited to publishing industry budget requirements, and—in my opinion—more likely to succeed.</p><p>Excluding the community by continuing with a closed process is not a good idea when the digital side of publishing is facing so many uncertainties in its near and distant future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9eb0f98e6332" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rhetorical questions about standards]]></title>
            <link>https://medium.com/@fakebaldur/rhetorical-questions-about-standards-f3458f50343c?source=rss-ec8c474ec577------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3458f50343c</guid>
            <category><![CDATA[publishing]]></category>
            <category><![CDATA[web-standards]]></category>
            <category><![CDATA[medium]]></category>
            <dc:creator><![CDATA[Baldur Bjarnason]]></dc:creator>
            <pubDate>Sun, 15 May 2016 12:26:55 GMT</pubDate>
            <atom:updated>2016-05-15T16:19:36.356Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s say we have two people.</p><p>One works for a publisher and has been tasked with working in a standards organisation to get technology specified that is strategically important to the publisher.</p><p>Another works for an organisation whose goal is to democratise access to longform text and to improve the lot of authors—something that’s only possible if publishers (education or trade) are forced to reform, which is incompatible with the publisher’s extant strategy.</p><p>If you get both to work on specifying a piece of technology is the project:</p><p>a) More likely to fail (neither is willing to give up on their incompatible goals)?</p><p>b) More likely to be complicated and messy and therefore less adopted and buggy when implemented?</p><p>c) More likely to take such a long time to finish that it will be irrelevant when done?</p><p>d) All of the above?</p><p>Both the publishing industry and the web community are incredibly diverse groups. The idea that a single specification (the nebulous portable web publications idea) can serve them all without intolerable compromises is not plausible. The idea that a single organisation can serve them all is not a given.</p><p>Why should the web community work with the publishing industry, when the financial strategies of most publishers do not coincide with that of most who work on and for the web?</p><p>From the web perspective, the strategy that’s most likely to succeed is to work separately, without having to worry about the issues, business models, dynamics, and strategies of the publishing industries. Why shouldn’t the web community try to just improve reading in browsers at their own pace, focusing on their own needs and use cases without having to solve the self-inflicted problems of publishing?</p><p>Why is it a given that the publishers who have so far not participated in the web community must have something constructive to contribute to the web stack?</p><p>If the strategic goals of big publishers were compatible with the web, they’d have participated ages ago, as many <em>many </em>other tech-savvy publishers already have. Why do the IDPF and the W3C need to merge for the publishing industry to get involed in the web?</p><p>Why should the web community be happy about being forced to be involved in—and required to solve—the utter mess that is the ebook space?</p><p>Why do the IDPF and the W3C just assume that everybody will be happy about the proposed merger?</p><p>Why do people think that it’s a good idea?</p><p><em>Update</em>: I clarified some of these issues in a <a href="https://medium.com/@fakebaldur/do-not-underestimate-how-problematic-drm-will-be-in-this-collaboration-9113d037020#.75wco9osu">short follow-up on possible points of contention</a>. And this post was preceded yesterday by a question I posed <a href="https://medium.com/@fakebaldur/one-question-about-ebook-related-standardisation-at-the-w3c-d45aa2bd1b52#.3etsb657a">about the implications of the merger</a>.</p><p>(On second thought, I decided to inline the follow-up below.)</p><p><a href="https://medium.com/u/837d0758313e">Tim Flem</a> asked this here question (<a href="https://medium.com/@fakebaldur/do-not-underestimate-how-problematic-drm-will-be-in-this-collaboration-9113d037020#.d1qjysjm6">reposted from here</a>):</p><blockquote><em>Can you specify what you consider to be the “intolerable compromises”? I can certainly see how DRM could be a sticking point, but what else?</em></blockquote><ol><li>Do not underestimate how problematic DRM will be in this collaboration. At the moment and as proposed, web DRM is limited to a plugin system for time-based media (which is bad enough). Adding publishers and a publishing industry interest group to the W3C will dramatically increase the pressure to extend that system to regular text. Extending that DRM system to general markup would be an intolerable compromise.</li><li>The portability concept isn’t easily compatible with the web’s current security model (See my post <a href="https://www.baldurbjarnason.com/notes/some-notes-on-security/">A few simplified points on web and document security</a> for an overview.) Fixing that incompatibility requires compromises in the web stack that I’m not excited about. Compromising web security to cater to the business models of publishers would be an intolerable compromise.</li><li>The publishing industry is deep into EPUB. Maintaining compatibility with their EPUB stack is one of the stated goals of many publishers and publishing industry companies. However, compatibility with something as complex and flawed as EPUB is expensive, hard, and fraught with challenges and has no value to the web community.</li><li>There is an opportunity cost to all of these features. The web stack is flawed and needs improvement on many levels. The work going into fixing ebooks for the publishing industry is often work that could go into fixing pressing issues elsewhere. Not fixing something important because of this would be an intolerable compromise.</li><li>One of Tim Berners-Lee’s stated goals with the merger is <em>tracking</em> (see <a href="http://www.bookbusinessmag.com/article/what-the-inventor-of-the-world-wide-web-sees-for-the-future-of-ebooks/"><em>What the Inventor of the World Wide Web Sees for the Future of Ebooks</em></a>) and from what I can tell this is also an explicit goal of many organisations in the publishing industry. Pervasive tracking however is one of the biggest <em>problems</em> plaguing the web industry. Settling on an acceptable compromise for tracking is already hard enough.</li><li>The web and the publishing industry are more heterogenous than people make them out to be. Designing a single portable document format that serves the digital publication needs of everybody involved is, IMO, next to impossible without somebody making major compromises in their use cases. Somebody will inevitably find the necessary compromises intolerable.</li></ol><p>Improving reading on the web can be done without introducing DRM, re-implementing its security model to cater to full-featured portability, making exhausting EPUB compatibility compromises, or making the online tracking situation even more complicated and consumer-hostile.</p><p>I also posted a few tweets that are relevant to the issue:</p><h3>Baldur Bjarnason on Twitter</h3><p>&quot;Do nothing and see what gets implemented&quot; is actually a valid course of action for a standards group. One that gets dismissed too easily.</p><h3>Baldur Bjarnason on Twitter</h3><p>Addendum: If nothing then gets implemented the problem isn&#39;t too few standards but that the value of implementation does not exceed its cost</p><h3>Baldur Bjarnason on Twitter</h3><p>Collaboration is not a good in and of itself. When the goals of the collaborators are incompatible it instead decreases the odds of success</p><h3>Baldur Bjarnason on Twitter</h3><p>When promoting the idea that two groups should collaborate, you need to have a convincing argument why it will increase the odds of success</p><h3>Baldur Bjarnason on Twitter</h3><p>Saying &quot;because collaboration is good&quot; is not convincing, esp. when the success rate of both organisations (IDPF/W3C) has been sporadic</p><h3>Baldur Bjarnason on Twitter</h3><p>Creating a specification for tech that does not yet exist (i.e. you aren&#39;t normalising variations between vendors) is product development.</p><h3>Baldur Bjarnason on Twitter</h3><p>I am extremely sceptical of the idea that the traditional W3C process is likely to succeed under those circumstances.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3458f50343c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why did Paul Graham argue against equality?]]></title>
            <link>https://medium.com/@fakebaldur/why-did-paul-graham-argue-against-equality-c952ca01f2ca?source=rss-ec8c474ec577------2</link>
            <guid isPermaLink="false">https://medium.com/p/c952ca01f2ca</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[inequality]]></category>
            <dc:creator><![CDATA[Baldur Bjarnason]]></dc:creator>
            <pubDate>Wed, 13 Jan 2016 00:00:00 GMT</pubDate>
            <atom:updated>2016-01-16T12:20:23.423Z</atom:updated>
            <content:encoded><![CDATA[<p>He has, in a very short space of time, written two different essays that argue in favour of economic inequality.</p><p>I won’t link to them because they are more agitprop than argument.</p><p>While the reasons why he has written them are obvious, I haven’t seen anybody state them outright.</p><p>Endemic economic inequality isn’t caused by startups and hasn’t been caused by startups in the past. Their effects on inequality tend to be more localised.</p><p>The massive economic inequality we face today was created through deregulation of the finance industry and a refusal at the part of the authorities to punish finance industry malfeasance.</p><p>That’s it. Deregulation and the decriminalisation of financial misconduct is the cause of most of the economic inequality we face in the West.</p><p>Trying to fix economic inequality without reversing deregulation or addressing finance industry malfeasance is like trying to resurrect a corpse with a low-sodium diet.</p><p>Then why is Paul Graham arguing so vociferously against pro-equality rhetoric? Why is a guy who is a startup guy through and through, building up an argument against economic equality?</p><p>Because, with Uber, startups have become proxies for extra-legal deregulation. The value Uber creates for its investors isn’t in technical innovation but in its ability to capture the market, at higher margins, by circumventing regulations and regulatory bodies.</p><p>Which might be a net improvement in places where regulatory bodies are completely captured, corrupt, and under the control of the market incumbents they’re supposed to regulate (like most US regulatory bodies, for example). But it is disastrous in countries and sectors where deregulation has met with resistance following the crash of 2008.</p><p>Startups in the style of Uber are vehicles for deregulation and <em>deregulation</em>, by letting the financial class grab more of the economy, directly causes economic inequality.</p><p>Ergo, if Paul Graham wants to continue to be a successful venture capitalist while maintaining a public presence, he has to come up with a plausible argument against restoring economic equality.</p><p>His first and second attempts failed miserably — only rallied more people to worry about inequality, if anything — but his won’t be the last.</p><p>Odds are that we’re going to see a <em>lot</em> more leaders in the tech industry come out against equality over the next few years. They have to because the tech industry is becoming an inequality industry.</p><p><em>Originally published at </em><a href="https://www.baldurbjarnason.com/notes/why-did-paul-graham/"><em>www.baldurbjarnason.com</em></a><em> on January 13, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c952ca01f2ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>