09:10 <+bridge> https://github.com/0xdeadbeefnetwork/ssh-keysign-pwn/ :pepeW: 09:15 <+bridge> the bun rust pr 09:15 <+bridge> it got merged.. 09:15 <+bridge> lmao 09:24 <+bridge> bro 09:24 <+bridge> https://cdn.discordapp.com/attachments/293493549758939136/1504746262749253734/1.jpg?ex=6a081ba9&is=6a06ca29&hm=a37d5731d4ed9ad98d35d1faebbbda183f6d5c3999267dea314cadc6b1c9ce61& 09:24 <+bridge> https://cdn.discordapp.com/attachments/293493549758939136/1504746263231332423/2.jpg?ex=6a081ba9&is=6a06ca29&hm=c67dfc59daab1a403eea9aa9490da08c4670f23bd1ecbd2d15141af0ddf0df77& 09:24 <+bridge> https://cdn.discordapp.com/attachments/293493549758939136/1504746263810277418/3.jpg?ex=6a081baa&is=6a06ca2a&hm=2faeec346ae5b9bc85a1cdd8e777fb1fd792c3adf61ae775f595f32e6d08a639& 09:24 <+bridge> https://cdn.discordapp.com/attachments/293493549758939136/1504746264321851392/4.jpg?ex=6a081baa&is=6a06ca2a&hm=6987d2036d5fdd68a34737171970fa31962011f25ac7024358cda3f28dbaa025& 10:03 <+bridge> zig drama 10:07 <+bridge> also i guess bun is now 100% AI now 10:47 <+bridge> was about to post this 10:51 <+bridge> I now know how I hack lots of stuff with this exploit ;_; told my colleague who is responsible for the affected service 10:52 <+bridge> oh yeah this makes more sense if you chain this with a new RCE, like with nginx: 10:52 <+bridge> 10:52 <+bridge> https://depthfirst.com/nginx-rift 10:59 <+bridge> followup PR by the same person to remove zig code got marked as slop and closed: https://github.com/oven-sh/bun/pull/30680 11:05 <+bridge> did the video arrive on discord? 11:05 <+bridge> I created a fork of ddnet-insta and basically changed the welcome chat message :D 11:05 <+bridge> and now the bullets sometimes do not despawn when they hit a wall 11:05 <+bridge> i am so confused what happened here 11:05 <+bridge> ah gg matrix cant bridge media to discord anymore 11:14 <+bridge> im confused whats going on on that repo xD 11:19 <+bridge> oh it seems to be a release mode only bug 11:24 <+bridge> :justatest: 11:24 <+bridge> https://cdn.discordapp.com/attachments/293493549758939136/1504776461494648962/Screenshot_20260515-112324.png?ex=6a0837c9&is=6a06e649&hm=dc53814887c0d9c96030eae1a370ea2c0d75a84889effa104df6edfadf0dd951& 11:27 <+bridge> no video arrived, chillerdragon 11:35 <+bridge> Such a vibe coding disaster 11:42 <+bridge> Isn't this the creator of bun? Who decided the PR is ai slop? Did they not discuss any of this? 11:44 <+bridge> the PR description was edited by github-actions, did LLM decide that it was slop? xd 11:44 <+bridge> https://cdn.discordapp.com/attachments/293493549758939136/1504781491975225465/image.png?ex=6a083c79&is=6a06eaf9&hm=5052dd9a924bfb2c49de040ce05ae29c3fa6025818ee02929ec78e8019a7bf56& 11:44 <+bridge> Oh they have an AI running in github actions that automatically marks PRs as ai slop 😭 11:45 <+bridge> ok so the ai slop mark is actually double misleading 11:46 <+bridge> But he deleted the branch anyway? 11:46 <+bridge> https://cdn.discordapp.com/attachments/293493549758939136/1504781925926305922/image0.jpg?ex=6a083ce0&is=6a06eb60&hm=98ccc8dbd83a12ef1427d1dabbb9969081f71e9168d88dfe9cc0555fdcec0c7a& 11:46 <+bridge> Did the LLM submit this PR too early by accident? 11:48 <+bridge> wow 11:48 <+bridge> github bots 11:48 <+bridge> closed 11:48 <+bridge> I have thought that's added by the repo owner 11:49 <+bridge> closed a PR 11:49 <+bridge> I had thought that's added by the repo owner 11:50 <+bridge> Ok its not an LLM, if anyone adds the slop label the action runs automatically 11:50 <+bridge> So he marked it as slop himself to close it 11:51 <+bridge> OnSlop is epic 11:51 <+bridge> what the hell 11:51 <+bridge> they uses LLM to do everything for the project??? 11:52 <+bridge> lol 11:52 <+bridge> oh 11:52 <+bridge> whats going on with bun 11:52 <+bridge> bun is being fully vibe-coded yes 11:52 <+bridge> even before the rust port 11:53 <+bridge> bun is written almost entirely by that one guy so he can do whatever he wants mostly 11:53 <+bridge> Its his project 11:53 <+bridge> such a slop 11:57 <+bridge> Tbh it is probably too early for a 1m loc rust rewrite. If they waited 6 months the quality would be much better but if they build new patches on the barely working rewrite then they might regret it later 11:59 <+bridge> Shipping the first possible version of this seems unwise but it looks like they're doing it anyway 13:56 <+bridge> safe rust is probably safer with llms than zig 13:56 <+bridge> ignoring logic bugs etc 13:56 <+bridge> also i guess zig code is less frequent 13:57 <+bridge> but bun was kinda like a zig showoff its why i dont get it 14:00 <+bridge> currently the rewrite is 1 to 1 from zig code. which means if patterns are just unsafe rust rn 14:01 <+bridge> currently the rewrite is 1 to 1 from zig code. some patterns are just unsafe rust rn 14:03 <+bridge> from what i understand. it's just bun's toolchain rely on some zig modifications which is stuck in their own codebase to maintain cuz zig can not accept any bun contribution due their LLM usage. rust on the other hand just already have what they needed. 14:27 <+bridge> <6_svz> https://cdn.discordapp.com/attachments/293493549758939136/1504822408698400798/image.jpg?ex=6a086294&is=6a071114&hm=7fadbe0c2f8bb31d76e14417a151741c62988e37e22febcd9790c86b66bbda9c& 14:27 <+bridge> <6_svz> https://cdn.discordapp.com/attachments/293493549758939136/1504822409742520471/image.jpg?ex=6a086294&is=6a071114&hm=1c1b926c305ad027cb3fb1c71abbd302d359c8ff20d81165c47a01c2e7a541f8& 14:27 <+bridge> <6_svz> https://cdn.discordapp.com/attachments/293493549758939136/1504822410233512067/image.jpg?ex=6a086294&is=6a071114&hm=04c83828d8b2678e41987f739e80cc8fec7731dfc65f648cb69ee19b11192fb3& 14:27 <+bridge> <6_svz> https://cdn.discordapp.com/attachments/293493549758939136/1504822410866589756/image.jpg?ex=6a086294&is=6a071114&hm=2667477ef1b097eb8e098b9337eabb5f7f692bce108cc80fe33dcb99f8f79593& 16:43 <+bridge> feels like i've seen this before 😂 17:21 <+bridge> ChillerDragon: Hey, is the code running on `chillerbot-zx` in Multeasymap public? Specifically, the code to detect players freezing other players. 17:57 <+bridge> you can use https://github.com/swarfeya/teeworlds-library-ts 18:21 <+bridge> That code looks very interesting, but there's no detection to know who caused someone to freeze. I was more interested in the logic behind `chillerbot-zx` because it's a ranking bot for blocking, and I want to understand how it avoids rewarding the wrong players. 18:39 <+bridge> https://www.youtube.com/watch?v=07nDEFv9780 18:42 <+bridge> good channel 22:28 <+bridge> @drafakiller: it is not public. Hammerhit is tracked based on distance of the player to the hit event. And player hook targets are sent by the server directly. 22:28 <+bridge> 22:28 <+bridge> Why do you ask? 22:35 <+bridge> I was interested to know the exact steps so that I can repurpose to detect block in racing servers, maybe also improve it. I wanted to avoid targeting innocent players, and hopefully I could learn something about it with that. 22:35 <+bridge> 22:35 <+bridge> Does your detection only works with hammer? Does accidentally hooking a player that is already frozen changes the player who's responsible? Nuances like that. 22:38 <+bridge> I was interested to know the exact steps so that I can repurpose to detect block in racing servers, maybe also improve it. I wanted to avoid targeting innocent players, and hopefully I could learn something about it with that. 22:38 <+bridge> 22:38 <+bridge> Does your detection only works with hammer? Does accidentally hooking a player who is already frozen changes the player who's responsible for it? Nuances like that. 22:41 <+bridge> I was interested to know the exact steps so that I can repurpose to detect block in racing servers, maybe also improve it. I wanted to avoid targeting innocent players, and hopefully I could learn something about it with that. 22:41 <+bridge> 22:41 <+bridge> Does your detection only works with the last hook/hammer? Does accidentally hooking a player who is already frozen changes the player who's responsible for it? Nuances like that. 22:54 <+bridge> I was going to implement a naive solution to detect who's responsible for a player to get frozen but then realized it would go bad quickly. There's no reason for me to find solutions to a problem someone else already solved. 22:54 <+bridge> 22:54 <+bridge> How long between hooking a player and the player being frozen for it to count as responsible? If a player hooks another, does it count as being responsible if the player only freezes themselves by accident a while later? If distance is important, will it be able to detect throwing a player into a deep pit where there's only freeze at the very bottom? I imagine those are things you would have to think about when adding points to their ranks, and 22:55 <+bridge> I was going to implement a naive solution to detect who's responsible for a player to get frozen but then realized it would go bad quickly. There's no reason for me to find solutions to a problem someone else already solved. 22:55 <+bridge> 22:55 <+bridge> How long between hooking a player and the player being frozen for it to count as responsible? If a player hooks another, does it count as being responsible if the player only freezes themselves by accident later on? If distance is important, will it be able to detect throwing a player into a deep pit where there's only freeze at the very bottom? I imagine those are things you would have to think about when adding points to their ranks, and ther 22:57 <+bridge> I was going to implement a naive solution to detect who's responsible for a player to get frozen but then realized it would go bad quickly. There's no reason for me to find solutions to a problem someone else already solved. 22:57 <+bridge> 22:57 <+bridge> How long between hooking a player and the player being frozen for it to count as responsible? If a player hooks another, does it count as being responsible if the player freezes themselves by accident later on? If distance is important, will it be able to detect throwing a player into a deep pit where there's only freeze at the very bottom? I imagine those are things you would have to think about when adding points to their ranks, and there are 22:58 <+bridge> I was going to implement a naive solution to detect who's responsible when a player is frozen but then realized it would go bad quickly. There's no reason for me to find solutions to a problem someone else already solved. 22:58 <+bridge> 22:58 <+bridge> How long between hooking a player and the player being frozen for it to count as responsible? If a player hooks another, does it count as being responsible if the player freezes themselves by accident later on? If distance is important, will it be able to detect throwing a player into a deep pit where there's only freeze at the very bottom? I imagine those are things you would have to think about when adding points to their ranks, and there are 22:58 <+bridge> I was going to implement a naive solution to detect who's responsible when a player is frozen but then realized it would go bad quickly. There's no reason for me to find solutions to a problem someone else already solved. 22:58 <+bridge> 22:58 <+bridge> How much time between hooking a player and the player being frozen for it to count as responsible? If a player hooks another, does it count as being responsible if the player freezes themselves by accident later on? If distance is important, will it be able to detect throwing a player into a deep pit where there's only freeze at the very bottom? I imagine those are things you would have to think about when adding points to their ranks, and ther 23:03 <+bridge> I was going to implement a naive solution to detect who's responsible when a player is frozen but then realized it would go bad quickly. There's no reason for me to find solutions to a problem someone else already solved. 23:03 <+bridge> 23:03 <+bridge> How much time between hooking a player and the player being frozen for it to count as responsible? If a player hooks another, does it count as being responsible if the player freezes themselves by accident later on? If distance is important, will it be able to detect throwing a player into a deep pit where there's only freeze at the very bottom? I imagine those are things you would have to think about when adding points to their ranks with `chi 23:39 <+bridge> bro 23:39 <+bridge> https://cdn.discordapp.com/attachments/293493549758939136/1504961438899507260/1.jpg?ex=6a08e40f&is=6a07928f&hm=fad4f48bf56f28509ac2bc079b8ad533bc5775d4c8897ed9c0bade80fb626a7b& 23:39 <+bridge> https://cdn.discordapp.com/attachments/293493549758939136/1504961439276732546/2.jpg?ex=6a08e40f&is=6a07928f&hm=59e10897b45f4e1349ad9efb2d6e6af243d93cfb912b7d30c3195547959b474a& 23:39 <+bridge> https://cdn.discordapp.com/attachments/293493549758939136/1504961439662866563/3.jpg?ex=6a08e410&is=6a079290&hm=a56f3306a408739376eb88aba4fb5270687e5b2a606ffce088642a1ed28c241b& 23:39 <+bridge> https://cdn.discordapp.com/attachments/293493549758939136/1504961440015192275/4.jpg?ex=6a08e410&is=6a079290&hm=da5dfee6b46d8a0c5d9374ddc75e96858f048480f0078491c9b21557ae61f8c9& 23:54 <+bridge> apparently, they use wildly unsafe rust: https://github.com/oven-sh/bun/issues/30719 23:56 <+bridge> soo thats probably the only day i can solve, but 24 is quite the christmas score to archive xdd 23:56 <+bridge> 23:56 <+bridge> ```R 23:56 <+bridge> #!/usr/bin/Rscript 23:56 <+bridge> df <- read.delim(commandArgs(trailingOnly = T)[1], header = F, sep = "\n") 23:56 <+bridge> p1 <- 0; p2 <- 0 23:56 <+bridge> for (i in 1:length(df$V1)) { ifelse(df$V1[i] > df$V1[i-1], p1 <- p1 + 1, NA); } 23:56 <+bridge> for (i in 3:length(df$V1)) { ifelse(df$V1[i] > df$V1[i-3], p2 <- p2 + 1, NA); } 23:56 <+bridge> cat("Part 01: ", p1, "\n", "Part 02: ", p2, "\n", sep = "") 23:56 <+bridge> ``` 23:56 <+bridge> https://cdn.discordapp.com/attachments/293493549758939136/915539393358483476/meh.png?ex=6a08e5c1&is=6a079441&hm=6beead9ee78aa390b7860bb3cefdac8075e9a621a6478642dcf0dd6179fd0f97&