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
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,
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.
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.
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.
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.
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.
[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.
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.
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.
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.
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