Time Nick Message 12:15 MinetestBot 02[git] 04AFCMS -> 03luanti-org/luanti: Bump Alpine from `3.19` to `3.23` in Docker image 1331d814c https://github.com/luanti-org/luanti/commit/31d814cabb60dd44fb248250b44593d7a0070512 (152026-02-19T12:13:36Z) 12:15 MinetestBot 02[git] 04Wuzzy2 -> 03luanti-org/luanti: Fix documentation: vertlabels can now be colorized 13cdbbf38 https://github.com/luanti-org/luanti/commit/cdbbf38a8371cf1d4d9972bbb2eb3e9388cc845d (152026-02-19T12:13:50Z) 12:15 MinetestBot 02[git] 04Desour -> 03luanti-org/luanti: Meshgen: Refactor and fix blend nodebox splitting (#16942) 13ae87536 https://github.com/luanti-org/luanti/commit/ae8753630fbd0adb599e30269df08ebd3073e839 (152026-02-19T12:14:02Z) 19:47 ireallyhateirc I see there was an issue for param3 which was closed as "Won't add". Is this still the consensus among core devs? 19:48 ireallyhateirc https://github.com/luanti-org/luanti/issues/6663 19:48 ireallyhateirc perhaps this could be reconsidered for 6.0 ? 19:49 ireallyhateirc while param2 often has special meanings in the context of meshgen, node visuals, etc. param3 could be a generic value for modders to use 19:53 MTDiscord Consensus is that we want something that allows us to extend the kind of data that can be efficiently stored per node, but this should be flexible and will thus probably need to be more than "just one more param, bro". See e.g. #16950 for a more elaborate proposal. 19:53 ShadowBot https://github.com/luanti-org/luanti/issues/16950 -- Typed node meta (tmeta) 19:56 ireallyhateirc sounds fair. Exile's original dev did a param3 typo once and it lives rent free in my head since then 20:39 ireallyhateirc Btw I'm reading this https://irc.luanti.org/luanti-dev/2026-02-17#i_6314948 20:40 ireallyhateirc and I want to clarify some things: I did contribute functions to our vector API in the past (manually) and have a decent understanding of Lua. After trying out the copilot coding agent I discovered that it actually makes fewer mistakes for simple changes like this than I'd do by manually writing that code. 20:41 ireallyhateirc LLMs are pretty good at following the style of the original code so with vector2 it was pretty much just removing one dimension 20:42 ireallyhateirc then I always read and/or at least skim the code 20:43 ireallyhateirc and if not I disclose it, just like I did with that PR 20:45 ireallyhateirc 90% of the mistakes AI did and appgurueu caught during the review were bugs/mistakes copied directly from the 3D vector API 20:45 ireallyhateirc and in the end I believe we did finish this pretty quickly, if not correct me 20:46 ireallyhateirc I would be able to write all the vector2 code myself by blindly copying all vector code and then removing one dimension from that, but it'd probably take a week and as much effort to review as the slop PR 20:47 ireallyhateirc . 20:48 ireallyhateirc So: either clarify your AI policy to disallow that OR add additional requirements 20:50 ireallyhateirc also generating that code and testing it in the game does cost me both time and money] 20:57 Helenah ireallyhateirc: Do you actually hate IRC? 20:57 ireallyhateirc sometimes yes 20:57 Helenah ireallyhateirc: Why? 20:57 ireallyhateirc configuring a bouncer was funny experience 20:58 ireallyhateirc I wanted my nick to be lord_of_the_dumpster but IRC complained 20:58 ireallyhateirc hence my nick 20:58 Helenah Yeah, that's down to nick length which is network specific. 20:59 Helenah EFnet has an even shorter nick length, one which is RFC compliant. 21:00 Helenah ireallyhateirc: What about, lord_dumpster, or dumpster_lord? 21:01 ireallyhateirc I wasn't that smart back then and am too lazy to configure the bouncer for a new nick 21:01 Helenah hmm 21:01 ireallyhateirc also the nick is funny 21:01 Helenah :D 21:01 MTDiscord I had my bouncer set up but then something happened and I was too lazy to fix it so I just killed it 21:02 Helenah sparky4: Hi, hows Windows ME going? 21:02 Helenah Yeah, this is the issue with bouncers, I get that they let you use like a dozen different client softwares, but that adds complexity. 21:02 ireallyhateirc IRC without bouncer is good, you join and don't have to read all the gossips 21:03 Helenah ireallyhateirc: That's not bouncer-specific, there's other solutions too. :) 21:03 Helenah But yeah, I get you. :) 21:03 ireallyhateirc yeah the network I use doesn't support IRC history or whatever the feature is 21:05 Helenah There's also quassel relay, weechat relay, there are... I assumed you used ZNC as a bouncer, there's the older psybnc, there's tui/cli client in combination with tmux/screen/dtach as an option. These days, there are... IRCd's (server software) which support erm... in-built bouncer. 21:06 Helenah I am not sure if network-side bouncer support is an IRCv3 feature or something specific to the ergo IRCd. 21:07 Helenah ireallyhateirc: The original intention of bouncers were to keep your nick online at all times, allowing access via any client, from anywhere, not chat history readback. :) 21:08 Helenah Not sure if you explored or noticed, but a bouncer is a pseudo IRC server in itself. :) 21:10 ireallyhateirc well I did expect IRC to be hacks upon hacks 21:10 Helenah Yeah, I mean... 21:12 Helenah In the 90s, Undernet was an IRC network that was born, the intention was for testing and experimentation of bots and stuff. At this point and prior, there were no such thing as IRC services, so you couldn't register nicknames and channels, these things were simply there for anyone to take and if you wanted to keep hold of a nick or channel, you had to hold them at all times, client leaving a client 21:12 Helenah idling. 21:16 Helenah But then Undernet started getting a lot of abuse regarding channel takeovers, so they implemented "CService", meaning "Channel Service", which basically provided a bot with the nickname X, you created an account, logged in, registered channels with it. But... you couldn't register nicks as yours. eggdrop was an IRC bot that became a thing at some point in the 90s, designed to try its very hardest 21:16 Helenah to re-gain control of channels it was configured to and hold them, that's a solution people still use on service-less IRC networks today, such as EFnet and IRCnet. Eventually, Epona and Anope became a thing, providing the *Serv bots we're familiar with on most IRC networks, finally, people could actually not only register channels, but also nicks. Anyway, you're right, we kind of... we created 21:16 Helenah bots, and a solution for linking between server and services. 21:17 Helenah And then called these... "IRC services". :D 21:17 Helenah ireallyhateirc: But this is more akin to the unix philosophy, right? Which was more commonly followed in the 90s. 21:18 Helenah The idea that you have two completely different pieces of software, but you glue them together, so they flow into each other. 21:18 ireallyhateirc this pretty much makes sense, unless you go overzelaous with this 21:18 ireallyhateirc modular designs are good overall 21:19 Helenah Yeah 21:21 Helenah There is an alternative... you modify IRCd code, to incorporate channel/nickname registration and login capabilities, but obviously this would require developers to modify IRC clients, to incorporate these features, but I think the thinking was that people should be able to use whatever IRC client they want, new and old. 21:23 Helenah Which contradicts what we're doing now, with IRCv3... client will negiotate with server, to see what IRCv3 features are supported, wouldn't it have made sense in the end to have just had clients and servers negotiate whether or not services are supported? :D 21:25 Helenah Ergo has its own in-built services, the thing is, it still follows the model of providing *Serv bots.