open source · github
Network diagnostic tools, a Minecraft client and a cooperative browser game: explore the problem behind each project, its development status and the source code.
$ tree --status
~/projekte ├── netsage/ python in development ├── signal-lost/ typescript in development ├── socketscope/ c# v1.0.0 ├── console-client/ c# v1.3.0 └── zvt2sumup/ c# v1.0.1
5 projects · 3 released · 2 in development
repositories
Network diagnostics should remain traceable, even with AI. I’m developing a foundation that gives the model sanitized findings and limited diagnostic tools, without credentials or shell access.
A cooperative puzzle built around communication: two to six players investigate the same station but receive different evidence. I’m developing separate role views and shared browser interactions.
Which process is behind an open port? My local inspector connects TCP and UDP endpoints with processes, services, containers and firewall evidence, without modifying systems.
Chat and AFK do not need a rendered game world. My Minecraft Java client maintains a real session through a Windows interface or a headless CLI on Windows and Linux.
The cash register speaks ZVT; the terminal uses SumUp. My Windows gateway bridges the two over TCP or COM and makes payment flows traceable with diagnostics and a simulator.
Release data checked:
Current, without visitor tracking.
The web server queries the public GitHub API every hour. Your browser loads the data only from oexyz.de and connects to GitHub only when you click a marked external link.