#arushI'm starting to think we may be able to blame Twitter and Facebook themselves for our webmentions not showing up. Just tested a couple with webmention.tech manually and they still don't show up, although they report as being received successfully.
#snarfedarush: i actually suspect your wm receiver isn't working at all. it's responding to the webmention POSTs by returning the post's HTML itself, which is a strong sign that your wordpress and/or the plugin itself are badly misconfigured
#snarfedKartikPrabhu: exactly, for the wm's target= param. that's how arush's server is interpreting it
#arushsnarfed: I see what you're saying. That does look like get.
#GWGYes, but I'm completely stumped as to how that happens.
#GWGThe only difference I've noticed is that arush.io doesn't use the pretty permalinks.
#arushgwg: No, it doesn't, and I've been meaning to go change that setting, but not sure why that would make a difference. This at least narrows things down a bit more though.
#arushAlso not opposed to exporting the content, nuking it from orbit, and rebuilding if necessary. It's just standard content and isn't reliant on any custom post types or custom fields.
#GWGarush: Also, I don't think Post Kinds could be the issue
#snarfedyup. GWG you have a clear repro case! try the same permalink format on your testbed, add a bunch of logging and have arush install that to see what it outputs, etc. lots of ways forward.
#GWGThat was what I was going to do. How do you clear the webmention cache? I have that test Twitter account.
tbbrown and benwerd joined the channel
#arushsnarfed: I don't think the content's the issue. It is, however, a long-existing WP install that's been through several migrations, and if it were reliant on a bunch of CPTs/custom fields it would make it more difficult to rebuild. Assuming the plugin isn't the problem it could probably use a rebuild anyway.
snarfed, gucci_meow, tantek, sl007, fzylogic_, barpthewire, deathrow1, gRegorLove, Pierre-O, cweiske, benwerd, jihaisse, friedcell, adactio and jeremycherfas joined the channel
#sebseloh, I blocked the ad, so I didn't see it. It used to have the first million digits of pi (says the text) but now he moved it to /index2.html and then to /index3.html and then to somewhere else.
benwerd, nitot, KevinMarks and leg joined the channel
#sl007Hello everybody - aaronpk Q: Wanted to implement the IndieAuth session logic to let login persist - but how can we invalidate that - let users log out from indieauth.com only means no possibility to self host and when we deliver a log out link to client_id there is no guarantee they use it …
#aaronpk1) treating an indieauth.com login as a session is probably not the best approach, since it was not designed to do that
#aaronpk2) remembering the user on future visits to indieauth.com and letting them click "approve" on login requests without re-verifying with a provider is useful
#aaronpkfor 2, you can have a "log out" link on the authorization screen, since the user will see the authorization screen on every request still.
#tantekaaronpk - the use case question is reasonable, however we can at least document the phenomenon since it is a (common?) existing publishing pattern
#aaronpktantek: i don't think it's required for salmention, because my comments display links to the original comment URL for each one
#aaronpkalso the wordpress situation is slightly different because those comments exist *only* as a comment on the site, not at their own URLs
#tantekA comment permalink is a permalink to where a [[reply]] is displayed as a [[comment]] on (in the context of) the original post that the reply is replying to, and supported by typical publishing systems such as [[WordPress]] and services like [[Blogger]].
#GWGThe first idea I'm exploring is that reply = comment.
#tantekGWG, sorta. a reply when syndicated to the post it is in reply to and shown there is a comment
benwerd joined the channel
#GWGtantek: In this case, reply = WordPress comment type 'comment'.
#tantekGWG, depends upon the context of that "reply"
#tantekif by "reply" you mean a reply coming from *some other site* via webmention to your WordPress site, then yes
#tantekif however by "reply" you mean, posting a "reply" *on* your WordPress site in reply to some other site, then no reply!=comment.
#GWGWordPress has a post type called post, and a comment type called comment. This gets nomenclature a bit confusing.
#GWGSo, comment types in WordPress built-in include 'comment', 'pingback', and 'trackback'
barryf joined the channel
#GWGIn order to display comments determined by Semantic Linkbacks to have the property in-reply-to...Semantic Linkbacks changes the type from webmention(a custom type), to comment, a built-in type
#tantekit sounds like new comment types were added not because they were semantically different, but people needed a hook in storage for doing things differently
#GWGBut this was over a decade ago, hard to track what the discussion was at the time.
fzylogic_ joined the channel
#GWGBut, fast forward to this decade, when, to match pingback and trackback, pfefferle declared webmention as a comment type.
cweiske joined the channel
#tanteksure, seems logical given that pattern, but if the history itself was hacks of convenience, then it doesn't make sense
#GWGBut declared like, favorite, bookmark, etc. as metadata attached to a webmention comment type.
#tantekI think your intuition of trying to treat received webmentions more like native "comments" (e.g. in how they're displayed etc.) makes sense
#GWGExcept for the exception of, if a reply, changing the comment type to comment.
#tantekGWG, it may make sense to declare all of those as "comment", since even the others are responses that should have fallback summary text that could work in comment form
#GWGSo, the only one that is established is reply maps to native 'comment'. So, I want to implement that in Webmentions.
#GWGI think about this stuff a lot, I just don't have enough time or influence to proceed sometimes.
barpthewire joined the channel
#GWGBut likely I'll be trying to see how I can move some of the infrastructure over to the Webmentions plugin before I bring over the parsing. Because the issue is if the current infrastructure scales.
#GWGRemember, this is a system where the source URL for a pingback, trackback, and therefore webmention is stored in a field called comment_author_url.
#tantekheh. classic here's a URL field, let's just re-use it for some other URL
#GWGtantek: I've done my research. Just trying to figure out how to address all this stuff and on what level
#amz3I read design first, format protocol later :)
#GWGOf course, some things developed in the community have turned into W3C recommendations.
#aaronpkamz3: several of us are in that W3C group :-)
#GWGaaronpk: As someone in both, is my summary accurate in your opinion?
[chrisaldrich] and sl007 joined the channel
#amz3you know I've been dealing with database NIH syndrom, for some reasons I've been build a EAV database on top of a logic "language"
#amz3it's not incremental at all! And outside the 'developer to developer' market, it's really difficullt for me to understand what other people would like to use
#arushYay! Webmention problem solved. Now I just need to find out if there's a way to submit them in a batch so I can resubmit all the ones that were missed.
#GWGarush: The version with the URL encode/decode fixed it?
#arushgwg: No, but that will probably fix it for some. What fixed it is excluding the webmention endpoint from casche.
#arushNot sure why that's the case, but there it is.
#arushI haven't updated to the latest version of the plugin but I have a WordPress install on the same host that I will test it on since on that setup the endpoint isn't excluded from casche.
#arushgRegorLove: Me too. I like being able to post status updates on my own site and then have interactions come back in from social media and other places.