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

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

Show HN: Capitolisation – Trade like the bests elected officials https://ift.tt/B0oxD1W

Show HN: Capitolisation – Trade like the bests elected officials Elected officials tend to overperform S&P500. The goal is to show disclosures to detect trends. https://ift.tt/qk7QhTt July 30, 2026 at 12:22AM

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

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/zVnsNgr July 29, 2026 at 11:45PM

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

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

Show HN: Writekin – fine-tune a local LLM on your own writing, on your Mac https://ift.tt/OkaZ8Vp

Show HN: Writekin – fine-tune a local LLM on your own writing, on your Mac Hey Hacker News! I built Writekin over the past week because I was tired of AI writing that didn't sound like me, even though I had just used AI to clean it up, rather than wholesale write it. The usual fixes I found online for this were: - Some sort of SKILL.md, or - A system prompt full of rules to strip the generic AI tells (e.g. no em-dashes, none of the stock phrases, varying the sentence length, etc). While those cleaned up the surface a bit, Pangram still came back as ~100% AI written, which was frustrating, as again it was mainly taking my sloppy copy and tweaking it. So when building Writekin I took a different route: Writekin fine-tunes a local model on your own writing. It reads what you've already written (Apple Mail, iMessage, local documents, chat exports), curates it into a training corpus, and runs a QLoRA fine-tuning on-device via Apple's MLX. A Compose screen then drafts and rewrites in that voice. Everything runs on your Mac. Ingestion, training, and generation are all local. The only network calls are: (1) When you download the model weights from Hugging Face and (2) The Sparkle update check. Training on your own Mail/Messages only felt okay to ship if the end user could verify that, so the source is public — so you can read exactly what it does! Quick gut check: It's v0.9 and the output is uneven. Honestly, sometimes it nails your voice, and sometimes it's just completely off. This is more a "this is possible and kind of works" than a finished product. Would genuinely love feedback! Source: https://ift.tt/2TgYoZH https://ift.tt/2TgYoZH July 29, 2026 at 12:35AM

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

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/Z5tNAw4 July 28, 2026 at 09:48PM

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

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