I'm hosting my personal gallery with it: https://captures.moe
Ask HN: What Are You Working On? (April 2026)
401–410 of 1001 posts
Re: Ask HN: What Are You Working On? (April 2026)
#402The goal is to provide AI agents with deep understanding of the codebase and help them understand the context, not just text
Re: Ask HN: What Are You Working On? (April 2026)
#403A site for looking up strata information for apartments in NSW, Australia
Re: Ask HN: What Are You Working On? (April 2026)
#404Recently it hit v3 spec conformance. (I'm executing the upstream spec test suite.)
I don't plan to make it a highly-performant decoder for use in production environments, but rather one that can be used for educational purposes, easy to read and/or debugging issues with modules. That's why I decided not to offer a streaming API, and why I'll be focusing on things like good errors, good code docs etc.
P.S. I'm new to the language so any feedback is more than welcome.
Re: Ask HN: What Are You Working On? (April 2026)
#405Re: Ask HN: What Are You Working On? (April 2026)
#406I am managing a discord community with over 1k+ members I found some people would regularly put spam links or message on all the channels and this been repetitive it's just take time deleting them one by one or reposting them into the specific channel. So I build a discord bot that would make this lot easier it catches the spam message post them into actual channel and also delete spam links. It's open source and easy to setup.
Re: Ask HN: What Are You Working On? (April 2026)
#407Re: Ask HN: What Are You Working On? (April 2026)
#408I've been writing a 'book' (more of an extended blog post that I'd like to put out for free) attempting to explain quantum computing to a layman-ish audience. I sort of got inspired to do this after seeing so many QC PR posts on HN, and finding the educational material in this space to be either too academic, too narrow in scope, or totally facile. I think given the incredible hype (and potential promise) of this ind…
Re: Ask HN: What Are You Working On? (April 2026)
#409The goal is to make every recipe foolproof on the first try, similar to when you walk into a restaurant and just pick what you want to eat without thinking about the details. The goal is to have the same experience, just pick what you want to eat, with recipes that tells you exactly what to do with no magic involved.
Technically it is probably very different from other recipe apps. The database is a huge graph that captures the relations between ingredients and processes. Imagine 'raw potato'->'peeled potato'->'boiled potato'->'mashed potato'. It is all the same ingredients but different processing. The lines between the nodes define the process and the nodes are physical things. Recipes are defined as subsets of the graph. The graph can also wrap around into itself, which is apparently needed to properly define some European dishes in this system. The graph also has multiple layers to capture different relationships that are not process related.
Why was it designed it in this way? Because food/cooking is complex to define. This design is the only way I have found that can capture enough of these complex relationships that the computer can also 'understand' what is going on.
My favourite thing about this is that each recipe is strictly defined in the graph. If the recipe skips a step, or something is undefined, the computer knows that the recipe is incomplete. It won't ask you to do 10 things at the same time and then have something magically appear out of nowhere. It is like compile time checking but for recipes.
It also enables some other superpowers, for example: • Exclude meat part of the graph = vegetarian. Same thing works with allergies. • Include meat part of graph = only show me recipes that contain meat. • Recursive search: search for 'potato' and the computer will know that french fries are made from potato. It can therefore tell you that you could make the hamburger meal, but you will need to complete the french fries recipe first, which should take 60 minutes. • Adjustable recipe difficulty (experimental): It knows which steps can be done in parallell, and which can't based on how the nodes connect. A beginner can get a slower paced recipe with breathing room between steps, while someone more experienced can do a faster pace and do more things in parallell.
If I knew what it would take to build this, I would never have gotten started. I completely underestimated the complexity of the problem I was trying to solve. But here we are, and now it is basically done and working.
The website captures the key points from a non-technical point of view, and you can enter your email and get notified when it will launch in your country.
Re: Ask HN: What Are You Working On? (April 2026)
#410My mother is living alone in her house and we are getting to the point where she might not be able to live alone. I built "Still Kicking", a picture frame that monitors her motion and sends back basic reports and can detect falls and sleep quality to a phone app, to help give her more time at home. It's just an mmWave sensor connected to an ESP32. But it works nicely, and I'm thinking of starting a company making the…