#GWGThe Parsing is better integrated than ever. But I had to do some minor hacks to get it to work properly with the existing code, which I will now need to clean up
#miklbGWG any suggestions on how I can move the syndicate-to function in micropub to fire later in the chain? It seems like it is being sent before the `wp_insert_post with args` does
#miklbI confirmed with snarfed that bridgy isn't getting the mf2 when it gets the webmention. So reading through the code and my debug log, that is what I've come up with
#miklbI understand scratching itches but rewriting a plugin and leaving it as "works for me" and moving onto something else seems counterproductive. Which is how I feel this whole micropub situation stands
#miklbunless you want to back burner micorpub 2.0 and which case I'll switch to 1.4.3 and work out my kinks there
#GWGmiklb I am not back burnering Micropub. I am still trying to figure out how to isolate the problems. Some people have them and some don't.
#GWGThe next question is how to add better error output
#GWGI wish I knew what the problem was to be honest.
#miklbok, so there are some isolated auth issues that we havent' tracked down, but the IndieWeb WordPress community has a plugin that recommends a suite of plugins. A user installing that and the suite of plugins is going to expect interoperability. Getting those plugins ready too is as important IMO. I get that you and pferrele don't use all of the plugins, but they still should be tested and updated. That's what I'm doing,
#miklb but you don't seem as interested in those issues.
#GWGThe new version integrates better into WordPress, but that doesn't mean anything if I doesn't work
#GWGmiklb, you mean the Bridgy issue or the markup issues?
#miklbI haven't been able to auth with Omnibear with any version of micropub/indieauth so for me it's an outlier, but seeing almost identical error coming from chrisaldrich and OYS does concern me
#miklbbut I wonder considering how micropub issues were still sporadic with the 1.x version if releasing 2.0 would get more data for those fringe issues and also help by having the media endpoint out there. I know aaronpk has been anxious for the new version for a while.
#miklbbut I wouldn't want to release 2.0 until it was interoperable with the recommended plugins, what ever that list is.
#GWGWell, for Post Kinds, I would release a filter change concurrent with the Micropub push or before
[eddie] joined the channel
#miklbwe are asking peolpe to test 2.0, it would be nice to also provide beta versions of any plugins that interact with micropub to be functional. Telling folks they need to checkout my fork or a PR is a barrier.
#miklbI mean, I'm cool breaking my site testing. I'm not normal though
#miklbbut truth is, right now, for what I have working, all of my IW plugins are installed from github repo with multiple remotes and hotfix branches.
#miklband again, I'm all about scratching itches. That's ultimately what I'm doing. I want to be able to reply to a note in Indigenous and it syndicate back to Twitter. That's broken, and what I'm trying to get working on my site.
#GWGGood point. Since I merged some new code into Master in Post Kinds, let me finish some fixes, merge what I am working on, do a release with that and the filter change that will work with both versions and release a new intermediate version.
#GWGI had that itch and the Twitter part got less itchy.
#miklbwhich is cool. If you said you weren't going to update the bridgy plugin and was removing it from the IW plugin, I'd totally understand and would work on a new plugin.
#miklbwould you consider not working with 2.0 beta of micropub a bugfix?
#miklbtruth is, when I can reply via micropub to a tweet I'll actually use Twitter less. There are just some folks that I have on a private list that I've turned into a feed that is already hooked up to microsub. I'd like to be able to still interact with them as they aren't leaving Twitter.
#miklband our we sure the problem is in bridgy and not in micropub firing the syndicate-to too early?
#GWGI don't think I ever tested replying though, to be honest
[chrisaldrich] joined the channel
#[chrisaldrich][keithjgrant] I've just tested the newest version of Omnibear with micropub's stable v1.4.3 and it works (though I'll also say I'm using the master branch of IndieAuth from github, which may possibly be a factor for some testing things).
#[chrisaldrich][keithjgrant] one UI piece that is quirky for me is the space separated tags, as in WordPress I have several tags/categories that use multiple words (and thus have spaces). Comma separated tags would thus be more useful.
[keithjgrant] joined the channel
#[keithjgrant]Good to know. I've considered making that input a little more intelligent than a simple text input
#[chrisaldrich]I also love the fact that there's a bookmark now!
#GWGAs well as the comments made about issues with Micropub posting bookmarks
#GWGBut I will release a version before getting to any of the post kind additions I had planned in order to have a version that includes the filter change.
#GWGOut of the mf2 post class because it isn't part of the post object.
#GWGI am trying to build in post type discovery to address it.
#GWGWorst case, the fetch function moves to Kind View so it isn't inside the mf2 post class
#GWGI don't want kinds to be a dependency of mf2 post because I am trying to make it part of the Parse This piece I want to be able to separate and include someday in other projects.
#GWGAs the most extensive user of Post Kind templates I know, I would want to ensure yours was working.
#GWGBeyond that, this version sees the retirement as announced of the Kind Meta class
#miklbI am using the default templates currently save for adding a reply kind and changing to using `u-url`
#miklbthose are in my fork of the plugin right now.
#miklbI'm still testing out 2016 and the fork of uf2 plugin.
#GWGI will be fixing the default templates. Enhancing in next version
#miklbbut that gets to my point GWG. We need a stable base line before introducing new features which invariably lead to new issues. All the parsing improvements in the world don't help if we do discover the the syndicate-to is firing too soon and not sending the data.
#GWGThat's why I am stopping what I am doing in enhancements to work on compatibility
#miklball of the plugins are tied together. So everything being in alpha/beta all the time we never even are sure what version anyone is running when reporting issues
#GWGI need to get data storage fixed l, which is why I am still finishing the parsing work