Hi, I'm
I'm a student in computer science, big data, and AI. Most of what I build started because I wanted the thing to exist: a tool for a server I run, a script to skip a chore I was tired of doing, a side project to learn something I didn't know yet.
I'm studying computer science, big data, and AI, with math and stats on the side. School covers the theory; the projects on this page are how I actually learn, by building, breaking, and trying again.
I tend to follow projects all the way through, from the first architecture sketch to the boring maintenance afterwards. Security gets a lot of my attention, mostly because I run things and have learned the hard way what happens when you don't.
Minecraft plugins are the side I keep coming back to; there's a small collection of them at the bottom of this page.
If you're working on something and want to chat, my inbox is open.
Streaming anomaly detection on crypto markets. Kafka carries the trades, Spark turns them into rolling z-scores over one-minute windows, an Isolation Forest decides what looks wrong, and a terminal client shows you what it flagged. It runs either on a simulator with anomalies injected on purpose, which is the only way to know whether the detector is any good, or on live Binance trades.
Point it at a host you are allowed to scan and it maps the attack surface: open ports and the services behind them, DNS records and subdomains, TLS and HTTP posture, WHOIS, and the files people forget on a web root. The port scanner is a separate Rust binary, so it can be tested on its own. No server and no account, just a SQLite file you can list, diff and export from.
A command line audit of the machine you are sitting at, on Linux, macOS or Windows: kernel and services, listening sockets and firewall, accounts and SSH keys, file permissions, and installed packages matched against OSV.dev. Out comes a score over 100 and one HTML file with everything inlined, so it opens offline, each finding carrying the commands that fix it.
Type in a GitHub username and the profile comes back as something worth looking at. Repos become stars in a force-directed constellation, sized by stargazers and pulled together by shared language, next to a clickable contribution heatmap, a streamgraph of how someone's languages shifted year to year, and a Wrapped-style recap with its own shareable URL. No login anywhere.
Two claim plugins and a framework with its own addons. Some open source, some paid, all in production on real servers. It is the corner of programming I keep coming back to.
Chunk-based land protection. Players claim, merge and sell territory from a set of menus, with more than 30 per-claim settings covering visitors, members and natural events. Claims show up on Dynmap, BlueMap and Pl3xMap, Bedrock players get native forms, and there is a sync and async API for other plugins. 1.18+, Folia included.
The rewrite, for servers that outgrew a single permission list. Four roles per claim plus as many custom ones as you like, 130+ permissions, 70+ protection flags, temporary invites, claim templates, an optional rent system and an audit log you can export. Caffeine in front, Redis optional, SQLite or MySQL behind.
The framework the other X plugins sit on. Three cache layers (Caffeine, Redis, database), cross-server sync over Redis Pub/Sub or database polling, an addon loader, GUIs described in YAML, a multi-currency economy that registers as the Vault provider, leaderboards, deliveries for offline players, and a web dashboard with a REST API.
Bans, mutes, warns and jails, plus ban waves you build quietly and drop all at once. A Bayesian chat classifier trained in five languages reads through obfuscation, and alt detection weighs eleven signals, from a shared address down to what sits in someone's options.txt. VPN, proxy and country blocking on top. The same jar runs on the proxy.
Fixed-price listings and live auctions in any currency XCore knows about, with snipe protection, tiered bid increments and automatic settlement. Eleven categories computed from the item rather than stored, search by name, price or material, standing alerts and price history. An expired listing nobody reclaims goes back to its seller through the mailbox.
Online mode decided per player: a premium account is verified against Mojang and connects with its skin and no password, everyone else registers. TOTP two-factor with single-use recovery codes, a captcha drawn on a map, PBKDF2 at 210k iterations, sessions shared across servers, Bedrock players through Geyser. One jar for Velocity, BungeeCord and XCore.
Prevention rather than cleanup: a chunk that has hit its cap will not accept another hopper. Mob and item stackers that keep loot tables honest, per-chunk limits, redstone clock detection, TNT rate limiting, and a TPS and MSPT monitor that walks up through optimisation levels as the server degrades and unwinds them once it recovers.
Email is the easiest way to reach me. I read everything that comes in, and reply to most of it: project ideas, questions, or just a chat about something you're working on.