lexbor VS utls

Project is deprecated in favour of the same developer's lexbor project[0].

[0]: https://github.com/lexbor/lexbor

It supports both CSS selectors and XPath like Nokogiri, but with separate engines - parsing and CSS engine by Lexbor, XPath engine by libxml2. (Nokogiri internally converts CSS selectors to XPath syntax, and uses XPath engine for all searches).

An HTML parser, probably the simplest relatively modern example I could find is 1MB https://github.com/lexbor/lexbor (haven't used it, but might look more into it now that I know it exists.)

Lazyweb link: https://github.com/rushter/selectolax

although I don't follow the need to have what appears to be two completely separate HTML parsing C libraries as dependencies; seeing this in the readme for Modest gives me the shivers because lxml has _seen some shit_

> Modest is a fast HTML renderer implemented as a pure C99 library with no outside dependencies.

although its other dep seems much more cognizant about the HTML5 standard, for whatever that's worth: https://github.com/lexbor/lexbor#lexbor

---

> It looks like the author of the article just googled some libraries for each language and didn't research the topic

Heh, oh, new to the Internet, are you? :-D

Lexbor is here: https://github.com/lexbor/lexbor

Well, regarding HTML5, what I've found was libxml (does not support tag-soup HTML5), https://github.com/lexbor/lexbor, for which I was unable to find good documentation ( see https://lexbor.com/docs/lexbor/#dom), Apache Xerces (appears to not support tag-soup HTML5 as well), and Gumbo, which does not appear to be active and to support selectors and XPath (although there are libraries that add that).

I think we've all (mostly?) tried it. It really is the Wild West of the web when you're trying to parse other people's HTML, though.

I've played around with this parser which is extremely quick. https://github.com/lexbor/lexbor

I’m glad to have the opportunity to contribute to an open-source project that is used by thousands of people. Hopefully, we will speed up Nokogiri (or XML parser it uses) to match the performance of html5ever or lexbor at some point in the future. 800 ms to extract data from HTML is still too much.

Does this offer any control at the TLS level? I have been looking for alternate TLS stacks for Go, and the only one I really found was uTLS:

https://github.com/refraction-networking/utls

Something that you'll run into for smarter anti-bot is that your JA3 tls signature will be checked. Easiest way to get around this is probably to use refraction-networking/utls. Especially true as go's tls signature is fairly unique.

Considering that the rocket league api isn't one of tracker.gg's listed apis, they probably enabled a lot of cloudflare'e antibot. If you really care to get around it, you can probably get fairly far with making sure you put the same headers as the chrome version you're trying to mimic. If that still doesn't work, then theres a chance that tracker.gg enabled ja3 fingerprint so you'd need to use a library like utls to fake your clienthello to look like chrome's.

do we have something like https://github.com/refraction-networking/utls but for rust?