Voldigoade
Loading Workspace
Voldigoade
Loading workspace
Voldigoade
Loading Workspace
I mostly build tools that give me a good excuse to understand what actually happens under the hood: Rust CLIs, OSINT, firmware, privacy, and systems. I like starting from a concrete behavior, tracing it back to how it really works, testing edge cases, and keeping only what can be verified. The code ends up on GitHub, the research and write-ups live here.
Command-line tools: strict typing, clean error handling, and standalone binaries.
Public footprint inspection, metadata exposure analysis, and encrypted protocol studies.
Semantic diffing of extracted firmware rootfs trees, file hierarchy inspection, and artifact extraction.
Standalone tools running locally without constant dependencies on external cloud services.
The first language I chose to learn seriously. I use it mostly for CLI tools, systems utilities, and backends where I want control, strict typing, and a standalone binary.
My daily environment to develop, test, automate, and understand what is actually happening on the machine.
The go-to choice for quick scripts, parsing, data analysis, and small tools where getting a fast result matters more than building a binary.
For web apps and interfaces: front-end, data integration, and anything that needs to run cleanly in a browser.
Rust CLI to inspect what a GitHub account or repository exposes publicly: commits, keys, and metadata.
Rust prototype to compare two extracted Linux firmware rootfs trees and produce clean diff reports.
Methodical comparison of secure messaging apps evaluated across threat models, metadata exposure, and audits.