#aaronpksnarfed: I've started using the value that comes back in from the token endpoint as the ID which lets you type stuff like "xyz.withknown.com" in the web sign in box and have the server return an ID of xyz.withknown.com/username
#KevinMarksif genius sent webmentions, that would be intereatsing
KartikPrabhu joined the channel
#KartikPrabhuKevinMarks: yeah that does look really really bad
singpolyma joined the channel
#aaronpkthat is tough, anyone can do anything with your content once it's online. but i feel like it's disingenuous to copy not just the quoted snippets but the full article *plus* the whole layout of the site, making it look like something she supports
#KartikPrabhuyeah that is part that is bothering me too
#KevinMarkswell, they present ti as a browser plugin adn WP plugin too
#KartikPrabhuand it does not load icons and avatars for some reason
#aaronpkalso what? genius.it redirects to genius.com which is "Genius is the world’s biggest collection of song lyrics and crowdsourced musical knowledge."
#LoqiSalmentions are a protocol extension to Webmention to propagate comments and other interactions upstream by sending a webmention from a response to the original post when the response itself receives a response (comment, like, etc.) https://indiewebcamp.com/salmention
#kylewmre; time for Known to get a queue, is this a use case for Amazon SQS? like a hosted service where I can send events, and it would dequeue them and send them back to my site as POSTs to a given endpoint
#kylewmit's a PITA because apache and nginx handle it differently
#kylewmso like when I try to do teh export, I always get a Gateway Timeout
#aaronpkthat's not actually going to be fixed by using wp-cron or another method that runs the queue via POST request, since you'll still be limited by that timeout
#aaronpkit's more like the super long-running jobs need to be rewritten to perform their tasks incrementally and in a way that can be resumed part way through
#gRegorLoveYes, PHP can keep executing after the page is delivered. That's how the "lazy cron" works in ProcessWire and the PW Webmention plugin uses it for async
#KevinMarkswhat I was thinking is that you could have a queue endpoint that you post to, it returns and keeps executing, and you then exit
#aaronpkthat only works if the task takes less time than the nginx/apache timeout
#aaronpkand in the case of nginx with php-fpm, it's actually nginx that's hanging up, not php quitting on its own
#KevinMarksI'm assuming PHP yields when waiting on network etc here, whcich may not be right
#aaronpk"gateway timeout" means nginx didn't get a response from the backend in time, so even if php is letting itself run forever, nginx will give up
#kylewmaaronpk: really interesting point about wp-cron, i hadn't thought of that
#aaronpkbut yes step 1 is going to be rewriting anything that runs >30 seconds to be able to run in smaller pieces on multiple requests
#aaronpkodds are async webmention verification won't take 30 seconds, so you can get away with the lazy cron approach for that
#kylewmand if you hit the cron every five minutes or something, then a big job could take a really long time
#aaronpkyeah but if you run it on every request like wp-cron it would go faster
#KevinMarkswhen testing salmentions with acegiak I had to turn up appengine's timeout from 5 seconds as sometimes fetching her posts was blocked by the feedreader task running
#KevinMarkswp-cron assumes you have a lot of requests
#KevinMarksthough I suppose if you POST and then load the posted page you're guaranteed at least one
#kylewmaaronpk: does nginx actually kill the thread before it's done executing, or just stops waiting for it to return a response?
#bearnginx will close the socket which should cause php-fpm to kill the process and recycle it
#bearto make sure your php has time I would use php-fpm pools and have one pool with a longer request_terminate_timeout and then configure nginx to set the pool for a location to the higher threshold one
#bearnginx is acting as a normal proxy so it will always just close the socket for a send/read timeout
#kylewmi'm thinking maybe the way forward with Known is to continue to do things like POSSE and PuSH and webmentions synchronously by default but add hooks so that a plugin could offload those tasks to a queue instead
#bearIMO known should always allow for sync processing because the average person will not want to work with a job queue
#kylewmi just want to have a way to experiment first ya know
#bearand if the code for doing a job is exactly the same but called from different entry-point helpers... then it's a total win IMO
#kylewmbear: do you think background jobs should be triggered by a long-running background process totally outside of the request/response world, or triggered by a POST?
#[shaners]!tell gregorlove: Yeah. I need to build up the redirects feature in Dark Matter better to handle the new URL scheme. (I’ve dropped the nth of day bit from my paths.)