Projects on Prateek Sharma

Goroomlib

Sun, 23 Aug 2026 00:00:00 +0000

Across the poker platforms I’ve worked on at Adda52 and Mind Sports League, one shape kept showing up: users joining a table, leaving it, sending messages to everyone at it, and the server keeping track of who’s where. Every time I touched a new real-time feature, I ended up rewriting the same User and Room bookkeeping from scratch. I wanted to pull that pattern out once, get it right, and stop reimplementing it.

Tidylnk

Sun, 23 Aug 2026 00:00:00 +0000

Tidylnk is a URL shortener I built to have a simple, self-hosted alternative to the usual third-party link shorteners, with an admin panel to manage and track links.

Tech stack

Backend — Go, serving the redirect and link-management APIs.
Frontend — a React admin panel for creating, organizing, and tracking shortened links.
Storage — PostgreSQL as the primary datastore for link records, with Redis on the redirect hot path for fast lookups.
Deployment — backend and database containerized with Docker and deployed on Railway.

Why I built it

I wanted a link shortener I fully controlled — no reliance on a third party’s uptime, rate limits, or analytics restrictions — and a project to exercise Go and Redis together on a workload where caching genuinely matters: redirect latency.

WazirX Go Connector

Sun, 23 Aug 2026 00:00:00 +0000

WazirX is one of India’s largest crypto exchanges, and while its REST API is well documented, it doesn’t ship an official Go client. I wanted to poke at their API for a side project and didn’t want to hand-roll request signing and endpoint plumbing every time, so I built wazirx-connector-go and open-sourced it once it was in decent shape.

Avoiding ~25 near-identical methods

The exchange exposes close to two dozen endpoints — tickers, order book depth, order placement, withdrawals, sub-account transfers, and so on. Writing a hand-rolled method for each one would have meant the same boilerplate repeated two dozen times: build params, sign if needed, pick GET/POST/DELETE, hit the URL, parse the response.

WazirX Java Connector

Sun, 23 Aug 2026 00:00:00 +0000

After building the Go connector for WazirX, I wanted the same thing on the JVM — but WazirX doesn’t publish an official Java client at all, REST or WebSocket. The REST half was a fairly direct port of what I’d already learned building the Go client. The WebSocket half turned out to be its own project.

Letting callers choose their failure granularity

For errors, I didn’t want every caller forced into one giant catch-all exception, but I also didn’t want to force a try/catch at every single call site. I split errors into two, with one extending the other:

Audio Cloning

Mon, 23 Jun 2025 00:00:00 +0000

This is an extension of the Video Translator tool that generates cloned audio for short subtitles, improving the quality of the dubbed output. It uses OpenVoice and MeloTTS to clone the original speaker’s voice.

Challenges

Library compatibility. The libraries weren’t functional on Python 3.12, which I was using — they worked on 3.10. So the TTS stage couldn’t live in the same script as the rest of the pipeline.
Short subtitles. The libraries needed a longer sample to clone a voice well, and very short lines (hello, hi, bye) errored out.

What I changed in the fork

openvoice/se_extractor.py had a check that discarded audio segments shorter than 1.5 seconds. Words like hello fall under that. I relaxed the check to allow segments down to ~0.5 seconds, and added a skip for lines too short to process.
Added melo-tts to requirements.txt (the docs mention it but don’t pin it).
Added a driver script that points at a video-translator output folder and runs cloning across every generated audio file.
Patched the library to run on CPU for Apple M1.

The fork is at github.com/pratts/OpenVoice ; test1.py runs the cloning over the translator’s output.

Video Translator

Mon, 23 Jun 2025 00:00:00 +0000

I always wanted to watch Japanese anime and other foreign-language films in English without living in the subtitles. During a break I decided to see how far open-source models could get me, and built a script that:

Extracts the background audio from the video.
Transcribes it to a subtitle file in the original language.
Translates each subtitle to English.
Converts the translated subtitles to audio.
Merges the translated audio with the background track.
Muxes the final audio back into the video.

I wanted to lean on open-source tooling and minimize paid services:

TTS Study Assistant

Mon, 15 Jan 2024 00:00:00 +0000

The TTS Study Assistant lets you select text on any webpage, save it as a note, hear it read aloud, and summarize it with AI for review. It’s a Chrome extension (Manifest V3), a Go/Fiber backend, and a React admin panel.

Architecture

Backend (Go) — Fiber for HTTP, PostgreSQL via GORM, JWT auth, OpenAI for summarization, deployed on Railway in a Docker container.
Frontend (React + TypeScript) — Vite build, React Query + Context for state, deployed on Vercel.
Extension — Manifest V3 service worker, Chrome Storage API for local state, Chrome TTS API for playback, content scripts for text selection.

Decisions worth noting

Source-based token lifetimes

Web sessions and extension sessions have very different UX expectations, so the access-token lifetime depends on where the request comes from: