Stefan Eissing

https://chaos.social/@icing

curl maintainer, protocol droid, likes to code.

"Nobody has any idea what is actually going on."

web: https://eissing.org
github: https://github.com/icing

Public Key

npub1uncykwynxpfvy27vnzns7xg74fnqu2ma7mg5hrxj75dmyzph6p0s28cvec

NIP-05 Address

icing_at_chaos.social@momostr.pink

Profile Code

nprofile1qqswfuzt8zfnq5kz90xf3fc0ry025esw9d7ld52t3nf02xajpqmaqhcprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hszrthwden5te0dehhxtnvdakq90r5v7

Publishing to

relay.snort.social

relay.damus.io

nos.lol

Author Public Key

npub1uncykwynxpfvy27vnzns7xg74fnqu2ma7mg5hrxj75dmyzph6p0s28cvec

Show more details

Last Notes

2026-10-18 07:39:39 UTC

The simple observation:
The #curl project is getting DoS‘ed by security researchers.
No mal intent, but driven by stock/work market evaluations.
Example: Aisle has shown its value by the curl CVEs claimed and was now bought by Cohere, presumably a good deal for both companies.
Economically reasonable behaviour for both. The FOSS projects are the roadkill, though.
All reporters have similar motivations, down to individuals improving their personal market value.

2026-08-30 06:49:19 UTC

If I get the suspicion that someone is slopping a #curl PR, I ask questions.
If they answer as human and explain their thoughts, this is fine. They used the LLM as a tool, but they are in charge of it. We review, they improve until it‘s accepted.
If their answer is likely from an LLM itself, we are dealing with a meatproxy („Apologies…“ etc). The chances of this PR landing become practically zero.
But I look at the idea behind the PR: was there one? Is it maybe worth doing in another way?