Lisias

Absolutely outstanding! https://github.com/net-lisias-ksp/UbioWeldContinuum/issues/5 I can't make any promises, I don't know even if this would be possible - but I will not forget the idea. It looks promising, at least, and may be the feature that would solve a lot of incompatibilities for good - the less modules I shove on the welded part, the lesser are the chances of some of them pick a fight with each other.

NEWS FROM THE FRONT Release for the 2025-03 is online. https://archive.org/details/KSP-Forum-Preservation-Project Wiki is updated too. https://archive.org/details/KSP-WIKI-Preservation-Project

Jesus, dude!!! Do you publish your craft files somewhere? I would like to give a peek on one of them!

"This message was deleted."

THIS. This is the reason we are clashing badly and getting exasperated with each other. We have fundamentally different visions about the role the Source Code have on modern Software, and I'm talking from a privileged position, because I had seen the whole evolution since the 80s. I was a strange kid, my friends were talking about computer games, I was reading about commercial and industrial automation and what Companies like Microsoft were doing about. I had installed and toyed with every single Spread Sheet ever launched for CP/M, MS-DOS and Windows since the 80s. And let me tell you, essentially nobody talks about SuperCalc and MultiPlan anymore. Not even about Lotus 1-2-3 or Quattro Pro (Borland really excelled on almost everything they did). Forget about Lotus Symphony. They are all dead bytes. Everybody and the kitchen's sink migrated to Microsoft Excel in the late 90's besides it being a dog-sheet , crashing now and then due badly coded COM Objects running on a half-baked OS called Windows 3.11 (that had one of the worst memory managers I ever had to deal with). Why? Because Microsoft wrote converters for every single damned Spreadsheet ever published over a silicon substrate integrated circuit ever soldered into a PCB and so ended up becoming the Common Language for Spreadsheets (that, and some other shady corporation practices, to tell you the true - interesting how some of them can be found on this very Scene lately...). No matter how good is your code - users don't care about code, they care about their data and how to use it. Me included - because I ditched Excel some years ago (besides it had become, really, one of the best written programs of all time - reading the History of the Team Excel inside the hell it was Microsoft in the 90s and 2000s is a hell of an interesting reading). I'm using LibreOffice, besides part of it still being written in Java and, so, using memory as it would be candies and being significantly slower than Excel on most workloads. Why? Because LibreOffice does everything I need it to do, and don't impose to me any restrictions I don't want to cope with, as Microsoft 365 is imposing nowadays. Heck, I can grab a Raspberry PI, install LibreOffice and open all my Cybervadis documents on it if something happen to all my home office infrastructure. And this worths more to me than any excellency in code that Excel can provide to me. Users playing games are the same. They are on the game (pun really intended) for the fun, not for the code. They just want their games to work properly - including savegames, that are essentially their own customized "Movie" that they are watching at the same time they are creating it. KSP¹ is absolutely magnificent on this matter: my savegames can be used on my MacOS desktop, on my Windows Notebook and on my Linux Steam Deck without reserves - I can literally close KSP on one rig, sync the savegames and keep playing from where I left no matter the device I'm using at the moment. I don't care if the game have the best and most efficient serialization code that is available today - in fact, KSP¹'s data (savegames et all) are pretty inefficient, but terribly tinkering friendly and the KSP¹ user base (or at least the ones that like toying with KSP) praises it a lot because it makes KSP¹ incredibly easy to tinker. And this is also a killer feature to me, I fully own my savegames and can tinker with it at will!!! Again, the code worth squat. The value is on providing users with the value they want, not to what the programmers considers excellency - today, Excel can be considered excellency on code and I had ditched it for years already for a not so excellent solution because the later fits my needs way better. Finally some argument worthing being discussed. How Cities Skyline owners handle closed source mods promoting the competition? How they are handling adversarial actors screwing their user base? How Cities Skyline 2 is doing nowadays? What happens when something change on Cities Skyline breaking mods, and an old closed source mod cease to work? https://steamcharts.com/cmp/949230,255710#All Interestingly, the curves are incredibly similar to KSP2's ones on steam, but - granted - the absolute numbers are way better. https://steamcharts.com/cmp/954850,220200#All But, being absolutely frank about, Cities Skylines 2 was a waste of money - had they just kept investing on the first installment, they would be earning way more money. In a way or another, it would be interesting to investigate how the Cities: Skylines moddding scene is doing this days, how many mods are open source, what would be the most used ones, etc. Would you fancy doing it for us? And this is where we clash badly. This thread is literally littered with arguments explaining ad nauseaum why Open Source helps to prevent copyright infringements and, yet, I need to replicate these arguments again and again because most contenders aren't here to discuss the idea, but to merely disprove the proposal following [pursuing] some personal agenda (not making any judgment of value about the agendas, they may be valid). Opening the Source is a game changer because everybody and the kitchen's sink will be able to legally read it and will be, potentially, a copyright enforcement agent by recognizing the code being used on adversarial 3rd parties. If you manage to have an engaging Community, that sees in you value and so make their best interest on defending your interests, they will help you fight adversarial actors because this is their best way to keep healthy the game they love playing. If they get most value from Copyright Infringers, heck, you are toasted because they will do the same, so, for your adversaries. With more people aware of the Source Code, better are the chances of any problematic code in your code being detected before you being in trouble. One example I gave (see here and here) is related to IBM and Zynga. Interesting bits: IBM first approached Zynga in 2014, but the at the time management failed to take proper action, and let things develop. TTWO bought Zynga in 2022. And it's probably the reason IBM jumped on Zynga's throat also in 2022 - because they know that now someone would have the money to foot the bill. Patents is another problem that encumbers Software, and Open Source is one of the possible (probably one of the best) ways to deal with it. And, let me tell you, Copyrights work like Patents and have similar side effects, being the reason I used the Zynga example on my argumentation. When you buy a Company, you acquire the bonus but also the onus. Every single obligation included. But... Let's play ball with your idea. Let's suppose you are right, and so Haveli won't have any obligation to me because I hadn't gave him any money. Well, it works both ways: this also means that I would only have obligations to TTWO, and so I won't need to respect any right Haveli currently have over the IP, right? After all, I had paid TTWO for the game, not Haveli. So this means that I could decompile the game, reuse the assets in paying closed source mods and even use mods as a vehicle for advertising the competition, because TTWO was essentially allowing people to do that since long time ago. Laws work both ways. If Haveli don't have any obligation to me, then I don't have any to them neither! But you had implied it when you suggest tactics used by companies that do that. https://www.scamwatch.gov.au/types-of-scams/jobs-and-employment-scams I'm bringing to the table the logical consequences of what you are saying [proposing]. This is the whole purpose of an argument. Things will be considerably more productive if you would dive in the subject being discussed, instead of getting defensive, thinking this is an attack to your persona. I'm fighting the ideas you are bringing to the table, not you.

