ec changed the topic of #elliottcable to: a ๐ฏ๐๐ ๐๐ ๐ฏ๐๐๐๐๐๐๐๐๐ ๐ฏ๐๐๐๐๐๐ slash sอฬuออpออeฬฬบrฬผฬฆiฬผฬoฬฬฌrฬฬ cฬอแปฅฬงอแธทฬกอลฃอฬ || #ELLIOTTCABLE is not about ELLIOTTCABLE
eligrey has joined #elliottcable
eligrey has quit [Quit: Leaving]
asecretcat has quit [Quit: let us connect our intestines and mutually digest]
asecretcat has joined #elliottcable
mylesborins has quit [Quit: farewell for now]
mylesborins has joined #elliottcable
<ELLIOTTCABLE>
joepie91: the `bhttp` documentation doesn't seem to actually document *how* to use an https agent in place of the default http agent?
<ELLIOTTCABLE>
the caveats section says โwatch out, do thisโ, and then the documentation for each method just points back to the caveats section ๐คฃ
<ELLIOTTCABLE>
joepie91: oh, and the highlight and then the URL the other day were unrelated
<ELLIOTTCABLE>
old habit in this channel, similar to old-school 4chan, I guess?
<ELLIOTTCABLE>
โqftโ, quote-for-truth: just copy-paste a message you agree strongly with, with no context.
<ELLIOTTCABLE>
kinda like an upvote or like or thumbs-up or w/e.
<ELLIOTTCABLE>
at one point the bot tracked that, lmao
<jfhbrook>
some hotshot node developer left me a broken PR with no description
<ELLIOTTCABLE>
jfhbrook: lmfao
<ELLIOTTCABLE>
โhere, haff codeโ
<ELLIOTTCABLE>
โthank plzโ
<jfhbrook>
yeah and I mean, while I wouldn't expect the guy to have the background it wasn't a change I casually wanted to make
<jfhbrook>
the maintainers of the mime package on node made a 2.0 that drops support for apache .types files
<jfhbrook>
meaning I'd have to drop support for them as well
<jfhbrook>
I guess I could dig up the parser from v1 and port it to a separate module
<jfhbrook>
or, y'know, someone could
<jfhbrook>
but they're patching 1.x still so I'm not in a hurry