Show HN: SerpApi MCP Server https://ift.tt/y5kejY0

Show HN: SerpApi MCP Server https://ift.tt/GKpYrI9 December 6, 2025 at 12:00AM

Show HN: Playwright for Windows Computer Use https://ift.tt/XzNyS3h

Show HN: Playwright for Windows Computer Use https://ift.tt/O1N2abr December 5, 2025 at 04:15AM

Show HN: Cheap OpenTelemetry lakehouses with Parquet, DuckDB, and Iceberg https://ift.tt/jLFoyvH

Show HN: Cheap OpenTelemetry lakehouses with Parquet, DuckDB, and Iceberg Side project: exploring storing and querying OpenTelemetry data with duckdb, open table formats, and cheap object storage with some rust glue code. Yesterday, AWS made this exact sort of data architecture lot easier with new CloudWatch features: https://ift.tt/26ZY9Pg... https://ift.tt/gMzInmQ December 5, 2025 at 02:12AM

Show HN: Fresh – A new terminal editor built in Rust https://ift.tt/VNQEOUd

Show HN: Fresh – A new terminal editor built in Rust I built Fresh to challenge the status quo that terminal editing must require a steep learning curve or endless configuration. My goal was to create a fast, resource-efficient TUI editor with the usability and features of a modern GUI editor (like a command palette, mouse support, and LSP integration). Core Philosophy: - Ease-of-Use: Fundamentally non-modal. Prioritizes standard keybindings and a minimal learning curve. - Efficiency: Uses a lazy-loading piece tree to avoid loading huge files into RAM - reads only what's needed for user interactions. Coded in Rust. - Extensibility: Uses TypeScript (via Deno) for plugins, making it accessible to a large developer base. The Performance Challenge: I focused on resource consumption and speed with large file support as a core feature. I did a quick benchmark loading a 2GB log file with ANSI color codes. Here is the comparison against other popular editors: - Fresh: Load Time: *~600ms* | Memory: *~36 MB* - Neovim: Load Time: ~6.5 seconds | Memory: ~2 GB - Emacs: Load Time: ~10 seconds | Memory: ~2 GB - VS Code: Load Time: ~20 seconds | Memory: OOM Killed (~4.3 GB available) (Only Fresh rendered the ansi colors.) Development process: I embraced Claude Code and made an effort to get good mileage out of it. I gave it strong specific directions, especially in architecture / code structure / UX-sensitive areas. It required constant supervision and re-alignment, especially in the performance critical areas. Added very extensive tests (compared to my normal standards) to keep it aligned as the code grows. Especially, focused on end-to-end testing where I could easily enforce a specific behavior or user flow. Fresh is an open-source project (GPL-2) seeking early adopters. You're welcome to send feedback, feature requests, and bug reports. Website: https://sinelaw.github.io/fresh/ GitHub Repository: https://ift.tt/bPTOVDn https://sinelaw.github.io/fresh/ December 3, 2025 at 08:15PM

Show HN: Golang Client Library for Gradium.ai TTS/STT API https://ift.tt/1TUN8KV

Show HN: Golang Client Library for Gradium.ai TTS/STT API https://ift.tt/OqyYwPE December 3, 2025 at 01:22AM

Show HN: Meeting Detection – a small Rust engine that detects meetings on macOS https://ift.tt/fcPaqps

Show HN: Meeting Detection – a small Rust engine that detects meetings on macOS I built a small open-source meeting detection engine for macOS. The goal is to provide a simple and accurate way for apps to know when a user is in a Zoom/Meet/Teams/Webex meeting. A lot of meeting recorders, productivity tools, and focus apps try to detect meetings, but the results are often unreliable. Some apps pop up “You’re in a meeting” suggestions even when nothing is happening. I wanted something that works consistently and is easy for developers to integrate. The engine is written in Rust and exposed to Node/Electron via napi-rs. It runs a lightweight background loop and uses two tiers: 1. Native app detection (Zoom, Teams, Webex) • process detection • meeting-related network activity 2. Browser meeting detection (Google Meet, Teams Web, Zoom Web, Webex Web) • reads browser tabs via AppleScript • validates meeting URL patterns • supports Chrome, Safari, and Edge It exposes a very simple JS API: init(); onMeetingStart((_, d) => console.log("Meeting started:", d.appName)); onMeetingEnd(() => console.log("Meeting ended")); console.log(isMeetingActive()); Would love feedback, especially from anyone building recorders, focus apps, calendar tools, etc. Windows + Linux support coming next. https://ift.tt/pe6JEQH December 3, 2025 at 01:47AM

Show HN: SMART report viewer – Simple tool to analyze smartctl outputs https://ift.tt/8BE0wsa

Show HN: SMART report viewer – Simple tool to analyze smartctl outputs https://ift.tt/28hA1yo December 3, 2025 at 12:29AM