Markus Unterwaditzer

IDK and I don't care. Have my approval for checkoff.

@cmr You didn't mention that those concerns were theoretical, I thought that there was a concrete use case (the Rust standard distribution).

Would there be a possibility to throw arbitrary types onto Context as well, in the style of `request.extensions`? Right now I would need to serialize data to JSON and back....

you are talking past each other @Seirdy @lebensterben It's without a doubt possible to generally redistribute lychee under the AGPL without requesting permission from the contributors. The MIT license requires...

A third, probably not very useful, option not mentioned: it'd be possible to put lychee's usage of check-if-email-exists behind a compile-time feature. If that feature is disabled, the resulting binaries...

if it's in a subcrate but you still have that subcrate as dependency, the AGPL violation just becomes less direct. I would recommend to drop this functionality.

I think we can build this into html5gum and it's going to be easier than html5ever (because I'm more familiar with the codebase), but if we go with the external-stream...

>@untitaker would filtering by CSS selector still be within the scope of html5gum? Would be nice if elements could be filtered out as early as possible to avoid unnecessary allocs....

@MichaIng there's no conceptual difference between html5gum tokenizer and html5ever tokenizer. outside of the tokenizer however, html5ever contains a full DOM tree builder while html5gum does not. You're entirely correct...

> Excluding code blocks and pre elements is now done by default. the next version of html5gum will include an option to not parse the `` tag inside of ``,...