#LoqiIndieWebCamps are brainstorming and building events where IndieWeb creators gather semi-regularly to meet in person, share ideas, and collaborate on IndieWeb design, UX, & code for their own sites https://indiewebcamp.com/indiewebcamp
gRegorLove, miklb, Loqi and ben_thatmustbeme joined the channel
#unicyclic.com maledited /projects (+101) "/*Dobrado*/ Just noticed Github was mentioned here when it should refer to git, which also isn't really required (gitlab.com provide a download option which I've linked to)." (view diff)
#Loqivoxpelli meant to say: Would perhaps be an idea to add a bot to #indiewebcamp that repeats the move message, it's already fairly high up in the logs
#aaronpki wonder if Loqi would be more stable if he connnected through a bouncer
#GWGsnarfed, I don't know either. That is why I only disabled the post content generation in Micropub and figured I would do the rest in Post Kinds.
#snarfedGWG: what's the wordpress convention for plugins to be aware of each other like this? directly like you had? or through one plugin's filter/hook? or...?
#snarfed(also fwiw, google calendar is arguably more a paid service than a free service :P)
#tantekthe evolution of Twitter's failwhale, robots etc. is quite hilarious
#voxpellithat PHP memory issue is pretty tricky – to fully avoid it one needs to take available memory on server, subtract memory requirements from non-php processes, then divide by maximum needed memory needed by ones PHP script and set the server to never process more than that amount of PHP requests at the same time
#voxpellias "non-php" processes can sometimes be a MySQL-server there can be lots of joy
#voxpelliand with shared hosting the responsibility for doing the calculations is on the one building the one-size-fits-all hosting and they likely won't have taken your app into consideration
#voxpelliin conclusion: never ever ever run Drupal on shared hosting
#rMdesvoxpelli, that's only for drupal or wordpress (if on shared host) falls under the same issues (trying to find out what i can do for my shared-hosted WP sites)
#tantekuh, aaronpk could you migrate the spammers list from #indiewebcamp to #indieweb-dev too?
#gRegorLovevoxpelli: Thanks. Good information added to /PHP. I was thinking of summarizing instructions for how to handle those fatal errors more gracefully, like at least logging + not displaying the error message.
#voxpelligRegorLove: I think it's hard to manage them gracefully – the only more "graceful" way would be a full on white screen of death
#gRegorLoveIt doesn't fix the error, but gives a better UX
#tantekand frankly if WP *can't* be fixed, then that's a criticism too - that this is a non-fixable problem with WP
loic_m joined the channel
#voxpelliI guess the same is true for any cgi:ish servers (but not really sure, but the fact that you load and run your entire framework into memory for each and every request is pretty crazy in a way)
#voxpelliwas the thing I loved the most when I started moving from PHP to Node.js – that suddenly global data and code could be loaded once and shared between all requests
#aaronpkcourse that comes with its own problems too
#tantekvoxpelli: that sounds notable enough to note on the /node page
#voxpellitantek: well, it's true for any similar such language/system like Go, Rust, C etc as well – don't know how Python and Ruby fit into it though, maybe they can run as both?
#GWGsnarfed1, so far, no WordPress answer to whose plugin the plugin dependent code belongs in
#tantek.comedited /2016/homepage (+526) "deleting "too overwhelming" as that applied to before 7/4 homepage, been edited down a lot, drop To Do (no one else bothered), note have been working homepage simplification, analyze examples a bit" (view diff)
#GWGI would suggest that we open it up to the wiki but I am suffering from voting fatigue
#snarfedeither is fine with me, along with a comment linking to the (other) plugin
#tantek!tell gRegorLove,KartikPrabhu I resolved the issue you added to https://indieweb.org/2016/homepage#Issues could you take a look? Also advocating using GH issues for new issues (link at that link). Thanks!
#GWGsnarfed, my plan is that Micropub disable automatic post content generation if Post Kinds is enabled, but detecting the type of post and setting the fields for Post Kinds stay in that plugin.
#miklbGWG that makes sense to me from just following the conversation
#voxpellimiklb: thinking about maybe squashing the history of the main micropub repo – lots of nonsense commits in there (even totally empty ones to trigger redeploys)
#tanteksounds reasonable (good topic for #indieweb-dev)
#miklbvoxpelli by main you mean the one that is currently private?
#voxpellimiklb: exactly, I'm making some final touches to add an app.json and an Heroku button and will make it public after that
#voxpellimy empty commits with messages like "WOHO!" looks kind of – odd
#miklbcool. I should be able to copy over my changes if necessary to a new deploy if need be
#miklbvoxpelli yeah, do what you need to do to be able to make that repo public. My code is pushed to heroku, so until I needed to make a change it shouldn't be affected.
#voxpellimiklb: super, I'll get it done during tomorrow then
#bearperfect forward secrecy is a concept in cryptography where the loss of long term keys (think certs) does not compromise the session keys derived from those long term keys