@burak dunno what? Tromsø has no sunlight at all this time of year. They qualify even more!

@FlippoFlip it's there already if you just type it as "curl.exe" ...

I'm proceeding with libstacktrace (https://github.com/ianlancetaylor/libbacktrace) - there is also a package already in Debian. Seems do to the job for me just fine.

Thanks everyone!

now added to the #curl dashboard: https://curl.se/dashboard1.html#hackerone

@natkr I also suspect there's an unknown number of issues where people were tricked by an AI into reporting something but they report it manually so we don't spot the slop.

@pitch we ban everyone we deem have submitted AI slop and we state that clearly in our policy. It might have some effect, but the there are a lot of people in the world, and it is also easy for people to start new accounts.

the primarily problem with marking them accurately as slop or not is that reporters almost always refuse to admit their use, probably because they know we frown upon it. So we're forced to make judgement calls and that's not an easy thing.

Added a third data-point. AI slop is currently 3x more common than confirmed vulnerabilities. And I might still have missed to mark up a few ...