00:05 <+bridge> <fokkonaut> @essigautomat Do you have an opinion on a "projectile hammer"?
00:05 <+bridge> <fokkonaut> I implemented redirecting any projectile with hammer hit, it's really fun and can be combined with tele grenade or gun too. Works solo and coop (after someone else redirected the projectile it always excludes that character from intersecting).
00:05 <+bridge> <fokkonaut> 
00:05 <+bridge> <fokkonaut> I can imagine some cool parts with this, but this feature would require a new map.
07:55 <+bridge_> <dontmila> mm
08:19 <+bridge_> <bamcane_tee237> I guess we need to optimize the client sixup
08:19 <+bridge_> <bamcane_tee237> join a local 0.7 server and you can get at least 6 ms latency
08:37 <+bridge_> <chillerdragon> It rebuilds the snapshots. If that got 6 times slower with the rust rewrite the sixup client might notice it
08:46 <+bridge_> <chillerdragon> That sounds rude. It took me quite some time to finish the 0.7 support it had high priority in my life for multiple years and when it landed hammering did work. Some other change not under my control broke it I assume. Also I still was active after it got merged and felt responsible for all 0.7 bug reports and fixed them within days.
08:46 <+bridge_> <chillerdragon> 
08:46 <+bridge_> <chillerdragon> But you are right I am currently not contributing to ddnet anymore as I am waiting for my prs to get merged first.
08:52 <+bridge_> <Assa> @comebackplay please work through some "How to write a good github issue guide" <https://blog.shakiltech.com/best-practices-for-using-github-issues/> or <https://oboacademy.github.io/obook/explanation/writing-good-issues/>
08:52 <+bridge_> <Assa> 
08:52 <+bridge_> <Assa> "bug with practice" is not a good title for example. I don't want to discourage you writing issues, but I want them to become cleaner - respectfully!
08:52 <+bridge_> <chillerdragon> Ah it indeed is caused by Heinrich’s rust rewrite. @fokkonaut you really can’t blame me for that -.-
08:52 <+bridge_> <chillerdragon> 
08:52 <+bridge_> <chillerdragon> Please don’t be so rude your comment did hurt me .\_.
08:53 <+bridge_> <milkeeycat> :feelsbadman:
08:59 <+bridge_> <triki> sorry but idk what is it, thats why i cant properly name it. cus i no idea what happens at all, its just dont work.
08:59 <+bridge_> <triki> and also its not only about naming title.
08:59 <+bridge_> <triki>  so u dont understend issue?
08:59 <+bridge_> <triki> sorry but idk what is it, thats why i cant properly name it. cus i no idea what happens at all, its just dont work.
08:59 <+bridge_> <triki> and also its not only about naming title.
08:59 <+bridge_> <triki>  so, u dont understend issue?
09:00 <+bridge_> <Assa> I do understand the issue, but this is a general problem across multiple of your issues
09:09 <+bridge_> <triki> so its cus im not a dev. sorry
09:10 <+bridge_> <triki> how i can explain the problem if i dont understend how it work?
09:10 <+bridge_> <triki> if i knew how it work i can fix it by my self.
09:10 <+bridge_> <triki> ofc i tried the best when explain with my knowledge.
09:11 <+bridge_> <triki> ofc i did my best to explain using my knowledge.
09:11 <+bridge_> <triki> ofc i tried my best to explain using my knowledge.
09:14 <+bridge_> <triki> also understand the issue so its mean all good.
09:16 <+bridge_> <triki> also г understand the issue so its mean all good.
09:16 <+bridge_> <triki> also u understand the issue so its mean all good.
09:17 <+bridge_> <qxdfox> you should put something more descriptive than "Bug with practice"
09:19 <+bridge_> <qxdfox> ddnet deletes files now?
09:19 <+bridge_> <qxdfox> fire
09:21 <+bridge_> <triki> i put screens or waht u mean?
09:24 <+bridge_> <qxdfox> the label should give you more info than that so you dont have to click on it to know what its actually about
09:27 <+bridge_> <chairn> probably some environment difference
09:56 <+bridge_> <fushi_gg> if you are using cfgs you should probably tell what they do since nobody can reproduce your scenario without it
09:56 <+bridge_> <Assa> 1. Your title should be saying enough information, that you know what this issue is about - your current title is very broad and ambiguous, it can be mistaken with other issues
09:56 <+bridge_> <Assa> 2. Describe the problem in detail, there were an issue where you didn't describe what this is about in the first place
09:56 <+bridge_> <Assa> 3. Give us all the information so we can reproduce the problem, ideally steps to reproduce. In the last issue you were talking about some binds not working, but you just didn't give us the binds, why not?
09:56 <+bridge_> <Assa> 4. Describe what you did expect as a result
09:56 <+bridge_> <Assa> 5. (Optional) What did you try to solve the problem? Did you find a workaround?
09:56 <+bridge_> <Assa> 
09:56 <+bridge_> <Assa> This is not a conclusive list, maybe not even ideal, but it helps developers like A LOT, it makes my job easier and gets potential bugs fixed fast
09:56 <+bridge_> <Assa> exactly
09:59 <+bridge_> <jxsl13> Sending 0.7 love
09:59 <+bridge_> <Assa> You are writing so many issues and I am sure you'll write more (which is fine), and you could be an even greater help for us if you make the quality better 🙂
10:05 <+bridge_> <jxsl13> https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository might make sense to add that to the repo
10:11 <+bridge_> <heinrich5991> which `i32`? 🙂
10:13 <+bridge_> <heinrich5991> as a contributor to open-source projects, I don't like issue templates
10:18 <+bridge_> <jxsl13> what is your solution to the problem of having (probably) non-tech people opening vague github issues.
10:18 <+bridge_> <jxsl13> see above.
10:18 <+bridge_> <jxsl13> without someone having to cleanup after people opening such prs.
10:18 <+bridge_> <jxsl13> without someone having to cleanup after people opened such prs.
10:19 <+bridge_> <heinrich5991> I prefer that to having them not open issues
10:19 <+bridge_> <heinrich5991> i.e. I prefer the status quoe
10:19 <+bridge_> <heinrich5991> i.e. I prefer the status quo
10:22 <+bridge_> <bamcane_tee237> I think not every open source project you can contact the team in discord or something else.
10:23 <+bridge_> <heinrich5991> I believe the opposite: most open-source projects have a communication medium that's not github alone
10:24 <+bridge_> <jxsl13> but they did open an issue.
10:24 <+bridge_> <jxsl13> what now?
10:25 <+bridge_> <jxsl13> assa is seemingly cleaning up afterwards, which probably is not what Assa wants to do :/
10:33 <+bridge_> <Assa> I already proposed this, but this was blocked by other maintainers - which I also understand, as we don't want to discourage anyone from writing issues
10:35 <+bridge_> <Assa> I am a maintainer, so I see it like a bit of my "job" to have a look at issues and moderate them a bit - yes I could spend this time on reviewing or writing PRs, but sometimes I need something to take my brain off
10:44 <+bridge_> <Assa> @comebackplay you now named the issue "something changed my files", I now renamed it to "Server seems to change configuration options", "files" is ambiguous, "something" is ambiguous
10:49 <+bridge_> <triki> look like u dont understand the problem. 
10:49 <+bridge_> <triki> next issue where i dont know what happens, i will drop just with "bug".
10:50 <+bridge_> <triki> or even better just dont create issue.
10:51 <+bridge_> <Assa> "something changed my files" is so ambiguous on a modern operating system, this could mean literally anything
10:54 <+bridge_> <heinrich5991> it'd be nice if you could spend some more time thinking about a good title
10:54 <+bridge_> <bamcane_tee237> that's right
10:56 <+bridge_> <qxdfox> I didn't mean to offend you
11:02 <+bridge_> <triki> the problem is in this case i dont know what title it need, cus i dont know what happens.
11:02 <+bridge_> <triki> Last few weak night build always crashed and have big bugs. 
11:02 <+bridge_> <triki> i catch 2 of them. 
11:02 <+bridge_> <triki> smth with graphic and smth with network.
11:02 <+bridge_> <triki> 
11:02 <+bridge_> <triki> I still dont know what title is good for this.
11:02 <+bridge_> <triki> and i see only 2 way 
11:02 <+bridge_> <triki> 1 didnt create issue at all
11:02 <+bridge_> <triki> 2 report about problem, but not "professional"
11:02 <+bridge_> <triki> 
11:02 <+bridge_> <triki> if u dont wanna issue from random guys, why u allowed that?
11:03 <+bridge_> <triki> i dont think its server issue, its swapping more likely swaping issue. but im not sure
11:03 <+bridge_> <triki> https://cdn.discordapp.com/attachments/293493549758939136/1496073976126898186/image.png?ex=69e88ef7&is=69e73d77&hm=a955c544a883ca7004275b037c4f26406ca16502d098d7190fbf857af95a3bbd&
11:04 <+bridge_> <triki> i dont think its server issue, its more likely swaping issue. but im not sure
11:04 <+bridge_> <triki> https://cdn.discordapp.com/attachments/293493549758939136/1496073976126898186/image.png?ex=69e88ef7&is=69e73d77&hm=a955c544a883ca7004275b037c4f26406ca16502d098d7190fbf857af95a3bbd&
11:05 <+bridge_> <triki> The problem is that I don't know what the title needs because I don't know what's happening.
11:05 <+bridge_> <triki> The last few night builds have always crashed and had major bugs – I caught two of them: one with graphics and one with the network.
11:05 <+bridge_> <triki> 
11:05 <+bridge_> <triki> I still don't know what title is appropriate for this, and I can only see two ways:
11:05 <+bridge_> <triki> 1) Don't create an issue at all.
11:05 <+bridge_> <triki> 2) Report the problem, but not in a "professional" way.
11:05 <+bridge_> <triki> 
11:05 <+bridge_> <triki> If you don't want issues from random people, why did you allow that?
11:05 <+bridge_> <bamcane_tee237> As the #12079 closed, then I edited the words here:
11:05 <+bridge_> <DDNet> https://github.com/ddnet/ddnet/issues/12079
11:05 <+bridge_> <bamcane_tee237> We have got a quicker development with less new features than few years ago.
11:05 <+bridge_> <bamcane_tee237> I still remember how the community suprised as the new HUD came out.
11:05 <+bridge_> <bamcane_tee237> tbh, I think we should solve those important issues more instead of doing some typo fix PR.
11:05 <+bridge_> <bamcane_tee237> the developement stick in the loop of minor refactor, and doing some Rusting that don't have a such improvement.
11:05 <+bridge_> <bamcane_tee237> and the accepted new features made smaller difference than what we did before. It's really upset to see that some mod-relevant things being closed or left because our maintainers and contributors don't have a same idea to do it.
11:05 <+bridge_> <bamcane_tee237> btw, I think a mod-relevant PR has to be discussed by the community modders instead of someone else.
11:07 <+bridge_> <Assa> I wrote that I explicitly want you to write issues and don't want to discourage you, but at least try to make them a bit more professional, I believe you are smart enough to do so 🙂 Like issues should not be "entertaining", we don't need to have a cliffhanger in the title "You don't believe what the ddnet client did to me" as an example. I know it can be hard to create good titles especially if you have trouble describing the exact problem
11:08 <+bridge_> <triki> i dont try clickbait at all.
11:10 <+bridge_> <triki> i dont try clickbait at all.
11:10 <+bridge_> <triki> I’m describing the problem in such broad terms not because I want to clickbait, but because the problem could be caused by anything.
11:19 <+bridge_> <aegisub> try to put yourself in the position of somebody who runs into the same problem and wants to see if there's already an issue about it. In that case, what keywords would you search the issue list for? A good issue will contain these keywords in the title to help other people find your issue.
11:39 <+bridge_> <triki> I don't think that will work in this case because the problem could be anywhere, and anything could break.
11:39 <+bridge_> <triki> I didn't even realize at first that the voting issue and the inability to teleport in Invincible
11:39 <+bridge_> <triki> were the same problem.
11:39 <+bridge_> <cellegenrih> "bug with practice" sounds the same as "a gun that is loaded" xd
11:41 <+bridge_> <cellegenrih> "best application at opening github issues"
11:41 <+bridge_> <cellegenrih> there, good title or smth
11:42 <+bridge_> <jxsl13> as heinrich pointed out to me, it would probanly be good to reach out to the devs in here in order to get help with deciding on the title and content of the issue.
11:42 <+bridge_> <cellegenrih> wait, not "application" as a software :kek:
11:43 <+bridge_> <jxsl13> as heinrich pointed out to me, it would probably be good to reach out to the devs in here in order to get help with deciding on the title and content of the issue.
11:44 <+bridge_> <cellegenrih> 2/3 of this sentence is a red flag given the previous events
11:45 <+bridge_> <jxsl13> what happened?
11:46 <+bridge_> <cellegenrih> just a typical dev to dev drama
11:46 <+bridge_> <jxsl13> some ppl need to work and can't read and write in discord all day 🔥
11:47 <+bridge_> <cellegenrih> tldr, Kebs went away due to receiving no response to his concerns on a PR (heinrich's security rewrite)
11:47 <+bridge_> <jxsl13> that one I know of.
11:47 <+bridge_> <jxsl13> the one that's seemingly less robust.
11:47 <+bridge_> <cellegenrih> Yeah, so that kinda sucks
11:47 <+bridge_> <cellegenrih> When you see
11:48 <+bridge_> <cellegenrih> that PR having plenty of issues to begin with
11:48 <+bridge_> <jxsl13> saw quite a few crash comments as a result of that pr.
11:48 <+bridge_> <cellegenrih> @essigautomat morning
11:49 <+bridge_> <cellegenrih> imo idc about the pr, just the fact that someone good got ghosted
11:50 <+bridge_> <cellegenrih> Maybe we should just think for a second who we are gonna ask help from
11:53 <+bridge_> <jxsl13> seemingly heinrich only answered selectively to anything that was either neutral or in favor of the pr. concerns were not adressed at all.
11:53 <+bridge_> <jxsl13> sadly those were valid.
11:54 <+bridge_> <jxsl13> i got no skin in the game, so who am i to talk.
11:55 <+bridge_> <Assa> I must say that this PR is/was an exceptional situation, usually maintainers do respond, but we are still waiting for a full disclosure, don't we?
11:56 <+bridge_> <cellegenrih> Im gonna treat this situation as in heinrich's not to be trusted fully
11:57 <+bridge_> <cellegenrih> regardless if he apologizes now or way later when it doesn't matter
11:59 <+bridge_> <Assa> Which is a crazy stance, as he is not only maintainer but also admin - but I wish he at least communicated at all, even saying "Sorry, I'll clarify that later" instead of ghosting
12:01 <+bridge_> <cellegenrih> Nah, he just have to own it
12:02 <+bridge_> <cellegenrih> it happened, one left, things continue
12:02 <+bridge_> <jxsl13> reflecting is hard... give it some time... no pressure.
12:03 <+bridge_> <cellegenrih> If you devs want better trust, apply a code of conduct and have actual rules around PRs
12:03 <+bridge_> <jxsl13> and continuing this conversation will not make it better.
12:03 <+bridge_> <jxsl13> @blaiszephyr CoC mentioned.
12:04 <+bridge_> <cellegenrih> I guess a coc is better?
12:04 <+bridge_> <cellegenrih> As long as it's not written by a 🐕
12:06 <+bridge_> <jxsl13> melon will not sign any CoCs
12:08 <+bridge_> <aegisub> asking for a CoC and calling people dogs in the same message
12:08 <+bridge_> <aegisub> average state of this discussion 👍
12:09 <+bridge_> <jxsl13> would not take that serious.
12:09 <+bridge_> <jxsl13> gotta lighten the mood
12:09 <+bridge_> <jxsl13> any i doubt it was cellegen calling anyone a dog.
12:09 <+bridge_> <jxsl13> and i doubt it was cellegen calling anyone a dog.
12:10 <+bridge_> <Assa> Wuff 🐶
12:10 <+bridge_> <jxsl13> well
12:10 <+bridge_> <jxsl13> you will not write the CoC
12:10 <+bridge_> <Assa> glad I don't have to do that
12:10 <+bridge_> <jxsl13> damn
12:11 <+bridge_> <ryozuki> who has the biggest CoC
12:11 <+bridge_> <ryozuki> sry i had to say that
12:11 <+bridge_> <aegisub> asking for a CoC and calling people dogs in the same breath
12:11 <+bridge_> <jxsl13> you mean the longest*
12:11 <+bridge_> <qxdfox> no biggest is right
12:11 <+bridge_> <jxsl13> it's text in the end
12:11 <+bridge_> <qxdfox> send screenie of clash of clans
12:11 <+bridge_> <cellegenrih> why do you even say that, you should know that idgaf about what you all do on the repo
12:11 <+bridge_> <Assa> melon can sign my CoC :kek:
12:11 <+bridge_> <jxsl13> we talking about written text.
12:12 <+bridge_> <Assa> okay enough mood for today xD
12:12 <+bridge_> <ryozuki> are we
12:12 <+bridge_> <ryozuki> https://tenor.com/view/castanholas-gif-1906157543912258921
12:12 <+bridge_> <cellegenrih> why do you even say that, you should know that idgaf about what you all do on the repo, nor any one of you wanna
12:13 <+bridge_> <cellegenrih> I mentioned code of conduct and every dev in a 20km radius wants to know my location all of a sudden
12:14 <+bridge_> <jxsl13> https://tenor.com/view/castanholas-gif-1906157543912258921
12:15 <+bridge_> <learath2> The duality of devs
12:18 <+bridge_> <jxsl13> this is called framing 👀🔥
12:25 <+bridge_> <miliashka> bro
12:25 <+bridge_> <miliashka> https://cdn.discordapp.com/attachments/293493549758939136/1496094590992777266/1.jpg?ex=69e8a22a&is=69e750aa&hm=fe7fd55ce08a6d5d4f879638d2832f6acccd1a8f40b0cba196a0eb2c1c1c240a&
12:25 <+bridge_> <miliashka> https://cdn.discordapp.com/attachments/293493549758939136/1496094591718264893/2.jpg?ex=69e8a22a&is=69e750aa&hm=509f9ef7a22c2a2959d254407727214b955f469f868cde05c9033efdcea4e3b4&
12:25 <+bridge_> <miliashka> https://cdn.discordapp.com/attachments/293493549758939136/1496094592078970960/3.jpg?ex=69e8a22a&is=69e750aa&hm=bf72c672cd3306790e674098f5b5fd35dec8337c9843cc15abaa3c9e8c1807ed&
12:25 <+bridge_> <miliashka> https://cdn.discordapp.com/attachments/293493549758939136/1496094592368644208/4.jpg?ex=69e8a22a&is=69e750aa&hm=8d7c3584ec88ea8ac038f9979600f2363795a9a5b635eaa11ffe4c2a73707288&
13:15 <+bridge_> <cheeser0613> I find out that getting the full log from console is harder than I expected, steam console inside the steamdeck will replace everything with "..." if the text is over display and the way to break this situation is to connect the developer kit on pc. To connect it, steam deck itself must run a dev software which call "SteamOS Devkit Service". This software itself is pre-installed for the steam deck developer kit (basically you just ask valve to
13:15 <+bridge_> <cheeser0613> Heres the hard part, "SteamOS Devkit Service" do run on the dev set steamdeck and selfbuild steamOS that valve provide, but if developer decide to buy himself a retail set steamdeck, it seems like it just not going to run and the CEF remote function will not going to work in order to access the steam console from pc even if valve clarify that the dev set steamdeck is same as what they deliver to consumer
13:16 <+bridge_> <cheeser0613> https://cdn.discordapp.com/attachments/293493549758939136/1242538465661292675/output.pdf?ex=69e864df&is=69e7135f&hm=986fd07233fa281fafa6833f41ae8b54e6c012f25a8ef64057a952cdaff3b66a&
14:02 <+bridge_> <h9njery> bro
14:02 <+bridge_> <h9njery> https://cdn.discordapp.com/attachments/293493549758939136/1496118828722294975/1.jpg?ex=69e8b8bd&is=69e7673d&hm=61d1c2b095d207cd5b84eecb81c8b7661e9d5b5d97207a361991b413341a94ed&
14:02 <+bridge_> <h9njery> https://cdn.discordapp.com/attachments/293493549758939136/1496118829036732478/2.jpg?ex=69e8b8bd&is=69e7673d&hm=6bd4a5fd2e5f63380c74a3270593664a3cdfa741aa357cec3b99d143ec30edd9&
14:02 <+bridge_> <h9njery> https://cdn.discordapp.com/attachments/293493549758939136/1496118829321814087/3.jpg?ex=69e8b8bd&is=69e7673d&hm=b5eb42030fc5cbdf12f3fc554e3b6daae57ec4419fca6c1c1988e823902ca48c&
14:02 <+bridge_> <h9njery> https://cdn.discordapp.com/attachments/293493549758939136/1496118829628264448/4.jpg?ex=69e8b8bd&is=69e7673d&hm=eb7dcfd52f738449d5eb5032d064b377cfcc6ef80eedad016823f6e86652a188&
15:00 <+bridge_> <heinrich5991> seems incorrect, I added fixes to some of the technical comments by kebs, in the PR that was split from the huge PR
15:08 <+bridge_> <heinrich5991> I ignored the "how is this an improvement" comments, because I didn't want to say that this fixes a security vulnerability
15:09 <+bridge_> <heinrich5991> in retrospect, we've now decided this was a bad idea and that we should work on security fixes in secret instead, so that we don't have to ignore requests for "why is this change made?"
15:29 <+bridge_> <kebscs> Yeah I helped with reviews and got completely ignored on the actual pr :)
15:30 <+bridge_> <kebscs> And most comments in the pr are "why is this rust"
15:36 <+bridge_> <jxsl13> what of that giant pr is the security fix. the whole rust rewrite?
15:40 <+bridge_> <jxsl13> maybe a good approach would be to use a second communication channel that is not public to inform the active maintainers?
15:41 <+bridge_> <bamcane_tee237> I have to say that what heinrich says always sound like Rust can solve all of the issues in Cpp implementation.
15:46 <+bridge_> <jxsl13> why was it rust?
15:46 <+bridge_> <jxsl13> unresolved question 🙁
15:50 <+bridge_> <jxsl13> or people participating in the review who have the dev role.
15:54 <+bridge_> <jxsl13> this at the very least gives us another perspective in order to understand what was going on.
15:56 <+bridge_> <jxsl13> the one below. I do not follow development outside of subscribed prs. it's more of a communication problem than an appreciation problem.
16:43 <+bridge_> <fokkonaut> Dont cry
16:43 <+bridge_> <fokkonaut> but i see
16:44 <+bridge_> <fokkonaut> It was obviously meant with a grain of salt
16:45 <+bridge_> <fokkonaut> It was unusable for me to begin with, because dummy does not have it's own clientdata and you never spent more time cherry picking the F-Client commit.
16:47 <+bridge_> <fokkonaut> That breaks dummy entirely on F-DDrace due to playermapping (and any other 0.7 server that sends different infos to both tees).
16:47 <+bridge_> <fokkonaut> I tried everything I could to make you apply it, explained everything I did and even opened an initial PR. But the codebase was too complex and similar to how you couldn't get my 128 branch to work properly, I couldn't finish this sadly.
16:47 <+bridge_> <fokkonaut> Maybe you can take another look at some point
16:52 <+bridge_> <bamcane_tee237> #9549
16:52 <+bridge_> <DDNet> https://github.com/ddnet/ddnet/issues/9549
16:57 <+bridge_> <fokkonaut> chillerdragon: (https://github.com/ddnet/ddnet/pull/8707)
17:01 <+bridge_> <fushi_gg> turning into ddnet-rs :owo:
17:16 <+bridge_> <fokkonaut> > some other changes not under my control broke it I assume
17:16 <+bridge_> <fokkonaut> 
17:16 <+bridge_> <fokkonaut> This is a common thing, finish it to a point "it works" and then nobody maintains it really xd
18:19 <+bridge_> <furry_mango> https://cdn.discordapp.com/attachments/293493549758939136/1496183617838256208/image.jpeg?ex=69e8f514&is=69e7a394&hm=506368d35879656a160d154aceb483d5e4f1de1f9996f8001a83dcfd8f659f69&
18:19 <+bridge_> <furry_mango> https://cdn.discordapp.com/attachments/293493549758939136/1496183618584838257/image.jpeg?ex=69e8f514&is=69e7a394&hm=5c845348ae4a29477485f75b05b6d92255956db6a5c3eea9c577e6cd966e8f44&
18:19 <+bridge_> <furry_mango> https://cdn.discordapp.com/attachments/293493549758939136/1496183619125772502/image.jpeg?ex=69e8f514&is=69e7a394&hm=2e1446047a25ef9f7c02792008acac470b631be8a449fbb6b113267f990eac7b&
18:19 <+bridge_> <furry_mango> https://cdn.discordapp.com/attachments/293493549758939136/1496183619541139628/image.jpeg?ex=69e8f514&is=69e7a394&hm=b12308b1ed0d2a402c21eea9fa3b39290c7adc358410eae2a575ba72d3df1ee3&
18:20 <+bridge_> <milkeeycat> @Discord Mod
18:37 <+bridge_> <learath2> It was a decently well tested implementation of snapshotting written in a language that makes this specific class of vulnerabilities impossible. So there is some sense in just plopping that implementation in rather then rewriting the C++ version
18:38 <+bridge_> <learath2> The fix shipped in the .2 release is partial, it only fixes the most critical issue. There are other bugs in there
21:38 <+bridge_> <kebscs> What rewriting c++ version
21:38 <+bridge_> <kebscs> Just fix the bug instead of rewriting
21:45 <+bridge_> <Assa> ...
21:50 <+bridge_> <fokkonaut> Can we support teewebs again?
21:53 <+bridge_> <robyt3> What's teewebs? #11920 is still waiting for review if you mean something like that
21:53 <+bridge_> <DDNet> https://github.com/ddnet/ddnet/pull/11920
21:53 <+bridge_> <fokkonaut> https://teewebs.net
21:54 <+bridge_> <fokkonaut> It was a web version of ddnet client, "javascript tee" was the default name
21:54 <+bridge_> <kebscs> Not loading for me, what is it?
21:55 <+bridge_> <kebscs> The emscripten above is basically a web version
21:55 <+bridge_> <robyt3> The Emscripten client already works (with some limitations). I'm waiting for 11920 before pushing the changes to build it officially and host it at web.ddnet.org or so
21:56 <+bridge_> <fokkonaut> Nice
21:57 <+bridge_> <kebscs> Sad that noone other than me reviewed it, I'd love to see ddnet on ddnet.org
22:08 <+bridge_> <berstqs74> bro
22:08 <+bridge_> <berstqs74> https://cdn.discordapp.com/attachments/293493549758939136/1496241115479933089/1.jpg?ex=69e92aa0&is=69e7d920&hm=d40fd7b45391ac7ec8d823637926855dbdc5ae6d74ade0815cda11998b6c3f3c&
22:08 <+bridge_> <berstqs74> https://cdn.discordapp.com/attachments/293493549758939136/1496241115999899648/2.jpg?ex=69e92aa0&is=69e7d920&hm=39be745773f328d81e78c0968fe2e93612afc46080b533c2cf130c9a2cef90ce&
22:08 <+bridge_> <berstqs74> https://cdn.discordapp.com/attachments/293493549758939136/1496241116369129524/3.jpg?ex=69e92aa0&is=69e7d920&hm=91e54de8bd35cc570dd4af922edfe228ac0859f56ecf353fdf822a5cffe0a72f&
22:08 <+bridge_> <berstqs74> https://cdn.discordapp.com/attachments/293493549758939136/1496241116721315860/4.jpg?ex=69e92aa1&is=69e7d921&hm=f77cd90adb1a7c2d594c867189e1036534864527bc5fec567d9b3833b2cff1da&
22:15 <+bridge_> <fokkonaut> https://discord.com/channels/685876551954202624/685878925624475714/1496240812965626000 gg krx virus
22:39 <+bridge_> <jxsl13> the longer I think about this whole sneaky vulnerability fix, the funnier it gets 😭.
22:40 <+bridge_> <jxsl13> what a total hilarious mess.
22:45 <+bridge_> <chairn> `#unknown` sad
22:47 <+bridge_> <Nouaa> https://discord.gg/fYaBTzY
22:47 <+bridge_> <Nouaa> don't be sad
22:58 <+bridge_> <01000111g> quick question to #12018 - wouldn't it be nicer to implement $n$ player support instead of these fixed numbers? or is so much hard coded, that we can't make it more abstract?
22:58 <+bridge_> <DDNet> https://github.com/ddnet/ddnet/pull/12018
23:02 <+bridge_> <robyt3> Changing the size of existing fixed arrays is much simpler than adding dynamically sized containers everywhere. Beyond 256 players the physics would probably be too slow as well.
23:06 <+bridge_> <01000111g> Ah okay, just asking from a naive data scientist viewpoint with infinite resources lol
23:35 <+bridge_> <0xfaulty> Physics is fine. About 70% of the tick time will be spent on snapshots (and without threading, it will lag heavily). I tested it once with around 170 players, but it’s unfortunate that I have to scale it to the maximum client count (which was 64 at the time of testing)