Added a job to my feed aggregator/Microsub server that quickly validates mf2 media, i.e., the URLs that end up in entries’ `photo` and `video` arrays, by means of a HEAD request. If the server returns a 404 (or similar), the URL is probably faulty (e.g., the result of a misplaced `u-photo` tag), and the item removed from the list. No more (well, definitely less) “broken images” below posts!
@bekopharm Haha, yes, I’ve finally come up with a way to work around that. I mean, the whole idea _is_ weird. Better to leave this up to reader software anyway. (Which is what happens, too: Indigenous, on my phone at least, does this for _every_ image, also for non-microformats, non-image posts. Super annoying when a longer article has image captions in it but the actual images are way at the bottom, with zero context!)
@bekopharm I think if “the IndieWeb” wanted people to use (semantic) HTML for content, for feeds, with microformats sprinkled on top, they shouldn’t tear that content apart because of how Instagram or whatever does it. Same way I dislike “channels” that are modeled after Slack. I mean, I think it’s good we extract metadata and offer that to readers so they can provide a richer experience; unsure about actually altering what people put together.
@jan true. I've that conflict all the time. For example when there is additional content for… a Like or Bookmark.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!