4 ms·
It looks like, if the website presents a cookie message, the tool just gets stuck on that and does not parse the actual content. As an example, I tried https:/
by old_dev 2y ago
It looks like, if the website presents a cookie message, the tool just gets stuck on that and does not parse the actual content.
As an example, I tried https://www.cnbc.com/ https://www.cnbc.com/ and all it created was a markdown of the cookie message and some legalese around it.
- jot 2y agoIt's not easy working around things like that. But here's how it could work: https://url2text.com/u/wYVake https://url2text.com/u/wYVake We were lucky to build this on a mature API that already solves loads of the edge cases around rendering different kinds of pages.