2018-07-24 UTC
# 00:02 snarfed ok, on to the next surprise in recent mf2py changes (eg in 1.1.1 vs 1.0.4):
# 00:02 snarfed when it parses this: <div class="h-entry">foo <a href="http://bar">bar</a></div>
# 00:03 Loqi [Tantek Çelik] microformats2 parsing specification
# 00:04 snarfed so weird. seems like it would result in a ton of false positives. for any post that doesn't explicitly include u-url, return any arbitrary link inside it?!
# 00:05 KartikPrabhu if you get this issue on parsing and it has consensus we can change it in 1.1.2
# 00:07 snarfed ok. i get that. just seems dangerous and unreliable in practice.
# 00:07 snarfed (support for minimalism totally makes sense for h-card. less so for h-entry, at least to me.)
[eddie] joined the channel
# 00:09 snarfed eh. very minor benefit in syntactic sugar from eliding the u-url class. major potential for false positives, eg when you change your markup and the permalink isn't the first link in the entry.
tantek__ joined the channel
# 00:11 snarfed even without known examples, i'm afraid to deploy this to bridgy, since if someone hits it, they'll start posseing posts that point to arbitrary other urls as the permalink, instead of their own original post
# 00:11 [kevinmarks] Well, part of cleaning up the mf tests repo should be getting rid of arbitrary cases in favour of real ones
# 00:13 [kevinmarks] Hm. There are classic feed cases that look like that though - where the permalink is elsewhere
# 00:13 KartikPrabhu aah, snarfed good point. there the u-url would be missing from the original post but some other post is linked too before?
# 00:14 snarfed ohhh i missed that this only happens when it's the *only* link in the h-entry. ok, i follow the intuition better now. that makes false positives seem much less likely.
# 00:17 [kevinmarks] (I generate more verbose markup but most of those posts have an external permalink in the u-url, with the local link on the star)
# 00:17 snarfed yup, those permalinks are at the end, but due to the "only link" rule, u-url wouldn't be implied, so no false positive
# 00:52 tantek I thought I already captured somewhere wanting to do the parallel rule for u-* as we have for implied p-name
# 00:53 gRegorLove It was mentioned in the implied p-name discussion, but not explicitly part of that proposed+implemented resolution
# 00:54 tantek yup we already had consensus on this for implied URL back at IWS 2016!
# 00:54 tantek "+1 consensus in the room at IWS 2016 (willnorris, gRegor, kylewm, tantek): do this for specifically for implied URL
# 00:55 tantek where "this" in context is: "I think it makes sense for u-url and can be easily added to the spec as e.g. ".h-x>a[href]:only-of-type:not[.h-*,.u-*]". Kylewm 00:46, 1 December 2015 (UTC) "
# 00:56 tantek not sure why I didn't make the edit to the spec at the time, probably just fell through the cracks :(
# 00:56 gRegorLove Cool. Might have been one of those items that missed getting the spec update. I recall another 2016-ish item like that
# 00:57 tantek this is why the spec still says: "Note: This specification is only marked as a "Draft Specification" because of pending edits from resolved issues before 2016-06-20."
# 00:58 tantek alright I'm going to make the spec change per the 2016 consensus resolution
# 00:58 tantek then if that needs further iteration we can iterate in 36
# 00:59 Loqi [Tantek Çelik] microformats2 parsing specification
# 00:59 Loqi tantek has 20 karma in this channel (463 overall)
# 00:59 Loqi gregorlove has 38 karma in this channel (263 overall)
# 01:05 tantek do we have a separate issue for implied u-photo?
# 01:08 Loqi [aaronpk] #21 reduce instances where photo is implied
# 01:34 Loqi gregorlove has 39 karma in this channel (264 overall)
# 01:35 gRegorLove I *think* that's everything from IWS 2016 updated in mf2-parsing now
# 01:41 tantek oh? guess I'll have to review all the issues!
# 01:45 tantek that's not too bad then. I thought I had a lot more work to do
# 01:47 gRegorLove I didn't double check the ones that explicitly say "spec updated"
# 03:13 KartikPrabhu this would be easier if every spec change came with a test case somewhere
[miklb] joined the channel
# 03:40 gRegorLove Oh, need to file one for implied u-*. We have an example of that.
# 04:07 Loqi [gRegorLove] #182 Fix parsing for iframe.u-*[src]
# 04:07 gRegorLove Those are the only two microformats-parsing updates from today
tantek__, KartikPrabhu, [snarfed], adactio, [pfefferle], [jgmac1106], snarfed, [schmarty], TallTed, taragon-pdx and [eddie] joined the channel
[cleverdevil] joined the channel
snarfed, [generativist], tantek__, [ryan339] and KartikPrabhu joined the channel; snarfed left the channel
# 19:25 sknebel I've got a current copy of the parsing spec ready if you need it?
# 19:28 Loqi [Tantek Çelik] microformats2 parsing specification
# 19:56 KartikPrabhu sknebel: ok the major objection I had is fine. Could you quickly add the comment before implied url and your PR is good :)
[joewillmott] joined the channel
[ryan339], jgmac1106 and [eddie] joined the channel
# 20:12 jgmac1106 hello all only used slack as I could never get #indieweb-microformats to work thx [KarthikPrabhu]
[kevinmarks], [generativist], tantek__, [jgmac1106], [cleverdevil], [eddie], hadleybeeman, dbaron, [chrisaldrich], strugee, dmcweeney and KartikPrabhu joined the channel