#microformats 2018-08-22

2018-08-22 UTC
[iambismark], [matpacker] and Dominian2 joined the channel
#
Dominian2 __
[chrisaldrich], [cleverdevil], tantek__ and f22 joined the channel
#
f22 *p e n i s b i r d p e n i s b i r d *
#
f22 e ( ..__`'-.,--, e
#
f22 n '-._'-.__`\a\\ n
ben_thatmustbeme, [eddie] and c0ded joined the channel
#
c0ded | .---------.
#
c0ded |
[matpacker], barpthewire, globbot and blacksyke12 joined the channel
#
blacksyke12 | ____
RaptorJesus14 joined the channel
#
RaptorJesus14 | | |
[kevinmarks] and biberao6 joined the channel
#
biberao6 __
Davesdowntime and TheSilentLink15 joined the channel
#
TheSilentLink15 _____________________
#
TheSilentLink15 /| /| | | |
#
TheSilentLink15 ||__|| | | DO NOT |
#
Loqi That looks like spam, bye!
#
Loqi That looks like spam, bye!
dysfigured26, KevinMarks, ben_thatmustbeme, [kevinmarks], barpthewire, [jgmac1106] and xset joined the channel
#
xset | __
[keithjgrant], barpthewire, [grantcodes], koddsson, KevinMarks and ChickeNES joined the channel
#
aaronpk ugh https://github.com/microformats/microformats2-parsing/issues/21 bites again
#
Loqi [aaronpk] #21 reduce instances where photo is implied
#
sknebel aaronpk: then make a proposal for fixes and we can see about implementing it
#
aaronpk i think my proposal is the same solution as the implied name solution
barpthewire joined the channel
#
sknebel in url parsing it's "if no explicit "url" property, and no other explicit u-* properties, and no nested microformats,"
#
sknebel vs name with "and no other p-* or e-* properties, and no nested microformats,"
tantek__, gRegorLove and jackjamieson joined the channel
#
sknebel not sure what's best for photo
jackjamieson joined the channel
#
aaronpk Zegnat heeeelp
#
sknebel certainly u-, but p-/e- might make sense too
#
Zegnat mumbles something about abollishing all that implied nonsense
#
tantek__ Zegnat, never throw out simple 99% cases because the 1% is harder.
#
tantek__ that's what leads to burdening everyone with excessively complex design
#
tantek__ and thought we addressed u-photo already like u-url. if not, what's the issue #?
#
aaronpk https://github.com/microformats/microformats2-parsing/issues/21
#
Loqi [aaronpk] #21 reduce instances where photo is implied
#
Zegnat Hmm, no, I think we only changed implied u-url. Imply rules are per property, not per prefix.
#
Zegnat Here is a question: has anyone ever published an h-entry that required implied photo? Or is that really only something that gets used for h-cards? I don’t really like the idea of limiting parsing rules based on the object vocabulary, but wondering if that could be a solution.
#
Zegnat Is there anyway to figure that out with indiemap? sknebel?
#
sknebel might be...
#
sknebel no, don't think so. you could maybe find candidates to manually check
#
gRegorLove I think the implied url update applied to photo would work: "if not explicit photo property and no other u-* properties and no nested microformats, then imply by..."
#
gRegorLove reviews the issue
#
Zegnat Would mean you can never get implied photos once you have added a u-url for your entry. But that might not be important.
#
sknebel that's probably ok, and/or necessary to avoid wrong u-photos on notes etc
[jgmac1106] and [keithjgrant] joined the channel
#
gRegorLove I think that's reasonable. Implied still works for minimal h-. Once a publisher starts adding u- properties I think it's reasonable to add other explicit u- they need.
#
sknebel only u-, or extend to other types?
KevinMarks joined the channel
#
gRegorLove Just the u- I think, to keep the changes conservative, and in parallel with the implied url
#
Zegnat I can’t really think of any objections
#
Zegnat Most of the known cases where implied photo might be important, small h-cards, wouldn’t have u-url anyway as that would be implied from the <a class="h-card">. So if we stop implied photo with u-, we are not harming those in the wild cases.
Ricardus5 joined the channel
#
Ricardus5 | ___
#
tantek__ gRegorLove's analysis makes sense to me
#
gRegorLove Could one of you make the proposal in #21?
#
gRegorLove Or I can get to it later.
#
tantek__ I like "I think the implied url update applied to photo would work" because it makes it easier to understand for web authors - same rules apply
#
sknebel https://github.com/microformats/microformats2-parsing/issues/21#issuecomment-415091509
#
Loqi [sknebel] Proposed resolution per IRC discussion right now: Following the example of #36, replace > if no explicit "photo" property, with > if no explicit "photo" property, and no other explicit `u-*` properties, and no nested microformats,
#
tantek__ great, let's get consensus on that proposal with thumb-ups etc., and someone can try it in a parser, I'll edit the spec
#
Zegnat thumbed-up
[grantcodes], [cleverdevil] and tasse26 joined the channel
#
tasse26 _____________________
[kevinmarks] joined the channel
#
[kevinmarks] I would expect that we are getting a lot of implied photos from WordPress because of the minimal hentry there.
#
tantek__ that makes no sense since backcompat = no implied properties
#
[kevinmarks] Oh, right. Nm then
#
Zegnat And because we don’t do implied property parsing on backcompat, we aren’t getting false positives from old templates either.
dougbeal|mb1, [pfefferle], marcoslater, KartikPrabhu, [jgmac1106], [chrisaldrich], ChanServ, [kevinmarks], [schmarty], iwaim, KevinMarks_, KevinMarks and barpthewire joined the channel
#
aaronpk oh great
[tantek], barpthewire, tantek__ and jackjamieson joined the channel
#
tantek__ alright then.
#
tantek__ wish Slack had a shortcut for deleting consecutive messages from the same person
#
aaronpk yeah :/ slack isn't really meant for public channels that might get spam
[kiai], koddsson, jackjamieson, [schmarty], gRegorLove, tantek__, tantek and KartikPrabhu joined the channel
#
gRegorLove Just noticed that implied photo bug affects Quill's and IBC's h-app: http://pin13.net/mf2/?url=https%3A%2F%2Findiebookclub.biz%2F
#
Loqi indiebookclub
#
aaronpk oh yeah
ChanServ and KevinMarks joined the channel