jonny (good kind)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.
Viss@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.
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 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.
unable to decrypt message