#microformats 2022-12-15

2022-12-15 UTC
#
gRegor
I'm continuing to merge those PRs. The main issue I see with this serial PR strategy is that each subsequent PR's diff contains all the past ones, so it's really difficult to review. There's no conflicts with main branch, so they can be merged, but it's just hard to tell what's actually changed in the individual PR.
#
gRegor
in https://github.com/microformats/microformats.io/pull/64/files the bulk of that was from 63 that's already merged, so I can't really tell what punctuation was changed.
#
M0x3b0b[m]
Theoretically rebases as you go should also work, but how well depends on your tooling (haven't tried it on Github), community, and religio--uh, philosophical opinion of rebasing
#
gRegor
Yeah. I use a branch like `dev/feature` on my fork and will rebase it as needed, since I only intend the lifecycle of the branch to be for the PR
#
gRegor
btrem, merged all but the last one, left a comment there
#
GWG
Microformats debate at HWC tonight
#
gRegor
oh no
#
gRegor
hopefully more of a productive discussion? :)
#
GWG
gRegor: I need backup?
#
gRegor
lol, is this just a ploy to get me to join HWC?
#
GWG
Maybe
#
GWG
The definition of u-photo in h-recipe
#
gRegor
I don't have experience with that / strong opinions
#
gRegor
Think I saw the github issue mentioning that, though
#
GWG
And why u-photo changes the meaning of h-entry
#
gRegor
Based on published examples, how consumers use them, and prior art of silos like Instagram. With a regular post (h-entry), u-photo makes it a photo post.
#
gRegor
With h-recipe, I don't know there's many published/consumed examples with photos. photo property was experimental in mf1 hRecipe apparently https://microformats.org/wiki/hrecipe
#
Loqi
[preview] Per Microformats_Wiki:Copyrights, hRecipe was placed into the public domain
#
[aciccarello]
I publish with a photo
#
gRegor
Oh nice!
#
btrem
I'm one of the people in that "debate". :-o
#
btrem
I publish h-recipe with u-photo. But I'm not sure what the purpose of u-photo is. In fact, I think I'm the one you were referring to who mentioned it in the github issue.
#
gRegor
One or more photos of the prepared dish I think, or perhaps photos along the way if you prefer
Seirdy joined the channel
#
btrem
I guess I'm unsure why I'd need to add `u-photo`. What would the point be? If there's a photo in e-content, wouldn't that be enough?
gRegor, ur5us_, ehmry and tiim joined the channel
#
Loqi
[preview] [Zegnat] #3 Swap querystring for body-parser
#
Zegnat
I have not swapped anything over to the typescript implementation. But I could have a look at that after work.
tiim, Saphire, barnaby and gRegor joined the channel
#
gRegor
Just double checking: node.microformats.io is using glennjones/microformats-node correct? Not microformats/microformats-parser? https://github.com/microformats/microformats-parser-website-node/blob/next/yarn.lock#L506
#
gRegor
typo: *glennjones/microformat-node
#
Zegnat
gRegor: yes. The discussion was about whether to swap that out. Should have probably filed an issue for that discussion
#
gRegor
Gotcha, thanks!
#
Loqi
[preview] [Zegnat] #4 Should we swap microformat-node for microformats-parser?
[timothy_chambe], [tw2113_Slack_], btrem and ur5us_ joined the channel; btrem left the channel
#
btrem
I feel like I'm the bearer of bad news, but the ruby mf parser site seems to be down: https://ruby.microformats.io/
#
btrem
Returns 500 server error with the message body reading as follows: "We're sorry, but something went wrong. If you are the application owner check the logs for more information."
#
gRegor
Quite a few dependabot automated PRs, https://github.com/microformats/microformats-parser-website-ruby/pulls Last commit was April 2020
#
gRegor
jgarber might be able to help