Posted by david927 20 hours ago
Ask HN: What are you working on? (June 2026)
Essentially, its a platform that takes in any study or learning material (epub, images, audio, lecture notes, etc) and it uses a series of AI models to create multimodal and interactive learning experiences adapted for 7 types of neurodivergent learners (adhd, dyslexia, asd, dysgraphia, etc..)
In this first round I want to see how players respond to the composure-driven knockdown system, and if they find the sample boss fight difficult enough to be interesting, but genuinely fair. In the background, I'm thinking about how to improve the training mode (it only kind of worked on my daughter), so the game can teach you how to play without telling you how to play.
90s of combat: https://www.youtube.com/watch?v=au6X7snM_G4
I'll also be urging myself to do some marketing during the world cup for my recently released physics soccer arcade game: https://store.steampowered.com/app/3802120/Put_One_In_for_Jo...
The problem I kept hitting with agent workflows (especially cloud hosted agents) was that the artifacts they produced became really awkward to handle across different cloud sessions.
So I built Artifacta as the boring storage layer underneath. Agents store and retrieve artifacts via CLI, REST API, Python SDK, or an MCP server. Artifacts are grouped by session/agent metadata, deduped on identical content, and safe to retry (idempotency keys), making it easy to handle artifacts across different sessions.
Would love any feedback for those who run mutli-agent orchestration or if you deal with artifacts across different agents.
I discovered this week, while the paper was being reviewed by SG1, that I've accidentally stumbled into tackling a rather important problem. Senders as shipped in C++26 can really only express the async equivalent of inline functions because, except for `task`, all the standard senders fully encode the shape of their computation in their type. With something like the `function` I'm proposing, you can use senders to express async algorithms that are separately compiled, just like sync functions.
If the feature lands in a shape similar to what I've proposed in P4223R0, then I think an obvious extension is to modify the core language to support a newer kind of "coroutine" that allows you to define a sender with imperative code. My vision here is that we act on the observation that `std::execution` is a language feature implemented in the library by teaching the compiler how to turn imperative C++ with `co_await`s sprinkled through it into the corresponding sender and operation state. I think this would open the door to putting async object lifetime analysis and optimization where it belongs (in the compiler) without the overheads and inconveniences of C++20 coroutines. It would even let us apply the inliner to async functions when the compiler can see the body of an async callee, not just its declaration.
For now, my next step is to write P4223R1 to incorporate feedback from this past week's WG21 meeting, and continue exploring the design space around specifying sender attributes for a `function`—I'm thinking the current approach of specifying query function signatures needs to be replaced with a key-value object like receiver environments, but I'm not sure yet what consequences that change would have on the design.
I've also recently setup Hermes to be a bit of a project manager for my side projects and it's worked quite well. Gave it a little CLI to see my todos, projects, and "areas" (ongoing long term things). Then it bugs me once in a while when a project is going stale. One of the nicest things is being able to add stuff to the past so if I did work on something but it wasn't associated with a todo I just let it know and then it'll backdate that.
I am close to buying a Claude sub but the thought of it going haywire and costing me extra money in tokens is too scary yet. Not to mention how much provider LLMs (not sure on the correct terminology for them as opposed to local) could hamper your reverse engineering efforts (looking at you Fable).
I really want to solve this scooter and have my own app for it. There's a firmware update feature in the app, maybe I could dump the firmware at least and that would help. Anyone have suggestions on what language model would be the best for this task (analyze decompiled and obfuscated android app / analyze dumped firmware ) ? i have a 96gb macbook and would prefer a local one (I guess to make myself feel better for having spent money on it?) but something through OpenRouter or whatever would do just fine as well
96gb macbook is crazy lol. Good luck!
When the limit is hit, you just cant use claude anymore until the new month / week / day starts , correct? We have Claude at work but we are just told to use it as much as needed and not worry about it so all of us each easily ammass around 100eur in usage every month on the enterprise seats plan.
Thank you for the answer
Then, I will slap an ESP32 & z-wave on it :D secretly to feed my Home Assistant. :D
Really just so I can see these neat things. Like these little tiny crabs, maybe thumbnail size at most (Ocypodidae ?). They come out at low tide, have one claw as big as their body, they stand at their hole and wave it at each out other like "hey! check THIS claw out! No, brah, check MINE out!" and, they do this all the way till tide comes in. Or, the rays sitting on their nests and will wait to the last moment to swim away when the tide is going out. At high tide all kinds of bigger things will come in and check the local scene.
Once I have HA linked, I can start a camera record some of this. Yes, it has to be a rube goldberg machine; a digital camera powered by tide, recording kicked of by an over-complicated mechanical device that is also driven by flowing water.
I'm also building a modern HTTPS-only transport utility called curb. It's an alternative to curl and wget. It's written in Go using only the standard library. curb can stream output or download files and picks the right behavior based on what the server returns and whether the output is going to a human or a pipe. It also has a '--vet' mode that runs the body through security sieves; this is meant to add some protection and friction for the 'curl | sh' use-case. https://gocurb.dev
Recently I've been trying to expand it from just coding focused to any kind of agent workflow. So now there are cron and webhook triggers, and more general agent tasks that aren't necessarily coding focused (https://github.com/jonwiggins/optio/blob/main/docs/persisten...).
I think next I want to try and add features for long term memory for agents, but haven't decided on a good way to do it.