For anyone doubting the extent of the slop problem, Daniel is on Mastodon and is very open about the slop reports he encountered. He even tried to get input from other OSS maintainers about what could be done to reduce the cognitive burden when receiving such reports. The thing is, even if an AI slop report is easy to identify, it still takes several minutes out of someone's day to respond, wait for the submitter to retract their submission or double down, and THEN ban them, because that's their SOP on HackerOne. And that doesn't even include the cost of switching contexts. When you are likely to receive dozens of these per day, that's a significant portion of your time being wasted.