Jackneill has quit [Remote host closed the connection]
<thoughtpolice>
gchristensen: Interestingly it was added to avoid curl hangs on macOS. https://github.com/NixOS/nix/commit/8215b75d36a6c60649dfc8721b8ddd44fbcf697c -- IOWs, my impression is that it was added to stop downloads that hung forever. So the extremely conservative numbers are just to detect hangs, eventually. I think bumping it to a lower limit is pretty reasonable.
<thoughtpolice>
"bumping to a lower limit"
ixxie has joined #nixos-dev
<gchristensen>
I'm sort of tempted to make it lowSpeedTimeout configurable, defaulting to the connectTimeout
<thoughtpolice>
Maybe like 1 byte over 1 minute. (Wonder what the TTFB latency on a satellite link looks like...)
<thoughtpolice>
lowSpeedTimeout being tuned lower and being configurable seems quite reasonable.
<thoughtpolice>
gchristensen: Though, actually, nix uses connectTimeout=0 by default, which means it uses curl's default
<thoughtpolice>
Which is actually... 300 seconds :)
<gchristensen>
yes
<infinisil>
Regarding docs, might be interesting to put Nix documentation in a tool like this: https://kumu.io/
<infinisil>
Getting away from the arbitrary linear structure they are in now
<simpson>
Example?
<simpson>
(I think that fancy ontologies are great, but I'm not sure what you're imagining.)
<infinisil>
The "packages" item there could link to the package listing
<infinisil>
The package listing could link to NixOS modules if they exist for a package
<infinisil>
And manual sections if they exist for the nixos module
<infinisil>
The "installing NixOS" section could link to a list of steps you could continue with
<infinisil>
Either with configuring for a server, or enabling a DE
<gchristensen>
I sort of think the one-page-ification of the nixos manual makes it appear linear when it doesn't need to be
<infinisil>
Yeah exactly, people won't read it from top to bottom, they'll just try to find what they need in it (and then probably want to know about related information)
<infinisil>
I don't think markdown is a good solution, but I think asciidoc or restructured text would be good candidates
<infinisil>
Probably tazjin just hasn't considered the different build targets for the docs
<gchristensen>
another important part is not having a massive build toolchain, since user machines often do build their own version of the docs
<gchristensen>
I'm poisoned of course, I don't mind docbook
<infinisil>
Slim dependencies are always nice
<gchristensen>
does this read well? The timeout (in seconds) for receiving data from servers during download. Nix cancels the download after this timeout without receiving any bytes.
<infinisil>
gchristensen: How about something like "How many seconds to wait until canceling a download that isn't receiving any more bytes"
<gchristensen>
that is a very complicated sentence :)
<timokau[m]>
I think the suggestion of markdown extensions (https://github.com/kjdev/hoextdown in particular was suggested) is interesting
<gchristensen>
how about The timeout (in seconds) for receiving data from servers during download. Nix cancels idle downloads after this timeout's duration.
ixxie has quit [Ping timeout: 245 seconds]
<infinisil>
gchristensen: Btw I mentioned the problem with shelling out to html in the thread