Even passionate IndieWeb evangelists, most of them running a custom WordPress theme, have often got empty, duplicate or wrongly named microformatted HTML in their blog entries.


I mean, I can only encourage everyone to run their h-feeds and, occasionally, an h-entry or two through xray.p3k.app.

@jan your mention of h-feed makes me wonder how many people read my site through the h-feed. It means they will only see a small part of my blog, as only the front page has an h-feed.

@ton @jan ssssame. Not going to put every chatter there.

@bekopharm @ton All my archive pages are h-feeds: the homepage (long-form content only), my notes section (microblog), tag archives, even search results pages. The only thing not shown in any of these are ... RSS-only items. I sometimes subscribe to multiple such feeds. I like the added functionality (avatars, the ability to quickly recognize bookmarks or replies, etc.). Quite a few RSS feeds out there are still lacking proper context for certain post types.

@bekopharm @ton (That said, if your h-feed is summary-only, Microsub servers might not recognize posts as replies or bookmarks or ... Which is why my Aperture fork will then try and fetch the actual posts! 😀)

@bekopharm @ton Most of the issues I was referring to, by the way, are in the h-entries themselves. Invalid HTML, missing tags, duplicate classes, etc. Happens in RSS, too, by the way. Items that are clearly notes but have title tags in them—which then read “A note,” or something—are one example.

@bekopharm @ton But, uh, in response to Ton’s remark: I definitely agree that Microsub is the most “optional” of all IndieWeb “building bricks.”

@bekopharm @ton (That's how most Underscores-based WordPress themes would do it, I think, back when they introduced microformats1.)

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!