u/the_big_flat_now

the node graph looks absolutly insane. https://i.ibb.co/DPzsNgBZ/Master-Selects-AAA-Scroll.png

This is what’s going on inside my head on rocky terrain

Live camera goes into the timeline like any other clip, gets a voxel effect, then I add a 3D camera and orbit around the whole thing. All realtime, no install.
It's part of a video editor I've been building for the last few months.

vanilla Three.js. Scroll position controls one shared timeline for the camera, layerexpansion, rotations, lighting and audio, so the scene can also run backwards without losing its state. I first treid svg, but the lack of camera orbit pushed me the three.js way. How would you improve the design? I played around with PBR materials, but perhaps its to much...

https://raios.tech
https://github.com/Sportinger/raios-website/tree/main/ui-lab/site/three-film

*Not another linux kernel* Hey! Lately I’ve been spending a lot of time on an operating-system idea called raiOS. Most individual parts are not new, but I haven’t found another system that combines them in quite this way. It is still early, but the custom Rust kernel boots on a Surface Pro 4. Framebuffer output and USB/HID works, and the Marvell Wi-Fi bring-up currently reaches firmware loading, scanning and the WPA2/PMK path. Association and actual traffic are not working yet.
The main bet is this: AI will make software extremely cheap to create, but potentially dangerous to install blindly. People who cannot read or audit generated source code still need enforceable boundaries and evidence about what happened before installation.
The rough architecture is:

1. A small custom Rust kernel owns hardware, recovery and the lowest-level authority. (its NOT smal atm lol)
2. A narrow “Genesis” layer creates services and grants explicit capabilities.
3. An interchangeable AI agent may receive limited network access for research.
4. Generated source enters the system as inert data.
5. An isolated builder compiles Rust to Wasm without ambient access to the live system.
6. The resulting artifact passes deterministic checks, negative tests and disposable test environments.
7. The reports, requested capabilities and exact artifact hash are presented to the owner.
8. Only after explicit approval may the Wasm service run with a minimal capability set.
9. The service should remain revocable, restartable and rollbackable.

Why not sel4?
At this stage, continuing with the existing Rust kernel is the fastest path because the hardware bring-up already runs on it.

Source: https://github.com/Sportinger/raios

I also did a Mock website, mostly to iterate on the UI design, and try to explain the hole idea to myself (its an attempt) www.raios.tech

I would like to talk about the basic principles here, if somebody is also interested :)
Perhaps its shit, but anyway its fun for me and iam learning so much.