There're 371 votes on the poll above, and this thread have about 25 months already. Now go to Reddit and count how many likes a single Screen Shot gets. People wants their problems solved, they pay for solutions, not source code. You and me know how this can backfire horribly, but, still, Users do what Users do. It's up to us to cope with the situation. Nope. The "Movie" is the content: missions, Kerbals. music, lore, the savegames. Code is unimportant - what really matters for the user is the user's data, not the code that it runs to generate the data. Delete all the user's savegames and see for how long they will play the game. Of course they can make such a decision! We would not need to pledge for it if they would have no other choice! Its the very reason for the existence of this thread! As I said, you not reading this thread and are rebating only the points I'm making to counter-argue yours. This is leading to a circular arguing that not only is not helping to promote the cause I'm advocating, but will seriously hinder it by burying the proposal into a mountain of empty arguing full of unfunded opinions. Do you really want to debate about the matter? Read the posts I had published here - or you prefer me to copy and paste all of them again? I'm afraid you are the one being dogmatic about the matter - I had posted links and evidences and cases of success for 2 years on this thread - while I don't see you publishing anything other than your opinions, none of them with any kind of material to support them. You are consistently ignoring the most recent (and, by far, the one with the worst consequences) problem right now: blatant Copyright Infringement by 3rd parties, some of them making money with P.D.'s IP without any kind of compensation, as royalties. Now we have even closed source mods advertising the competition using their own game. What's next? Mods with Casino ads? The value of an IP is directly linked to the ability to defend it from adversarial 3rd parties. How they intend to sell DLCs if their users are using the money to buy 3rd parties addons? Why allow them to advertise the competition inside their own game? Why let 3rd parties to use their IP to prototype features that will be, so, sold to their users by the competition? How much worths a Company where everybody make money at their expenses? Would you buy shares from such a Company? I won't. Now consider the options: Do nothing. Play havoc over the scene, suing everybody so their shareholders (or funders) believe they got back the control of the IP. Open the Source of the KSP¹, allowing anyone to code the same add'ons, detecting and fixing fixes to be used on the next product and leveraging the playfield by allowing the users to get the add'ons they want and modders to do their mods without coping with shady practices that can bite their arses badly later on a Court of Law. The option 1 is obvious what's happening now, I think. Where this is going? KSP2 is being developed? There's someone trying to talk to Lego so they can finish and publish that game they were developing with them? Is the user base expanding? Their users are buying their DLCs or are using the money to fund copyright infringers? The option 2 works. It's exactly what Nintendo does, by the way, and Nintendo is hardly a looser in the Game Business. Problem: there will be a nasty backslash from the Scene, the same one that kept KSP¹ afloat for so much time. Losing this audience will impact negatively the rest of the userbase, because essentially people are here to play mods most of the time. But, at least, on the long run they will have a better grasp on protecting their IP and, perhaps, manage to find a buyer to keep it going (as it's improbable that the Franchise would recover while they are on the helm, due the backslash I mentioned - they are not Nintendo, they can't do what Nintendoes and walk without consequences). Option 3 is my proposal. KSP¹ is a finished product, it's essentially running to its EoL by now. There's no one available to fix the current bugs and protected the Source Code from bit rotting (did you noticed the problems Windows 11 users are getting?) There's no further development in the near future to keep the Franchise in evidence, there's nothing happening at all promoting KSP. There will be no KSP 2.x/3/whatever before the competition (the ones that are using their assets to promote theirs, by the way) hits the market - a situation in which they will surely see their userbase shrinking even more, be due the new game taking users from them, be because modders will abandon the Scene for doing something else, in a nasty self feeding cycle that will render a new installment of the Franchise yet more unlikely. There're other options? Probably - but I'm not seeing any alternatives with good endings that would not start with Option 2 or 3. And I think I don't need to explain why I hugely prefer 3. Now it's your turn. Please give us your rationale for your arguments. Give examples, use cases, anything. The ball is in your park now. Make your case for us. I think that most of this Community already did that, and for years already. I agree that the new owners are... well... New on this scene, so they just didn't lived the whole process. But, still, they are the ones in need to catch up, no? We have 25 months of discussion on this very thread, an very rich (most of the time ) source for arguments (cons and pros). I myself had already discussed about possible drawbacks - but that was way before the current drama about Copyrights - this changed everything. Everybody is more than welcome to read them and to quote old posts to reignite a new debate about the subjects. The community want bugs fixed, and I don't think it is willing to foot more money just to get whatever they already had bought working right (what it was expected to happen on the moment of the purchase). You see, I think that you really lost the point here: this isn't a Community of Game Developers looking for a job, neither professional game developers willing to invest time and money in a new entrepreneurship. Neither a bunch of masochists willing to work for free - what I doubt would cope well with the DoC at first place. This is a Community of KSP enthusiasts that for years helped to debug problems and fix bugs at the same time added some content, made by amateurs on their free, spare time. Modding is made by the Community for the Community. I really don't think it will be a good idea to try to sell us the privilege of doing free work for them, because if this is where this is going to go, I'm afraid they are going to have a hell of a Reality Check: we are paying customers that like to use our free time modding games, no cheap/free workforce at their disposition to do their work, what to say about paying for doing their work? If anyone from Haveli is reading this thread, it's with an open heart that I strongly advise: don't go trough this venue, it will end in tears. Context. You are lacking context. This poll mas made in 2023, on a time that P.D. was known to publish games like Outer Worlds, a very tongue-in-cheek humor anti-corporation game...

