05:35:09 <321bob321> this why we need closed sauce. So we dont see the CVE 05:53:39 @321bob321: That only work if your the only one with the binaries. 05:54:10 Now you can just throw binaries to some clanker and wait for some... results 05:56:29 That limit closed source usefulness to only online service backend. 05:56:29 Freeware that are not important in the grand scheme of thing and are not related to online shit 05:56:29 And stuff you made for yourself.. 05:56:29 pretty much 05:57:32 Closed source might allow more time for the patch to "disclose" the vulnerability but at this point it's only a question of time. 05:57:57 <321bob321> i think cal.com used that excuse to go closed sauce 06:03:57 It might help if they are the only one running the code. 06:03:57 But if it was opensource before then people already have the old code, I don't think they updated all the code since switching to closed source. And they have an opensource version (cal.diy). Are they sharing code between cal.com and cal.diy? 06:06:45 If you can get the binaries, you don't really need to know how to reverse engineer stuff anymore to do it... https://github.com/morluto/rea . 15:44:22 This repo got so popular that even non-technical people I know have heard of it 15:51:55 it would suck to be a maintainer look at how many issues are created per minute 💀 15:52:25 however thankfully it's AI that maintains it 15:52:59 maybe that's what anthropic meant about replacing git lmao 15:55:00 A lot of large companies have their own things besides Git 15:55:17 Meta has Sapling, Google has Piper...