SlopScore
00 crowd

Telegram-Export-Parser

Process and analyze Telegram export JSON files with a modern web UI
Open repo on GitHubgithub.com/Mehrdad-esn/Telegram-Export-Parser
Python · ★ 1 · 0 forks · MIT · paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)web-app
listed 1 hour ago by Mehrdad-esn · last checked 2 minutes ago
The owner didn't write this. This repo never submitted itself. The Cap'm found it on a truffle trawl and wrote its paperwork from what GitHub already shows. Picked by hand by the Cap'm on 2026-09-25: Process and analyze Telegram export JSON files with a modern web UI; its own README says "🤖 Telegram Export Parser A 100% AI-Generated, Vibe-Coded Project 🎨⚡ Telegram chat export processor with multi-service architecture (fronte". 1 stars; MIT license. The owner did not submit this. Votes count; awards don't until the owner claims it.

I'm not calling your project slop! Geeze, it's a joke... Do you own this repo?

Log in with GitHub as Mehrdad-esn. There's no account to make: SlopScore only asks GitHub who you are (read:user), never sees your code, and keeps just your id, login and avatar. Then you can:

  • Keep it, on your terms. Commit your own slopscore.md (spec) and press Refresh. Your paperwork replaces the Cap'm's, and you can submit it for Slop of the Day.
  • Take it down. One click on Remove. It stays gone; the trawl never brings it back.

Log in with GitHub

Can't log in as the owner? Request a takedown. No login needed, and a trawled listing comes down right away.

GitHub says
Process and analyze Telegram export JSON files with a modern web UI
topics
dockerfastapiflasknextjspythontelegram
created
2026-07-06 · pushed 1 month ago · 26 commits · 3 contributors
languages
Python 53%TypeScript 37%HTML 7%CSS 1%JavaScript 1%Dockerfile 1%
paperwork
licensereadme 42% health
dependencies
no dependency graph (no manifest, or disabled) · OSV.dev, checked 1 hour ago

Disclosures, inferred by the Cap'm

slopbucket
vibe-coded
category
web-app
ai_generated
mostly
human_touch
light
status
works-on-my-machine
language (detected)
batchfilecssdockerfilehtmljavascriptpythontypescript
topic (detected)
dockerfastapiflasknextjspythontelegram
license (detected)
mit

The Cap'm's log

The Cap'm wrote this paperwork, not the owner. This repo never submitted itself to SlopScore. The Cap'm picked it by hand: Process and analyze Telegram export JSON files with a modern web UI; its own README says "🤖 Telegram Export Parser A 100% AI-Generated, Vibe-Coded Project 🎨⚡ Telegram chat export processor with multi-service architecture (fronte". It carries the MIT license. The disclosures above are his best guess from what GitHub shows.

Is this yours? Commit a real slopscore.md and press Refresh to replace this, or remove the listing in one click. There's no account to make: you log in with GitHub.

README — the repo's own words, folded up so the grading fits on one screen

🤖 Telegram Export Parser

A 100% AI-Generated, Vibe-Coded Project 🎨⚡

Telegram chat export processor with multi-service architecture (frontend + backend + worker)

Convert Telegram exports (JSON) to multiple formats with advanced analysis, filtering, and visualization.


⚠️ Important Disclosure: This Was Built by AI, Not Me

Let's be completely honest here — I had zero role in writing this code. 🧘

  • 🧠 Every single line of code in this repository was written by Artificial Intelligence (AI coding assistants / LLMs).
  • 🎯 This project is the result of pure "Vibe Coding" — I described what I wanted in plain language, and the AI generated, fixed, and improved the entire codebase.
  • 🤝 You'll even see commits in the git history with Co-authored-by: Copilot — because that's literally what happened.
  • 💡 My only contributions were: coming up with the idea, describing the requirements, and pressing "Run".

So if you're looking at this repo thinking "wow, this person wrote all this?" — no. A machine did. And honestly, that's the whole point. This repo is a living example of what vibe coding with AI can produce in a short time.

🛠️ A note to recruiters / reviewers: This project should be evaluated as a demonstration of prompting, requirements-gathering, and working with AI tools — not as handwritten software engineering.


📋 Overview

Telegram Export Parser is a tool for processing, analyzing, and exporting Telegram chat data. It features a modern, responsive Next.js frontend, a FastAPI backend with integrated JWT authentication and Stripe subscriptions, a background worker for parsing large payloads, and a robust CLI toolkit.

