Replied to https://beko.famkos.net/2023/08/07/15628749/ by Beko PharmBeko Pharm (beko.famkos.net)

I like eye-candy for my #hCard and for the longest time I did override the generic icon for missing SVGs via CSS. This never fixed the titles thought and after starting to mass non descriptive links all named “website” I started to dig into the code class-relme-domain-icon-map.php of the plugin.
Turns out Rel_Me_Domain_Icon_Map does some file system shacking for unknown domains in wp-content/plugins/indieweb/static/svg/ so I fixed myself some symbolic links:

discuss-dot-tchncs-dot-de.svg -> lemmy.svg
live-dot-famkos-dot-net.svg -> owncast.svg
nerdpol-dot-ch.svg -> diaspora.svg
social-dot-tchncs-dot-de.svg -> mastodon.svg
t-dot-me.svg -> telegram.svg
tube-dot-tchncs-dot-de.svg -> peertube.svg
[…]

The title is read directly from the SVG so adding a title tag so custom SVGs helps with that.
That’s a lot of CSS that I can remove now 🤓

Anything I can help with?
Bought a photo scanner with an automatic feeder. Back in 2013-4 I paid for a service to scan thousands of family photos. Then I found more. This time, doing it myself. Went through 1200 photos in a day.
Filed an Issue Authorship (github.com)
I’ve found URLs where the top level has two items…one of which is an h-card, the other an h-entry. There are two questions that come from this for the specification.

First, if there is no author property on the h-entry(it could be a different h- element), can I assume that a top-level h-card also reflects the page author?

Second, if there is an author property that is a URL, is there a point in checking to see if there is a more complete top-level h-card with the same URL on the page? It seems this is also a practice that people do.

Consistent Microformats

One of the problems in consuming microformats is consistency. There are a variety of different ways people structure their pages.

Many people have written code to solve this problem. I do it in my library, Parse This. Aaron Parecki does it in his XRay library.  The Microsub specification has a stricter jf2 output in order to simplify the client having to make all sorts of checks.

This is the point. It is easier to consume a clean and consistent parsed microformats structure.  Some of this would probably be solved by some consensus on the matter.

So, what does Parse This, and its ilk do? I lack a name for this sort of code.

  • It has two options: feed or single return
  • Feed tries to identify and standardize an h-feed. This means if there are multiple top level h- items, it will try to convert it into an h-feed.
  • Single will try to identify the top level h- item that matches the URL of the page.
  • In both cases, it will run authorship discovery in order to find the representative author and add this as an author property to the h-feed, or single h-entry etc.
  • It will try to run post type discovery.