1. Evan Prodromou: If you were thinking about Kickstarting an Open Source RSS reader, well, today's the day.

    evanp funny, I’ve been thinking of doing that for a while. Not sure I’ve got what it takes though, and I’m booked up for the next 4 months :/

  2. Jovian Salak: Yippee a new #pope. Why is everyone so excited? The new pope will still have to defend the *integrity* of a ridiculous religious corporation

    Jovian Salak u dissin pope? HE WHO WEARS POPE GEAR (large, medium or small), WHOSE COMING IN THE POPEMOBILE IS ANNOUNCED BY WHITE SMOKE? BOW BEFORE HIS POPE HAT

  3. Josh Emerson: @BarnabyWalters One-day-olderness day surely. It’s not like you become a year older in a day.

    Josh Emerson well that’s the point — the way we calculate age is so arbitrary I thought I'd poke fun at it. “One day olderness day” is even better, but not so feasible for putting on cards :)

  4. In order to express how arbitrary birthdays (and all their western connotations) are to me, I will from now on refer to them as “one-olderness days”.

  5. I’m noticing a pattern emerge whilst writing the simplified auth code: multiple event listeners which don’t know about each other working on the same object, augmenting and changing it.

    E.G. RememberMeListener looks for an encrypted cookie with a URL (my user ID of choice) in — if it finds one it makes an ActivityStream person object and puts it in request.attributes.user.

    Then, in the same event chain but at a lower priority level, the Contacts module looks in request.attributes.user for a URL. It looks up the URL in my people DB and, if there is anyone, augments request.attributes.user with all the extra info (full name, roles, photo URL, rel value, etc.)

    Then, another listener could run, looking for request.attributes.user with only URL — and look the URL up on identengine.com, caching the response.

    Other example is @-name autolinking, working on a similar basis of: basic transformation (raw data => common data format), then progressive augmentation adding URLs, names and rel values.

    I think this a very powerful and flexible pattern and something I will make a founding principle of Taproot.

  6. The problem with all mapping software ever:

    “Hm, that placename is a bit small to read” (zooms in) “TEXT, WHY U GET SMALLER AGAIN”

  7. Finally decided that symfony Security component is way too complicated for my little , so ditching it — but I’ve learnt a lot from digging through it and my further efforts will try to provide some of the amazing flexibility it gives whilst being more performant and easier to understand #php

  8. I really can't stress just how brilliant the identengine.com API is. Solves so many problems, implements so many standards, but more importantly: it is truly, truly webby. Forming a graph of a persons profiles by following rel links, then accumulating all that info is a vital building block. Great work Glenn Jones!