The idea is to guide spending before it happens, not just track transactions afterward.
Ask HN: What are you working on? (May 2026)
801–810 of 1001 posts
Re: Ask HN: What are you working on? (May 2026)
#802Logs are local, but some claims need to travel. As agents, MCP tools, metered APIs, and automated payment flows do more work, there needs to be a simple way for another system to verify what was reported later. PEAC issues portable signed records for that boundary.
Re: Ask HN: What are you working on? (May 2026)
#803Re: Ask HN: What are you working on? (May 2026)
#804Since primarily interested in FT8 and MeshCore here in the local SoCal MC region (wcmesh.com) I put together a Pure-Golang implementation to combine both modes into the same GUI client. The FT8 modem might be the only functional Golang decoder right now, unsure, but it’s entirely open source and here:
https://github.com/kyleomalley/nocordhf
The workflow releases cross compiled for MacOS (notarized), Windows, Linux and uses Fyne for the UI.
In the future, I plan to add other more interesting modes like JS8Call and VeraHF modes, FT4 etc.
Re: Ask HN: What are you working on? (May 2026)
#805Re: Ask HN: What are you working on? (May 2026)
#806It uses flutter under the hood, with Kotlin and SwiftUI for native home screen widgets. A simple nodejs backend powers push notifications too.
Re: Ask HN: What are you working on? (May 2026)
#807To validate the approach I trained the model on generating synthetic data. I did look at datasets available at: https://github.com/logpai/loghub, https://www.unb.ca/cic/datasets/index.html but couldn't find one that would suit my needs.
The approach seems to work on synthetic dataset (with ROC AUC score: 0.9957) but couldn't try it out in a real world dataset. Seeking feedback on the approach.
Re: Ask HN: What are you working on? (May 2026)
#808Re: Ask HN: What are you working on? (May 2026)
#809Re: Ask HN: What are you working on? (May 2026)
#810For context, I built out Playboy's age verification system, and watched as it hurt conversion (nobody wants to upload an ID to an adult website, who would have thought!). Cryptographic signatures from issuing authorities (DMVs, universities, employers, etc) with selective disclosure (e.g. you don't need to upload your full ID, just the fields that matter) is how verification _has_ to work going forward -- AI can fake documents, but not private keys.
I've been working on this 6 months full time, and implemented all the W3C VC, OpenID4VCI/VP, SD-JWT specifications myself.
Would love to get people's thoughts on it!