1. 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!

  2. Twitter’s “you only see replies from people you follow if you also follow the target of the reply” model is quite fascinating because it means that, within a particular community, the number of tweets you see is not directly proportional to the number of people you follow. It’s probably square or cubic, perhaps I’ll model it and see.

  3. I love that now has shiny namespacing and a thriving code sharing community, but I think the heavily hierarchical namespacing practises used by some of the community (e.g. symfony components) are unhealthy.

    They are difficult to memorise, relying on (often slow) IDE autocomplete, and encourage a use statement for each class. That’s pretty much a scoped equivalent of from x import * in python — not a good practise! It’s still namespace pollution, it just takes longer to write.

    I am trying to use a more python–like, package-centred approach with much fewer subnamespaces. The outcome of this should be that you use the package name:

    use BarnabyWalters
osse;

    …and then using all the classes/subnamespaces from that root, e.g: $t = Posse\Helpers::convertHtmlToTwitterFormat($s);

  4. Question: What Status code should I use for “You haven’t provided enough/correct information to carry out that method”? Currently I’m thinking 422 Unprocessable Entity.

    Context: POST request to a list resource for the creation of a new sub-resource.

  5. Aral Balkan: @BarnabyWalters …maybe ‘articles’ would be a better name for ‘notes’ and ‘notes’ a better name for ‘scribbles’ :)

    @aral that would certainly be more consistent with the naming schemes @aaronpk, Tantek Çelik and myself are using, which we borrowed from the activitystrea.ms schema.

    It's great that you're self–hosting shorter units of content as well as longer articles now! Maybe tweets next? ;)

  6. URLs don't just give addressability, they give accountability. When there's a URL, someone is responsible for it. When a thing (concept, object, document, proposal, idea, etc.) has a URL, it can be discussed, supported, contested, referenced and documented.

    URLs are valuable things. We must treat them with respect.