#pfefferleGWG I started rewriting some parts... I think we should start with a non hookable handler solution and implement it later... perhaps with the async part...
#pfefferlewhat do you think about the changes so far?
#GWGWell, the random delay asynchronous option is a good solution for the short term.
#pfefferleyes, and I am not a huge fan of live testing ;)
#pfefferlebut that makes it hard to debug, cause you have to deploy it with every change
#GWGLive as in on a site others can see or live as in on your own site? I test on a site that can be seen, but isn't my site. It's labeled as a test site
#GWGpfefferle, I think we are getting closer to a stable release though.
#pfefferleGWG I try to get the branch stable today or tomorrow... so that we can release a first version and start with the linkbacks stuff
#GWGpfefferle, I look forward to continuing to contribute.
#pfefferleGWG thanks for the initial rewrite! I like the switch to the API a lot!
#GWGtantek: Pingbacks didn't pass the source HTML so it could be used by a plugin when pfefferle wrote the original code. I was able to get that change into Core in a previous release, so we could do it.
#pfefferleGWG have you opened an issue regarding wp-json?
#GWGpfefferle: Anything else on your mind for the future? I know I always have a lot of things I'm trying to accomplish and hoping one or two of them work out.
#GWGI keep trying to slip things into Core, but I don't think I have momentum for a big change yet
#GWGI can't even get jorbin to proof my Make Core Pingbacks/Webmentions blog post
#pfefferleGWG for webmention: getting a stable release that matches the spec and supports async
#pfefferleGWG für SL: implement the new changes and support facepiles
#GWGpfefferle: Full async I think is a 3.1 thing. Basic async, the time delay one, is doable in 3.0
#GWGpfefferle: Re Facepiles...Look at the code I put in the Linkbacks proof of concept plugin with the comment walker. That design isn't bad for non-Facepile stuff as well.
#pfefferleah ok... you meant for 3.0? I would like to implement a stable API version that matches the spec...
#pfefferleGWG but it does not support grouping does it?
#GWGpfefferle: No. But you have to support grouping and non-grouping to accommodate people's themes.
#pfefferleGWG I started this branch with a basic implementation
#GWGpfefferle: I know we still disagree on the Walker idea. But either way, I think it will be better than what we have and support enhancements on top of it.
#GWGpfefferle: It doesn't have to be implemented using a walker. You can also use the comment callback option which is also commonly used. I was talking about the design.
#GWGThe domain is inline with the name or the date as opposed to being in the content, for example.
#GWGpfefferle: A problem with any possible solution.
#GWGIt is only safe to generate a Facepile if the theme doesn't show pingbacks/trackbacks/webmentions at all because you could end up with duplicate content.
#GWGThere has been a change in how notifications work that I pushed in and I may try to redo my Notifications implementation that makes the emails clearer with Semantic Linkbacks data.
#GWGAnd I want to fix some problems in my Location code.
#pfefferleGWG the indents, the indents .... tststs ;))
#GWGpfefferle: It is adding dynamically to the post content, not statically.
#GWGI considered having it do it statically, which is what snarfed does.
#GWGpfefferle: I just always think there is a better way to do things. I wanted to abstract the microformats properties more into the meta. But I need to revisit how they are stored/generated.
#GWGBasically, how do you add microformats to a post using post meta in WordPress is the bigger question to tackle. Because that can be adopted by multiple plugins interoperably.
#GWGAnd how do you work that into the WordPress Post UI?
#tantek.comedited /Planning (+479) "/* 2017 */ instructions, place holder subsections for current cities" (view diff)
#tantekSince we haven't seen any recent progress on planning DC or Florida, going to move those to 2017
KevinMarks joined the channel
#tantek.comedited /Planning (+123) "move DC and Florida to 2017 as more likely (unlikely in 2016, no recent planning done on them)" (view diff)
#tantekgRegorLove: do you have thoughts on how we can best archive past Planned IndieWebCamps?
#tantekI feel like it is helpful to capture the final state of how planning ended up for various cities, as that will likely provide information to help plan future IWCs in those cities
#aaronpkmaybe move each one to a page like 2016/Planning?
#tantek2016/Planning is planning for IndieWebSummit 2016