M.K.

I researched a bit more about how to best pass proxy settings to the build process and found that doing it securely (not revealing proxy hostname and credentials in the...

It seems that the tarballs are expected in `/tmp/invidious-videojs-dep-install` and if I understand the crystal downloader correctly it will not currently accept any pre-existing file. I suggest we * skip...

> Invidious hasn't been designed for complicated network setups. Any file retrieval mechanism can fail for lots of reasons, so it's always good to have a way for users to...

I updated the opening post to reflect my current understanding of what would be a good approach. I'll try and make a PR that separates downloading from the checkusm validation,...

Thanks! I wasn't quickly able to merge it with the proxy support branch, but I'll try again later.

I agree that we should *not* ignore those errors. That's why I suggested a message that to me seems more productive. We can still include the backtrace in a `Technical...

> People don't care, they will still send a bug report anyway. Maybe. I wonder if you can measure and compare how many people have instead gone the route described,...

Can this be solved by loading a custom Promise library that supports long stack traces? IIRC bluebird advertized this as one of its features.

Then as I understand the original request, it is out of scope of this spec.

> tracking-down entry-point for http-requests. This sounds arbitrary and overly specific. Why should one special method of communication receive more attention than others, e.g. reading from standard input, or a...