Show HN: Let's Seal – Let's Encrypt for document signing, free and self-hosted https://ift.tt/GaPiSQD

Show HN: Let's Seal – Let's Encrypt for document signing, free and self-hosted TLDR, Let's Seal gives the finger to Adobe and every doc signing tool (docusign, google, etc) who pay to play with the Adobe Approved Trust List and then charge you for something that should be free. Currently even the person checking if a document/contract is sealed or code is authentic has to also be inside the same Adobe walled garden too. Verification, the part that should be free is the part everyone charges for. Thats the shape Let's Encrypt fixed for TLS, and I wanted the same thing for documents and files. The core idea therefore needed to go a bit beyond e signatures and i created an open standard (SEAL), plus free tools that implement it. When you seal a file, three independent things happen. 1. it gets a signature from a certificate authority, chaining to a public root. 2. its record is appended to an RFC 6962 transparency log. and 3. its SHA256 is timestamped on a public blockchain (Bitcoin) via OpenTimestamps. Those three give you integrity, transparency and a timestamped proof. And importantly, none of those depend on Let's Seal and none are gated. You can verify with the tools you already have, no Let's Seal account and no Let's Seal software. A sealed PDF carries a standard PAdES signature, so any PDF reader validates it. A sealed build artefact carries a cosign compatible signature and a SLSA provenance attestation. The Bitcoin timestamp verifies with stock ots. 3 ways to use it. 1. The free web app. We kindly have backing from Backblaze to cover storage costs for the foreseeable. So you can upload or issue any number of documents, get a public proof page at /d/ and verify it at https://ift.tt/45eYC9k for free. Multiple accounts, multiple seats, enterprise functions. Free. 2. Self host the whole thing. Apache-2.0, one Next.js app plus a signing service that holds the CA key on localhost. Storage is any S3-compatible bucket or local disk. If you'd rather run your own root of trust, you can. 3. Programmatically. via the CLI and a hosted API. This is the Let's Encrypt/certbot angle. Seal or anchor things from CI, or have a backend seal every invoice or report as its generated. The CLI is sealbot. It runs anywhere Node runs (npx sealbot) and there are native binaries for macOS, Linux and Windows with no runtime needed. Theres a GitHub Action wrapping the same tool, so a release workflow can seal its own artifacts. Its what proves our own releases. KYC is semi-handled (to a degree) it's hard to do for free (at least for now), but issuers (your companies or websites) domains can be authenticated with a DNS record added, which proves the issuer has control over a domain. Sign-in can be authenticated to an email via Google Sign in and a few others will be added to the web app in time (Same as Docusign currently). Ideas welcome on future KYC should there be a demand. Feedback welcome on the standard (SPEC.md in the repo). Repo: https://ift.tt/dMuwXT5 Site: letsseal.org Thx https://ift.tt/dMuwXT5 July 27, 2026 at 10:52PM

Show HN: FeyNoBg – Automatic background removal model and training library https://ift.tt/42yG8wW

Show HN: FeyNoBg – Automatic background removal model and training library Hey HN, I’m Shreyash from Feyn. We help companies build custom models from their data. Today, we’re releasing FeyNoBg, an automatic background removal model. Alongside it, we're open-sourcing NoBg, the Python library we built to train and run it. Try the model here: https://ift.tt/5sVGQPN . Check out the library here: https://ift.tt/pdbw2WT Some sample outputs: (1) Soccer Freekick: https://drive.google.com/file/d/1MZkAGLwbhNVOZ0Oi7XvpCfSEu9Q... (2) Hair in wind: https://drive.google.com/file/d/1Odc2m0XMVH9uZtvI_KjaRbXzhLL... (3) Bicycle with visible spokes: https://drive.google.com/file/d/1h99ahjfrtS1MFQJJgiKE2fuM3HZ... (4) Live Demo video: https://youtu.be/b1heHPvY8BM Background removal separates an image's subject from its surrounding. We've all tried it at some point. Often it is to reuse the subject in a different artifact. Nowadays, it is common to make chat stickers out of it. It is one of the most common but under-appreciated uses of AI. It is also surprisingly complex. Models can be easily confused by camouflage, motion blur, or fine structures like hair. The task requires two skills. First, a model has to identify the foreground. Second, it has to trace the foreground’s boundary and estimate an opacity value for each pixel. Generally, these skills are taught with different datasets. That creates a failure point. A poor training mix can improve one skill at the expense of the other. We saw this in our controlled evaluation. A training run with just the MaskFactory dataset improved on the CAMO benchmark but regressed on DIS5K. For FeyNoBg, we took an interpretability-first approach to training. We first studied how BiRefNet’s stages contribute to finding the foreground and reconstructing its boundary. We discovered that the third stage of it's feature extractor holds a lot of information. Both localization and boundary reconstruction depend heavily on the feature map produced here. This led us to expand this stage from 18 to 24 blocks while preserving the pre-trained weights. We then trained FeyNoBg on 26.1K diverse examples assembled from 10 datasets. The goal was to improve foreground identification and boundary precision without sacrificing either one. Across eight benchmarks, FeyNoBg achieves the best published score on four and comes within 2% of the leader on the rest. Building FeyNoBg also exposed a tooling problem. Image matting models are usually released as isolated repositories with incompatible preprocessing, training, and evaluation code. We built NoBg to solve this. NoBg puts these workflows behind one Python interface. It supports BiRefNet today, with more architectures coming. We hope you build something exciting with it! Happy to answer any questions! https://ift.tt/T3OSXuj July 27, 2026 at 11:59PM

