EloqKV, a distributed database with Redis compatible API (GPLv2 and AGPLv3)
Hacker News (score: 29)Description
More from Hacker
Show HN: bbcli – A TUI and CLI to browse BBC News like a hacker
Show HN: bbcli – A TUI and CLI to browse BBC News like a hacker hey hn!<p>I (re)built this TUI tool for browsing BBC News in the terminal, it uses an RSS feed for getting headlines and previews and you can read articles too.<p>Try it out and let me know what you think! :)
Launch HN: Inkeep (YC W23) – Open Source Agent Builder
Launch HN: Inkeep (YC W23) – Open Source Agent Builder Hi HN! I'm Nick from Inkeep. We built an agent builder with true 2-way sync between code and a drag-and-drop visual editor, so devs and non-devs can collaborate on the same agents. Here’s a demo video: <a href="https://go.inkeep.com/video">https://go.inkeep.com/video</a>.<p>As a developer, the flow is: 1) Build AI Chat Assistants or AI Workflows with the TypeScript SDK 2) Run `inkeep push` from your CLI to publish 3)Edit agents in the visual builder (or hand off to non-technical teams) 4) Run `inkeep pull to edit in code again.<p>We built this because we wanted the accessibility of no-code workflow builders (n8n, Zapier), but the flexibility and devex of code-based agent frameworks (LangGraph, Mastra). We also wanted first-class support for chat assistants with interactive UIs, not just workflows. OpenAI got close, but you can only do a one-time export from visual builder to code and there’s vendor lock-in.<p>How I've used it: I bootstrapped a few agents for our marketing and sales teams, then was able to hand off so they can maintain and create their own agents. This has enabled us to adopt agents across technical and non-technical roles in our company on a single platform.<p>To try it, here’s the quickstart: <a href="https://go.inkeep.com/quickstart">https://go.inkeep.com/quickstart</a>.<p>We leaned on open protocols to make it easy to use agents anywhere: An MCP endpoint, so agents can be used from Cursor/Claude/ChatGPT A Chat UI library with interactive elements you can customize in React An API endpoint compatible with the Vercel AI SDK `useChat` hook Support for Agent2Agent (A2A) so they work with other agent ecosystems<p>We made some practical templates like a customer_support, deep_research, and docs_assistant. Deployment is easy with Vercel/Docker with a fair-code license and there's a traces UI and OTEL logs for observability.<p>Under the hood, we went all-in on a multi-agent architecture. Agents are made up of LLMs, MCPs, and agent-to-agent relationships. We’ve found this approach to be easier to maintain and more flexible than traditional “if/else” approaches for complex workflows.<p>The interoperability works because the SDK and visual builder share a common underlying representation, and the Inkeep CLI bridges it with a mix of LLMs and TypeScript syntactic sugar. Details in our docs: <a href="https://docs.inkeep.com">https://docs.inkeep.com</a>.<p>We’re open to ideas and contributions! And would love to hear about your experience building agents - what works, hasn’t worked, what’s promising?
Show HN: CrabCamera – Cross-platform camera plugin for Tauri desktop apps
Show HN: CrabCamera – Cross-platform camera plugin for Tauri desktop apps After building several Tauri desktop apps, I kept hitting the same wall: there's no reliable way to access cameras across Windows, macOS, and Linux. Every project meant reinventing camera integration, dealing with platform-specific APIs, and debugging permission issues.<p><pre><code> So I built CrabCamera – a Tauri plugin that handles all the camera complexity for you. What it does: - One API, three platforms: Same Rust code works on Windows (DirectShow), macOS (AVFoundation), and Linux (V4L2) - Permission handling: Automatically requests camera permissions on each platform - Format conversion: Takes care of the messy bits between platform formats and what your app needs - Error handling: Proper Rust error types instead of mysterious crashes - Hot-plugging: Detects when cameras are connected/disconnected The problem it solves: Before CrabCamera, adding camera support to a Tauri app meant: 1. Writing separate native code for each platform 2. Managing three different permission systems 3. Handling format conversions manually 4. Debugging platform-specific edge cases 5. Maintaining it all as OS APIs change Now it's just: use crabcamera::Camera; let camera = Camera::new()?; let frame = camera.capture_frame().await?; Why I built it: I was working on a plant monitoring app (botanica) that needed reliable camera access for time-lapse photography. Existing solutions were either abandoned, platform-specific, or required complex native bindings. The Tauri ecosystem is growing fast, but camera support was this obvious gap. Every desktop app eventually needs camera access – video calls, document scanning, AR features, security monitoring. Technical highlights: - Uses nokhwa for the heavy lifting but wraps it in Tauri-friendly APIs - Proper async/await support throughout - Memory-efficient streaming for video capture - Built-in image processing pipeline - Extensible plugin architecture What's next: - WebRTC integration for video calls - Built-in barcode/QR code scanning - Face detection hooks - Performance optimizations for 4K streams The crate is MIT licensed and available on crates.io. I'd love feedback from other Tauri developers who've wrestled with camera integration. Links: - Crates.io: https://crates.io/crates/crabcamera - GitHub: https://github.com/Michael-A-Kuykendall/crabcamera - Documentation: https://docs.rs/crabcamera</code></pre>
Google to require developer verification to install and sideload Android apps
Google to require developer verification to install and sideload Android apps
No other tools from this source yet.