Battle for the planet of the APIs by Jeremy Keith — nice piece of writing, it’s worth pointing out that Twitter still includes rel=me links back to homepages, but is increasingly wrapping them with t.co, making them fairly useless.
Whilst I admire RSS as a rallying cry for the openness of data on the web, I don’t like it much, mainly due to it’s DRY violation. microformats2 is the better solution.
.h-entryis better off where you’ve got
.idno-entryso then the author
.h-cardcan be scoped into the entry
.h-entryto explicitly declare authorship
.h-as-*on the same element as
.u-urlwhere you currently have
“How about a garage door you can see through? Well almost”
“The neat thing is that these are overhead sectional garage doors just like any other.”
“Can you acquire a bucket of paint?”
“you'll amaze yourself”
“Now that you understand how financially important your garage door really is to you, it is time to get to work.”
Hopefully h-card entities should get expanded in the reply context for this note (crosses fingers)
Turns out the #microformats 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
Aaron Parecki testing reply context microformat entity expansion, please ignore :)