Rtarun3606k/TakaTime

🚀 Problem Statement TakaTime generates beautiful statistics cards (visible in public/taka-*.png) via a GitHub Actions workflow. These are pull-based: a user must visit their GitHub Profile to see them. However, many developers never visit their profile weekly and have no passive way to receive insights. The platform already tracks: total coding time per week, top languages, top projects, and streak data. But none of this is surfaced proactively to the user. Real impact: Developers who install TakaTime but don't check their stats lose the behavioral feedback loop that makes the tool valuable. A weekly summary ("You coded 18.5 hours this week — that's 3 hours more than last week! 🚀") significantly increases tool engagement and the habit of reviewing one's coding patterns. Proposed Fix Backend — add GET /api/weekly-report endpoint: // cmd/report.go func getWeeklyReport(mongoURI string) WeeklyReport { // Query MongoDB for the past 7 days of heartbeat data startOfWeek := t

🚀 Problem Statement The repository root contains tree.txt, which appears to be a manually committed snapshot of the directory tree. As the repository evolves across 926 commits and 12 releases, tree.txt will inevitably fall out of sync with the actual structure — creating a misleading reference for contributors. This is a common anti-pattern: manually maintaining a generated artifact in version control. The file creates two concrete problems: Accuracy: Every directory added or restructured makes tree.txt inaccurate. A contributor looking at tree.txt to understand the project structure gets an outdated picture. Maintenance burden: Either the maintainer must remember to update it on every structural change, or it becomes a silent lie in the repo. Proposed Fix Option A — Remove it: git rm tree.txt echo "tree.txt" >> .gitignore The PROJECT_STRUCTURE.md pattern (a hand-curated architectural explanation) is more valuable than a raw file listing. Option B — Auto-generate via GitHub

🚀 Problem Statement The README's Editor Compatibility table explicitly shows: Feature Neovim VS Code Antigravity JetBrains Privacy Controls ✓ Supported ⚙ Planned ⚙ Planned ⚙ Planned PRIVACY.md documents the privacy architecture for Neovim (file path masking, project exclusions, sensitive file pattern matching), but VS Code (vscodePlugin/), JetBrains (jetbrains/), and Antigravity lack this feature entirely. Real user impact: A developer working on proprietary client projects in VS Code is silently sending file paths like /Users/john/clients/acme-corp/salary-negotiations.xlsx or /secret-project/algorithm.py to their MongoDB database. Without privacy controls in their primary IDE, TakaTime's "privacy-first" branding is misleading for most users (VS Code has ~74% market share among developers). Proposed Fix Implement the same privacy controls already in the Neovim plugin for VS Code: Step 1 — Read privacy config in vscodePlugin/Takatime/src/config.ts: interface Priva

🚀 Problem Statement TakaTime's core value proposition is "Bring Your Own Database" — but a self-hosted MongoDB instance (laptop closed, VPN down, free-tier Atlas cluster paused, etc.) is far less reliable than a managed SaaS backend like WakaTime's. Because sync is "non-blocking" and happens in the background, there's a strong chance that if a connection attempt fails, that batch of coding-activity events is dropped silently rather than retried — the user has no way of knowing minutes/hours of tracked time never made it to their database. Proposed Fix Add a small durable local buffer (BoltDB, SQLite, or even an append-only JSON-lines file in the user's config dir) that the sync goroutine writes to first, then drains to Mongo with exponential backoff: // internal/sync/queue.go package sync type Event struct { Timestamp time.Time Project string Language string DurationSec int } func (q *LocalQueue) Enqueue(e Event) error { return q.store.Append(e) //

Description As the project grows, contributors need a standard, cross-platform way to build binaries, run tests, lint code, and clean up their workspace. Right now, developers have to manually type out complex "go build" commands with all the required production flags. We need a "Justfile" to streamline Developer Experience (DX). Task Breakdown Create a "Justfile" in the root directory with the following recipes: "just build": Compile both "taka-upload" and "taka-report" using the production flags: "-trimpath -ldflags="-s -w -buildid="" "just test": Execute: go test ./... -v "just clean": Remove any compiled binaries and clear the local: ~/.takatime/debug-logs.log file for a fresh development state. "just lint": Run: golangci-lint run Testing Requirements Test every recipe locally on Linux and/or macOS to ensure they execute correctly without syntax errors. How to Claim Comment below if you would like to improve the developer experience of this repository. Wait for assign