mastodon 4.7.2CTO at satoshi-connect.ch.
@bebop@tooting.ch ambassador.
I’m curious and passionate about free software, decentralized systems and decentralized finance. I’m interested in Haskell, Nix, Rust but also embedded systems, radio comm ops and the occasional math paper.
In my free time, I contribute to open source projects, promote blockchain-based solutions to real-world problems or study RF signals around me.
Salvadorian. I also *really* like trains :)
@moschehaus@social.moschehaus.com Made some progress this we. Most of the setup works: Clone a repo, list the recipients used by the repo and import the age identities in the #yubikey #PIV on both #cosmic and #android both using #slint.
The critical paths now work, next up:
The first release will be a read-only vault you can use to unlock and audit secrets.
Mythbusters vibes :)
Embedded development is such a pleasure in 2026.
I remember using eclipse in 2010, with "golden" BSPs you would never date to update. You had one shot at setting up **one** cross-compile toolchain and don't even think about using a different compiler version than the one specified by your vendor (or downloaded during install).
Now, simply specify the compiler in devenv.nix. Gone are the long hours of looking in the library documentation on how to use this untyped API.
Hey @drakulix@social.dreampi.es!
I discovered that mapping a touch or pen input to an output is supported by cosmic-comp, but there's no UI for that in the cosmic-settings.
I need this setting when working with an external display with touch and stylus input and I think other people would appreciate this.
Does it make sense to add a section to cosmic-settings, next to the screen position settings that allows the user to map an input device to an output?