1. Bret Victor: How can you call the web a publishing medium when your bookshelf can just vanish? URLs and HTTP are a disaster. Doesn't have to be this way.

    @worrydream “bookshelf” is completely the wrong mental model. A “list of links” is like a list of postal addresses of places (hence web “address”) as a physical analogy, or the contents of their authors brains as a human analogy. Complaining about their contents changing/disappearing is as complaining that space/time/humans are “a disaster” (which admittedly may broadly be true).

    “your bookshelf” is whatever personal archives you make of your favourite things (analogies: photos, notes, physical books), and therefore the solution is better personal archival tools. I’ve made a start — my website automatically takes an archive of every page I link to and stores it as HTML+HTTP headers in the filesystem, which has proven to be a quite robust format.

    Of course if you actually have a practical idea about how to improve on the infrastructure of the web, speak up and/or build it :)

    Edit: reflecting on this, “completely the wrong mental model” is incorrect, and better expressed as “a mental model which is inconsistent with reality”. There are no “wrong” mental models, only a variety of co-existing metaphors with varying levels and areas of consistency with reality.

  2. Spotted on google.com: people searches return rich contact data in autosuggest box:

    Predictably, it only works for people with Google+ data.

    Turns out that selecting that option and pressing return doesn’t navigate to aaronpareki.com, or even a Google+ page, but adds a weird state indicator and a “this option does not exist” warning:

    (just in case anyone’s wondering, the reason I was searching was to attempt to reproduce this)

  3. Learning about umw.domains, a project to give UMW students+faculty their own personal domains. It’s a great project!

    My own has been a place of experimentation and self-expression for years now and I’ve learnt a lot, and connected with many people through it. Anything which makes personal domains more accessible is a move in the right direction.

  4. bruce lawson: .. correction; Opera 21 shows domain + path by default, hides protocol and query strings. (On feedback, we added setting to show full URL).

    @brucel that sounds like a good balance between informing the user and visual noise — should also help discourage the use of query string parameters in permalink design too, hopefully.

  5. Thoughts about whilst reading Lakoff’s Women, Fire and Dangerous Things — mf vocabularies e.g. h-card, h-entry, h-event are basic-level categories, the level at which:

    • it is easiest for humans to learn and reason about,
    • we have the shortest, most common names for them,
    • defined by how we interact with them

    E.g. h-entry ≈ “post”

    • short name
    • extremely common on the web
    • well-defined interaction patterns e.g. writing, posting, replying, reading, browsing through a feed, searching for/within, liking, reposting, quoting etc.

    Rather than RDF or schema.org which seek to create pure, objectivist, hierarchies of categories — our brains simply don’t work like that.

  6. Apparently we, as an industry, are over the whole ninja/rockstar thing and have moved onto “mountaineer” weworkremotely.com/jobs/472

    “Why yes, my company are interested in hiring PHP-based sailors and javascript treeclimbers. Bring your ropes to the interview, you’re going to need them.”

  7. At any given time my web archive HTTPS to HTTP domain ratio is almost exactly 1:10. Right now it’s at 410 HTTP domains and 41 HTTPS domains. Note that this is just the count of the domains I link to (and which link to me), unweighted by the number of actual physical links.

  8. The medium with which you choose to express a message shapes that message — be careful it doesn’t contradict it.

    Case in point: A Rational Web Platform (via @brucel)

    • hosted on google silo
    • long complex ugly URL
    • presentation tied to paged dead-tree media with ugly results: text breaks across artificial “pages”
    • no author URL, just corporate silo email, and email != web
    • javascript required
    • no microformats2 or even semantic HTML article markup — even js-generated markup is predictably disgusting with vast quantities of nested divs and spans with inline styles
    • Redirecting to different (non-canonical? difficult to tell due to ugliness) URL due to large amounts of traffic, likely indicative of infrastructural problems or incorrect medium
    • Broken on mobile devices:
      the body text is tiny and does not wrap, the high-traffic warning is truncated and unreadable

    Everything about this is anti-web, practically screaming “ignore me”.

    Improvements:

    • Host on personal site or project commons with CC license
    • Short, consistent, readable URI
    • Static semantic HTML with microformats2 h-entry for easy citations, archival and replying, no JS required — this would also solve infrastructural problems as HTML is pretty easy to serve and much faster than JS-rendered DOM-heavy “documents”applications
    • Author attributed by name+personal (non-silo) URL, with profile photo/logo for quick human association
  9. This evening: documented Yahoo! Pipes UI in case of sudden shutdown, built first mockup of web dataflow UI using jsplumbtoolkit.com — really excellent library, exactly the right balance between functionality and framework. It gives you a lot but doesn’t dictate how to use it.