KartikPrabhu, [Raphael_Luckom], [chrisaldrich], [tw2113_Slack_] and [tantek] joined the channel
#[tantek]nice! its first 1.x release presumably? congrats!
[Rose], KartikPrabhu, [Raphael_Luckom] and [jgarber] joined the channel
#[jgarber][tantek] Thank you! It is indeed the first 1.x release for this gem.
#[jgarber]I took a controversial approach to _not_ parse classic microformats so it’s not gonna be a tool to suit everyone. But, I wanted to challenge myself and see what I could make.
[Murray], iwaim, [chrisaldrich], [jgmac1106], [KevinMarks] and [tantek] joined the channel
#[tantek]I think it'll work great for common IndieWeb use-cases, without any need for fallback parsing like that.
[Rose] joined the channel
#KartikPrabhualso, mf1 parsing can be added as a separate thing. In mf2py it was much simpler to have it as a "separate" code
iwaim and mauz555 joined the channel
#[tantek]sort of. I'm pretty sure the parser relies on knowing *where* classes/properties came from (whether backcompat or not), not just renaming into equivalents
#[tantek]so you can't really do a "pre-processor" as it were, without parsing both the mf1 and mf2 anyway and that point you've already done all the work
#[tantek]jgarber++ great job and nice README too. made a couple of minor suggestions if you like! (pull request)
KartikPrabhu, [Raphael_Luckom], [spieper] and [jgarber] joined the channel
#[jgarber][tantek] Thanks! I’ll give your PR a look later today.
[jgmac1106], [chrisaldrich], mauz555 and [KevinMarks] joined the channel
#[KevinMarks]The python backward compatible parser does look for specific classes (and rels) and adds mf2 classes accordingly. I was able to use it as a remapper for silo markup by adding to that data structure