#microformats 2023-03-28

2023-03-28 UTC
angelo, IWSlackGateway, [jeremycherfas], btrem, omz13-, jeremycherfas, ur5us, [0x3b0b], Seirdy_, mambang[m] and beedellrokejulia joined the channel
#
@MsKolleen Structured data formats are rules that standardize the structure and content of a webpage. Google is asking all of us to surface structured data to their crawlers by marking up our HTML with RDFa and Microformats. https://lttr.ai/907R (twitter.com/_/status/1640671934298959873)
mambang[m], Seirdy_, IWSlackGateway1, [snarfed], btrem, [tantek] and [KevinMarks] joined the channel
#
[tantek] well that's spam
[schmarty] and gRegor joined the channel
#
IWDiscordRelay <L​unarequest#0122> is `wm-property` form the webmentions api a html class or should i look for `in-reply-to` and `like-of` etc?
#
IWDiscordRelay <L​unarequest#0122> nvm I figured it out sorry for the silly question
btrem joined the channel
#
[tantek] Lunarequest++ for "html class" :face_holding_back_tears:
#
Loqi Lunarequest has 1 karma in this channel over the last year (2 in all channels)
ur5us and [dave] joined the channel
#
[dave] Lunarequest++ soy muerte
#
Loqi Lunarequest has 2 karma in this channel over the last year (3 in all channels)
#
[snarfed] I'm trying to figure out why mf2 parsers are suddenly only returning the h-card in this HTML and ignoring the outer h-entry. can't see it for the life of me. anyone have any ideas? https://fed.brid.gy/render?id=https%3A%2F%2Findieweb.social%2Fusers%2Fsnarfed%23likes%2F706326
#
[snarfed] eg https://pin13.net/mf2/?url=https://fed.brid.gy/render?id=https%3A%2F%2Findieweb.social%2Fusers%2Fsnarfed%23likes%2F706326
#
[dave] I copied and pasted the source into https://pin13.net/mf2/ and it worked ok. Did you test it earlier before you'd made changes? Maybe it's cached?
#
[snarfed] huh, true. odd! I'm pretty sure pin13 doesn't cache, but not 100%. cc [aaronpk]
[chrisbergr] joined the channel
#
gRegor I see the h-entry in the parse using that first pin13 link [snarfed]
#
[snarfed] So odd. I still don't, even on an entirely separate device. And I don't think the BF HTML has ever changed anyway
#
aaronpk I don't see the h-entry in the parse
#
aaronpk what the heck
#
aaronpk no h-entry https://pin13.net/mf2/?url=https://fed.brid.gy/render?id=https%3A%2F%2Findieweb.social%2Fusers%2Fsnarfed%23likes%2F706326
#
aaronpk yes h-entry https://pin13.net/mf2/?url=https%3A%2F%2Ffed.brid.gy%2Frender%3Fid%3Dhttps%253A%252F%252Findieweb.social%252Fusers%252Fsnarfed%2523likes%252F706326
#
Loqi [preview] Ryan Barrett
#
Loqi [preview] [Ryan Barrett] likes this.
#
aaronpk something about the url encoding
#
[snarfed] ohh yeah the ?'
#
[snarfed] argh, sorry, all user error 😆
#
aaronpk i still don't understand what is going on
#
[snarfed] heh true fair
#
[snarfed] looks like the first URL is only looking after the second ? and coercing it to the indieweb.social profile URL, so it's not fetching and parsing anything from fed.brid.gy at all
#
aaronpk i just added two properties to the pin13 debug to show what URL was input and what curl fetched
#
aaronpk i didn't notice the percent encoding but the one without the h-entry has the URL with the fragment for the like ID
#
aaronpk https://pin13.net/mf2/?url=https://fed.brid.gy/render?id=https%3A%2F%2Findieweb.social%2Fusers%2Fsnarfed%23likes%2F706326
#
Loqi [preview] Ryan Barrett
#
aaronpk `https://indieweb.social/users/snarfed#likes/706326`
#
Loqi [preview] Ryan Barrett
#
aaronpk the one that works properly escapes the # so is actually sent to bridgy
#
[snarfed] right
#
[snarfed] if I enter the BF URL into the form on https://pin13.net/mf2/, it works. the problem is, I'm used to making pin13 URLs manually, in the browser's URL bar, which usually works, but not this time
#
[snarfed] sorry!
#
aaronpk is this a problem with pin13 tho? because there's no literal # in the URL
#
[snarfed] true. maybe? not sure