智能助手网
标签聚合 Show

/tag/Show

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: 2 # Comments: 0

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

hnrss.org · 2026-04-18 13:34:28+08:00 · tech

Artificial intelligence is an amazing tool for brainstorming, programming, or generating images. But it’s also incredibly good at writing long, meaningless text filled with platitudes or producing code that continuously reinvents the wheel or misses edge cases. This has become known as slop. My inboxes have been increasingly filled with low-effort slop. I’m sure that this happens to many of you, too. The reddest of flags is being sent slop for work; at first glance, it may look credible, but it falls apart when you actually read the text. This prompted me to write three principles for working with AI and creating a website to send to your friend or colleague when they send you slop. Let's stop the slop and get back to doing great work together. Comments URL: https://news.ycombinator.com/item?id=47813403 Points: 2 # Comments: 1

hnrss.org · 2026-04-18 13:30:28+08:00 · tech

Built InGaming as a frontend MVP for the iGaming space, with two main parts: 1. a back-office admin for casino / gambling operations 2. a multi-brand storefront system for casino sites The starting point was simple: in all the years I’ve worked around iGaming, I haven’t seen a single admin panel I’d call genuinely good. Most of them are either bloated, awkward to use, or patched together from disconnected tools that don’t really fit how teams work day to day. So I decided to build the kind of admin I actually wish existed. On the admin side, the MVP includes flows for players, payments and transactions, casino and sportsbook operations, content and static pages, reporting, and website configuration. On the storefront side, I built a separate frontend repo to validate a multi-brand setup on shared foundations. Right now that includes two demo brands: BetStake and ShipBet. Important caveat: this is frontend work and product validation, not a finished end-to-end platform. I’m treating it as an expanded MVP that is already strong enough to be a serious starting point, rather than just another rough concept. What I’m really trying to figure out now is whether this is already valuable as a project someone could buy as a head start. My view is that it could save a lot of time for a team that would otherwise need to build the admin, storefront layer, and overall product structure from scratch. Happy to answer product or frontend architecture questions. Comments URL: https://news.ycombinator.com/item?id=47813386 Points: 1 # Comments: 0

hnrss.org · 2026-04-18 12:58:06+08:00 · tech

Hey y'all, Here's a walkthrough of how I use the 9front distribution of Plan 9 on Windows: https://www.youtube.com/watch?v=IzEa2L_Pgw0 Topics covered: - 9front distribution of Plan 9 running in qemu on Ubuntu inside WSL on Windows 11 - Drawterm running natively on Windows 11 - Running arbitrary commands on Plan 9 from Ubuntu - Mounting a directory from Plan 9 on Ubuntu - Using OpenAI codex LLM with Plan 9 - Editing files on Plan 9 with vscode Comments and suggestions are welcome. Comments URL: https://news.ycombinator.com/item?id=47813252 Points: 1 # Comments: 0

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

I found myself reaching for SF Symbols' 'Copy Image As…' quite often during agentic design sessions, so I made a command-line tool that the agent can use by itself. It exports Apple SF Symbols as SVG, PDF, or PNG. The vector paths come directly from macOS's symbol renderer. Internally it reaches a private ivar on NSSymbolImageRep to get the CUINamedVectorGlyph, draws into a CGPDFContext, then walks the PDF content stream back out as SVG `d` commands. The output matches what the system draws, rather than an approximation traced from rasters. A few things about it: - Every subcommand accepts `--json`, and `sfsym schema` returns a machine-readable description of the whole CLI. - Symbol enumeration reads the OS's Assets.car BOM tree, so the list of 8,300+ names stays current with macOS updates without a version table in the binary. - Each SVG ` ` carries a `data-layer` attribute, so you can retheme in CSS without touching geometry. It's been saving me a bunch of clicking. Please let me know if you have any other ideas for it. Comments URL: https://news.ycombinator.com/item?id=47812964 Points: 8 # Comments: 1

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

devnexus is an open-source cli that gives agents persistent shared memory across repos, sessions, and engineers. It maps out dependencies and relations at the function level, builds a code graph, and writes it into a shared Obsidian vault that every agent reads before writing code. Past decisions are also linked directly to the code they touched, so no one goes down the same dead end twice. Still building it out but I would love to hear any thoughts/feedback Comments URL: https://news.ycombinator.com/item?id=47812829 Points: 4 # Comments: 0

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

Hi all, I've been working on Small for a bit now, and I think it's ready to share. The idea being that larger writing platforms have memberships and have become an untenable way to truly share content. Small represents a return to paying writers and creators for their content. We chose to use x402 to embrace open protocols and payment rails. Still lots to do, so please leave any things you do or don't like and we'll start to address them! Comments URL: https://news.ycombinator.com/item?id=47812511 Points: 3 # Comments: 0

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

I've been studying interval arithmetic for the past few weeks and it's a really interesting field because while there is a ton of super interesting research published over the past decades, it has never really gotten the recognition that it deserves, IMO. One reason for this is that standard interval arithmetic has really poor handling of division by intervals containing zero. If you compute 1 / [-1, 2] in regular interval arithmetic, you get either [-∞, +∞], or you have to say that the operation is undefined. Both solutions are virtually useless. The real answer of course is [-∞, -1] U [0.5, +∞]: i.e. a union of two disjoint intervals. This is useful because you can confidently exclude a non empty set of the real numbers ([-1, 0.5]) from the set of possible values that you can get by dividing 1 by a number between -1 and 2. But this definition of interval division yields a value that is not an interval. This is a problem if you want to define a closed arithmetic system, where you can build and evaluate arbitrary expression over interval values. (This behavior extends to any non continuous function like tan() for example, which is implemented in my project - not without difficulties!) Well the obvious solution is to define your arithmetic over disjoint unions of intervals. This is the subject of a 2017 paper called "Interval Unions" by by Schichl, H., Domes, F., Montanher, T. and Kofler, K.. This open-source project I made implements interval union arithmetic in TypeScript in the form of a simple interactive calculator, so you can try it out for yourself! The underlying TypeScript library is dependency free and implements interval union arithmetic over IEEE 754 double precision floats (JS native number type) with outward rounding. This guarantees accuracy of interval results in the presence of rounding issue inherent to floating point. Comments URL: https://news.ycombinator.com/item?id=47812341 Points: 180 # Comments: 32

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

I built this to run OpenClaw safely. The problem: every sandbox I tried still handed the real API token to the agent as an env var. nilbox never gives the agent the real token. It gets a fake placeholder instead (ANTHROPIC_API_KEY=ANTHROPIC_API_KEY). nilbox intercepts outbound API calls and swaps in the real token at the network layer. So if the agent leaks the "token" — attacker gets a useless string. That's it. Also ships a managed Linux runtime (consistent across mac/win/linux) and a Store for one-click agent app installs. Full shell access too. Available for macOS, Windows, and Linux https://nilbox.run Curious how others are thinking about token security when running agents locally. Comments URL: https://news.ycombinator.com/item?id=47812193 Points: 3 # Comments: 0