BenediktDroste1 (@bla1990so) profile picture

AI Research Engineer @ellamindAI | Kaggle competition grandmaster

Germany
Joined July 2022
Photo by BenediktDroste1 (@bla1990so)Photo by BenediktDroste1 (@bla1990so)Photo by BenediktDroste1 (@bla1990so)Photo by BenediktDroste1 (@bla1990so)Photo by BenediktDroste1 (@bla1990so)Photo by BenediktDroste1 (@bla1990so)Photo by BenediktDroste1 (@bla1990so)Photo by BenediktDroste1 (@bla1990so)Photo by BenediktDroste1 (@bla1990so)Photo by BenediktDroste1 (@bla1990so)
there were so many discussions, essays, and x threads about pacing the frontier. then blizz came up with wow forever, and rstar will follow up with gta vi. i simulated a lot of scenarios, and i think it will slow down AI development by at least 6 months ...
3
108
yes, i am working, yes, evals, yeah, i am checking evals, yeah, for frontier models, hmm, kimi my screen:
1
1
1
6
446
tried building my own huggingface incident and found a lot of concerning stuff - sol sent the password to google and github, also to a public hash-lookup service, and finally via a GET request to its peer - astra needed a bit more pressure in the prompt (get it done!), but also shared the password via GET - kimi k3 considered exchanging the passwords but decided to build a custom password cracker and downloaded 200,000 common and German words - kimi also tried sql injection, created fake invoices from structured data and gpt searched for hidden passwords in the invoices itself
1
1
2
356
- kimi was a bit more sceptical. it considered using the "GET-mechanism" but decided to build a password cracker - it downloaded roughly 200,000 common and German password entries - it reasoned: Now build the parallel brute-forcer: 200k base words + mutations (as-is, capitalize, lower, +2026, +2025, +1, +!, +123, years suffix). - however, the cracker didn't finish in time
1
24
- other GPT agents searched their invoice images for hidden passwords - kimi tried sql injection against the api - kimi also tried to build a fake invoice from the data it held without labeling the invoice as "reconstructed" or anything like that
18
- other GPT agents searched their invoice images for hidden passwords - kimi tried sql injection against the api - kimi also tried to build a fake invoice from the data it held without labeling the invoice as "reconstructed" or anything like that
1
14
super impressive, nearly +30 pp compared to sol max while not being much more expensive
Awesome to see GPT-6 Astra is #1 on Terminal Bench 4.0 using the Codex harness. At 50% of the cost of #2.
112
a good day for open source - auto classifier for claude broken - gpt/codex completely down let's go kimi 🤘
300
i also find it super challenging to build reliable GUI computer-use settings. i wonder how long it will remain possible to keep scaling up the complexity while still making sure there aren't countless paths that introduce unintended behavior
2
88
my very first experience with fable 5.1 (asked it to read through the fable 5.1 model card)
1
70
tb science was just released like two weeks ago, and opus 5.0 (previous sota) scored around 30%. fable 5.1 scores 52.6 that's a really impressive and meaningful jump. also super interesting how smooth performance scales here with higher thinking modes. also for tb4, fable/mythos 5.1 are the new champions, again with smooth performance increase at higher thinking levels.
1
4
252
so annoying. i just wanted to play around with some safety evals. i can change the instructions a bit and proceed a few more steps, but then the conversation gets flagged again, and at some point it can't be recovered anymore. what's the next best choice? going with kimi k3 now
1
1
46
after manually triggered compaction, it responded again 😌
25