00:33 < bridge> hi 02:57 < bridge> Huh, he already left. I wonder what annoyed him so much to come back and create that issue 02:58 < bridge> :thonk: 02:59 < bridge> I’m guessing he doesn’t really have the right to rescind his contributions either due to the license. Sooo I guess nothing to be done about it 03:12 < bridge> He left 3 months ago exactly, because melon and ryozuki talked about rust. Didn’t hear anything from him through anyone at all either for 3 months. Then he shows up with that issue. Truly an enigma 03:41 < bridge> teedrama 03:41 < bridge> again 03:58 < bridge> Onlyfans leaks 03:58 < bridge> https://discord.gg/girls18q 03:58 < bridge> @everyone 04:06 < bridge> Onlyfans leaks 04:06 < bridge> https://discord.gg/girls18q 04:06 < bridge> @everyone 05:16 < ChillerDragon> @learath2 lawyer lerato could you explain how the license disallows withrading contributions? 05:17 < ChillerDragon> voxel seems upstet something else has to had happend other than people talking about rust. is he okay? :( 05:22 < bridge> Im 👌 so Close to Just commenting "i Use Rust btw" 05:23 < bridge> But Hes Not in His right state of Mind so i rather not 05:23 < bridge> (yet) 05:24 < bridge> Is everything he did really going to be deleted? 05:28 < bridge> Im still wondering what happened that He ended Up Like that, i remember looking at His Twitter and seeing enough Salt to replicate the ocean 06:52 < bridge> We all had that feeling, that the game was not moving forward, regardless of how much development went to the game itself. 06:53 < bridge> I think the main problem lies in providing community made contents, especially hq ones. We have great potential mods like Infection and Teeware, which in itself could be a unique game, separated from ddnet. 06:54 < bridge> Sadly making maps are also dependant on the community / creators and we somehow push these problems to ddnet devs, who themselves try to improve their own servers and adding gameplay ideas which are also provided by the community (latest being Konsti's weapon shields idea, with my design being contributed to). 06:55 < bridge> From that moment I realized, that you guys don't make more gameplay stuff in ddnet, cuz it would create more and more distance within what was originally supposed to be "ddnet". I get that now. 06:57 < bridge> But to either blame the devs for not making the game different... I would never do that if I were Voxel. 06:57 < bridge> But to either blame the devs for not making the game different... I would never do that if I were Voxel. We appreciate his work. 06:58 < bridge> But to either blame the devs for not making the game different... I would never do that if I were Voxel. We appreciate his work. (and sorry for the long messages.) 07:01 < bridge> Aint it more of a Github ToS thing? 07:53 < bridge> Anybody could verify my statement? Don't wanna make false statements, it would be gaslighting lmao 07:53 < bridge> https://github.com/ddnet/ddnet/issues/8127#issuecomment-2005980138 07:57 < bridge> Multeasymap 08:20 < bridge> good 08:20 < bridge> he is making drama out of nowhere 08:23 < bridge> also completly dishonest comment of the effort of all other devs they put 08:23 < bridge> i hate people like this 08:24 < bridge> https://www.zdnet.com/article/no-you-cant-take-open-source-code-back/ 08:24 < bridge> I mean Voxel is right, the community sucks ass and the developers waste their time doing useless things when it is obvious what this game needs. I dont want to complain about developers as they basically work for free but Voxel has a point 08:25 < bridge> the game has never seen so much new features as today, and as u said, nobody is getting paid, **you** are not **entitled** to anything here 08:26 < bridge> i think people heavily understimate the effort for someone to work on free projects besides their work and daily life 08:26 < bridge> yea, mostly useless features🤏🏼 08:26 < bridge> if you qant something, do it yourself first and foremost 08:26 < bridge> if you want something, do it yourself first and foremost 08:27 < bridge> This is the worst argument around. I didnt want to hurt your feelings little man, sorry for criticising the developers 08:27 < bridge> but you know... account system ;) 08:28 < bridge> Also battle pass would be nice 08:28 < bridge> And eeeh paid skins 08:29 < bridge> account system would solve 90% of the problems within the community 08:29 < bridge> its not the worst, its actually the beat 08:29 < bridge> best 08:29 < bridge> because you actually think are entitled to others work 08:29 < bridge> and that actitude should gain u a timeout at least 08:29 < bridge> I never said I was entitled to anything 08:29 < bridge> you dont have to say something to mean it 08:30 < bridge> receiving a timeout for stating an opinion? you should maybe touch some grass homie 08:31 < bridge> ok im not arguing with this troll further 08:31 < bridge> random 08:35 < bridge> Well all code is under zlib and zlib is perpetual. So while he can relicense his parts, he can't revoke our use of it under the original zlib conditions he first licensed it as. Atleast that's how I interpret it. I am not a lawyer 08:36 < bridge> I wonder so aswell but as far as I know no one really interacted with him after he left, so idk what might have went wrong there 08:42 < bridge> Community has always been the same, it is what it is. It's a niche old game with a community that puts heavy emphasis on nostalgia. 08:42 < bridge> 08:42 < bridge> On the developer side, the "useless things" are mostly maintainance, which is indeed not very visible to the users. But that's all any of us seems to have time for. Nothing much can be done about that, you can't tell someone what they should do with the free time they have, you can only gently nudge them. 08:43 < bridge> Heavy emphasis on backlash for new features xd 08:44 < bridge> even when i added telegun everyone was against it 08:44 < bridge> 2015-6 08:45 < bridge> but its also true u can't add new things willy nilly without thought 08:45 < bridge> because most devs are paaserbys and guess who end up maintaining those new features 08:45 < bridge> the same devs always are here 08:45 < bridge> the same devs that always are here 08:47 < bridge> There is also a lot of politics in adding new features, which I'm sure voxel realised on the very first pr they made. You need to please the right groups within the community to minimize outrage. 08:47 < bridge> 08:47 < bridge> Then there is internal developer politics. Every person with push access has different views on a lot of things. Which makes it hard to get (especially large features with many components like an account system) things through. No one is interested in writing thousands of lines of code just for it to be rejected or mostly having to be rewritten 08:49 < bridge> It's just a consequence of the way we went about structuring this project without any real hierarchy. Most other open source endeavors have a dictator that just pushes such things through 08:54 < bridge> Fwiw I wouldn't be completely opposed to just removing their contributions just to let them have a nice clean break as it seems the contributions are what brought them back. I was just stating the license technically allows us to keep it (as far as my interpretation of how licensing of source code works) 09:06 < bridge> i think its more a tantrum, something must be happening to him 09:06 < bridge> as far as i know no one is rly in contact with him here 09:06 < bridge> and im against removing the contributions if legally allowed to keep them 09:07 < bridge> which im sure we are 09:10 < bridge> Legal is one thing but the post really seemed like they were in some sort of distress. That's why I would consider it just to not add to their burden 09:10 < bridge> to me it seemed more like a kid throwing a tantrum but well i rly dont care much, do what you want xD 09:10 < bridge> also should think this might set a preceent for new contributions 09:10 < bridge> we should think about adding something to prevent this drama in the future 09:11 < bridge> also should think this might set a precedent for new contributions 09:11 < bridge> > I'm tired of having to be tied within development with this game 09:11 < bridge> its weird because 09:11 < bridge> i doubt ppl reach to him at all 09:11 < bridge> I don't think it's actually ambiguous but a CONTRIBUTING file that explicitly states that all contributed code is under perpetual zlib might be nice to just so future issues like this are very clear 09:11 < bridge> he seems to be coming back here on his own 09:12 < bridge> u can definitly also delete ur account 09:12 < bridge> he also has several ddnet-related forks and one source ddnet repo 09:13 < bridge> so he doesnt seem to be wanting to cut at all 09:13 < bridge> just being "annoying" 09:13 < bridge> I at the very least don't know of anyone that reached out to them about anything. Especially doubt anyone reached out about contributions since the rage cycle for those features ended a while ago 09:13 < bridge> yeah 09:13 < bridge> maybe he has an alt 09:13 < bridge> here 09:13 < bridge> and read something from someone 09:14 < bridge> i guess xd 09:14 < bridge> tbh this is just sad and the only thing i can think of is his life might be on some sort of bad phase 09:15 < bridge> stress at work or something 09:15 < bridge> depression 09:16 < bridge> If only you werent a rust and linux snob we wouldn't be in this situation 09:16 < bridge> xd 09:16 < bridge> i highly doubt its cuz me 09:16 < bridge> i know i can be annoying about it sometimes 09:17 < bridge> but if that affects you this much, idk.. maybe im not the problem 09:17 < bridge> Btw when voxel left you and melon were teasing me about rust, not them. We were all just joking around 09:17 < bridge> yeah 09:18 < bridge> thats why it was weird 09:18 < bridge> xD 09:18 < bridge> btw rust is adding C-string literals 09:18 < bridge> > 09:18 < bridge> > Reveal opaque types within the defining body for exhaustiveness checking. 09:18 < bridge> > Stabilize C-string literals. 09:19 < bridge> > Stabilize THIR unsafeck. 09:19 < bridge> > Add lint static_mut_refs to warn on references to mutable statics. 09:19 < bridge> > Support async recursive calls (as long as they have indirection). 09:19 < bridge> > Undeprecate lint unstable_features and make use of it in the compiler. 09:19 < bridge> > Make inductive cycles in coherence ambiguous always. 09:19 < bridge> > Get rid of type-driven traversal in const-eval interning, only as a future compatiblity lint for now. 09:19 < bridge> > Deny braced macro invocations in let-else. 09:19 < bridge> next update 09:19 < bridge> Aanyway, there isn't any use to speculating. They were clearly annoyed at something and it occupied their mind for 3 months after they left no-contact 09:19 < bridge> Finally some good features 09:19 < bridge> > §Stabilized APIs 09:19 < bridge> > 09:19 < bridge> > array::each_ref 09:19 < bridge> > array::each_mut 09:19 < bridge> > core::net 09:19 < bridge> > f32::round_ties_even 09:19 < bridge> > f64::round_ties_even 09:19 < bridge> > mem::offset_of! 09:19 < bridge> > slice::first_chunk 09:19 < bridge> > slice::first_chunk_mut 09:19 < bridge> > slice::split_first_chunk 09:19 < bridge> > slice::split_first_chunk_mut 09:19 < bridge> > slice::last_chunk 09:19 < bridge> > slice::last_chunk_mut 09:19 < bridge> > slice::split_last_chunk 09:19 < bridge> > slice::split_last_chunk_mut 09:19 < bridge> > slice::chunk_by 09:19 < bridge> > slice::chunk_by_mut 09:19 < bridge> > Bound::map 09:19 < bridge> > File::create_new 09:19 < bridge> > Mutex::clear_poison 09:20 < bridge> > RwLock::clear_poison 09:20 < bridge> core::net 09:20 < bridge> this means ip on bare metal 09:20 < bridge> https://doc.rust-lang.org/stable/core/net/index.html 09:20 < bridge> (core can be used without std) 09:20 < bridge> Is drain_filter stable yet? 09:20 < bridge> :justatest: 09:20 < bridge> Allah willing one day they will stabilize it 09:21 < bridge> i cant find it in std 09:22 < bridge> weird 09:22 < bridge> it should be there right? even as experimental 09:22 < bridge> https://doc.rust-lang.org/std/vec/struct.Drain.html 09:22 < bridge> vec drain method returns this iterator 09:22 < bridge> It may have gotten removed and/or renamed 09:22 < bridge> which has a filter method 09:22 < bridge> it all seems stable 09:23 < bridge> so u would do 09:23 < bridge> It's called `drain_keep_rest` now it seems 09:23 < bridge> x.drain().filter(|a| a.x) 09:23 < bridge> ah 09:23 < bridge> nightly 09:24 < bridge> @learath2 no 09:24 < bridge> its this 09:24 < bridge> https://github.com/rust-lang/rust/issues/43244 09:24 < bridge> extract_if 09:24 < bridge> Ah no, it's callee 3xtract_if 09:24 < bridge> there was some progress 09:25 < bridge> After 7 years, it got renamed, many progress 😄 09:25 < bridge> :owo: 09:26 < bridge> @learath2 is 18.1 out? 09:26 < bridge> ddnet web is not updated 09:26 < bridge> ah 09:26 < bridge> it was cache 09:27 < bridge> Cloudflare has been caching a little too aggressively lately 09:27 < bridge> @heinrich5991 is it maybe something you did? 09:27 < bridge> drama alert? 09:28 < bridge> discord highlight notification is at it again 09:28 < bridge> ? 09:28 < bridge> u were not highlighted i think xd 09:28 < bridge> ``` 09:28 < bridge> /var/tmp/portage/games-action/ddnet-18.1/work/ddnet-18.1/src/engine/external/json-parser/json.c: In function ‘new_value’: 09:28 < bridge> /var/tmp/portage/games-action/ddnet-18.1/work/ddnet-18.1/src/engine/external/json-parser/json.c:140:45: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing] 09:28 < bridge> 140 | value->_reserved.object_mem = (*(char **) &value->u.object.values) + values_size; 09:28 < bridge> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 09:28 < bridge> /var/tmp/portage/games-action/ddnet-18.1/work/ddnet-18.1/src/engine/external/json-parser/json.c: In function ‘json_parse_ex’: 09:28 < bridge> /var/tmp/portage/games-action/ddnet-18.1/work/ddnet-18.1/src/engine/external/json-parser/json.c:402:27: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing] 09:28 < bridge> 402 | (*(json_char **) &top->u.object.values) += string_length + 1; 09:28 < bridge> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 09:28 < bridge> cc1: some warnings being treated as errors 09:29 < bridge> [24/304] /usr/lib/ccache/bin/x86_64-pc-linux-gnu-g++ -DCONF_INFORM_UPDATE -DCONF_OPENSSL -DCONF_VIDEORECORDER -DGAME_RELEASE_VERSION=\"18.1\" -DGLEW_STATIC -I/var/tmp/portage/games-action/ddnet-18.1/work/ddnet-18.1_build/src -I/var/tmp/portage/games-action/ddnet-18.1/work/ddnet-18.1/src -I/var/tmp/portage/games-action/ddnet-18.1/work/ddnet-18.1/src/rust-bridge -O2 -pipe -march=native -mtune=native -flto=8 -Werror=odr -Werror=lto-type-mismatch -Wer 09:29 < bridge> ninja: build stopped: subcommand failed. 09:29 < bridge> * ERROR: games-action/ddnet-18.1::guru failed (compile phase): 09:29 < bridge> * ninja -v -j16 -l0 failed 09:29 < bridge> * 09:29 < bridge> * Call stack: 09:29 < bridge> * ebuild.sh, line 136: Called src_compile 09:29 < bridge> * environment, line 3365: Called cmake_src_compile 09:29 < bridge> * environment, line 1655: Called cmake_build 09:29 < bridge> * environment, line 1622: Called eninja 09:29 < bridge> * environment, line 2093: Called die 09:29 < bridge> * The specific snippet of code: 09:29 < bridge> * "$@" || die -n "${*} failed" 09:29 < bridge> * 09:29 < bridge> * If you need support, post the output of `emerge --info '=games-action/ddnet-18.1::guru'`, 09:29 < bridge> * the complete build log and the output of `emerge -pqv '=games-action/ddnet-18.1::guru'`. 09:29 < bridge> * The complete build log is located at '/var/tmp/portage/games-action/ddnet-18.1/temp/build.log'. 09:29 < bridge> * The ebuild environment file is located at '/var/tmp/portage/games-action/ddnet-18.1/temp/environment'. 09:29 < bridge> * Working directory: '/var/tmp/portage/games-action/ddnet-18.1/work/ddnet-18.1_build' 09:29 < bridge> * S: '/var/tmp/portage/games-action/ddnet-18.1/work/ddnet-18.1' 09:29 < bridge> ``` 09:29 < bridge> @learath2 lol i fail to compile 18.1 on my ebuild 09:29 < bridge> https://cdn.discordapp.com/attachments/293493549758939136/1219563237750865950/IMG_20240319_162841.jpg?ex=660bc1c6&is=65f94cc6&hm=13f370b91a0fda06b4bc427bbe7019c43a9c4865e8a125e5e4b8ab4f9457dc2f& 09:29 < bridge> I wonder why it was fine before 09:30 < bridge> Hm, I never get these. I guess it uses some activity metric 09:30 < bridge> I think you exaggerated a little here, there's different pov's and you clearly didn't get his. But I do understand Voxel, community sucks, and what he said about the dev's attitude is also not entirely wrong. Now don't get ME wrong, but it is what it is 09:30 < bridge> weird 09:32 < bridge> well i have a modern system 09:32 < bridge> i updated gcc 09:32 < bridge> and clang 09:32 < bridge> i think its using gcc 09:32 < bridge> gcc version 13.2.1 20240210 (Gentoo 13.2.1_p20240210 p14) 09:32 < bridge> Can you compile outside the ebuild? 09:32 < bridge> ok 09:32 < bridge> Just curious if it happens outside portage context 09:33 < bridge> ``` 09:33 < bridge> CMake Warning (dev) at cmake/FindMySQL.cmake:7 (exec_program): 09:33 < bridge> Policy CMP0153 is not set: The exec_program command should not be called. 09:33 < bridge> Run "cmake --help-policy CMP0153" for policy details. Use the cmake_policy 09:33 < bridge> command to set the policy and suppress this warning. 09:33 < bridge> 09:33 < bridge> Use execute_process() instead. 09:33 < bridge> Call Stack (most recent call first): 09:33 < bridge> CMakeLists.txt:511 (find_package) 09:33 < bridge> This warning is for project developers. Use -Wno-dev to suppress it. 09:33 < bridge> 09:33 < bridge> CMake Warning (dev) at cmake/FindMySQL.cmake:16 (exec_program): 09:33 < bridge> Policy CMP0153 is not set: The exec_program command should not be called. 09:33 < bridge> Run "cmake --help-policy CMP0153" for policy details. Use the cmake_policy 09:33 < bridge> command to set the policy and suppress this warning. 09:33 < bridge> 09:33 < bridge> Use execute_process() instead. 09:33 < bridge> Call Stack (most recent call first): 09:33 < bridge> CMakeLists.txt:511 (find_package) 09:33 < bridge> This warning is for project developers. Use -Wno-dev to suppress it. 09:33 < bridge> ``` 09:33 < bridge> unrelated but i also get this 09:34 < bridge> I guess we can move to `execute_process` if our minimum cmake version is a 3.xx nowadays 09:35 < bridge> doesnt seem to happen 09:35 < bridge> on my normal build 09:35 < bridge> wait 09:35 < bridge> /usr/lib/ccache/bin/x86_64-pc-linux-gnu-gcc -O2 -pipe -march=native -mtune=native -flto=8 -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing -fdiagnostics-color=always -fno-exceptions -Wno-implicit-function-declaration -MD -MT CMakeFiles/json.dir/src/engine/external/json-parser/json.c.o -MF CMakeFiles/json.dir/src/engine/external/json-parser/json.c.o.d -o CMakeFiles/json.dir/src/engine/external/json-parser/json.c.o -c /var/tmp/portage 09:36 < bridge> maybe its cuz cc cache? 09:36 < bridge> ima clean 09:36 < bridge> Yeah good idea 09:36 < bridge> Also maybe dont use ccache at all? 09:36 < bridge> Oh but ebuild was using it too 09:37 < bridge> <.< 09:37 < bridge> idk if my normal build used ccache 09:37 < bridge> it uses /usr/lib/ccache/bin/c++ 09:37 < bridge> so it should 09:38 < bridge> ``` 09:38 < bridge> ddnet on  master [$⇡] via △ v3.28.3 via 🦀 v1.76.0 09:38 < bridge> ❯ /usr/lib/ccache/bin/x86_64-pc-linux-gnu-gcc --version 09:38 < bridge> x86_64-pc-linux-gnu-gcc (Gentoo 13.2.1_p20240210 p14) 13.2.1 20240210 09:38 < bridge> Copyright (C) 2023 Free Software Foundation, Inc. 09:38 < bridge> This is free software; see the source for copying conditions. There is NO 09:38 < bridge> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. 09:38 < bridge> 09:38 < bridge> 09:38 < bridge> ddnet on  master [$⇡] via △ v3.28.3 via 🦀 v1.76.0 09:38 < bridge> ❯ /usr/lib/ccache/bin/c++ --version 09:38 < bridge> c++ (Gentoo 13.2.1_p20240210 p14) 13.2.1 20240210 09:38 < bridge> Copyright (C) 2023 Free Software Foundation, Inc. 09:38 < bridge> This is free software; see the source for copying conditions. There is NO 09:38 < bridge> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. 09:38 < bridge> ``` 09:38 < bridge> So it doesn't happen building free standing? 09:38 < bridge> ``` 09:38 < bridge> local mycmakeargs=( 09:38 < bridge> -DANTIBOT=$(usex antibot ON OFF) 09:38 < bridge> -DAUTOUPDATE=$(usex autoupdate ON OFF) 09:38 < bridge> -DCLIENT=$(usex client ON OFF) 09:38 < bridge> -DDOWNLOAD_GTEST=$(usex download-gtest ON OFF) 09:38 < bridge> -DHEADLESS_CLIENT=$(usex headless-client ON OFF) 09:38 < bridge> -DINFORM_UPDATE=$(usex inform-update ON OFF) 09:38 < bridge> -DSERVER=$(usex server ON OFF) 09:38 < bridge> -DTOOLS=$(usex tools ON OFF) 09:38 < bridge> -DUPNP=$(usex upnp ON OFF) 09:38 < bridge> -DVIDEORECORDER=$(usex videorecorder ON OFF) 09:39 < bridge> -DVULKAN=$(usex vulkan ON OFF) 09:39 < bridge> -DWEBSOCKETS=$(usex websockets ON OFF) 09:39 < bridge> -DSECURITY_COMPILER_FLAGS=OFF # Set by gentoo toolchain, see https://bugs.gentoo.org/888875 09:39 < bridge> ) 09:39 < bridge> ``` 09:39 < bridge> not to me 09:39 < bridge> ``` 09:39 < bridge> #!/bin/bash 09:39 < bridge> 09:39 < bridge> rm -rf build/* 09:39 < bridge> 09:39 < bridge> cmake -S . -B build/ \ 09:39 < bridge> -DCMAKE_BUILD_TYPE=Debug \ 09:39 < bridge> -GNinja \ 09:39 < bridge> -DVULKAN=ON \ 09:39 < bridge> -DDEV=ON \ 09:39 < bridge> -DMYSQL=ON \ 09:39 < bridge> -DCMAKE_EXPORT_COMPILE_COMMANDS=ON 09:39 < bridge> #-DDEV=ON \ 09:39 < bridge> 09:39 < bridge> ln -f -s build/compile_commands.json compile_commands.json 09:39 < bridge> ``` 09:39 < bridge> this is my build free standing 09:39 < bridge> ah 09:39 < bridge> maybe gentoo sets 09:39 < bridge> this warning! 09:39 < bridge> which should tell us its a bug (?) 09:39 < bridge> Could be, gentoo does add stuff 09:40 < bridge> It's inside an external library though. It'd be very annoying to fix 09:41 < bridge> I'm guessing it's not a union based variant, type punning like that I think is fine for the compiler 09:41 < bridge> No it does look like a union. Well idk I'll have to look at it later. I'm starving 09:42 < bridge> same 09:42 < bridge> time to get protein 09:42 < bridge> :justatest: :poggers2: 09:42 < bridge> I'll do carbs 10:33 < bridge> :justatest: :kek: :owo: 10:34 < bridge> I Use Rust Windows and Rust btw :feelsbadman:, i muss my nixOS 10:34 < bridge> I Use Rust Windows and Rust btw :feelsbadman:, i miss my nixOS 10:34 < bridge> I Use Windows and Rust btw :feelsbadman:, i miss my nixOS 10:34 < bridge> Windows detected, opinion discarded 10:34 < bridge> :pepeW: 10:35 < bridge> i always thought its [] detected, opinion rejected 10:35 < bridge> `windows detected, opinion rejected` 10:35 < bridge> I have no idea what the original is 10:35 < bridge> :angy: get your mei mei's right! 10:56 < bridge> @learath2 om 10:56 < bridge> omg 10:56 < bridge> i know why! 10:56 < bridge> i wanted to enable lto 10:56 < bridge> on gentoo 10:56 < bridge> and it recommended adding strict-aliasing warning 10:56 < bridge> to find possible lto incompatibilities 10:56 < bridge> -flto=8 -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing 10:57 < bridge> Btw strict aliasing is an issue for lto 10:57 < bridge> We should get a fixed version of the lib or patch it ourselves properly 10:57 < bridge> i mean thats why the flag is added right 10:58 < bridge> lto is broken on ddnet probs 10:58 < bridge> There is no guarantee it breaks 10:58 < bridge> but there is no guarantee its ok 10:58 < bridge> xd 10:58 < bridge> Exactly 11:16 < bridge> ryo what is the best way to communicate with a FIFO named pipe in rust? do i use ` tokio::net::windows::named_pipe` 11:16 < bridge> or do i use the winapi `interprocess::os::windows::named_pipe` 11:17 < bridge> ryo what is the best way to communicate with a FIFO named pipe in rust? do i use ` tokio::net::windows::named_pipe` 11:17 < bridge> or do i use the winapi `interprocess::os::windows::named_pipe` 11:17 < bridge> there is also `interprocess::os::windows::named_pipe::tokio` 11:36 < bridge> uhh idk i dont rly know much about windows 11:36 < bridge> but i would bet the tokio one is well maintained 11:37 < bridge> but if u dont use tokio use the other 11:44 < bridge> this kinda reminds me the godot is a scam bandwagon 11:47 < bridge> idk if something can be done about this: i just downloaded 18.1 and when i run it windows defender goes crazy and quarantines DDNet.exe as Trojan:Win32/Wacatac.B!ml but when i check it before running no detection and virustotal has 0 detections on that file as well. 11:47 < bridge> Only weird thing is that steam 18.1 has a different hash and can be run without windows defender freaking out, is the steam release build differently? 11:48 < bridge> Steam has no autoupdater. Which is what usually triggers defender 11:50 < bridge> it is possible for some virus to modify executables to turn them into trojans tho but i guess the virus would've been caught first in that case 11:52 < bridge> I guess you can check hash to make sure. Do we even put hashes on the website? 11:52 < bridge> ive been thinking about making a PICO-8 type of game "console"/"engine" thing but its just wasm reading / writing a specified memory layout. 11:53 < bridge> yes 11:54 < bridge> i couldnt find any hash info on the download page 11:55 < bridge> there is link to this file: https://ddnet.org/downloads/sha256sums.txt 11:55 < bridge> oh cool 11:56 < bridge> oh found it. im just bind 11:56 < bridge> oh found it. im just blind 13:10 < ws-client> its not even a false positive is it? auto updaters are viruses. Especially automatic updates are basically remote code execution coming from a server that could be compromised. 13:16 < bridge> omg thanks 13:17 < bridge> :owo: 13:32 < bridge> Windows defender triggers on practically anything 13:32 < bridge> It feels random 13:33 < bridge> You don't need to be making an auto updater to trigger defender, I assume valve signs/handles your code in some way beyond that so windows defender doesn't mess with it 13:33 < bridge> I think it's a protection racket scheme to sell signing certificates 13:33 < bridge> People call me a conspiracy theorist for saying but I seriously don't see another reason 13:52 < bridge> I like that conspiracy theory 13:54 < bridge> They might have a back channel that they submit binaries to get them whitelisted (doubtful). But I think we verified that they don't touch our binaries 13:56 < ChillerDragon> @0xdeen could i get you on irc once again this time itll be quick i promise 13:56 < bridge> <0xdeen> antivirus software for unknown malware is snake oil anyway 13:57 < bridge> <0xdeen> Absolutely 13:57 < ChillerDragon> marry me 13:58 < bridge> <0xdeen> If you can figure out that a software is malware, you can probably solve the halting problem too 13:59 < bridge> If windows defender was for "defending" it wouldn't be giving me fearmongering messages like this 13:59 < bridge> https://cdn.discordapp.com/attachments/293493549758939136/1219631376005988452/unknown-20.png?ex=660c013b&is=65f98c3b&hm=cfd914c4c67fb0409ad55acac888f79edd1c51fc570c20617105e6f197d469fe& 14:00 < bridge> It's great as a developer when your users get told you're a "remote attacker" making a "ulthar.a!ml trojan" to "execute commands" 14:00 < bridge> Whatever a ulthar.a!ml is 14:02 < bridge> The whole way it operates is completely opaque, sometimes it deletes the executables as soon as you download them 14:02 < bridge> Everything with it is a "dark pattern" 14:02 < bridge> I would 14:05 < bridge> Not to mention the resources it consumes, or more accurately **steals** 14:05 < bridge> This was my recent experience building GCC 14:05 < bridge> And yes, this is *after* I added those directories to the "exclusion" list 14:05 < bridge> https://cdn.discordapp.com/attachments/293493549758939136/1219632730871038044/IMG20240317192842.jpg?ex=660c027e&is=65f98d7e&hm=717671df21f9f5bcb76747f9fc30d087c294ffb402951a962bb3c022316564bc& 14:06 < bridge> Hot 14:13 < bridge> You might be able to heuristically through behavioral analysis. I can't think of any other way 14:14 < ws-client> the word heuristics got replaced by the buzz word LLM cool kids ask chatgpt these days if software is a virus or not 14:15 < bridge> Let's make LLMs illegal 14:15 < ws-client> There is an LLM for that 14:15 < ws-client> is the new there is an app for that 14:16 < ws-client>