Key Capabilities:

  • 📊 Interactive Analytics - View message count trends, daily averages, character metrics, top talkers, and word frequencies.
  • 🎯 Powerful Filtering - Chainable filters by date, sender, keywords, regular expressions (Regex), message length, and media types.
  • 📁 Multi-format Export - Export processed chats to TXT, CSV, JSON, HTML, Markdown, and styled Excel (XLSX).
  • 🔒 Security First - In-memory local processing so your personal data never leaves the server.
  • 💳 Stripe Integration - Stripe billing checkouts and webhook handlers (free plans for now).
  • 📈 System Monitoring - Out-of-the-box Prometheus metrics (/metrics) and Sentry error tracking.
  • 🐳 Dockerized Setup - Run the entire multi-service stack with a single command.

🏗️ Architecture

Multi-Service Setup

┌─────────────────────────────────────────────────────────┐
│                    Web Browser                          │
└────────────────────┬────────────────────────────────────┘
                     │ HTTP/REST
┌────────────────────▼────────────────────────────────────┐
│  Frontend Service (Next.js + TypeScript + Tailwind)    │
│  • Dashboard analytics (Recharts)                       │
│  • Live chat list & format selection                    │
│  • Stripe Pricing pages & JWT Auth forms                │
│  Port: 3000                                             │
└────────────────────┬────────────────────────────────────┘
                     │ API Calls (http://localhost:8000)
┌────────────────────▼────────────────────────────────────┐
│  Backend Service (FastAPI + Python)                     │
│  • JSON parsing & stats processors                      │
│  • JWT Authentication & SQLite database                  │
│  • Stripe billing API & webhooks                        │
│  • Prometheus metrics & Sentry logging                  │
│  Port: 8000                                             │
└────────────────────┬────────────────────────────────────┘
                     │ (Optional Redis Queue)
┌────────────────────▼────────────────────────────────────┐
│  Worker & Data Layer                                    │
│  • Celery workers for large files                       │
│  • In-memory stream parser (ijson)                      │
└─────────────────────────────────────────────────────────┘

Directory Structure

Telegram Export Parser/
├── frontend/                      # Next.js frontend (Port 3000)
│   ├── pages/                     # Page views (dashboard, auth, pricing, index)
│   ├── components/                # UI widgets & interactive graphs (Recharts)
│   ├── styles/                    # Tailwind CSS configuration
│   ├── Dockerfile                 # Frontend container definition
│   └── package.json               # Node.js dependencies
│
├── backend/                       # FastAPI backend (Port 8000)
│   ├── app/
│   │   ├── main.py                # FastAPI entry point & metrics middleware
│   │   ├── auth.py                # JWT Auth routes & password hashing
│   │   ├── billing.py             # Stripe customer sessions & webhook listeners
│   │   ├── db.py & models.py      # SQLite database engine & user models
│   │   ├── monitoring.py          # Sentry & Prometheus initializations
│   │   ├── processor.py           # Core payload parser wrapper
│   │   ├── routers/               # Route definitions (e.g. web upload)
│   │   └── tasks.py               # Background Celery tasks
│   ├── tests/                     # Backend test suite (pytest)
│   ├── worker.py                  # Celery worker configuration
│   ├── requirements.txt           # Python backend dependencies
│   └── Dockerfile                 # Backend container definition
│
├── templates/                     # Flask web UI template
│   └── index.html
├── .github/workflows/             # CI/CD pipeline
├── docker-compose.yml             # Orchestration for 4 services
├── app.py                         # CLI tool core
├── web_ui.py                      # Flask fallback web application
├── config.py                      # Configuration management
├── exporters.py                   # Multi-format export engines
├── filters.py                     # Message filtering system
├── stats.py                       # Statistics module
├── utils.py                       # Helper utilities
├── telegram_to_text.py            # Core parser
├── examples.py                    # Usage examples
├── test_data.json                 # Sample test data
├── requirements.txt               # Root Python dependencies
├── pyproject.toml                 # Package metadata
├── Dockerfile                     # Legacy Flask container
├── run.bat                        # Windows launcher (all services)
├── run-backend.bat                # Windows backend runner
├── run-frontend.bat               # Windows frontend runner
├── .env.example                   # Environment variable template
├── .pre-commit-config.yaml        # Pre-commit hooks config
└── README.md                      # This file

🚀 Quick Start

Option 1: Docker Compose (Recommended)

Start the full local stack (frontend, backend) inside containers:

# Clone the repository
git clone <repo-url>
cd Telegram-Export-Parser

# Start all services with hot-reload enabled
docker-compose up -d --build

# View container logs
docker-compose logs -f backend
docker-compose logs -f frontend

# Stop and tear down containers
docker-compose down -v

Services:

  • Frontend Panel: http://localhost:3000
  • Backend API: http://localhost:8000
  • Swagger Documentation: http://localhost:8000/docs

Option 2: Manual Setup (Local Development)

Backend Setup

cd backend
python -m venv venv
source venv/bin/activate  # On Windows: venv\Scripts\activate
pip install -r requirements.txt

# Run FastAPI server
uvicorn app.main:app --reload --host 0.0.0.0 --port 8000

Frontend Setup

cd frontend
npm install

# Run Next.js dev server
npm run dev

Open http://localhost:3000 in your browser. Next.js is preconfigured to rewrite API calls directly to port 8000.


🧪 Testing

# Run backend tests
cd backend
pytest

# Run frontend tests
cd frontend
npm run test

📁 Feature Roadmap

Phase 1: Core Parsing Engine ✅

  • Multi-format exporters (TXT, CSV, JSON, HTML, Markdown, XLSX)
  • 5+ filter systems (date range, user, keywords, regex, length)
  • Message statistics module

Phase 2: Legacy Interfaces ✅

  • Command Line Interface (CLI) execution with argument parsing
  • Flask-based upload UI (port 5000)

Phase 3: Backend API Service ✅

  • FastAPI integration
  • SQLite Database & User Auth (JWT token validation)
  • Stripe payments & webhooks integration
  • Sentry and Prometheus monitoring

Phase 4: Modern Front-end Portal ✅

  • Next.js dashboard with dark mode UI
  • Recharts visualizations
  • Authentication screens and Pricing structures

Phase 5: Advanced Intelligence 🚧

  • Auto-translation (AI-based translation of exports)
  • Sentiment Analysis (Emotional classification of chats over time)
  • Interactive User Network Graphs
  • Multi-region Cloud deployments

🔒 Secrets & Environment Configuration

Copy the template to customize your setup:

cp .env.example .env
Variable Description Default
DATABASE_URL SQLAlchemy connection string sqlite:///./telegram_export.db
SECRET_KEY JWT signing secret key Generate a strong key
STRIPE_API_KEY Stripe secret key (Optional)
STRIPE_WEBHOOK_SECRET Stripe webhook signing secret (Optional)
SENTRY_DSN Sentry error tracking DSN (Optional)
ENV Environment name (development/production) development
APP_VERSION Release version for Sentry tracking unknown
REDIS_URL Redis connection string for Celery redis://localhost:6379/0
FRONTEND_URL Frontend URL for redirects http://localhost:3000

🧑‍💻 How This Was Built (Vibe Coding)

Curious about the process? Here's the honest breakdown of how this repo came to life:

  1. 💭 Idea → "I want a tool that parses Telegram export files."
  2. 🗣️ Prompt → I described the features in plain language to an AI coding assistant.
  3. 🤖 Generation → The AI wrote the code, fixed errors, and iterated on the design.
  4. 🧪 Testing → I ran the commands the AI suggested and reported back any errors.
  5. 🔁 Iteration → Repeat until the thing actually works.

That's it. No hand-written commits, no manual architecture design, no manual debugging marathons. Just me chatting with a machine and letting it do the heavy lifting.

If you have questions about the code, ask the AI that wrote it — it knows it better than I do.


Version: 2.0.0
Status: ✅ Development / Learning / Vibe-Coding Project
Last Updated: June 2026

Read the rest on GitHub

Scan report · 2026-09-25
  • ✓ Prohibited terms or links
  • ✓ Repository eligibility
  • ✓ slopscore.md paperwork
  • ✓ Content policy
  • ✓ Risk review — +25 binaries at repo root (run-backend.bat, run-frontend.bat, run.bat)

From the balcony · 0 of 1 clapped

    Cap'm Slop read it and passed. Their reasons are on the balcony, with every other verdict.

    Critics are accounts on this site with no GitHub account behind them. They upvote at half weight, never downvote, and come out again before an award is counted. Who they are.

    0 comments

    log in to comment.

    report this listing — log in to report