I was not ready for that thread to break containment so hard, but I was especially not ready for people quoting it to think that (good kind) was my last name and I find that extremely charming.
@jonny I appreciate so much how you broke it all down. I’m not a developer and wouldn’t be able to understand the implications of the leak and what it showed. I love when people can translate things in ways that others can understand. Thank you. <3
@Meznor
That is so good to hear. I will be writing a more organized blog post this weekend and that is one of the main goals, to make it clear to people who are not locked in the dungeon with the vibe monsters all the time what it actually looks like
@jonny @Meznor I am particularly interested in this blog post version and would like to cite it, please toot the heck out of it
@jonny @Meznor
been following your posts from the inital ones - they're the most coherent info on why the code is so bad I've seen thus far. Thanks for sharing it with us.
@jonny it was a great thread :D
@Viss
It is not over (I just have to work, and I have to break it into a second thread because it is uh challenging our server to serve the whole reply tree). I estimate i've skimmed 10% of it and read 5%, and I haven't even gotten into the core agent and tool call logic, if one can call it logic. I am trying to do my due diligence so I can say "that thing right there is actually a mountain of diapers" from a place of knowledge.
@jonny @Viss I will say, the dopamine hit of seeing you reply with more messy screenshots was so good. I look forward to more of whatever you're willing to write about this tire fire.
@theorangetheme @Viss so the function-level mess is already bad enough, but from the glimpses i have seen about how the tools and agents are "orchestrated" it is actually such a bigger mess than i thought (and explains a lot of the totally perplexing errors i have gotten while using the thing) but that kind of library-level analysis takes time and i want to be responsible with my description of the code and do it right so it's not easy to discredit.

@jonny when the news broke i fetched like 2-3 zips from github, i havent uncompressed em yet, i hope i grabbed the right code. i heard there was some threat actor posting bullshit code for folks to try and run that would infect them.

absolutely crazypants that we're 'here' as infosec - attackers are now poisoning leaks and trying to do drivebys to pop researchers

@Viss i know, the chain of custody got broken almost immediately. the copy on archive.org went up quickly enough and was just the actual sourcemap and source, and archive.org isn't like a 'prestige' thing or the first place you would think of as an attack vector that i feel comfortable enough doing static analysis on the source. but yeah i am static analysis only there is no way you could get me to run this code for that reason lol.
@jonny @Viss If nobody can feasibly understand how the hell any of it works, what is the difference between that and "some threat actor posting bullshit code for folks to try and run that would infect them"?
@be @jonny thats actively happening already
@jonny
It was fun seeing it show up on a slack I'm on!
@jonny I've always been wondering, do you have an evil twin (who's also called Jonny)?
@dngrs hahaha this name is from awhile ago when i found another @jonny account on here it and it turned out they were a nazi and i was just like 'ok i do not want to be associated with the other bad kind jonnys necessarily i am a good kind'

@jonny

Complete aside: there was a terrible joke opportunity for you to label that first jonny as "jonny A" and then label yourself as "jonny B (good)".

Apart from that: thanks for the excellent analysis!

@dngrs

@aaribaud @dngrs
what a fool i have been!!!!!!!!!