03:37 <ocdtrekkie> I've learned I hate making a makefile.

03:39 <ocdtrekkie> so allegedly I think the proxy should work with the go 1.11 that's in this package, but I get a tls version not supported when I try to build it

03:39 <isd> Oh, no the proxy probably doesn't work that far back.

03:39 <isd> That's like 3 years ago

03:40 <isd> No, 4-5 years

03:40 <isd> 2 releases a year, 1.20 is current

03:40 <isd> Where did you get 1.11?

03:40 <isd> Er, where did you get the notion it should work with that, rather?

03:41 <ocdtrekkie> Oh, the proxy said it needs go modules and a post said go 1.11 supported go modules.

03:41 <isd> 1.19 is current actually; 1.20 is due soon

03:42 <isd> Since then go-capnp started using generics, so I suspect it won't work with < 1.18

03:42 <ocdtrekkie> Yeah but I'm building a package from 2018 and trying not to break it too badly.

03:42 <ocdtrekkie> I have no idea what it currently uses Go for anyways, mind you. I guess I should look.

03:42 <isd> Yeah, worth checking.

03:43 <isd> Note that Go is really good about backwards compatibility; updating to a new version will probably not break anything.

03:43 <ocdtrekkie> But yeah, JJ did a whole Makefile setup in this thing. And I like the concept of not doing my own thing but I also hate this Makefile thing in particular.

03:44 <ocdtrekkie> I am really tempted to just go plaster the proxy stuff in build.sh and call it good.

03:59 <ocdtrekkie> That's what I'm gonna do. If someone wanted to make this repo look pretty, they'd start over anyways.

06:36 <ocdtrekkie> Okay! So I think I am 98% done adding the powerbox-http-proxy to WordPress... and it's gonna require a lot more work...

06:39 <ocdtrekkie> In theory, all I need to do is figure out where to embed the proxy JS file in WordPress to launch the powerbox request. But right now, the moment you launch WordPress, it's trying to make a call home for the news on the wp-admin panel... Clearly we don't want the app to ask to call home the moment you launch it, so I probably need to either only include the JS selectively on pages for functionality I want, or we need to tune down the call

06:39 <ocdtrekkie> home behavior.