english moderator application, klango 3.5.4 discontinuation, klangten, archival of old klango posts

Hello all of you klangons.

Wow, we are actually over 300 now. This is still kind of hard to believe. Thanks to everyone for trying klango out.

The last 2 weeks were pretty exciting for klango. Let me list everything that happened.

English moderator poll now open

In the last 2 weeks, people had time to submit their moderation applications for the klango english community. 4 people did. Now, the poll to vote is open. It will also last for 2 weeks, starting today, so till the 22.10.2026. Feel free to vote, and ask the applicants questions in their topics. Poll results will be disclosed after these 2 weeks.

Klango 3.5.4 is discontinued

Now, don't panic, this does not at all mean the end of the klango client. Just the end of that particular version. Klango 3.5.4, as you maybe can tell from the name, is a direct followup to the old klango3.5.3 program. It uses old klango source code, which is a licensing issue to say it mildly. Also, a lot of code is old, the rust host for the lua engine especially under windows never ran as i wanted it to run, and under mac it runs good though has massive ram leakage issues that i just could not wrap my head arround.
People that were there from the start maybe remember the klango4 alpha link on the klango.online website. Klango4 is a full rewrite of klango. New engine, better code, better performance. Klango4 is rewritten from the ground up in python, based on my fork of the lucia audiogaming engine. It is much much easier to maintain, and finally offers same performance over windows and macos. I am typing from it right now, on a windows machine, and it runs extremely smooth, no longer takes 30 seconds to boot up etc.
It also makes it better for the community. It runs on a much better translation system (po edit), and it has a better program system. For klango programs, lua was becoming a problem as it made it harder to include dll files and external libraries. Every new library that was added required a klango host update since the rust host had to forward the dll functions and flags to lua. That made releasing new programs anoying for me as the developer, and nearly impossible for others, also the klango api was undocumented. With the new klango4, we have the flexibility of python for programs, a documented api, and a script for ai agents to help them generate klango programs. All existing programs are already ported over, and we have a new one, klango whatsapp. Yes, a whatsapp client, build into klango.
Funfact, people were asking me why spotify in klango is under the files submenu. When i first had the idea for spotify in klango, spotify was soposed to be a program. How ever, due to this host difficulty, i decided to just build it into klango, and i thought files was the most fitting of all the menus.
Klango 4 also has other nice things, for example, a real chromium browser so you can actually use real websites, much faster youtube playback, and maybe more. Klango4 will replace klango3.5.4b soon. All your data will be carried over at first klango4 launch, so no vorries, you are not loosing anything, and the usage concept stais the same.

Archival of old klango archived topics
I had a poll open on what we should do with the old klango archived posts, and it concluded on archive them. All of the old klango archived topics are now no longer in the active communities, with the only difference beeing topics that were already responded too since last month. They are now in groups on klango, which are read only.

Klangten

Klangten was released, a fork of the elten client. It is for these people that like the elten client more but still want to explore the klango community. Also, it changes some design choices, for example, file manager and youtube are back included and no longer require downloading. Klangten also runs on android and IOs, so check it out. One thing. The elten developer was, let's say, not particularely pleased about klangtens release. I tried to talk with him in private about this matter, but this is difficult and most discussions about it are running in the pollish community. I corrected a licensing issue about klangten which he also pointed out in the pollish community, but in general i think that i am free to distribute klangten, as it is, like elten, open source under gplv3 just like elten. I will try to keep klangten as long as possible.

So as you see, this was a pretty interesting time for klango. Thank you all for staying tuned, and enjoy klango.

TWhisk