Unfortunately it seems to be a completely proprietary kernel. I did find a paper on it (presented by Huawei in a conference): https://www.usenix.org/conference/osdi24/presentation/chen-haibo

The first line of the abstract reads

This paper presents the design and implementation of HongMeng kernel (HM), a commercialized general-purpose microkernel that preserves most of the virtues of microkernels while addressing the above challenges.

Another interesting tidbit from the paper:

We started the HongMeng kernel (HM) project over 7 years ago to re-examine and retrofit the microkernel into a general OS kernel for emerging scenarios. To be practical for production deployment, HM achieves full Linux API/ABI compatibility and is capable of reusing the Linux applications and driver ecosystems such that it can run complex frameworks like AOSP [42] and OpenHarmony [35] with rich peripherals.

thats a very fair point, I had not seen anyone else make this one But the problem is that in this case, this functionality was entirely undocumented. I dont think it was intended for programmers.

Now if the firmware was open source, people would have gotten to know about this much sooner even if not documented. Also such functionality should ideally be gated somehow through some auth mechanism.

Also just like how the linux kernel allows decades old devices to be at the very least patched for security risks, open firmware would allow users of this chip to patch it themselves for bugs, security issues.

It was a skin, now its a completely different OS. The initial version, HarmonyOS, was based on Android/Linux, the new HarmonyOS Next, is a proprietary version (or successor) of HarmonyOS based on an open source project/OS, OpenHarmony. It uses a new microkernel instead of the linux kernel.

OpenHarmony is essentially an open source base for making an operating system on top. Its not like the Linux kernel, in the sense that its not just a kernel (in fact you can use the linux kernel with it), but rather a bunch of components people can build upon. And since it uses a permissive license, you can build a proprietary OS on top of it (like the HarmonyOS Next).

Huawei actually launched OpenHarmony many years back but it was not ready for phone usage yet. It was only with the launch of the 5th version that Huawei was confident enough in it to start using it on their own phones.

So the data of the 24 people, who signed for the beta program, were accessible to each other, to all the 24 people? Sounds like nothing burger to me. The odds of someone in the 24 people knowing about this issue beforehand I would say are pretty low.

deleted by creator

We really should be pushing for fully open source stack (firmware, os) in all iot devices. They are not very complicated so this should be entirely possible. Probably will need a EU law though.

aha thanks! i was wondering how ppl do this yeah but tbf discord has a lot of features

depending on which client you use, the ui can be very discord-like (this is cinny): https://raw.githubusercontent.com/cinnyapp/cinny-site/main/assets/preview2-light.png

Also matrix has calls (at least element does), though not sure about screen share. And since when was discord e2e?

I ll admit matrix was for a long time really slow but matrix 2.0 largely solves this and other usability issues. Calls and screen share are still not standardized but its all being worked on.

With matrix, its not just about building one app, its about building a decentralized ecosystem all connected by the matrix protocol. So things tend to take more time.

but it can look similar to discord: https://raw.githubusercontent.com/cinnyapp/cinny-site/main/assets/preview2-light.png

It seems the function has been moved to kglobalacceld/src/component.cpp: https://github.com/KDE/kglobalacceld/blob/master/src/component.cpp#L162

why dont you make something like r/SubredditSimulator? It would be cool to see what modern llms can do in this respect.

rpm-ostree is intended to be the last resort because layering causes issues with updates and other things

you really didn’t have to go through the trouble of writing all this, thats really kind of you!! thank you so much!

Your ansible thing sounds really cool but might be a bit too much for me tbh 😄 Maybe someday I ll have such a smooth setup but for now Im hoping I dont have to reset too much

There is actually an app, konsave, that can backup/restore plasma config but sadly it hasn’t been ported to plasma 6 yet.

Thanks again for all the explanation of the config files. Im planning to create a repo documenting all the info I find so this helps a lot.

thanks thats really useful! its amazing how much utility the linux shell has

(thanks both of you)

a site to sail the high seas iirc

Don’t want to backup the whole folder because I only want to keep a few key settings (specifically my taskbar/widgets positions/config) but I guess I will backup whatever I think is probably related.

Izzy takes apks directly from devs repos iirc Fdroid builds everything themselves so its kinda like the debian repos on linux

You can use ADB to disable them

They will become cheaper over time. In the future buying robots like these could be like buying a new car i.e. expensive but still reachable for most and for others they might be able to buy used ones.

But I dont have much faith in modern tech companies to not fumble this really badly. Will probably end up like the IoT stuff nowadays which have potential but are handicapped by cloud BS and enshittification.

thanks for the comprehensive answer!