#GWGIt's not really a WordPress specific issue, which is why I brought it up in here
#GWGI'm wondering if annoying people about not running HTTPS is the right move for a Micropub endpoint
#GWGI suppose it is one step above disabling the plugin entirely if it isn't SSL
swordsmanz19 joined the channel
#GWGI'm wondering...does anyone only allow their Micropub endpoint to operate over SSL?
#sknebelI'd assume most people that don't have an HTTP version of their site don't
#sknebelsince the typical pattern is redirecting all HTTP request
jmac joined the channel
#sknebel+ the endpoint is what I declare on my site: if I put an HTTPS url there, then that's *the endpoint*, even if it technically would be reachable over HTTP no conforming client would try that
#GWGsknebel, do you think checking is a good move?
mblaney joined the channel
#sknebelIt's not really specific to micropub at that point. if you log in to the wordpress backend over HTTP that's just as insecure as micropub over HTTP
#sknebelso while I'd generally recommend HTTPS, and nowadays have little patience for providers not offering it, I'm not sure it fits for the plugin to loudly complain and it'd be a very low-priority thing for me to implement if it all
#eli_oatmy own endpoint is based off of that gist I shared...and despite my site working 100% as I'd like at the moment, I've been toying with re-writing it from the ground up :P
#eli_oatand looking for examples of different micropub implementations
Dave4, eli_oat, FrozenFox6 and [grantcodes] joined the channel
meme1, tafthartharath, AimHere14, ketas6, KanerixWolfe3, abrotman29, vdamewood, trqx18, walle303, lbft27, thurin4, [kevinmarks], Captain_Beezay, kepler_mach27, justanotheruser1, Vorpal11, Guest22027 and justyns joined the channel
#@pstuifzandI have added the `-verbose` flag to `ek`. This makes it possible to see the HTTP requests that are sent to the Microsub server and the responses that are returned. It can be a tool when creating your own Microsub server of client. https://p83.nl/p/880 (twitter.com/_/status/1030759224954040322)
mdk19, exezin3, jgmac1106_, Jguy, [metbril], [kevinmarks], [jgmac1106], casdr18 and jgmac1106 joined the channel
#NinjaTrappeurNice! I'm amazed by the whole indie-web chat based setup.
#ZegnatSo looking at that, it seems like the person making the post gets listed as the author on the h-cite rather than on the h-entry. That seems wrong to me.
#ZegnatThe author property on the h-cite (if supplied) should be the author of the outside page. The author property on the h-entry should be the person creating the post on lobstr.
#Zegnat(I hope that is the kind of feedback you are looking for.)
#NinjaTrappeurI see. Yes, thank you, this is exactly what I am looking for!
#ZegnatI think everything is contained in that div.details? So I would move thhe .u-repost-of and .h-cite onto the nested span.link element.
#ZegnatAnd the div.byline can probably be the .h-card. That way you can get the avatar marked up as u-photo for the author
#ZegnatThough... Hmm. Byline also contains the post timestamp. So that might make it impossible to mark that up :(
#NinjaTrappeurYup, that's the problem I had. Besides, the picture is 32x32px, it's maybe a bit small... I though using the link as an h-card was maybe easier.
#ZegnatSo it sends everything needed for the server (nginx/apache/etc) to response, this means the server can finish the entire browser-server back and forth, but it doesn’t stop PHP running yet and you can continue to run code.
iasai joined the channel
#ZegnatSo an HTTP request (e.g. a webmention) can start a PHP script, and the server response no longer depends on the PHP script being done.
#sknebelof course still keeps the worker process busy during that time
letty24 joined the channel
#aaronpkyeah, it's not a true backgrounding workflow, but better than keeping the browser connection open
leg, jgmac1106, mblaney and Iota8 joined the channel
#GWGI need to add auto-location retrieval for my posts. I had to go in afterward and do this, because my Micropub client doesn't yet support location. https://david.shanske.com/2018/08/18/2044/
#aaronpkmost Micropub apps probably won't handle it very well if the token expires tho, like Quill will show you the 401 error and then you have to know to log out and back in again.
change joined the channel
#GWGaaronpk: I was thinking of just putting in an admin ui button to expire tokens that haven't been used in a year.
#ZegnatIf someone is taking action to do it that sounds like revocation
#Zegnataaronpk, I realise that. I just mean that it seems fine to have the native UI revoke tokens, since the concept of revocation is known by anyone who reads the spec
#ZegnatPossibly more so than automatically expiring tokens
#ZegnatIt is true that from an app’s point of view, there isn’t really any difference though.
#aaronpkcould the mf2 parser be brought in by a different plugin that might make more use of it, and then the indieauth plugin could use it if it's there?
#GWGaaronpk: Post Kinds and Semantic Linkbacks already do
#aaronpkcool so you could just check for it and use if it's there?
#ZegnatHmm, aaronpk, webmention.rocks does not have a test case with <BASE> element? I just enabled coverage reporting on my endpoint discovery code and it told me that part of my code isn’t covered by any of the tests.
#Zegnat(I wonder what coverage reporting would say of the mf2 repo.)
#GWGPlugins are supposed to be self contained, but I suppose this is a decent compromise.
#aaronpkthese plugins all depend on each other already anyway
#aaronpkbut i think this is okay because it's essentially just an enhancement, not required for the core functionality