Show HN: Framer Theme Toggle Component for Light and Dark Mode https://ift.tt/vjWraQ5

Show HN: Framer Theme Toggle Component for Light and Dark Mode A free light and dark theme toggle for Framer that remembers what visitors pick, plus a code override for the components that colour styles cannot reach. https://ift.tt/syzJwV5 August 3, 2026 at 12:49AM

Show HN: My public second brain – 660 notes, 15 years, open source https://ift.tt/D1rIPeH

Show HN: My public second brain – 660 notes, 15 years, open source Author here. ~660 notes published from a private Obsidian vault of 8,360 (3M words). Started in OneNote around 2011, moved to Obsidian in 2021 [1], imported everything with a Python script [2]. Notes are compounding over time, and that is where my writing comes from. The Semantic Layer note started in 2022, became a four-part blog series, then a chapter of my book. Materialized Views, One Big Table, dbt and OLAP were separate notes written years apart. I only later noticed they were the same pattern, and that became another chapter. Publishing: add #publish to a note, run `make deploy`. Quartz + Hugo, rsync to my own server [3]. Code [4]. Semantic search over the graph [5]. [1] https://ift.tt/b6vjiRQ [2] https://ift.tt/zoj2kGF... [3] https://ift.tt/D7dlYJw [4] https://ift.tt/vn6BC8r [5] https://explore.ssp.sh https://ift.tt/lB8QxM9 August 3, 2026 at 01:12AM

Show HN: SteerPlane – Deterministic runtime guardrails for AI agents https://ift.tt/Zhf7mBa

Show HN: SteerPlane – Deterministic runtime guardrails for AI agents https://ift.tt/m1APHRM August 1, 2026 at 11:39PM

Show HN: Schema-backed, Git-based structured state for agentic systems https://ift.tt/8m72K3x

Show HN: Schema-backed, Git-based structured state for agentic systems I looked into how to store agentic state in a) a structured way that b) runs without any dedicated MCP memory/state servers and where I can get c) a clear diff-able audit trail of all state changes over time. Nothing that I could find fit the bill. In https://ift.tt/ceUJnx7 , I demo an implementation that fulfills these requirements by combining Claude agents with my previously published Commitspark library and its entirely Git-backed GraphQL API. In the demo, two independent Claude agents are simulated that contribute to a task tracker. A third agent reviews any task changes and rolls back obviously bad ones. A full demo transcript is included in the README, including the agents' raw tool calls. Task agent access to data happens via a small MCP server that exposes two Commitspark APIs (GraphQL API, schema API). These agents can then fetch the schema and author their own GraphQL calls, with GraphQL automatically enforcing written data is schema-conformant. The validator agent additionally has access to basic git functionality to view diffs and revert commits. I'm looking for feedback specifically on: whether schema validation on shared agent state is a problem people actually have, or whether loosely-typed JSON + retries is good enough in practice. July 31, 2026 at 11:50PM

Show HN: Tally – check a spreadsheet's numbers against their source, in-browser https://ift.tt/oNx5mSg

Show HN: Tally – check a spreadsheet's numbers against their source, in-browser https://ift.tt/jDXS2WG July 30, 2026 at 11:25PM

Show HN: Dreeve, a self-hosted dashboard for your sports and fitness data https://ift.tt/MNw5h2m

Show HN: Dreeve, a self-hosted dashboard for your sports and fitness data I've been building this for a few years under the name "Statistics for Strava" but I renamed it to Dreeve recently because of Strava's recently changed API usage terms. They paywalled their API. You point it at your activity files (FIT/TCX/GPX) or connect a Strava account, and it gives you a dashboard with segment efforts, gear and maintenance tracking, a heatmap, monthly calendar view, milestones and a year-in-review. It runs as a Docker container, stores everything in SQLite, and nothing leaves your machine. Stack is PHP 8.5 + Symfony, SQLite, Docker Compose. Simple, straightforward and fast. Caveats: it's built around a single user, so there's no multi-tenant story. The AI workout assistant is optional and off unless you configure it. Segment data still comes from Strava if you want it, which is the one dependency I haven't been able to remove. Docs at https://docs.dreeve.app . Happy to answer any questions you have https://ift.tt/jm8Sslt July 29, 2026 at 11:45PM

Show HN: Vyne – Zapier for DeFi users, run from any LLM or the workflow builder https://ift.tt/HclfReX

Show HN: Vyne – Zapier for DeFi users, run from any LLM or the workflow builder https://ift.tt/oXcZbWs July 29, 2026 at 02:31AM

Show HN: Verifiable receipts for firmware CVE reproduction https://ift.tt/swZXNA3

Show HN: Verifiable receipts for firmware CVE reproduction https://ift.tt/AraY2hx July 29, 2026 at 02:23AM

Show HN: Beakdown – a game inspired by Joust/Skirmish https://ift.tt/hQj3Amc

Show HN: Beakdown – a game inspired by Joust/Skirmish I used to play Joust with my little brother on the BBC Micro many moons ago and have fond memories of it. So when I was experimenting with Claude Opus 5 it was a nice inspiration for this game. Did a little research and found there aren't many games out there that just work in a browser without ads, loading screens or account sign-ups. So I've put this directly on the landing page with no noise in the way - it works on any browser on any device and loads instantly. If it doesn't work at all, please tell me. And also let me know if you think it needs music - I went without it to begin with but don't know if that's what people would prefer or not. Would also love to know how far you get, my personal best is 199,000. Thanks for your interest! https://beakdown.fun/ July 29, 2026 at 01:18AM

Show HN: Somebodyhire.me https://ift.tt/J1mfNT0

Show HN: Somebodyhire.me I originally had this as a personal resume site but decided to build it out into a platform where anyone can sign up and host a resume page. Once I build up the talent pool, I plan on marketing to hr depts and hiring managers. I just don't know a single person who's happy with hiring on either side right now and this feels like a better solution to me. https://ift.tt/nqlMHF1 July 28, 2026 at 09:48PM

Show HN: A 538-style dashboard for upcoming Knesset elections https://ift.tt/yTsURGB

Show HN: A 538-style dashboard for upcoming Knesset elections https://ift.tt/A6PHQvU July 28, 2026 at 12:34AM

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

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/nzhEkOJ 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/lSJ3LXt Site: letsseal.org Thx https://ift.tt/lSJ3LXt July 27, 2026 at 09:22PM