🛠️ Hacker News Tools

Regulator contacts Meta over workers watching intimate AI glasses videos

Google Workspace CLI

Show HN: Potatoverse, home for your vibecoded apps DEMO: <a href="https:&#x2F;&#x2F;tubersalltheway.top&#x2F;zz&#x2F;pages&#x2F;auth&#x2F;login" rel="nofollow">https:&#x2F;&#x2F;tubersalltheway.top&#x2F;zz&#x2F;pages&#x2F;auth&#x2F;login</a>

NRC Issues First Commercial Reactor Construction Approval in 10 Years [pdf]

BMW Group to deploy humanoid robots in production in Germany for the first time

Show HN: Qlog – grep for logs, but 100x faster I built qlog because I got tired of waiting for grep to search through gigabytes of logs.<p>qlog uses an inverted index (like search engines) to search millions of log lines in milliseconds. It&#x27;s 10-100x faster than grep and way simpler than setting up Elasticsearch.<p>Features: - Lightning fast indexing (1M+ lines&#x2F;sec using mmap) - Sub-millisecond searches on indexed data - Beautiful terminal output with context lines - Auto-detects JSON, syslog, nginx, apache formats - Zero configuration - Works offline - Pure Python<p>Example: qlog index &#x27;.&#x2F;logs&#x2F;*&#x2F;*.log&#x27; qlog search &quot;error&quot; --context 3<p>I&#x27;ve tested it on 10GB of logs and it&#x27;s consistently 3750x faster than grep. The index is stored locally so repeated searches are instant.<p>Demo: Run `bash examples&#x2F;demo.sh` to see it in action.<p>GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;Cosm00&#x2F;qlog" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Cosm00&#x2F;qlog</a><p>Perfect for developers&#x2F;DevOps folks who search logs daily.<p>Happy to answer questions!

Building a new Flash

Making Firefox's right-click not suck with about:config

The Iran War's Most Precious Commodity Isn't Oil, It's Desalinated Water

Factory Logic

Show HN: I put HN discussions next to the article where it belongs It it always bugged me when I read or share an article, the discussion lives separately from the article. I imagined being able to add Google-Docs or Notion style comments on any website. We save a snapshot of the website and allow adding discussions that live side-by-side and directly reference parts of the article.<p>HN articles are automatically indexed in <a href="https:&#x2F;&#x2F;cooo.link&#x2F;hackernews" rel="nofollow">https:&#x2F;&#x2F;cooo.link&#x2F;hackernews</a><p>and you can add any website, PDFs on <a href="https:&#x2F;&#x2F;cooo.link&#x2F;" rel="nofollow">https:&#x2F;&#x2F;cooo.link&#x2F;</a><p>Built with SvelteKit, SingleFile(for archiving page), Railway. Solo dev. Would love feedback if you found it interesting! Thanks

Show HN: AI Code Review CLI This week we released the Kodus CLI.<p>It took a bit longer than we expected to ship. The reason was simple: there are already many ways to run reviews locally today. IDEs, extensions, terminal commands, agents inside the editor. So building “just another AI CLI” didn’t seem like a good idea.<p>The question that guided the project was different: how can we bring the quality of PR reviews to the moment when the code is still being written?<p>Today the CLI does two main things.<p>The first is running local reviews using the same context we use in PRs. The goal was to avoid that shallow review that only looks at the diff currently open in the editor. We try to reconstruct more repository context, similar to what happens during a PR review.<p>The second is helping resolve comments that Kody has already left on a PR, but directly from the local environment. Instead of opening the PR, reading the comment, going back to the editor, making the change, and repeating the process, you can work through those fixes directly in your coding workflow.<p>The whole idea revolves around reducing the feedback loop time.<p>Some design decisions came from things we heard from teams using other CLIs.<p>Auth in large teams often turns into friction. Many tools assume each developer will create an account before using the CLI. That becomes painful when someone just wants to try it, or when an entire team decides to experiment.<p>We introduced team keys. An admin generates the key and shares it with the team. Anyone who installs the CLI can start using it right away.<p>Rate limits can ruin the local experience. Some tools work well at first but become too restricted for continuous use.<p>The CLI runs BYOK by default, so you can use your own API key if you want.<p>Code agents are already part of the workflow. Instead of treating this as something separate, we built two layers.<p>The CLI works as a direct interface to our API. On top of that, there are Skills that teach agents how to use the same review flow.<p>There’s still a lot to improve. Repo context, how suggestions are presented, integration with different developer workflows. We’re using it heavily internally and adjusting things as problems show up.<p>If anyone wants to try it or contribute:<p>- repo: <a href="https:&#x2F;&#x2F;github.com&#x2F;kodustech&#x2F;cli" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;kodustech&#x2F;cli</a> - feedback is very welcome - issues and PRs are too<p>If you usually run local reviews, I’d be curious to hear what actually works and what only sounds good in theory.

Show HN: Open-sourced a web client that lets any device use Apple's on-device AI I use Claude every day but there are things I will not type into a cloud service. I have a Mac with Apple Silicon running Apple Foundation Models locally and privately. But I was not always at my Mac. So we built Perspective Intelligence Web. One Mac runs Perspective Server. Any device on your network opens a browser and chats with Apple Intelligence through it. Phone, Windows laptop, Chromebook, Linux machine. Streaming responses, token by token. Nothing leaves your network. MIT License. Next.js, TypeScript, Tailwind. Full writeup: <a href="https:&#x2F;&#x2F;taylorarndt.substack.com&#x2F;p&#x2F;i-opened-claude-and-then-i-stopped" rel="nofollow">https:&#x2F;&#x2F;taylorarndt.substack.com&#x2F;p&#x2F;i-opened-claude-and-then-...</a>

A Visual Guide to DNA Sequencing

Qwen3.5 Fine-Tuning Guide – Unsloth Documentation

Nobody Gets Promoted for Simplicity

Show HN: Glyph, a local-first Markdown notes app for macOS built with Rust Glyph is an open-source, local-first Markdown notes app for macOS built with Rust (Tauri)<p>It stores notes as plain files, supports fast search, wikilinks&#x2F;backlinks, and includes optional AI chat, including implementation of Codex so you can use your chatgpt sub, all without requiring a cloud-first workflow.<p><a href="https:&#x2F;&#x2F;glyphformac.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;glyphformac.com&#x2F;</a>

Show HN: A shell-native cd-compatible directory jumper using power-law frecency I have used this tool privately since 2011 to manage directory jumping. While it is conceptually similar to tools like z or zoxide, the underlying ranking model is different. It uses a power-law convolution with the time series of cd actions to calculate a history-aware &quot;frecency&quot; metric instead of the standard heuristic counters and multipliers.<p>This approach moves away from point-estimates for recency. Most tools look only at the timestamp of the last visit, which can allow a &quot;one-off&quot; burst of activity to clobber long-term habits. By convolving a configurable history window (typically the last 1,000+ events), the score balances consistent habits against recent flukes.<p>On performance: Despite the O(N) complexity of calculating decay for 1,000+ events, query time is ~20-30ms (Real Time) in ksh&#x2F;bash, which is well below the threshold of perceived lag.<p>I intentionally chose a Logical Path (pwd -L) model. Preserving symlink names ensures that the &quot;Name&quot; remains the primary searchable key. Resolving to physical paths often strips away the very keyword the user intends to use for searching.

To understand our fascination with crystals, researchers gave some to chimps

RFC 9849. TLS Encrypted Client Hello