LibreFang 2026.4.27 Released LibreFang v2026.4.27 ships the changes below. See the full changelog for the complete list. TUI setup wizard now offers microsoft, zai, zai_coding, volcengine, volcengine_coding, byteplus, byteplus_coding alongside the existing first-run options. The wizard's PROVIDERS list had drifted from PROVIDER_REGISTRY and silently hid these from new installs; a unit test now p
If this is useful, a ❤️ helps others find it. Everything I keep looking up when building Tauri v2 apps — in one place. // Define #[tauri::command] fn greet(name: String) -> String { format!("Hello, {}!", name) } // With error handling #[tauri::command] fn read_file(path: String) -> Result { std::fs::read_to_string(path).map_err(|e| e.to_string()) } // Async #[tauri::command] async fn fet
TL;DR: I built ChessDada — a free multiplayer chess platform inspired by old Yahoo Chess. No signup, no download, just instant browser-based chess. Built with Node.js, Socket.IO, and chess.js. Modern chess sites are bloated. Chess.com forces you through signup. Lichess defaults to account creation. The "5-second click and play" experience that made Yahoo Chess legendary in the 2000s is essentially
The repo is finally unlocked. enjoy the party! The fastest repo in history to surpass 100K stars ⭐. Join Discord: https://discord.gg/5TUQKqFWd Built in Rust using oh-my-codex.
A practical look at using tower as the middleware layer for Rust AWS Lambda functions, with examples that build up to a DynamoDB-backed per-IP rate limiter. It covers Service, Layer, stack ordering, short-circuiting, boxed async futures, and testing middleware without deploying a Lambda. Comments
The EU's Digital Product Passport (DPP) requirement is moving from regulatory text to technical reality. Under the Ecodesign for Sustainable Products Regulation (ESPR), products sold in the EU must carry a DPP—a machine-readable identifier linking to standardized lifecycle data. For developers and compliance teams, 2026 marks the year where pilot programs transition to real deployments. Here's wha
TL;DR: I built a P2P file transfer tool that runs entirely in the browser. No install, no server relay, no account. Here's what I learned about WebRTC data channels, resumable transfers, and the browser storage mess along the way. Most file transfer tools follow the same pattern: upload to a server, get a link, the recipient downloads from that server. Your file sits on someone else's infrastructu
Live: https://nulkratos-core.web.app GitHub: https://github.com/nulkratos/nulkratos-core Every "private" messenger I found had the same tradeoffs: Signal → needs your phone number. That's an identity anchor. Telegram → not E2E by default. Server-side messages. WhatsApp → Meta. Enough said. Matrix/Element → self-host complexity, still needs an account. Briar → great, but mobile-only and requires i