Matthias Endler

Where the cookies come from might be irrelevant to lychee. The scenarios you mention are out of scope for lychee itself and should be the user's responsibility. At least curl...

Oh, yeah I agree with that. Not sure if @egrieco meant that. lychee's cookie support will be very basic: manually set cookies, optionally accept cookies from websites. That's it. 👍...

Yeah, that's a known limitation of the current caching implementation. If a worker receives a URL that is also handled by a different worker but the URL is not cached...

Basic support for this will be merged together with #330. It provides directory support and will check `html` and `markdown` by default. We want to be a bit conservative in...

The question is if we also want to test the current directory when omitting the `.`. So ``` lychee ``` would be the same as ``` lychee . ``` I...

I thought about it and decided not to test the current directory when omitting the `.` and instead show the usage instructions.

With #330 being merged, `lychee .` will check all markdown and html files recursively by default. The missing piece to close this issue is to allow overwriting the extensions with...

Lychee can extract links from plaintext documents, so technically it could work with files like YAML or XML as well. Even files without an extension might be fine (e.g. `README`)....

Yeah, doing what ripgrep does sounds like a sane default. In the end, lychee is like a tiny ripgrep with a different objective. 😉 On the other hand I'm not...

To summarize: * [ ] Support overwriting extensions (`lychee . --extensions md,html,txt,json,yaml` would only check these extensions) * [ ] Check all text files by default. Do what ripgrep does...