Hello Genodians,

I'd like to reiterate the mobile emphasis without tracking features.  My spare SSD is occupied by Haiku release1 beta4 and I see little chance of that being evicted in favor of another desktop OS.  My PinePhone would be a much better target, however.  I bought it specifically to see how secure a mobile platform could be!  Genode was one of the mobile targets I was hoping to try.

My primary SSD on my desktop (a 3rd-gen i7), my laptop (a PineBook Pro) and my PinePhone (3GB RAM, 32GB internal storage) are presently all running Manjaro Linux.  If I could evict Manjaro from all 3 places, that would be a good year for me.  Despite liking the desktop experience, Manjaro has no privacy features that I'm aware of.  Microkernels that keep every driver in user-mode and don't allow drivers to "call home" to their manufacturer or their manufacturer's government would be an ideal privacy feature.  Binary blobs should be disallowed from such behavior.

Finally, I foresee an involvement with WebAssembly to be a replacement for most binary blobs in a short period of time and as soon as that takes place, address sanitizers and other sandboxing technologies could be complimentary to the AGPL license strategy.  I have already submitted some patches to the W2C2 project on GitHub at https://github.com/turbolent/w2c2 and would like to hear your thoughts on the subject of using bytecodes to sandbox drivers and other binary blobs.

Note:  presently drivers cannot be represented in the WASI standard APIs so another API variant will be needed.  There is a discussion started on the subject at https://github.com/WebAssembly/WASI/discussions/501#discussioncomment-4188701 if interested.

Thanks for your time and efforts,