Why Did I Build This?
"Operating on the Tor network requires uncompromising adherence to OPSEC principles—most notably, the absolute elimination of client-side JavaScript to prevent deanonymization, IP leaks, and zero-day executions. I engineered this blog architecture to function flawlessly under the Tor Browser's 'Safest' security level. It strips away modern SPA bloat, replacing it with a highly optimized, dynamically generated HTML/CSS frontend, ensuring maximum anonymity and rendering speed over high-latency onion routing."
Architecture & Decisions
The backend is a high-performance Go application utilizing the Fiber v3 framework for rapid HTTP routing. Data persistence is managed by a CGO-free SQLite driver (`modernc.org/sqlite`), ensuring lightweight, seamless cross-compilation without external C dependencies. Authentication relies on bcrypt hashing and hardened `HttpOnly`, `SameSite=Strict` cookies. The frontend is entirely Server-Side Rendered (SSR) using Go templates; it contains zero JavaScript. The relational database schema is designed for a scalable blog architecture, mapping Categories to Topics and specific Blog Nodes (Communities), while enforcing strict server-side authorization middleware for all CRUD operations.
Key Features
- 01.Absolute Zero-JS frontend guaranteeing compatibility with Tor Browser's maximum security tier
- 02.High-speed Server-Side Rendering (SSR) via Go templates to combat onion network latency
- 03.CGO-Free SQLite database integration for simplified deployment and embedded data persistence
- 04.Bcrypt-secured authentication pipeline with hardened, HttpOnly cookie session management
- 05.Multi-tiered blog architecture (Categories > Topics > Nodes) with dynamic SQL generation