- improved prompts with your feedback
- added post/comment shuffling to remove recency bias
- tried to fix the speech attribution errors in the xkcd
8,465 karma · joined June 23, 2019
Also made HN Wrapped (hn-wrapped.kadoa.com)
Happy to chat about data, AI, startups, or anything else: adrian@kadoa.com
- improved prompts with your feedback
- added post/comment shuffling to remove recency bias
- tried to fix the speech attribution errors in the xkcd
The xkcd should be saved and cached once generated, I'll look into the issue.
How would you improve saving?
EDIT: a retry worked. Enjoy: https://hn-wrapped.kadoa.com/jaggs
We’re automating web scraping at scale with AI. Web scraping used to be the same for decades (writing and maintaining rule-based scripts for each source), and we're fully automating that process with LLMs. We're also heavily focused on making ethical scraping the default (robots.txt checks, rate limiting, any custom compliance rules).
But we can't do it alone. We are looking for people who share our passion for software craftsmanship, data, and AI. We are growing fast, have a “no-bullshit” policy, and try to minimize the distance between the code you write and the customers who use it. We iterate to greatness :)
We're currently looking for a senior web scraping engineer: https://www.kadoa.com/careers/web-scraping-engineer
If that sounds like you, please email me at (adrian at kadoa dot com) and mention HN in the subject line. Ideally you include an ETL or scraping project you've been working on in the past.
We're somehow still stuck with CAPTCHAs (and other challenges), a 25 years old concept that wastes millions of human hours and billions in infra costs [0].
Why would I use a chat to do what could be done quicker with a simple and intuitive button/input UX (e.g. Booking or Zillow search/filter)? Chat also has really poor discoverability of what I can actually do with it.
We’re automating web scraping at scale with AI.
But we can't do it alone. We are looking for people who share our passion for software craftsmanship, data, and AI. We are growing fast, have a “no-bullshit” policy, and try to minimize the distance between the code you ship and the customers who use it.
We have openings for:
- Web Scraping Engineer: https://www.kadoa.com/careers/web-scraping-engineer
- Frontend Developer/UX Designer: https://www.kadoa.com/careers/frontend-dev-ux-designer
If that sounds like you, please email me at (adrian at kadoa dot com) and mention HN in the subject line.
The Swiss Air Force is regularly practicing starting and landing on highways: https://www.youtube.com/watch?v=wYkleF72du8
We’re automating web scraping at scale with AI.
But we can't do it alone. We are looking for people who share our passion for software craftsmanship, data, and AI. We are growing fast, have a “no-bullshit” policy, and are very execution focused.
We have openings for:
- Senior Software Engineer: https://www.kadoa.com/careers/senior-software-engineer
- Frontend Developer/UX Designer: https://www.kadoa.com/careers/frontend-dev-ux-designer
If that sounds like you, please email me at (adrian at kadoa dot com) and mention HN in the subject line.
It’s funny and occasionally scary
Edit: be aware, usernames are case sensitive
We're building AI agents for unstructured data.
80% of data is unstructured and traditional methods such as web scraping, PDF parsing, and manual data preparation require expensive engineering resources and constant maintenance.
We’re solving this at scale, but we can't do it alone. We are looking for talented people who share our passion for crafting exceptional software and data products.
We have openings for:
- Senior Software Engineer: https://www.kadoa.com/careers/senior-software-engineer
- Frontend Developer/UX Designer: https://www.kadoa.com/careers/frontend-dev-ux-designer
If you want to iterate to greatness and work at the intersection of data and AI, please email us at (adrian at kadoa dot com) and mention HN in the subject line.
So how will Cloudflare detect bots and get them to pay? And how many humans and legitimate bots will get blocked as a side effect? We're somehow still stuck with CAPTCHAs, a 25 years old concept that wastes millions of human hours and billions in infra costs [0].
How can we enable beneficial automation while protecting against abusive AI crawlers?
Since you were part of YC 21, could you share a bit about your pivots/product iterations you went through over the last 4 years?
So what are potential solutions? We're somehow still stuck with CAPTCHAS, a 25 years old concept that wastes millions of human hours and billions in infra costs [0].
How can enable beneficial automation while protecting against abusive AI crawlers?
I'll add a selection for different models soon.
Let me know what I should improve.
Kadoa is an AI platform that automates unstructured data ETL.
80% of data is unstructured and traditional methods such as web scraping, PDF parsing, and manual data preparation require expensive engineering resources and constant maintenance.
We’re solving this at scale, but we can't do it alone. We are looking for talented people who share our passion for crafting exceptional software products.
There is one official role, but we welcome conversations with anyone interested in joining the team.
- Frontend Developer/UX Designer: https://www.kadoa.com/careers/frontend-dev-ux-designer
If you want to iterate to greatness and work at the intersection of data and AI, please email us at (adrian at kadoa dot com) and mention HN in the subject line.
Good bots: search engine crawlers that help users find relevant information. These bots have been around since the early days of the internet and generally follow established best practices like robots.txt and rate limits. AI agents like OpenAI's Operator or Anthopic's Computer Use probably also fit into that bucket as they are offering useful automation without negative side effects.
Bad bots: bots that have a negative affect website owners by causing higher costs, spam, or downtime (automated account creation, ad fraud, or DDoS). AI crawlers fit into that bucket as they disregard robots.txt and spoof user agent. They are creating a lot of headaches for developers responsible for maintaining heavily crawled sites. AI companies don't seem to care about any crawling best practices that the industry has developed over the past two decades.
So the actual question is how good bots and humans can coexist on the web while we protect websites against abusive AI crawlers. It currently feels like an arms race without a winner.