updated

README.md

@@ -15,15 +15,32 @@ pinned: false
 
 ### Temporary anonymous rooms for quick file sharing between devices.
 
-No account. No phone login. No personal messenger on office PCs.
+No account. No phone login. No personal messenger on shared PCs.
 
 **Open a room. Share what you need. Everything clears after 5 hours.**
 
-[Live Demo](#) . [Quick Start](#quick-start) . [Why It Exists](#the-little-office-problem) . [Architecture](#how-it-works)
+<p>
+  <a href="https://huggingface.co/spaces/parthmax/TriChat"><img alt="Live Demo" src="https://img.shields.io/badge/Live%20Demo-Hugging%20Face-ffcc4d?style=for-the-badge" /></a>
+  <img alt="FastAPI" src="https://img.shields.io/badge/FastAPI-009688?style=for-the-badge&logo=fastapi&logoColor=white" />
+  <img alt="WebSockets" src="https://img.shields.io/badge/WebSockets-Realtime-3b82f6?style=for-the-badge" />
+  <img alt="Temporary" src="https://img.shields.io/badge/Auto%20Delete-5%20Hours-f472b6?style=for-the-badge" />
+</p>
+
+<p>
+  <a href="https://huggingface.co/spaces/parthmax/TriChat"><b>Live Demo</b></a>
+  ·
+  <a href="#quick-start"><b>Quick Start</b></a>
+  ·
+  <a href="#the-little-office-problem"><b>Story</b></a>
+  ·
+  <a href="#how-it-works"><b>Architecture</b></a>
+</p>
 
 </div>
 
-![TriChat hero banner](docs/images/trichat-hero-banner.png)
+<p align="center">
+  <img src="docs/images/trichat-hero-banner.png" alt="TriChat hero banner" width="100%" />
+</p>
 
 ```text
         [ PC-1 ]  ---- room: project-drop ----  [ PC-2 ]
@@ -33,62 +50,41 @@ No account. No phone login. No personal messenger on office PCs.
                  temporary by design: 5 hours
 ```
 
-> Screenshot/GIF idea: add a short demo here showing two browser windows joining the same room and sharing a file.
+<table>
+  <tr>
+    <td align="center"><b>No Login</b><br />Open a room instantly.</td>
+    <td align="center"><b>Share Fast</b><br />Drop files, links, and notes.</td>
+    <td align="center"><b>Temporary</b><br />History clears after 5 hours.</td>
+    <td align="center"><b>Any Device</b><br />Works in a browser.</td>
+  </tr>
+</table>
 
 ---
 
 ## The Little Office Problem
 
-![The little office problem](docs/images/office-problem-scene.png)
-
-Scene: three friends at work. Three computers. One tiny task.
-
-> "Can you send me that file?"
-
-> "Sure. Wait... should I log into WhatsApp Web on your PC?"
-
-> "Maybe email?"
-
-> "No no, I don't want my personal account open here."
-
-And suddenly, sharing one small file becomes a weird little ritual:
-
-- open personal messenger
-- scan QR code
-- wait for sync
-- remember to log out
-- hope nothing private stays open
+| | |
+| --- | --- |
+| <img src="docs/images/office-problem-scene.png" alt="The little office problem" width="100%" /> | **Scene: three friends at work. Three computers. One tiny task.**<br><br>> "Can you send me that file?"<br><br>> "Sure. Wait... should I log into WhatsApp Web on your PC?"<br><br>> "Maybe email?"<br><br>> "No no, I don't want my personal account open here."<br><br>And suddenly, sharing one small file becomes a whole ritual: open a personal messenger, scan a QR code, wait for sync, remember to log out, and hope nothing private stays open. |
 
 So TriChat started as a tiny escape hatch.
 
-Not a social network.  
-Not a permanent chat app.  
-Just a quick temporary room where teammates can drop files, links, and notes without logging into personal accounts.
+Not a social network. Not a permanent chat app. Just a quick temporary room where teammates can drop files, links, and notes without logging into personal accounts.
 
 ---
 
 ## The Idea
 
-![The idea moment](docs/images/glowing-room-idea.png)
-
-```text
-What if sharing between office PCs felt like passing a sticky note?
-
-1. Create a room
-2. Tell your friend the room name
-3. Drop files, links, or text
-4. Leave
-5. History disappears after 5 hours
-```
+| | |
+| --- | --- |
+| **What if sharing between office PCs felt like passing a sticky note?**<br><br>1. Create a room<br>2. Tell your friend the room name<br>3. Drop files, links, or text<br>4. Leave<br>5. History disappears after 5 hours | <img src="docs/images/glowing-room-idea.png" alt="The TriChat idea moment" width="100%" /> |
 
 That is TriChat.
 
-It is made for quick, low-friction sharing:
-
 | Need | TriChat Answer |
 | --- | --- |
 | Move a file from one PC to another | Join the same room and upload it |
-| Avoid logging into personal WhatsApp/email | No account needed |
+| Avoid logging into WhatsApp or email | No account needed |
 | Share quick links or notes | Send them as messages |
 | Avoid long-term clutter | Auto-clears after 5 hours |
 | Use any device | Works in a browser |
@@ -97,21 +93,26 @@ It is made for quick, low-friction sharing:
 
 ## Features
 
-- Anonymous rooms
-- No signup, no phone, no QR login
-- Text, links, images, and file sharing
-- Real-time WebSocket chat
-- Works across laptops, office PCs, lab machines, and phones
-- 5-hour message and file expiry
-- Small in-memory history cache for faster room loading
-- Supabase-backed storage and database
-- Docker-ready and self-hostable
+<table>
+  <tr>
+    <td><b>Anonymous rooms</b><br />Join with a name and room. No account ceremony.</td>
+    <td><b>Quick sharing</b><br />Send text, links, images, and files between devices.</td>
+    <td><b>Realtime chat</b><br />WebSocket-powered messages feel instant.</td>
+  </tr>
+  <tr>
+    <td><b>5-hour expiry</b><br />Messages and uploaded files are temporary by design.</td>
+    <td><b>Room cache</b><br />Small in-memory cache keeps recent room loading snappy.</td>
+    <td><b>Self-hostable</b><br />Run it locally, in Docker, or on Hugging Face Spaces.</td>
+  </tr>
+</table>
 
 ---
 
-## Story Mode Flow
+## Sharing Flow
 
-![TriChat sharing flow](docs/images/temp-room-flow.png)
+<p align="center">
+  <img src="docs/images/temp-room-flow.png" alt="TriChat sharing flow" width="82%" />
+</p>
 
 ```mermaid
 flowchart LR
@@ -122,12 +123,22 @@ flowchart LR
     E --> F[History clears after 5 hours]
 ```
 
-If GitHub does not render Mermaid in your environment, replace this with an image from `docs/flow.png`.
+---
+
+## Temporary By Design
+
+| | |
+| --- | --- |
+| <img src="docs/images/auto-delete-scene.png" alt="TriChat auto delete scene" width="100%" /> | Every saved message and uploaded file gets an expiry time.<br><br>`created_at + 5 hours = expires_at`<br><br>The cleanup worker runs in the background and removes expired database messages, uploaded files, and stale cached history.<br><br>TriChat is intentionally short-lived. It is for quick exchange, not forever storage. |
 
 ---
 
 ## Quick Start
 
+<details open>
+<summary><b>Run TriChat locally</b></summary>
+<br />
+
 ```bash
 git clone https://github.com/parthmax2/TriChat.git
 cd TriChat
@@ -164,11 +175,15 @@ Open:
 http://127.0.0.1:7860
 ```
 
+</details>
+
 ---
 
 ## Setup
 
-### 1. Create The Database
+<details open>
+<summary><b>1. Create The Database</b></summary>
+<br />
 
 In your Supabase SQL editor, run:
 
@@ -182,7 +197,11 @@ This creates the `messages` table and adds:
 - `file_path` so uploaded files can be deleted from storage
 - indexes for faster room history
 
-### 2. Create The File Bucket
+</details>
+
+<details open>
+<summary><b>2. Create The File Bucket</b></summary>
+<br />
 
 Create a public storage bucket named:
 
@@ -192,16 +211,26 @@ chat-files
 
 TriChat stores uploaded files there and deletes expired file objects during cleanup.
 
-### 3. Add Environment Variables
+</details>
+
+<details open>
+<summary><b>3. Add Environment Variables</b></summary>
+<br />
 
 Use `.env.example` as your guide.
 
 Never commit your real `.env` file.
 
+</details>
+
 ---
 
 ## How It Works
 
+<details open>
+<summary><b>Architecture map</b></summary>
+<br />
+
 ```text
 Browser
   |
@@ -218,19 +247,17 @@ Supabase Postgres
 Supabase Storage
 ```
 
-### Temporary Cleanup
-
-Every message gets an expiry time:
-
-```text
-created_at + 5 hours = expires_at
-```
+</details>
 
-The app cleanup task runs every `CLEANUP_INTERVAL_SECONDS` and removes:
+Core stack:
 
-- expired database messages
-- expired uploaded files
-- stale cached history
+| Layer | Tool |
+| --- | --- |
+| Backend | FastAPI |
+| Realtime | WebSockets |
+| Database | Supabase Postgres |
+| File storage | Supabase Storage |
+| Deployment | Docker / Hugging Face Spaces |
 
 ---
 
@@ -251,48 +278,18 @@ Inserted, read, and deleted test row id: ...
 
 ---
 
-## Screenshots
-
-Add these before launch:
-
-| Screen | Preview |
-| --- | --- |
-| Join room | `docs/screenshots/join-room.png` |
-| Two users chatting | `docs/screenshots/chat-room.png` |
-| File upload | `docs/screenshots/file-share.png` |
-| Mobile view | `docs/screenshots/mobile.png` |
-
-> Tip: a 10-second GIF is more powerful than four static screenshots.
-
----
-
-## Image Prompts
-
-Use this shared visual style for every image so the README matches the app theme:
-
-```text
-dreamy anime-style illustration, soft sky-blue and white glassy UI glow, pastel pink highlights, tiny mint-green accents, cozy modern office, clean rounded shapes, gentle bloom, cinematic lighting, professional but cute, no readable text, no watermark
-```
-
-| File name | Where it appears | Prompt |
-| --- | --- | --- |
-| `docs/images/trichat-hero-banner.png` | Top hero banner | Three young office friends at separate computers in a cozy modern workplace, their screens connected by a soft glowing temporary chat room, floating files and notes moving between devices, white glass panels, sky-blue glow, pastel pink highlights, mint-green status dots, wide cinematic banner composition |
-| `docs/images/office-problem-scene.png` | The Little Office Problem | One coworker hesitating before logging into a personal messenger on someone else's office PC, two friends waiting with a file, privacy concern shown with subtle lock shapes and a phone silhouette, awkward but cute expressions, soft blue-white office lighting, pastel pink monitor glow |
-| `docs/images/glowing-room-idea.png` | The Idea | A small magical chat-room portal appearing between three computer screens, files, links, sticky notes, and image cards floating through it, coworkers smiling with relief, glassy white interface elements, blue glow, mint accents, dreamy startup energy |
-| `docs/images/temp-room-flow.png` | Story Mode Flow | Two office computers connected through a temporary room bubble, files and messages traveling safely between screens, a gentle hourglass symbol showing 5-hour expiry, calm blue-white workspace, pastel pink rim light, clean readable composition with no text |
-| `docs/images/auto-delete-scene.png` | Optional cleanup section image | A temporary chat room gently dissolving into sparkling light after 5 hours, old files and message cards fading like soft particles, hourglass glow, peaceful night office, blue-white base colors, pink highlights, mint safety accents |
-| `docs/images/friends-success-scene.png` | Optional final CTA image | Three office friends smiling around glowing computer screens after sharing files successfully, calm satisfied mood, sunrise light, clean desks, blue-white glass UI, pastel pink warmth, tiny mint-green online indicators |
-
----
-
 ## Perfect For
 
-- Office teammates sharing files across PCs
-- Students in computer labs
-- Hackathon teams
-- Support desks
-- Temporary project rooms
-- People who do not want to log into personal messengers on shared machines
+<table>
+  <tr>
+    <td><b>Office teammates</b><br />Move files across shared PCs without personal logins.</td>
+    <td><b>Computer labs</b><br />Share notes and files between lab machines.</td>
+  </tr>
+  <tr>
+    <td><b>Hackathon teams</b><br />Drop links, screenshots, builds, and quick notes.</td>
+    <td><b>Support desks</b><br />Create a temporary room for fast exchange.</td>
+  </tr>
+</table>
 
 ---
 
@@ -304,7 +301,7 @@ Do not share passwords, private keys, confidential company documents, or anythin
 
 ---
 
-## The Short Story For GitHub
+## The Short Story
 
 I built TriChat because my coworkers and I often needed to move files between office PCs.
 
@@ -316,16 +313,27 @@ TriChat is a temporary anonymous room: open a room, share files or links, and th
 
 ## Roadmap
 
-- Copy invite link button
-- Room expiry countdown in the UI
-- Drag-and-drop file upload
-- Dark mode
-- Optional room password
-- Admin cleanup dashboard
-- One-click deploy buttons
+<table>
+  <tr>
+    <td>Copy invite link button</td>
+    <td>Room expiry countdown in the UI</td>
+  </tr>
+  <tr>
+    <td>Drag-and-drop file upload</td>
+    <td>Dark mode</td>
+  </tr>
+  <tr>
+    <td>Optional room password</td>
+    <td>One-click deploy buttons</td>
+  </tr>
+</table>
 
 ---
 
+<p align="center">
+  <img src="docs/images/friends-success-scene.png" alt="TriChat friends success scene" width="100%" />
+</p>
+
 <div align="center">
 
 ### If TriChat saved you from logging into WhatsApp on a random PC, give it a star.

docs/images/README.md

@@ -1,6 +1,6 @@
 # TriChat README Images
 
-Generate the README images with the prompts in the main `README.md`, then save them here:
+These images are used by the main `README.md` and are tracked with Git LFS.
 
 - `trichat-hero-banner.png`
 - `office-problem-scene.png`
@@ -8,9 +8,3 @@ Generate the README images with the prompts in the main `README.md`, then save t
 - `temp-room-flow.png`
 - `auto-delete-scene.png`
 - `friends-success-scene.png`
-
-Recommended sizes:
-
-- Hero banner: `1600x700`
-- Story scenes: `1200x800`
-- Flow/CTA images: `1200x700`

test.py

@@ -1,110 +0,0 @@
-from datetime import datetime, timedelta, timezone
-from pathlib import Path
-from uuid import uuid4
-import os
-import sys
-
-import httpx
-
-
-def load_env_file(path: str) -> None:
-    env_path = Path(path)
-    if not env_path.exists():
-        return
-
-    for raw_line in env_path.read_text(encoding="utf-8").splitlines():
-        line = raw_line.strip()
-        if not line or line.startswith("#") or "=" not in line:
-            continue
-
-        key, value = line.split("=", 1)
-        key = key.strip()
-        value = value.strip().strip('"').strip("'")
-        os.environ.setdefault(key, value)
-
-
-def require_env(name: str) -> str:
-    value = os.getenv(name, "").strip()
-    if not value:
-        raise RuntimeError(f"Missing {name}. Add it to .env or .env.example.")
-    return value
-
-
-def main() -> int:
-    load_env_file(".env")
-    load_env_file(".env.example")
-
-    supabase_url = require_env("SUPABASE_URL").rstrip("/")
-    supabase_key = require_env("SUPABASE_SERVICE_ROLE_KEY")
-
-    headers = {
-        "apikey": supabase_key,
-        "Authorization": f"Bearer {supabase_key}",
-        "Content-Type": "application/json",
-    }
-
-    test_room = f"test-{uuid4().hex}"
-    test_text = f"Supabase integration test {datetime.now(timezone.utc).isoformat()}"
-    payload = {
-        "room": test_room,
-        "username": "integration-test",
-        "message_type": "text",
-        "text": test_text,
-        "created_at": datetime.now(timezone.utc).isoformat(),
-        "expires_at": (datetime.now(timezone.utc) + timedelta(hours=5)).isoformat(),
-    }
-
-    with httpx.Client(timeout=20) as client:
-        insert_response = client.post(
-            f"{supabase_url}/rest/v1/messages",
-            headers={**headers, "Prefer": "return=representation"},
-            json=payload,
-        )
-        insert_response.raise_for_status()
-
-        inserted = insert_response.json()
-        if not inserted:
-            raise RuntimeError("Insert succeeded, but Supabase did not return a row.")
-
-        inserted_id = inserted[0]["id"]
-
-        select_response = client.get(
-            f"{supabase_url}/rest/v1/messages",
-            headers=headers,
-            params={
-                "select": "id,room,username,message_type,text,expires_at,file_path",
-                "id": f"eq.{inserted_id}",
-            },
-        )
-        select_response.raise_for_status()
-        rows = select_response.json()
-
-        if not rows or rows[0]["text"] != test_text:
-            raise RuntimeError("Inserted test row could not be read back correctly.")
-
-        if not rows[0].get("expires_at") or "file_path" not in rows[0]:
-            raise RuntimeError("Expiry columns are missing. Run supabase_schema.sql again.")
-
-        delete_response = client.delete(
-            f"{supabase_url}/rest/v1/messages",
-            headers=headers,
-            params={"id": f"eq.{inserted_id}"},
-        )
-        delete_response.raise_for_status()
-
-    print("Supabase database integration successful.")
-    print(f"Inserted, read, and deleted test row id: {inserted_id}")
-    return 0
-
-
-if __name__ == "__main__":
-    try:
-        raise SystemExit(main())
-    except httpx.HTTPStatusError as exc:
-        response_body = exc.response.text[:500]
-        print(f"Supabase database integration failed: {exc}", file=sys.stderr)
-        print(f"Response body: {response_body}", file=sys.stderr)
-        raise SystemExit(1)
-    except Exception as exc:
-        print(f"Supabase database integration failed: {exc}", file=sys.stderr)
-        raise SystemExit(1)