Show HN: Infrawrench – a tool to manage cloud and svcs with workflows and chat https://ift.tt/DAVTva5

Show HN: Infrawrench – a tool to manage cloud and svcs with workflows and chat https://infrawrench.com July 27, 2026 at 11:25PM

Show HN: An interactive way to exploit an LLM without going to jail https://ift.tt/31B5Nkp

Show HN: An interactive way to exploit an LLM without going to jail https://ift.tt/9iSdLuX July 27, 2026 at 01:16AM

Show HN: Temporal Context Map https://ift.tt/ZAIQUtc

Show HN: Temporal Context Map Timeline with depth. https://ab.neudice.eu/ July 26, 2026 at 07:59PM

Show HN: IPAbet – A fast, memorable keyboard for International Phonetic Alphabet https://ift.tt/no5TDUc

Show HN: IPAbet – A fast, memorable keyboard for International Phonetic Alphabet https://ipabet.org July 25, 2026 at 09:41PM

Show HN: Crisp – Open-source display manager for macOS (DDC, HiDPI, presets) https://ift.tt/aC8t3RM

Show HN: Crisp – Open-source display manager for macOS (DDC, HiDPI, presets) I recently bought a new 1440p monitor and connected it to my mac, but at native resolution the UI felt so tiny and unfamiliar. I'm fairly new to mac in general so I checked my options for scaling, but quickly learnt (afaik) that this wasn't a thing for external monitors. I found some options in BetterDisplay and Lunar, but it felt stupid to pay for a feature that should be included. FreeDisplay seemed like the perfect option, but when I tried it on my mac it didn't work for me. Development seemed stale so rather than adding a PR, I forked it and fixed it. After that I wanted to do some changes and add some features, which suddenly ended up in a full rewrite. It covers the thing I initially wanted, which was HiDPI, but I also wanted it to look native, so I added some native elements. I kept the display arranger and fixed a lot of the issues with e.g. auto and combined brightness, profiles for the monitors, presets etc. Can be installed with brew (brew install --cask didriksg/tap/crisp) or use the dmg file in the releases in the repo. It’s unsigned though, so you’ll probably get some warnings I’ve been using it for a week now and thought I’d share it with anyone that wants it. Open source and PRs are welcome. https://ift.tt/mtPp65r July 24, 2026 at 11:05PM

Show HN: Flow Matching model inference in C https://ift.tt/rGhqEPn

Show HN: Flow Matching model inference in C As the title and description of the GitHub repo suggest, I’m working on a small project for purely educational purposes, with the goal of implementing generative model inference (small models capable of modeling 2D distributions) based on the Flow Matching paradigm in C. I’ve worked on generative AI models based on Flow Matching from a more “abstract” perspective, using frameworks like PyTorch, and I wanted to understand what goes on behind the scenes. The repository is still a work in progress and is also one of my first "serious" projects in C. https://ift.tt/VZ6OXHd July 24, 2026 at 12:01AM

Show HN: NeoBox – a native macOS NeoGeo emulator front end https://ift.tt/GsfHySq

Show HN: NeoBox – a native macOS NeoGeo emulator front end I am 90's kid. And NeGeo console was something I always longed for and only ever saw ONE person ever owning! For those who are following...there's a new NeGeo AES console coming out later in the year! I got excited and wanted to remember playing OG SNK games that I loved (Super Sidekicks, Metal Slug, Art of Fighting). I first reached for the amazing OpenEmu native macOS emulator fronted, but found out it did NOT have support for NeoGeo console (FYI I later found out there is experimental support for it) MAME is there, but wanted a nicer macOS fronted similar to Openemu. I've built plenty of macOS / iOS in my career before (for fun and professionally). So decided to give it a shot. Soon this turned into NOT just a MAME frontend...but I wanted a NICER experience and embedded the amazing libGeoLith emulator library. NeoBox can use either GeloLith (iwht native Metal rendering pipeline) or a frontend for a self-managed MAME installation. So... what was AI generated and what wasn't: * Main native macOS frontend was all hand written code, nothing fancy here. Just native AppKit code * Painstakingly testing as many NeoGeo ROMS as possible and fixing bugs AI-assisted: * Website (duh ;) ) * libgeolith and Metal rendering pipeline. This truly was new terrority for me and I could NOT have done this without AI. I'm not well versed in graphics rendering pipelines so it was amazing to me how well Claude was in getting this working! My goal...simple...hoping it funds my purchase of the new NeoGeo AES+ Ultimate Edition console :) That's it! Mac App Store Link: https://ift.tt/m6V5cvn... https://neo-box.app July 23, 2026 at 10:42PM