An April Fool's April Fools! A Meta April Fools!

The EULA explicitly forbade reverse engineering and accessing private data, and the law explicit forbids decompiling and changing in memory bytecodes. Some people around here, since August 2024, lost any protections they had under any possible law they could think no matter where they live - again, Berne Convention. And it's simple like that. You are still deluded on a dead-end argument about the source code being the reason people buy games. Really, it's a moot point. People don't care about Source Code, no matter what your codewarrior friends says. Source Code is a medium, a way to deliver content - and, as such, it's extremely important. But, still, it's not the reason people buy Games. People buy games for the content, and this is not going to be open sourced. We buy TV sets to watch Movies, we don't buy Movies because we want to use TVs. KSP¹ source code is pretty old, outdated and unfortunately bit rotting, and right now there's absolutely no way for any KSP 2.x to be published without the competition getting on market first. The very best chance P.D. have now is to bet on the KSP¹ Modding Scene as a way to keep the Franchise relevant and be able to uphold the increasing competition with the product they are selling now. There's no next product if the current one dies first. I will say it again: THERE'S NO NEXT PRODUCT IF THE CURRENT ONE DIES FIRST. WHAT-THA-HELL???? o.O May I politely ask to avoid this specific subject again? With all the information being leaked lately, you are dangerously flirting with spin-doctoring. There's absolutely no way TTWO would not be involved on the decision making of a 100M USD game. At very, very, very least, they hired the P.D. staff that promoted the mess, so they are still the ultimate responsibles for the tragedy. IT'S NOT WORKING. People are happy with the features they have, or the ones that modders are adding to the game. What people want is a bug-free gaming experience, and this is exactly what KSP¹ is consistently failing since the Unity 2017 migration. The path to KSP 1.12.5 is littered of corpses, and no one is really cleaning them. KSP¹ have a terrible case of code-rottentitis, and the current medicine being applied is not only disapproved by FDA, but also currently criminalized. And I'm kindly ignoring the collateral effects. What just not going to fly if people that made KSP¹ what it still is (besides somewhat battered) leaves the scene. You are still thinking that KSP¹ Source Code is an asset. Right now, it's a liability, with this Scene dangerously flirting on becoming a Warez subculture. Even if you would be right about this Source Code being still valuable, such value had just evaporated by the current Copyright Infringing practices that is the norm today. What value have something that any rogue party can use to make money for themself, disregarding the Law, Licences and even Ethics? As a matter of fact, releasing it as Open Source will probably recover some of the value currently being lost by rogue 3rd parties. At very least, it will allow non rogue 3rd parties to play the same game, leveraging the field into a more P.D. friendly one. Sometimes I fear you are just not listening/reading what is being told to you. This Scene, right now, is at large incurring in blatant Copyright Infringement - we are not dealing dealing with an EULA Infringement anymore. Our problem right now are the Penal Code and Courts of Law. What kind of damage do you think it will happen if all the current mods that relies on in memory bytecode changes are just took down? It's a matter of time until the current hosting services will have their reputation tampered by association with to Infringements practices, including GitHub and GitLab. Again, we are risking living Naspter all over again. And exactly how do you think this will affect the Franchise? Even if you would be right (and you aren't) releasing the Source Code as Open Source is now a matter of survival, this Scene needs legal access the Source Code to prevent the whole scene from being criminalized by the (now) rampant Copyright Infringements. If the Source Code is legally available, them its respective binaries are also a Open Source derivative, and we get rid of the problem that currently the code decompiling and in memory bytecode changes are bringing to this Scene. I will say it again: THERE'S NO NEXT PRODUCT IF THE CURRENT ONE DIES FIRST. And what keeps KSP¹ alive is the people gathered together on this Community - people that will leave if they fear a Witch Hunt like the Napster one. TTWO indulged P.D. into trapping themselves on a corner with a ticking bomb in their hands, one that they built themselves. The current P.D. owners weren't part of that problem, but inherited it and now are the ones that need to disarm the bomb - or just let it explode and deal with the splash damage, I don't know what they intend to do with the Franchise to be frank about.

Today is April Fools. (hundreds of undesired Easter Eggs popping in your screens over the World!)

From that 1000 parts, how many of them are Procedural? Perhaps some optimization while building the thing can help. Wondering if it would be possible to extract a mesh from Unity's Memory and export it as a MU file, "degenerating" the procedural part into a stock one. That would allow the Welding Tool to work with them... Not sure if it's feasible, or even possible, but right now is the solution I guessing could work with the Welding Tool.

But only the Assets have real value. The Source Code doesn't worth that much at this point (if at all)- had you forgot that anyone not caring about copyright infringements already have access to it? The Genie is out of the bottle, KSP¹ source code is already in the wild to anyone that don't care about legalities. Where is the worth of such code if no one is defending it? I'm proposing that legally releasing KSP¹ to anyone willing to toy with it will give to the current IP owner way more value that allowing only the copyright infringers to do it. There're many technically skilled people that would love to dig this code and hunt bugs, but are not going to do it as very few people wants to cope with a Warez subculture (what do you think it would happen to a NASA engineer if they are caught in copyright infringement?) - that it's what one need to do right now to access the Source Code by illegal (since August 2024, when Bungie won the lawsuit I mention ad nauseaum) practices. Please note this is not a moral stand, but a legal one. Copyrights are serious business, and anyone ignoring the laws are jeopardizing the modding Scene. You completely missed the point. Why Doom Eternal is selling nowdays? Due some fantastic and marvelous Source Code that only they are capable to write? Nonsense. People are buying and playing Doom Eternal because the Doom Franchise have a hell of an appeal. And one of the reasons this Franchise survived very well the decades is because people just don't stop making free advertisings by porting Doom to anything that have a screen, no matter the size. Guess what else have a hell of an appeal? Half Life. Did you now that VALVe recently released the Team Fortress 2 source code on the Source Engine Dev Kit? Expect the TF2 Community to hunt down all that pesky bugs and security flaws, and this is probably the reason the TF2 skyrocketed to 250K concurrent players when the announce was made in 2023 And since TF2's source code was already (and illegally) leaked in 2016, what VALVe lost with the move? KSP¹ and even KSP2 'source code' is already "leaked". What P.D. have to loose by legally releasing the Source Code, since it's already "leaked"? Why allowing people to legally read the Source Code would devaluate the Franchise, while allowing copyright infringers to do it would not? What suggests they should consider exploring new possibilities for whatever they have in hands now. It's clear for me that if they keep doing things the way TTWO did, they will get the same results. It's time to reevaluate some positions and talk to different people. Yes, "security" is the key factor. Even by Haveli being benevolent nowadays, they can decide to jump ship and offload the IP to someone else that my decide not to be. When money starts to walk, usually bullets start to fly.

AFAIK Procedural Parts just don't know how to play together themselves, they are intended to be used on a single part. UbioWeld can only weld parts that we "already ready to be use" or "premade" when you draw them from the Part's Menu. Anything that reconfigures itself at runtime just can't be touched by it. Even using variants can be problematic. And, frankly, if you have Procedural Parts in your menu, why bother with UbioWeld? The very reason for Procedural Parts is to avoid the need of tools like this...

You couldn't be more wrong. Right NOW we are in the situation you describe, and anyone telling you otherwise is misinformed at best, and I will decline to further comment at worst. It's exactly the other way around. To keep the KSP¹ Modding Scene secure, people would need to have access to the KSP¹ source code - otherwise only copyright infringers would be able to keep the modding scene ongoing - and this is as hairy as it can be. If only more people that lived the RIAA drama could step ahead and help educating the youngers about that era. Why? Who would benefit from this, besides the copyright infringers? The code doesn't worth squat. It's outdated, with a serious case of bit rotting. The IP is where the real value of the thing is. No one will be able to publish a "new KSP¹" with the source code, at least legally. And we are already on the illegal status around here, the Franchise is already being undervalued because everybody and the kitchen's sink is being able to use their IP to earn money or promote alternate products without paying them a dime! What you fail to understand is that we are already on the worst possible situation, where copyright infringers can do whatever they want and the only ones with their hands tied are the ones not willing to dive on a Warez kind of a Scene. See what happened with Doom: had Doom III had any problems by Doom I and II source code been published? Had Quake Arena failed because Quake 1 to 3 source code were published? In a very permissive license, by the way? Did you know that Tomb Raider is being re-release in Physical Media again? And that the Publisher had hired he dude that created and maintained Open Lara? Your argument, unfortunately, lacks Real Life™ evidences, while mine have plenty. ---- POST EDIT --- See KSP2: where it's the value, on the crappy source code, or on the Soundtrack? The sound effects? The tutorials? You can rip the code from the product, write new code and it will be KSP2 but working fine this time. You remove the Kerbals, the sounds, visuals, music and tutorials, what you get? Do you see what I mean now? THIS is where the value of a Franchise is. Code is the glue that keeps everything working together. It's a very important part of the game, but people don't buy games due the glue, they buy games due the IP. A bad code will screw your product after the sale, but a bad IP will prevent the sale to happen at first place, rendering the code useless no matter how good it is. Damn, DOOM I is on par with KSP on concurrent players on Steam right now, and last week had a peek at least twice the size! https://steamcharts.com/cmp/379720,220200#3m And it's a franchise with 3 times the age! Do you think releasing the original Doom source code damaged it?

How is your Kerbals reusability rate?

Forum's license is being renewed regularly, no changes detected since Haveli bought PD. There's no sureness on Internet. EVERYTHING can go kaput at any moment, by any reason. Orkut, eGroups (later Yahoo Groups, and then discontinued), Google+, you name it. In a way or another, the less unsureness we can get right now is still this Forum. Keeping a Forum costs money and man-power, how much money and time one would he willing to foot to fund an alternate Forum like this? Not to mention that the posts are copyrighted, so one would need to secure authorization from all Posters before attempting a data migration. Just not going to happen. So any alternative right now is moot, already dead on arrival. A Forum without content is useless, and the content is here and nowhere else.

Everybody knows that the F-35B lacks range, but I'm pretty sure there're better ways to solve the problem! (CH-53K Super Stallion carrying a F-35 and being refueled)

Please understand that this thread is about releasing the Source for KSP¹, KSP2 is not part of the deal and KSA is completely off-topic. I just don't care about KSA on this thread. T2 is not here anymore. There're these new kids in the block, Haveli and the ex-Annapurna Gang , that footed some money on the whole P.D. , hired the "Gang" (literally yanking them from Annapurna Interactive - the whole staff!) and now are figuring out how to make money from what they have in hands, KSP included. HELL, NO!! They do what T2 was doing, they will get the results T2 got. Exactly, and, to achieving that, having the Source code available will be hugely beneficial - and there's the legal problem now. See this post for datails, but TL;DR: decompiling was already against the EULA but now it was criminalized and, worst, changing in memory bytecode is now formally a Copyright Infringement in USA, and anyone doing it (theoretically, including users) are since August 2024 subject to a Copyright lawsuit in the same sense it happened in past when RIAA gone predatory to even kids listening MP3 in their homes. Things keep going this way, KSP¹ will be reduced to a Warez sub-culture, where Educational Institutes and Space Agencies will do whatever they can to erase their presence from the Scene (no Company wants to be associated to illegal stuff) and the main source for modding will be the Dark Web - kiss baby bye-bye to CurseForge, SpaceDock et all because they would be violating their Country's laws by publishing "warez". Keep in mind that the tragic drama started by RIAA in the past was using Napster as conduit, Napster users were systematically tracked down and sued using a thing called "vicarious copyright infringement" - no one will be safe from it. Again, I don't care about KSP2 and KSA on this thread. No matter what they will deliver, I want KSP¹ to be still available and moddable. Safely moddable by anyone, and not only by some people hidding behind nicks that can go rogue at any time without consequences - essentially, the development model we have on Warez. I will say again: KSP¹, since August 2024, is risking being reduced to a Warez Scene where only rogue 3rd parties will be able to make some money at expenses of the Scene. Things are risking going that way, it's really as bad is it can get. This crap will contaminate the whole niche - make no mistake, the splash damage will hurt everybody, including KSA that decided to formally hire one professional that openly does exactly what the lawsuit won by Bungie says are Copyright Infringements now and used this material on KSA. Remember the Berne Convention, and how Copyright owners have 70 years to do something, essentially putting an axe over KSA's neck for life, to be set in motion as soon as KSA makes any money,

A battle beetle. Nuff Said. https://www.noticiasautomotivas.com.br/pronto-para-a-guerra-este-fusca-equipado-com-esteiras-de-um-tanque-militar-esta-a-venda-por-25-000-dolares/ Source is PT-Br so I'm linking it using Google Translator here. ----- Wait, the Moscow Circus will be reallocated at very least? Or they will be forced to perform under this thing? You know, I used to attend this circus when a kid, they have a branch on South America. Interesting enough, they were around here this month but I didn't knew about, lost the show essentially by 2 weeks -they stay on a pace for a week only. https://circomoscouinternacional.com.br/ I can't imagine a Circus performing no anything other than a circus tent...

I'm screwed for the rest of the month. Since I'm screwed beyound salvation at this time, I took some time to sleep, do some side tasks and relax a bit before going back to grinding. And I decide to vent the reason I got really screwed: KEA. What a marvelous piece of crap, really. We are using pfSense on DayJob©, as it's the tool the Infra Dude is used to use and, frankly, until not too much time ago it was up to the job without reserves. But then someone there decided they were leaving money on the table and started the.. hum... crapfication of the damned thing - because, really, I just can't think of any other reason someone would do such a major blunder as replacing ISC with KEA - really really, why??? Back to the story: middle 2024 I was working on a plan to ditch our last VMWare machine (also the first, and the only too.. hehe) and migrate the last VMs on it to ProxMox on a beautiful new Host, 4 times the size of our old one - and since we were using pfSense on it before, why change it? A newer version of pfSense was installed on the new Host too. But then something very important happened and I was diverted to a new task that took almost 6 months to complete (we are Cybervadis certified now! #hurray). Now I finally took time (and courage) to face that VMWare dragon again, but since them a lot of infrastructure was already migrated to the new Host, and I wasn't there to see what was happening. Essentially, we replicated what we were used to use on VMWare on ProxMox, as pfSense, to save the work of retraining and relearning and what else. It appeared to work fine for Windows and SAP machines, and this is the key that leaded me to conclude about the crapfitication - the new pfSense version replaced ISC with KEA and once I finally started to install our new QAS infrastructure on the new host, KEA decided it was a good time to bite my cheeks. Badly. KEA has a very nasty "antifeature": it think MACs are useless, and if any other meaning of identify a host is possible, it silently uses it and screw the consequences - it's up to you to guess what's happening. After 2 days of battling against it, I finally understood I wasn't the point of failure, started to probe the problem beyound my NIC and found KEA's hands still on the candy pot. Ok, after reading some tickets opened and cavalierly dismissed and closed by both pfSense support and KEA's developers ("it's working for most people, so you are the problem"), I found ONE ticked on pfSense now last Xmas where someone finally acknowledge that prioritizing MACs may be a better idea after all, and implemented a configuration option to tell KEA to do it. Problem solved. right? Uhh. Nope. Since I'm the sole administrator for the subnets I'm migrating, I do not need to care about any other systems than mine on it and so I don't need to coexist with SAP, Windows or anything else on that network, so I could coerce KEA to use only MACs by filtering out any other possible means to identify the NIC on both sides (KEA's and client's configuration). This would save us from the downtime needed to update pfSense (not to mention the risk of the new version is being even worse...). And now I found another bug, this one a functional one. And yet nastier... Sometimes, KEA fails to identify a client with address reservation is offline, and if the poor stand-up guy tries to lease the IP again, KEA's will think the IP as still busy, WILL IGNORE THE MAC of the requesting host and will give it a IP from the dynamic pool instead. So the poor stand-up guy will suddenly get a new IP if the NIC is downed and upped again, and everything will go down in flames because KEA's DDNS is another piece of crap (and isn't available on our pfSense - and I doubt it would work anyway since the damned thing can't detect when a host crashes and reboots. How we would trust our DNS to such <piiiiii> anyway?). And no matter what I do, once KEA gets a grudge with a host, it will screw its life forever no matter what you restart, from the victim host to the KEA's service itself, the problem is probably on its persistent database - and it just can't be worked around, the best I managed to accomplish was to convince KEA to switch victims: by completely wiping out all the configurations and starting again from scratch, the problem appeared to be fixed on the first host getting the heat just to another be selected to take its place and be thrown under the bus instead. And now I'm back to doing static configurations on the requesting host, with all the problems it causes and that made my life miserable a few years ago. (sigh) Talking about the problem with the dude responsible for the other subnets, he said that everything just works for him - but using VMs with Windows, and using static allocations for the SAP boxes (DHCP appears to be a bad idea when handling SAP boxes). And then something clicked inside my skull and I remembered the "you are the problem" answer I found on the pfSense and KEA bug trackings and forums. These guys are trying to sell services to the Windows ecosystem, I think. This single dimensioned thinking is common on Software, and being absolutely frank, it's also flagellating our KSP scene for some years already. I checked that OPNSense is still using ISC (besides implementing KEA support in parallel), so I will try it on the next Server we commission - or just ditch this whole crap is migrate to something else, as PowerDNS (never touched this thing, though). Heck, I hacked a freaking TP-Link router to use OpenWRT and I'm using DNSMasq for years already on a very chaotic network lab, and I never had one single problem with it. My freaking home lab is 200% more stable and reliable than my DayJob©, believe it of not. And now that I had vented, I have a backlog of a whole week to tackle down until Saturday's night unless I would want to work on Sunday (heck! I wanna play KSP, damnit!) because next week we have some interesting events scheduled and I need to have these tasks tackled down or I will be fighting a multiple front war. Bom, de volta pro tronco...

Worst. Last time I had notice of them, they were still sustaining, unchecked, what they said here on Forum - only in a different place, where they can fully control the timeline and harass or ban anyone that would contradict them. In the end, they are the ones that don't understand how Forum (and similar services) really work - but they will double down on their narrative until the end, because they have nothing to lose by keep lying. As a matter of fact, most of this Forum's problems in the past can be reduced to people not willing to cope with Reality.

Since I'm in deep sheet in the last 2 weeks, all I manage to get now and then are breaks of 15 to 20 minutes max. Can't even play KSP this way, what to say about modding? So I'm playing Rodina again, finishing what I left unfinished in early 2024, last time I played it. Interesting enough, by coincidence a DEV branch is in the works, some new features are coming!

And yet another one, this time with FOSS people fighting back. Ultimetaley, this insanity must stop at some point. https://techcrunch.com/2025/03/27/open-source-devs-are-fighting-ai-crawlers-with-cleverness-and-vengeance/

Hey now, hey now What's the matter with you? Kerbals just wanna have fun now Come on Hey now, hey now What's the matter with you? Kerbals just wanna have fun now (yeah, yeah, yeah, yeah) Come on I light that candle before countdown, MIPSER yells "When you gonna launch it right?" Oh, Gene dear, we're the fortunate ones And Kerbals, they wanna have fun Oh, Kerbals just wanna have fun Hey now, hey now What's the matter with you? Kerbals just wanna have fun now (yeah, yeah, yeah, yeah) Come on A Com Check in the middle of flight, Control Center yells What you gonna do on the maneuver node? Oh, Gene dear, you know you're still number one But Kerbals, they wanna have fun Oh, Kerbals just wanna have That's all they really want, some fun When the launching stage is done You know Kerbals, they want to have fun Oh, come on Hey now, hey now What's the matter with you? Kerbals just wanna have fun now (yeah, yeah, yeah, yeah) Come on (10 + 10 + 5 +2)

As a matter of fact, there's some microbial life with rotors! At that minuscule scale, the simplicity of the solution outweighs the drawbacks.

Hey now, hey now What's the matter with you? Kerbals just wanna have fun now Come on Hey now, hey now What's the matter with you? Kerbals just wanna have fun now (yeah, yeah, yeah, yeah) Come on I light that candle before countdown, MIPSER yells "When you gonna launch it right?" Oh, Gene dear, we're the fortunate ones And Kerbals, they wanna have fun Oh, Kerbals just wanna have fun Hey now, hey now What's the matter with you? Kerbals just wanna have fun now (yeah, yeah, yeah, yeah) Come on (10 + 10 + 5 +1)