It turns out Readability then loops through all these ‘paragraphs’ and assigns a score to them based on how ‘content-y’ they look. This score is determined by things like the number of commas, class names used in the markup, etc. The content’s length appears to be measured by using .innerText; for every 100 characters inside a paragraph, that paragraph’s score goes up. Eventually, the number of elements is counted, adding their individual scores. I think it’s safe to assume Safari Reader is triggered based on this algorithm.
Video-only posts may never work since there’s basically no text content to work with.
We might have better luck lobbying BB to standardize markup a bit more.
I am not sure this is the case here, its stripping the image for some crazy reason … will have a look.
EDIT
The reason we are having trouble is cause the markup structure is just real hard to deal with automatically, the image is nested in 2 divs, the algorithm is having trouble understanding that the image belongs with the post.
I will see what we can do about this general pattern.