I’ve modified my feed reader to accept `figure` and `figcaption`—I mean, why not?—but because of how _microformats feeds_ are parsed, images themselves are stripped from _photo posts_, to be shown underneath, leaving the caption rather lonely. One way to deal with this is interpret photo posts’ content as (mostly) plain text, I guess.
Thing is, I _can't_ just _not_ strip images and pretend `h-entry`s are no different from, e.g., RSS items, because it is possible and quite common to have `u-photo`s adjacent to, rather than in, `e-content`. (What I could do, I suppose, is again check if images are in `e-content`, and only display, separately, I mean, those that aren't.)
One thing I really like is implicit post types. We don't hardcode one, it is implied by the (meta)data. What I don't like is how we then go and treat posts completely differently based on their type instead of establish a consistent "baseline behavior." Might as well have set an explicit post type then.
@jan Somewhat related, i'm working an extended native feed element. All it does is fetch a feed from a federated platform and spit it out in some native article, fieldset tags and such. I'm hoping i can show it off in a day or two when i put up my devlog website
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!