智能助手网
标签聚合 Show

/tag/Show

hnrss.org · 2026-04-18 21:10:24+08:00 · tech

Readox is a Chrome extension that reads web pages, PDFs, selections, text files (ie markdown), and text input notes aloud with TTS. You can just play the current page, or save things to a library and queue them up. It highlights as it reads, keeps your place across items, and can OCR scanned PDFs. TTS (for text and PDF) and OCR run on-device, and it works offline after setup. I’m interested on feedback on the library collections as a "playlist-like" functionality, or if most people just want a play button for the current page. Also interested in anything that feels missing or awkward. Thanks! Comments URL: https://news.ycombinator.com/item?id=47815638 Points: 2 # Comments: 0

hnrss.org · 2026-04-18 20:30:16+08:00 · tech

I built LogsGo as a learning project to explore log ingestion, querying, and storage tradeoffs. It’s a small Go-based system where logs come in over gRPC, land in memory first, then flush into local storage and optionally S3-compatible object storage. I also added a simple query language plus a small UI to inspect log occurrences over time. This wasn’t built because I think the world needed “another logging system” or because I’m an expert here. I mostly wanted to learn by building something end to end: ingestion paths, storage layering, querying, retention, auth/TLS, and some UI work. Repo: https://github.com/Saumya40-codes/LogsGO I’d genuinely appreciate feedback, including “this design is wrong for X reason” type feedback. If parts of it feel overengineered / naive / badly thought through, that’s useful for me too. Comments URL: https://news.ycombinator.com/item?id=47815402 Points: 1 # Comments: 0

hnrss.org · 2026-04-18 20:17:13+08:00 · tech

150 applications. One offer. Each application took 5+ manual steps. Separate tools, separate tabs, separate sites — none of them talking to each other. Generic output. Over an hour per application. Paste a job description — or pull it from any job site with the Chrome extension — and five AI agents run an orchestrated pipeline in under 30 seconds: analyzing the role, scoring your fit, researching the company, writing a targeted cover letter, and tailoring your resume to the role. Sequential where it needs to be, parallel where it can be, each agent's output feeding the next. Also includes a dashboard to track every application. And tools for everything around it: interview prep with mock sessions, salary negotiation, job comparison, follow-ups, thank you notes, and references. Runs on your machine. No subscriptions, no data stored on our servers — just your own Gemini API key connecting directly to Google. Comments URL: https://news.ycombinator.com/item?id=47815326 Points: 1 # Comments: 0

hnrss.org · 2026-04-18 18:11:09+08:00 · tech

I got tired of maintaining two files that describe the same thing: an OpenAPI spec for documentation and a Postman collection for testing. They always drift. Someone updates the spec, forgets the collection. A new engineer joins and runs outdated tests against an endpoint that was changed two months ago. VolcAPI lets you define test scenarios directly inside your OpenAPI spec using a custom extension (v-functional-test), then run them from the CLI. Single source of truth. It's a Go binary no runtime, no node_modules. The goal is for it to drop into GitHub Actions with zero friction once JUnit XML output lands (in progress). Repo: https://github.com/aliamerj/volcapi This is early alpha. GET/POST/PUT/DELETE work, response validation works, environment configs work. CI output formats are the next thing I'm building. Honest question for the HN crowd: is the "spec as test suite" concept something you'd actually use, or do you prefer keeping tests separate from the spec? I've gone back and forth on this and would genuinely like to hear from people who've felt this pain. Comments URL: https://news.ycombinator.com/item?id=47814655 Points: 1 # Comments: 1

hnrss.org · 2026-04-18 16:53:41+08:00 · tech

Hello, I built chlibc, a linux tool to change the system interp and glibc to your custom one. Normally, running an ELF against a different glibc, you'd use LD_LIBRARY_PATH and patchelf, or use chroot/docker. chlibc allows you to change the dynamic linker of a process on the fly without patching and root access. Key Features: - zero disk modification: no need for patchelf --set-interpreter. - no root required: works entirely in user-space via ptrace - multi-arch: native support for x86_64, AArch64, and RISC-V. - lightweight: unlike PRoot, which intercepts every syscall to translate paths, chlibc only intervenes during the initial execve() phase. Once the loader is swapped, it almost has no runtime overhead. I’d love to hear your thoughts about this tool, thanks! Comments URL: https://news.ycombinator.com/item?id=47814330 Points: 2 # Comments: 0

hnrss.org · 2026-04-18 16:25:29+08:00 · tech

Read an article about analyzing Garmin data with AI. Sounded great — except I didn't want to send my health data to any cloud service. So I asked Claude to write me 2-3 scripts and a dashboard. This escalated a bit. 30 days and 20$ later I have this: A local-first Garmin archive with interactive HTML dashboards, Excel exports, weather and pollen context, AES-256 encrypted token storage, and a self-healing data pipeline with 515 automated tests. Windows desktop app, no terminal needed. Nothing leaves your machine. I never wrote a line of Python. I understood the problems and made the architectural decisions. Claude wrote everything else. GitHub: github.com/Wewoc/Garmin_Local_Archive Comments URL: https://news.ycombinator.com/item?id=47814208 Points: 3 # Comments: 1

hnrss.org · 2026-04-18 15:43:17+08:00 · tech

Hi HN, I've been doing freelance work and realized the most stressful part of the entire lifecycle isn't doing the work, it's the final handoff. You send over the final ZIP file or Figma link, attach your invoice, and then just wait and hope the client actually pays instead of running off with your files. To fix this, I built TimeDrop to act as a mechanical intermediary. It basically removes the "trust" variable from the final delivery. Here is the workflow: You secure your final project link behind a "delivery gate" in the app. The app emails the invoice to the client on your behalf. The client receives the invoice and sees that the files are ready, but the link is strictly locked. The second you mark the invoice as paid on your dashboard, the system automatically unlocks and delivers the final files to the client. It acts as the bad cop so you never have to send another awkward "just following up on the payment" email. The site is https://timedrop.work I would love to hear your thoughts on the mechanics of this workflow, or if you see any glaring edge cases I'm missing.. Comments URL: https://news.ycombinator.com/item?id=47814004 Points: 1 # Comments: 1

hnrss.org · 2026-04-18 14:49:26+08:00 · tech

Hi HN, I'm the builder. I realized that using cloud AI APIs for sensitive workflows—like transcribing board meetings, OCRing employment contracts, or cleaning up ID photos—is a massive privacy liability. So I built a client-side workspace using transformers.js, Whisper, and WebGPU. Everything runs locally. You can turn on Airplane Mode after the initial model load, and it still transcribes and extracts text perfectly. To keep myself honest, I wrote a technical audit of how the data flows (or rather, doesn't flow). My only backend is a tiny 2-core node in Singapore running self-hosted Plausible analytics: [ https://gist.github.com/ygx2378/3275b333504c6a9def50ef531b54... ] I'm still learning the ropes of browser-based memory management, so I'd love your feedback on how the models load on your specific GPUs! Comments URL: https://news.ycombinator.com/item?id=47813703 Points: 1 # Comments: 0