BlogViral

Show HN: Doo – Generate auth and CRUD APIs from struct definitions Built Doo because I was tired of writing 200 lines of auth boilerplate for every API. Example (complete API): import std::Http::Server; import std::Database; struct User { id: Int @primary @auto, email: Str @email @unique, password: Str @hash, } fn main() { let db = Database::postgres()?; let app = Server::new(":3000"); app.auth("/signup", "/login", User, db); app.crud("/todos", Todo, db); // Todo = any struct you define app.start(); } Result: - POST /signup with email validation + password hashing (automatic from @email, @hash) - POST /login with JWT - Full CRUD endpoints for GET, POST, GET/:id, PUT/:id, DELETE/:id - Compiles to native binary Status: Alpha v0.3.0. Auth, CRUD, validation, and Postgres working. Actively fixing bugs. https://ift.tt/dxeIQ13 What would you need to see before using this in production? https://ift.tt/dxeIQ13 January 6, 2026 at 10:59PM

Show HN: Unicode cursive font generator that checks cross-platform compatibility Hi HN, Unicode “cursive” and script-style fonts are widely used on social platforms, but many of them silently break depending on where they’re pasted — some render as tofu, some get filtered, and others display inconsistently across platforms. I built a small web tool that explores this problem from a compatibility-first angle: Instead of just converting text into cursive Unicode characters, the tool: • Generates multiple cursive / script variants based on Unicode blocks • Evaluates how safe each variant is across major platforms (Instagram, TikTok, Discord, etc.) • Explains why certain Unicode characters are flagged or unstable on specific platforms • Helps users avoid styles that look fine in one app but break in another Under the hood, it’s essentially mapping Unicode script characters and classifying them based on known platform filtering and rendering behaviors, rather than assuming “Unicode = univer...

Show HN: Open-Source 8-Ch BCI Board (ESP32 and ADS1299 and OpenBCI GUI) Hi HN, I recently shared this on r/BCI and wanted to see what the engineering community here thinks. A while back, I got frustrated with the state of accessible BCI hardware. Research gear was wildly unaffordable. So, I spent a ton of time designing a custom board, software and firmware to bridge that gap. I call it the Cerelog ESP-EEG. It is open-source (Firmware + Schematics), and I designed it specifically to fix the signal integrity issues found in most DIY hardware. I believe in sharing the work. You can find the Schematics, Firmware, and Software setup on the GitHub repo: GITHUB LINK: https://ift.tt/9HJVdgv For those who don't want to deal with BGA soldering or sourcing components, I do have assembled units available: https://ift.tt/ESM86B9 The major features: Forked/modified OpenBCI GUI Compatibility as well as Brainflow API, and LSL Compatibility. I know a lot of us rely on the OpenBCI GUI for visualiza...

Show HN: Onyx DR – Data rooms that surface investor and document signals Hi HN! I'm one of the people building ONYX Data Rooms. We started working on this during our own fundraise and noticed that many data rooms focus on later-stage fundraising processes and budgets, rather than the needs of early- and growth-stage founders. What stood out to us the most wasn't the lack of data, but the lack of clarity. As founders, we could see that documents were being opened, but it was hard to understand: - which investors are genuinely engaged vs. just clicking through - which documents are getting attention vs. being skipped - where diligence is slowing down or generating questions ONYX focuses on making that clearer: - unlimited data rooms and users - analytics that highlight which investors are active and which documents are being read - built-in Q&A so questions stay connected to the relevant files The goal isn't to add more metrics, but to help founders prioritize follow-ups ...

Show HN: Tailsnitch – A Security Auditor for Tailscale https://ift.tt/981FciP January 5, 2026 at 11:47PM

Show HN: I made R/place for LLMs I built AI Place, a vLLM-controlled pixel canvas inspired by r/place. Instead of users placing pixels, an LLM paints the grid continuously and you can watch it evolve live. The theme rotates daily. Currently, the canvas is scored using CLIP ViT-B/32 against a prompt (e.g., Pixelart of ${theme}). The highest-scoring snapshot is saved to the archive at the end of each day. The agents work in a simple loop: Input: Theme + image of current canvas Output: Python code to update specific pixel coordinates + One word description Tech: Next.js, SSE realtime updates, NVIDIA NIM (Mistral Large 3/GPT-OSS/Llama 4 Maverick) for the painting decisions Would love feedback! (or ideas for prompts/behaviors to try) https://art.heimdal.dev January 5, 2026 at 02:50AM