Skip to content
View Deadtrix21's full-sized avatar
🌴
On vacation
🌴
On vacation

Block or report Deadtrix21

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
Deadtrix21/README.md

Deadtrix21 — I build to understand. Software, systems, and the interfaces between them.

Software developer. Systems enthusiast. Always learning.
I like understanding what happens underneath—and making the surface feel right.

Selected work · Noxius Studium · My repositories


The person behind the code

I'm Deadtrix21. I learn by building: take an idea apart, turn it into something executable, and find out which assumptions survive.

My interests sit between low-level systems, cryptography experiments, and thoughtful interfaces. I care about memory use, throughput, and small application footprints—but I also care about the details that make a tool pleasant to use. Moving between those layers is part of the fun.

Not everything here is a finished product. Some projects are practical tools; others are experiments or reference implementations. I would rather make that distinction clear than pretend every repository is production-ready.

What keeps me curious

My interests connect systems, contracts, and interfaces: native code and FFI; events, protocols, and conformance; desktop tools and interaction design.

  • What is the machine actually doing? Native code, memory behaviour, FFI boundaries, and the cost of moving data.
  • Can I make the behaviour explicit? Event systems, comparable APIs, shared specifications, and useful diagnostics.
  • Would I enjoy using this? Desktop utilities, clear controls, and interfaces with attention to detail.

Selected work

A lot of my recent work lives under Noxius Studium. That is where the wider collection of tools and experiments lives.

FluidMusic: one queue coordinates Spotify Connect, internet radio, and local music while keeping their playback engines separate.

A music workspace for Hermes Desktop: Spotify Connect, internet radio, a persistent local library, mixed playlists, and source-aware controls. One listening workflow, without pretending every provider has the same playback engine. Audio visualization is available only where the source exposes samples—not Spotify Connect.

Architecture · Limitations

Enchanted Composer: unsent drafts, reusable prompts and undo/redo are separate from explicitly started, owner-bound voice.

Draft enhancement, reusable prompt libraries, multi-step undo/redo, and explicitly started, owner-bound live voice for Hermes Desktop. Native send controls stay intact. Ordinary voice transcripts remain temporary; delegated tool work stays with the captured chat.

Installation · Architecture

EventFlowSys routes messages with priority and TTL to threaded and async subscriber groups, with hooks and metrics.

A Python event bus with threaded and asyncio implementations, grouped subscriptions, priority, TTL, hooks, and metrics. An exploration of making message delivery and its boundaries easier to inspect.

Examples & tests · PyPI

ZNRG public artifact shelf: znrg.dll and example original, encrypted and restored files. Published samples are not an independent cryptographic security audit.

My experimental cryptography and native-library work. The public repository currently contains binary artifacts, example files, and screenshots, rather than the implementation source. It is a research project—not a claim of independently audited or production-proven cryptography.

Also worth exploring: REST / GraphQL / SOAP / gRPC, an educational comparison built around one shared resource registry, SQLAlchemy domain model, and contract tests. My private workbench also includes South African ID-number conformance, Rust/Tauri desktop tooling, and Kotlin cross-platform experiments; those are not public downloads.

Tools I reach for

My current workbench: C#, PHP, Python, JavaScript, TypeScript, React, Next.js, HTML, CSS, Rust, C++, C, Tauri, FastAPI, Laravel, SQLAlchemy, REST, GraphQL, SOAP, gRPC, databases, Docker, Linux, PowerShell, Playwright, pytest, Vitest, and active exploration in Go, Kotlin, Java, and Swift.

How I work

Question, build, test, measure, refine.

Say hello

Have a reproducible bug, a focused improvement, or an interesting technical question? Open an issue or pull request in the relevant public repository.

If my work helps you build something, a visible link back is appreciated. Check each repository's license before reuse—public visibility does not mean identical terms.


Keep the curiosity. Test the assumption. Make the next version better.

@Deadtrix21's activity is private