Show HN: React Web Camera – Fix <input type=file> single-photo limit
Show HN (score: 6)Description
React Web Camera is a lightweight, reusable React component that allows users to capture multiple photos in one camera session, in-browser. It works across standard web apps, responsive UIs, and Progressive Web Apps (PWAs)—unlocking a smoother experience than the default <input type="file" capture> element.
The problem
On mobile (and increasingly on desktops), using: <input type="file" accept="image/*" capture="environment"> only allows taking one picture before the camera closes. Want to add more? You have to reopen it each time.
How React Web Camera solves it
Opens the camera inline in-browser, Lets the user capture multiple photos in one go, Allows previewing captured photos, removing unwanted ones, and submitting everything in a batch, Fully client-side, respects user privacy, Supported across web, responsive UIs, and installable PWAs.
More from Show
Show HN: Opal Editor, free Obsidian alternative for markdown and site publishing
Show HN: Opal Editor, free Obsidian alternative for markdown and site publishing A fully featured markdown editor and publisher. Free, open-source and browser-first (no backend required). Built with modern technologies like React, TypeScript, Shadcn/UI, and Vite. (thoughtfully crafted, not vibe coded)
Show HN: Control Claude permissions using a cloud-based decision table UI
Show HN: Control Claude permissions using a cloud-based decision table UI We’ve been building visual rule engines (clear interfaces + API endpoints that help map input data to a large number of outcomes) for a while and had the fun idea lately to see what happens when we use our decision table UI with Claude’s PreToolUse hook.<p>The result is a surprisingly useful policy/gating layer– these tables let your team:<p>- Write multi-factor, exception-friendly policies (e.g. deny rm -rf / when --force; allow cleanup only in node_modules; ask on network calls like curl/wget; block kubectl delete or SQL DROP, each with a clear reason)<p>- Roll out policy changes instantly (mid-run, flip a risky operation from allow → ask; the next attempt across devs and agents is gated immediately– no git pull, agent restart, or coordination)<p>- Adopt lightweight governance that is somewhat agent agnostic and survives churn (MCP/skills/etc)- just add columns/rules as new tools and metadata show up<p>- Get a quick central utility to understand which tools are being used, which tools get blocked most often, and why
Show HN: Claude Code Scheduler
Show HN: Claude Code Scheduler I found myself frequently wanting to schedule tasks in Claude Code (both one-time and recurring) so I built a CC plugin to help with that.<p>To install: /plugin marketplace add jshchnz/claude-code-scheduler /plugin install scheduler@claude-code-scheduler<p>Then just tell Claude what you want (some examples):<p>Every Wednesday at 3am find dead code: unused functions, unreachable branches, commented-out code, and unused imports. List by file with line numbers.<p>Schedule a code review every weekday at 9am. Review commits from the last 24 hours, check for bugs, security issues, error handling gaps, and code that needs comments. Summarize with file:line references.
Show HN: Webctl – Browser automation for agents based on CLI instead of MCP
Show HN: Webctl – Browser automation for agents based on CLI instead of MCP
No other tools from this source yet.