currently doing shit

I make shits
that shouldn't exist.

FarizGD is a fake developer playground spanning Geometry Dash, Minecraft, WhatsApp bots, AI, Android, Linux, APIs, server tooling and a frankly unreasonable number of experiments.

62
repositories in the connected account
8
recurring technical worlds
OSS
open-source bias
∞
side quests

the pattern

One stack was never going to be enough.

The READMEs paint a surprisingly consistent picture: practical tools first, polish second, and curiosity everywhere. There are old bot projects, infrastructure experiments, game tooling, Android forks, AI templates, APIs, Minecraft plugins and tiny “let's see if this works” repositories.

Geometry DashMinecraftWhatsAppAI / LLMAndroidLinuxWeb / APIsAutomation
README signalwhat keeps showing up
Building things to solve immediate problemshigh
Open-source / fork culturehigh
Game / Minecraft ecosystemhigh
AI experimentationrising

project atlas

The repository wall.

Search it. Filter it. Click something weird.

README DNA

The documentation tells a story.

The strongest recurring signals are not a particular programming language. They're the desire to fork, modify, deploy, automate and make software useful on real devices. Some READMEs are polished upstream documents; others are gloriously short. Both are part of the history.

🎮

Games are a recurring anchor

GDBrowser, Minecraft tooling, FLauncher, Oraxen and the custom CD plugin connect the profile to game infrastructure rather than just game-playing.

🤖

Bots → AI is a natural progression

The repository history moves from WhatsApp/Termux bots and Baileys modifications toward chatbot and LLM projects using modern web stacks.

📱

Devices matter

Termux, scrcpy, Telegram client work and Android-focused projects suggest a preference for software that touches actual hardware.

🧪

Experiments are allowed to be experiments

Tiny repos with one-line READMEs sit beside huge projects. That's not necessarily mess—it is a public lab notebook.

final summary

Developer by curiosity.
Gamer by default.

If a tool is annoying, build one. If an API is missing, make one. If a project is interesting, fork it. If an idea sounds stupid, that's probably enough reason to prototype it.

View GitHub ↗