1. And the compliment of that : the simpler the text-publishing service, the more interesting uses it’s users will put it to, provided it paves their cow paths (e.g. Twitter with RTs, and @-replies).

    Give users constraints and simplicity, see what they do, then solidify that functionality — or, from an point of view, give yourself constraints, then pave your solitary cowpaths.

  2. That excellent post of Tantek Çelik’s, like all well–hyperlinked documents, lead me to a whole raft of great resources I hadn’t come across before:

    (In other news: I need to make a “dump tabs into new note dialog” browser )

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

  4. Made some updates to my note autolinking flow — instead of lots of unstable regexes, only one runs now (courtesy of cassis) and the rest manipulate the XML–compatible HTML which results. Much more robust, much more extendable

  5. This evening’s project: quoting UIs. Why they suck or for some reason do not exist, research into existing ones (found a nice github example) and silo equivalents.

  6. So, which is more annoying, POSSE permalinks w/ … if continued, in () if not, or Aral Balkan’s …tweet…continued…thing…? For comparison:

    Personally I find the …/() permalink/shortlink/short id pattern to be much more readable, especially when there are multiple long tweets happening at the same time, and they are mainly one or two words over Twitter’s limit. But it is more cluttered than the … technique.