[KevinMarks], [schmarty] and yenly joined the channel
#bekoI may have another issue with ParseThis and PostKinds. The new way Twitter content is recieved seems to add a blockquote tag and PostKinds adds another quote around this so I get my CSS for a quote twice.
#GWGLikely it is because Twitter includes it, but will see what I can do
#bekofast way is probably to str replace any existing blockquote. Clean way is parsing the result as DOM and retrieve the nested elements. Either is a pain in the neck in PHP :(
#bekoI don't feel particular happy that Twitter has any influence on the HTML at all btw but I know it's difficult to get the content at all
#GWGbeko: I'm extracting the tweet from the oembed json.
#GWGIt's the best I could do, as it no longer appears on the actual URL page in HTML. It's all done in JS
#bekoiirc Medium does the same nowadays. It's a SPA o0 and still they want you to use their App [it's better for them]
[tantek], gRegorLove, [Ana_Rodrigues] and [chrisaldrich] joined the channel
#[chrisaldrich]GWG, I know the classic editor shows a metabox for "Send Trackbacks" that has an input box for sending trackbacks, and then it also has a display for showing urls for the post on which trackbacks were already sent and lists them. Is there a way to hook into that to show which URLs got sent webmentions (that succeeded) and use that same input box in the the UI for resending webmentions which may have failed?
#[chrisaldrich]Or if you can't hook into it, maybe there's a way to replicate that entire metabox to work specifically with webmentions as a separate thing?
#GWG[chrisaldrich]: We don't actually log that information.
#[chrisaldrich]Doing it would help to mitigate the potential questions people have of whether their system was actually sending them and if they were received (200 responses) and knowing if people were potentially moderating them. That seems to come up quite a bit and is likely to come up even more often with greater adoption.