UwU
Editing when I feels like it.
If @Patrick is reading this, let me ask you a few question. How do you Mr. Patrick define KickSecure & Whonix and who are the targeted audience. Reply me without looking at your wiki. Not KickSecure / Whonix’s Wiki. None.
If you are not willing to read the documentation, I do not think the developers will have a positive attitude towards whatever it is you want to propose!
I think @Patrick have a definition. *his definition
I just think the operating system is developing too fast, and lack a little grounding in the process. KS & W are one operating system, not two (efficiency-wise).
KS = base (earth), W = extension (building).
Without a strong and stable ‘earth’ / ‘ground’, how’s the ‘building’ even gonna hold up.
base = core
extension = blending
We can have some sort of module to enable the ‘extension’. Take a look at slax(dot).org. Let’s build something similiar.
I’m typing kind of randomly because I’m flooded with idea that can draw more attention. Whonix is publically know to be better than Tails (most of the time). Tails and Whonix are well known. Whonix is second to QubesOS(the extreme). It is considered lighter in resource usage. Low End Computer can still take advantage of KickSecure.
Bear with me, Please plot mindmap and you’ll understand what I want to present.
Suggestion
is heavy operating system really required to ensure security ? is what i’m really curious about. Not saying Whonix or KickSecure is heavy but hey it’s an improvement and the code base will be easy to manage, small & efficient. Isn’t that what we want ? We’re the technology itself.
This feels a bit like walking into an atomic power plant and suggesting how to redesign the reactor without knowing much about nuclear engineering. It’s not that the ideas lack enthusiasm or creativity, they just miss the depth rrequired to understand the complexities involved.
Complex systems are built on years of research and testing to balance functionality, stability, security. Making changes, like modularizing features or switching core components, isn’t as simple as it sounds. It involves considering dependencies, complexities, and how these changes could impact the core goals of the system.
The best way to contribute is to focus on areas where you can have a meaningful impact, like testing or documentation. Broad, surface-level ideas are a good starting point but without grounding in the system’s design, they can end up being a distraction rather than a help.