Show HN: Brew doctor` for Skills and MCP loadouts https://ift.tt/y8Ec5Tm

Show HN: Brew doctor` for Skills and MCP loadouts Recently, I've had agents reach for the wrong skill or tool. This tends to happen in the middle of longer reasoning chains, which frustratingly means lots of chatter polluting the context before a correction can be issued. To chase these issues down, I built `drskill`: a CLI tool that checks for conflicts and security issues among your agent's Skill and MCP loadout. In addition to spotting conflicts that might trip up your agents, security alerts were added as well. Did an MCP provider silently add a tool due to a supply chain attack? Running `drskill` on bootup or during CI will flag those changes. `drskill` works without access to an LLM, though connecting it to one will yield better conflict reports and allows for suggesting alternate, non-clashing descriptors. A ledger is maintained globally and locally, tracking acknowledgements and preferences. This is the type of tool that heavily benefits from contributions (your loadout is very different than mine!), so please file issues or submit PRs if you're interested. https://ift.tt/TpNWFjA July 22, 2026 at 10:50PM

Show HN: PMG, open source package firewall https://ift.tt/x0E7eDC

Show HN: PMG, open source package firewall Hi HN I am the founder of SafeDep. We have been detecting malicious packages for a while. Coming from DevSecOps background, I always considered malicious package detection & protection to be a build stage problem. But I was wrong since the S1ngularity and early Shai-Hulud days. In 2026, we pretty much started worrying more about our own dev machines than CI/CD environment. Depending only on threat intelligence data (OSV / SafeDep / Socket / any other source) to protect our own dev machines did not feel right. We wanted to build a multi-layered protection that can get 100% visibility of OSS packages coming in, and can protect against known and “hopefully” unknown threats. That’s how Package Manager Guard (PMG) started. Core idea was simple: - Start a local proxy (localhost) - Make sure supported package managers like npm, pnpm, pip etc. goes through it - Use threat intelligence data to fail fast on known malicious packages - Apply policies like dependency cooldown as additional guardrails - Adopt a policy language like CEL to support custom policies (roadmap) - Everything stays local with stackable policies and audit log - Threat model - Protect “willing” developers against malicious open source packages Note: PMG does not consider a malicious developer as part of its threat model. So no real effort has been put to “enforce”, rather the goal is reduced friction while being effective. Then came across Anthropic’s SRT and suddenly realized that in-process OS-native sandboxing is a good solution for limiting blast radius against unknown threats, especially since package managers have predictable runtime behaviour that can be allowed via. a sandbox while denying larger user permissions. Adopted seatbealt on MacOS and Landlock + Seccomp BPF for Linux. Seccomp BPF with Go was a battle of its own due to lack of control on OS threads, but finally managed to get it working without major performance cost. To summarize, PMG does not only depend’s on SafeDep’s ability to find malicious packages. It enforces dependency cooldown (useful if you are stuck with older npm/pnpm), sandbox to protect against malicious packages. Our near term goal is to support CEL as a policy language and improve tooling around sandbox rules to make adoption easier. Any feedback is welcome. https://ift.tt/96mhksw July 21, 2026 at 11:58PM

Show HN: Cross-Harness self hosted registry and analytics for AI Agents https://ift.tt/BfU5qus

Show HN: Cross-Harness self hosted registry and analytics for AI Agents https://ift.tt/6AuUPji July 21, 2026 at 11:57PM

Show HN: LectureToBook – Turn Videos into a PDF/ePub https://ift.tt/EdlDuLz

Show HN: LectureToBook – Turn Videos into a PDF/ePub Lecturetobook takes a video presentation and turns it into an editable document, with photos, diagrams, etc. extracted from your slides. I came up with this idea because I was enrolled in an online course and it was all videos. I spend all day long on the computer for work, so the last thing I want to do after work is spend more time staring at a screen. I wanted something that could take those videos and turn them into a readable format. The most difficult part was detecting what frames in the video are slides, and extracting from those what is useful content to add to the document. I didn't want to just stick a screengrab of the slides in the text, I wanted it to read like an actual book, so it uses an AI model to take from the slides what is useful and ignores what is just repeated in the transcript. Here is an output sample from an NIH video: https://ift.tt/ePIyLsp Feedback welcome! This is my first side-project that has made it to launch. https://ift.tt/kLps0dM July 20, 2026 at 10:36PM