The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Textile – A desktop app for weaving together bits of text
Hi all,<p>I'm excited to show off Textile, a desktop app I recently built.<p>Textile can combine bits of text using various inputs, such as commands on your computer, the contents of your clipboard, and hard-coded strings that you provide. It lets you carefully build up and modify a dynamic string, step by step, until it's exactly how you need it. The saved steps can then be executed on demand, with the click of a button or using a keyboard shortcut.<p>I built Textile because I was often constructing complicated, dynamic URLs from various sources that all existed on my computer. I got tired of manually switching between different apps, copying and pasting various chunks of text, and assembling them all together somewhere. I've also found Textile to be quite useful as a kind of repository for obscure bits of static text, such as ½ and other fraction characters, when I can't be bothered to remember their built-in keyboard combinations.<p>I also built Textile because I wanted to learn Electron, although I expect there will be some gnashing of teeth about this here. :) I think desktop development is quite interesting, in part because it doesn't require me, the developer, to pay for an API server and database in the cloud. The app itself is both the UI and the "server," and the local drive is effectively the "database." I knows this trades away syncing with the cloud but, on the other hand, there's something nice about knowing that your files are on your drive and not on somebody else's server.<p>I realize that something like Textile may already exist, and may have much more functionality but, again, I wanted to learn. I must say that multi-sequence keyboard shortcuts are hard, and there are cases that don't work right in Textile. I feel vulnerable admitting that my approach has much room for improvement!<p>For what it's worth, I did not use an LLM to write any code for Textile (although I did ask many questions of an LLM, as an alternative to Googling).<p>Textile is open source, free to use, and does not require sign up, email, phone, or other such barriers. Try it and let me know what you think!<p>(Note: I don't have access to hardware running Windows or Linux, so Textile is only available for macOS at the moment.)
Show HN: A CSS 3D Engine (no WebGL)
Show HN: Atomic Editor – Obsidian-style live preview for CodeMirror 6
Show HN: Atomic Editor – Obsidian-style live preview for CodeMirror 6
Show HN: Streambed – Stream Postgres to Iceberg on S3, Supports Postgres Wire
Show HN: Streambed – Stream Postgres to Iceberg on S3, Supports Postgres Wire
Show HN: Breathe CLI – Paced resonance breathing in the macOS terminal
I built a terminal app that paces slow breathing at 6 breaths per minute for vagal tone training. It's a single Python file, stdlib only, no dependencies — just run breathe and follow the bar.<p>I'm a cardiology patient (HFrEF). Slow breathing at resonance frequency is one of the few non-pharmacological interventions shown to improve cardiac vagal tone and baroreflex sensitivity (Bernardi et al., Circulation 2002; Lancet 1998). I wanted a frictionless daily habit tool — no app store, no account, no subscription, just open terminal and go.<p>Design constraints, all grounded in the clinical literature:<p>- No breath retention — Valsalva risk in cardiac patients<p>- No rapid breathing — minimum 8-second cycles<p>- Exhale ≤ 2x inhale — no evidence for extreme ratios<p>- Immediate exit, always — q or Ctrl+C restores the terminal even on crash<p>The README includes a resonance frequency measurement protocol for anyone with a chest-strap HRV monitor who wants to find their individual optimum instead of using the 6 bpm default.<p>macOS only (uses afplay for audio cues). MIT licensed.<p>pip install breathe-cli<p>or<p>brew tap marekkowalczyk/breathe && brew install breathe.
Show HN: Breathe CLI – Paced resonance breathing in the macOS terminal
I built a terminal app that paces slow breathing at 6 breaths per minute for vagal tone training. It's a single Python file, stdlib only, no dependencies — just run breathe and follow the bar.<p>I'm a cardiology patient (HFrEF). Slow breathing at resonance frequency is one of the few non-pharmacological interventions shown to improve cardiac vagal tone and baroreflex sensitivity (Bernardi et al., Circulation 2002; Lancet 1998). I wanted a frictionless daily habit tool — no app store, no account, no subscription, just open terminal and go.<p>Design constraints, all grounded in the clinical literature:<p>- No breath retention — Valsalva risk in cardiac patients<p>- No rapid breathing — minimum 8-second cycles<p>- Exhale ≤ 2x inhale — no evidence for extreme ratios<p>- Immediate exit, always — q or Ctrl+C restores the terminal even on crash<p>The README includes a resonance frequency measurement protocol for anyone with a chest-strap HRV monitor who wants to find their individual optimum instead of using the 6 bpm default.<p>macOS only (uses afplay for audio cues). MIT licensed.<p>pip install breathe-cli<p>or<p>brew tap marekkowalczyk/breathe && brew install breathe.
Show HN: Open Envelope – an open schema for defining AI agent teams
Built an open JSON Schema for defining AI agent teams.<p>Multi-agent systems are becoming a real deployment pattern — not single assistants, but teams with roles, handoffs, and human checkpoints. But there's no shared way to define one that travels across frameworks. Every implementation is scattered, locked to whichever tool you picked first. Built the schema to fix that.<p>The schema lives at schema.openenvelope.org and is registered in SchemaStore, so if you drop a .envelope.json file in VS Code you get autocomplete and validation without installing anything. It's also on npm as @openenvelope/schema if you want to validate programmatically.<p>The spec covers: agent definitions (role, prompt, model, access policy), supervisor/sub-agent hierarchy, human-in-the-loop gates, pipelines, schedules, and secrets/variables that get injected at deploy time. Access policies let you declare exactly which hosts each agent can call — the runtime enforces this at the network level, not in the prompt.<p>The goal is a portable definition format — define a team once, any compatible runtime can execute it. Similar to how Dockerfiles describe a container without being tied to a specific host. There's a managed runtime at openenvelope.org but the schema is Apache 2.0 and anyone can implement it.<p>Happy to answer questions on any part of the spec — especially interested in feedback from people who've built multi-agent systems and have opinions on what's missing.
Show HN: Open Envelope – an open schema for defining AI agent teams
Built an open JSON Schema for defining AI agent teams.<p>Multi-agent systems are becoming a real deployment pattern — not single assistants, but teams with roles, handoffs, and human checkpoints. But there's no shared way to define one that travels across frameworks. Every implementation is scattered, locked to whichever tool you picked first. Built the schema to fix that.<p>The schema lives at schema.openenvelope.org and is registered in SchemaStore, so if you drop a .envelope.json file in VS Code you get autocomplete and validation without installing anything. It's also on npm as @openenvelope/schema if you want to validate programmatically.<p>The spec covers: agent definitions (role, prompt, model, access policy), supervisor/sub-agent hierarchy, human-in-the-loop gates, pipelines, schedules, and secrets/variables that get injected at deploy time. Access policies let you declare exactly which hosts each agent can call — the runtime enforces this at the network level, not in the prompt.<p>The goal is a portable definition format — define a team once, any compatible runtime can execute it. Similar to how Dockerfiles describe a container without being tied to a specific host. There's a managed runtime at openenvelope.org but the schema is Apache 2.0 and anyone can implement it.<p>Happy to answer questions on any part of the spec — especially interested in feedback from people who've built multi-agent systems and have opinions on what's missing.
Show HN: Open Envelope – an open schema for defining AI agent teams
Built an open JSON Schema for defining AI agent teams.<p>Multi-agent systems are becoming a real deployment pattern — not single assistants, but teams with roles, handoffs, and human checkpoints. But there's no shared way to define one that travels across frameworks. Every implementation is scattered, locked to whichever tool you picked first. Built the schema to fix that.<p>The schema lives at schema.openenvelope.org and is registered in SchemaStore, so if you drop a .envelope.json file in VS Code you get autocomplete and validation without installing anything. It's also on npm as @openenvelope/schema if you want to validate programmatically.<p>The spec covers: agent definitions (role, prompt, model, access policy), supervisor/sub-agent hierarchy, human-in-the-loop gates, pipelines, schedules, and secrets/variables that get injected at deploy time. Access policies let you declare exactly which hosts each agent can call — the runtime enforces this at the network level, not in the prompt.<p>The goal is a portable definition format — define a team once, any compatible runtime can execute it. Similar to how Dockerfiles describe a container without being tied to a specific host. There's a managed runtime at openenvelope.org but the schema is Apache 2.0 and anyone can implement it.<p>Happy to answer questions on any part of the spec — especially interested in feedback from people who've built multi-agent systems and have opinions on what's missing.
Show HN: Context-aware Japanese furigana using Sudachi and ModernBERT
Show HN: 500 years of Joseon court omens as an observability dashboard
Show HN: 500 years of Joseon court omens as an observability dashboard
Show HN: 500 years of Joseon court omens as an observability dashboard
Show HN: Open-source private home security camera system (end-to-end encryption)
Hey everyone,<p>I previously introduced an open source private home security camera in 2024, which uses OpenMLS for end-to-end encryption: <a href="https://news.ycombinator.com/item?id=42284412">https://news.ycombinator.com/item?id=42284412</a>.<p>It was called Privastead then and it's now renamed to Secluso.<p>John Kaczman found my project from here and has been working on it with me over the last year and half. We've made a lot of improvements to the software, which we would like to share with you:<p>- You can now set this up on your Raspberry Pi in less than 5 minutes with no technical expertise using our easy-to-use GUI deploy tool. We've put together a comprehensive build-your-own guide that walks you through the required steps (you can find a link at the top of the repository README).<p>- We use a customized, minimal OS based on the Yocto project for the camera.<p>- Every part of our stack except for the iOS app has reproducible builds. This includes our Android app, camera/server binaries, deploy tool, and the aforementioned OS.<p>- We've re-designed our mobile app, which is now on the iOS App Store and Google Play store.<p>- We now support UnifiedPush for more privacy-preserving push notifications.<p>Looking forward to seeing what you all think!
Show HN: Open-source private home security camera system (end-to-end encryption)
Hey everyone,<p>I previously introduced an open source private home security camera in 2024, which uses OpenMLS for end-to-end encryption: <a href="https://news.ycombinator.com/item?id=42284412">https://news.ycombinator.com/item?id=42284412</a>.<p>It was called Privastead then and it's now renamed to Secluso.<p>John Kaczman found my project from here and has been working on it with me over the last year and half. We've made a lot of improvements to the software, which we would like to share with you:<p>- You can now set this up on your Raspberry Pi in less than 5 minutes with no technical expertise using our easy-to-use GUI deploy tool. We've put together a comprehensive build-your-own guide that walks you through the required steps (you can find a link at the top of the repository README).<p>- We use a customized, minimal OS based on the Yocto project for the camera.<p>- Every part of our stack except for the iOS app has reproducible builds. This includes our Android app, camera/server binaries, deploy tool, and the aforementioned OS.<p>- We've re-designed our mobile app, which is now on the iOS App Store and Google Play store.<p>- We now support UnifiedPush for more privacy-preserving push notifications.<p>Looking forward to seeing what you all think!
Show HN: Open-source private home security camera system (end-to-end encryption)
Hey everyone,<p>I previously introduced an open source private home security camera in 2024, which uses OpenMLS for end-to-end encryption: <a href="https://news.ycombinator.com/item?id=42284412">https://news.ycombinator.com/item?id=42284412</a>.<p>It was called Privastead then and it's now renamed to Secluso.<p>John Kaczman found my project from here and has been working on it with me over the last year and half. We've made a lot of improvements to the software, which we would like to share with you:<p>- You can now set this up on your Raspberry Pi in less than 5 minutes with no technical expertise using our easy-to-use GUI deploy tool. We've put together a comprehensive build-your-own guide that walks you through the required steps (you can find a link at the top of the repository README).<p>- We use a customized, minimal OS based on the Yocto project for the camera.<p>- Every part of our stack except for the iOS app has reproducible builds. This includes our Android app, camera/server binaries, deploy tool, and the aforementioned OS.<p>- We've re-designed our mobile app, which is now on the iOS App Store and Google Play store.<p>- We now support UnifiedPush for more privacy-preserving push notifications.<p>Looking forward to seeing what you all think!
Show HN: Helios – what plug-in solar could generate for any address in Britain
Plug-in solar panels (no electrician needed) have just become legal in the UK and will go on sale soon. Helios estimates how much electricity a typical installation could generate at a given address and what that's worth against your tariff.<p>It uses UK government LIDAR data to reflect the actual skyline, so it knows whether there's a building or a hill blocking the sun.<p>Caveats:
- Outside LIDAR coverage (most of Scotland and Wales) it falls back to a synthetic horizon (less accurate).
- Trees and recent developments (post-2022 or so) may not be in the data, and some address placements could be off (geocoding via OSM).<p>Feedback on the shading model especially welcome.
Show HN: Helios – what plug-in solar could generate for any address in Britain
Plug-in solar panels (no electrician needed) have just become legal in the UK and will go on sale soon. Helios estimates how much electricity a typical installation could generate at a given address and what that's worth against your tariff.<p>It uses UK government LIDAR data to reflect the actual skyline, so it knows whether there's a building or a hill blocking the sun.<p>Caveats:
- Outside LIDAR coverage (most of Scotland and Wales) it falls back to a synthetic horizon (less accurate).
- Trees and recent developments (post-2022 or so) may not be in the data, and some address placements could be off (geocoding via OSM).<p>Feedback on the shading model especially welcome.