Trying to think of a good reason to make a #js library called bach.js
Aaron Parecki seems like that would be blurring the line between presentation and behaviour — where do you stop? Weather media queries? Proximity? Acceleration?
Pondering the utility of a “draft blog post titles” listing on my homepage, partly as a teaser, partly as a reminder to myself
Laughing at the @twitter docs using “t.co” and “best practices” in the same sentence: dev.twitter.com/docs/tco-url-wrapper/best-practices
I’m thinking the time might have come to write a wrapper around #php DOMDocument which actually makes it usable. Thoughts:
querySelectorAllare implemented for both the document and individual elements via Symfony XPath → CSS converter and relative XPath queries
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
Trying out note posting on a fresh install of the new #taproot
Digging through some mailing list archives I pulled recently revealed some familiar faces, some interesting stories and SO MUCH amazing information lost in the depths of the web.