#microformats 2023-02-01

2023-02-01 UTC
btrem joined the channel
#
btrem https://chat.indieweb.org/microformats/2023-01-30/1675109128710900
#
Loqi btrem: Zegnat left you a message on 2022-12-16 at 11:19am UTC: I filed a PR for using the newer TypeScript parser, do have a looksy. I think if we want to clean up the JS microformats.io version it would be swell to bring this along. https://github.com/microformats/microformats-parser-website-node/pull/5
#
Loqi [preview] [[aciccarello]] On my feeds, my posts are wrapped in a link. Since the wrapper is a link I can't have another link inside to point to the author card. Is there a way to reference the h-card inside an h-entry without href?
#
btrem @[aciccarello] You can put the info in plain text, if that doesn't mess up your feed. `<a class="h-entry u-url mdc-card disable-link-styles" href="/posts/2022/03/30/post-slug/">...<span class="p-author h-card"><span class="p-email">foo@example.com</span></span></a>`
#
btrem `<a class="h-entry u-url mdc-card disable-link-styles" href="/posts/2022/03/30/post-slug/">...<span class="p-author h-card"><span class="p-name">aciccarello</span><span class="p-email">foo@example.com</span></span></a>`
#
btrem @Zegnat It looks like PR 5 has already been merged, unless I misread things.
#
[aciccarello] Thanks btrem. I realized I didn't need a link so much as I wanted to be able to reference my main h-card with `u-author` . The data element worked well enough for that. https://github.com/aciccarello/ciccarello.me/commit/fe0ba3824cd746f21dccdc43571f7a517722b075#diff-c43605d69b6141c33d868[…]84960992dc322a89cd4b8d6R57
#
[aciccarello] On a related note, I added automated testing of my microformats this week to help identify how my markup is parsed. https://github.com/aciccarello/ciccarello.me/blob/fe0ba3824cd746f21dccdc43571f7a517722b075/_build/tests/microformats.test.mjs
#
gRegor Nice! I still see that `u-rul` typo btw
#
[aciccarello] ha, I swore I fixed that
#
[aciccarello] Oh, could be a failed build
#
btrem [aciccarello] I looked at the commit; I'm not an expert, but I don't think u-author is correct, as that will set the author to the root page of the site. Or maybe that's what you want?
#
[aciccarello] That's the intention
#
[aciccarello] There should be an h-card on that page
#
[tantek] sounds familiar 🙂
#
[aciccarello] gRegor, theoretically should be fixed now
#
gRegor looks good!
#
btrem Hmm, ok I don't know how that works. Something to look into some day.
#
gRegor btrem, it's part of the authorship spec, https://indieweb.org/authorship-spec#Algorithm
#
btrem But I'm happy to see someone else here using 11ty. Maybe I can pester you with 11ty questions. (Not sure which room would be the right one.)
#
[aciccarello] btrem, feel free to ping me in #indieweb-dev
#
btrem Thanks!
#
btrem @gRegor I'm trying to follow those authorship rules. It looks like I'd need an author page with an h-card whose u-url is the same as the author page. IOW, the h-card on the author page would link to itself. Is that right?
#
gRegor Ah, for publishing authorship you want https://indieweb.org/authorship. There's several ways and it doesn't have to be on a separate page.
#
gRegor I used the separate page (homepage) method for a while, but recently switched back to embedding an h-card in each post, because I'd prefer to keep my historical avatars for each post.
#
gRegor The authorship-spec page is for if you're given a post URL, how do you determine the author
#
btrem Well, that didn't clear things up :( but it probably doesn't matter. I put an h-card on every post on my site. Easier that way, and seems to make sense to me.
#
gRegor Yep, whatever makes sense for your publishing! The Monocle Preview is probably the easiest way to check author name and photo shows up the way you want: https://monocle.p3k.io/preview You can plug individual permalinks in there too, not just a feed.
#
[tantek] hopefully indiewebify.me can also help with that too (and if not, worth filing a feature request)
#
gRegor yep, an old one: https://github.com/indieweb/indiewebify-me/issues/6. A newer one also mentions at least linking to the authorship test tool https://github.com/indieweb/indiewebify-me/issues/108
#
Loqi [preview] [barnabywalters] #6 Implement /authorship
#
gRegor I'd really like to get indiewebify.me off of Silex since that isn't maintained anymore. Barnaby and I discussed Slim PHP framework since we're both familiar with that and it's maintained.
#
[tantek] yeah, worth chatting that in #indieweb-dev or maybe #indieweb-meta to your preference
m5zs7k and IWSlackGateway joined the channel; btrem left the channel
#
@eniehack ↩️ see also: http://microformats.org/wiki/RelMeAuth (twitter.com/_/status/1620680942431133696)
ur5us, gRegor, [KevinMarks], Guest6, khurtwilliams1, [jacky], [tantek], [snarfed], [dave] and [schmarty] joined the channel
#
[tantek] ^ good timing for the day 😄
[tw2113_Slack_], [aciccarello], heyyyy and btrem joined the channel
#
btrem @ Zegnat apologies for the message yesterday. You asked Loqi in December to send me a message, but Loqi decided not to give it to me until yesterday. And I responded before I realized that the message was a month-and-a-half old! :-o
ur5us and [benji] joined the channel
#
@chrismessina ↩️ This is cool — because if you add your GitHub profile to your @joinmastodon profile, you're creating a bi-directional claim, verifying the links! Welcome back to the web, rel-me! https://microformats.org/wiki/RelMeAuth (twitter.com/_/status/1620910675739688961)
#
[tantek] !meme rel-me on the web? Always has been
#
Loqi http://meme.loqi.me/m/5P9pEK22.jpg
#
[tantek] No Loqi, you're supposed to use this format: https://imgflip.com/memegenerator/Always-Has-Been
#
[snarfed] ugh, implied properties strike again, implied u-url here is wrong: https://pin13.net/mf2/?url=https://geekosaur.com/post/geekosaur-news-26/ , https://microformats.org/wiki/microformats2-implied-properties#root_class_with_one_child_hyperlink
#
Loqi [preview] Geekosaur News 26: Migrating To Kobo
#
[snarfed] what's the recommended workaround? there isn't currently a link to the permalink that they can just add u-url to
#
[tantek] [snarfed] wow, that
#
[tantek] is the kind of case that the rule ".h-x>a[href]:only-of-type:not[.h-*]" was supposed to protect against with only-of-type but failed apparently which is quite surprising given the complexity of markup there
#
[tantek] [snarfed] do you mean parsing workaround or publishing workaround?
#
[tantek] for parsing, I'm thinking of adding a no e-* properties restriction
#
[snarfed] publishing workaround
#
[snarfed] parsing 🤷
#
[tantek] because e-* indicates the presence of non-trivial markup and thus there should be no implied properties
#
[tantek] publishing workaround off the top of my head would be <data class="u-url" value=""></data>
#
[tantek] per relative URL resolution rules for u-* properties that *should* result in a u-url property of the current page
#
[tantek] inside the h-entry obv
#
[tantek] yup, just tried <div class="h-entry"><data class="u-url" value=""></data></div> in pin13 and it worked
#
[snarfed] thx, I'll tell them
#
gRegor Hm, that `.h-x>a[href]:only-of-type` means if there's only one <a> inside the h-entry, right? Might be a php-mf2 bug
#
gRegor Ah, from MDN, :only-of-type "represents an element that has no siblings of the same type"
#
gRegor Initially I like the no implied if e-* properties idea
#
gRegor Seems in line with the implied p-name restriction: "if no explicit "name" property, and no other p-* or e-* properties, and no nested microformats,
#
gRegor "
#
[tantek] ahhh yes
#
[tantek] why didn't I extend that to u-* at the time
#
[snarfed] fwiw php-mf2 and mf2py currently both do this. https://python.microformats.io/?url=https://geekosaur.com/post/geekosaur-news-26/
#
Loqi [preview] Geekosaur News 26: Migrating To Kobo
#
[tantek] I mean that behavior is spec compliant
#
[tantek] that's my point, the :only-of-type was an insufficient protection
#
[tantek] I thought it would work for the 'simple' markup cases that could result in false positives
#
gRegor should we re-open https://github.com/microformats/microformats2-parsing/issues/36 since [snarfed] commented there, or new parsing issue?
#
Loqi [preview] [sknebel] #36 Falsely implied u-url
#
tantek edited /microformats2-parsing (+120) "add "Proposed:" "or no e-*" to both implied 'photo' and 'url' properties, issue # tbd, use-case https://geekosaur.com/post/geekosaur-news-26/" (view diff)
#
[tantek] alright, captured the proposed fix inline in case anyone (parser devs) want to review!
#
[tantek] figuring good reason to patch both photo & url implied parsing this way (don't imply if any e-* properties present)
#
[tantek] new issue, because that original issue use-case was solved
#
[tantek] issue 36 was solved which was an explicit u-* property that was not u-url being implied to be a u-url
#
[tantek] I strongly prefer atomic issues for specific problems, rather than "feature x is broken" then being continually expanded
#
gRegor ok
#
[tantek] much easier to track precise proposals to solve precise problems, and precise changes accordingly that way
#
[snarfed] thanks [tantek]!