1. Turns out the 2 JSON structures enable safe entity expansion just like twitter entities.

    In my reply contexts I am not wanting to embed 3rd party HTML in my site, so I take the p-summary and strip tags. But, I want embedded h-cards to be expanded just like at-mentions on twitter. Pseudocode:

    let h-card = canonical JSON structure for a note, with .summary as a plaintext representation of the content;
    for item in h-card.children:
     if not in_array('h-card', item.type) continue;
     let html = HTML representation of the child from properties.url, name, etc;
     replace item.value in h-card.summary with html

    Example here.

  2. Just hooked up my notes to Brennan Novak’s rather awesome @emoome sentiment analysis API! So all my notes will have automated emotion/language analysis applied now, which I can query through machine tags.

    At the moment I’m not publicly showing this data, but if you can read HTML it’s in the source (machine tags not shown by default) and if you can read JSON, add .json onto the end of the URL.

  3. This evening’s project: catching up on a bit of dev. :

    • remove lines — whitespace FTW
    • get rid of crappy AJAX+backbone for calling new note UI into notes page, replace it with iframe+postMessage
  4. 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.