[dead]
Ask HN: What Are You Working On? (April 2026)
331–340 of 1001 posts
Re: Ask HN: What Are You Working On? (April 2026)
#332I'm connecting LLMs directly to robots, to see how well they can perform robot things by directly controlling motors and sampling the camera/sensors. Initial results are encouraging!
https://colinator.github.io/Ariel/post1.html
I just got a bigger robot, further results forthcoming!
Re: Ask HN: What Are You Working On? (April 2026)
#333A browser extension & windows app that automatically redacts the text you paste to prevent your private data from leaking to the third parties. Its an AI model that runs 100% locally on your own device so that your clipboard contents do not leave your device.
http://redactor.negativestarinnovators.com
Re: Ask HN: What Are You Working On? (April 2026)
#334[dead]
Re: Ask HN: What Are You Working On? (April 2026)
#335i'm creating (another) learning platform so people with no background in tech can learn sql and python for data analysis
Re: Ask HN: What Are You Working On? (April 2026)
#336https://codeinput.com
2 products released (merge conflicts/codeowners) and now working on workflow automation. Basically trying to use Cloudflare Workers for a different paradigm of executing workflows instead of the traditional n8n VM.
Re: Ask HN: What Are You Working On? (April 2026)
#337Still working on a specialized slicer for a new 3D metal printing process. Mostly addresses material safety, model accuracy, and bringing technology within hobby budgets.
Also, cleaning up a microscope 4-axis micro-positioning stage project control-loop.
Finding spare time to deal with a backlog of various other small projects. =3
Re: Ask HN: What Are You Working On? (April 2026)
#338I've been building Jikimi, a privacy-first parental control platform. It started because my kids were spending too much time on the computer, only stopping if we asked them to. If we forgot, they'd just keep playing. We were also worried about online predatory behaviour like grooming, bullying, that kind of thing.
So I built an on-device OCR engine (PaddleOCR) that reads screen text locally and feeds it into an AI sentiment analysis pipeline. No screenshots leave the machine. We now get alerts if there's detection of concerning interactions. The client is written in Rust, with DNS filtering, game detection (Steam/Wine/Proton), and screen time enforcement built in.
It started as a home project that worked really well. My wife suggested other families wouldbenefit, so I've been building it out as a product. The client shipped on Linux first, we're a Linux gaming family, with Windows coming soon.
There are many more features I haven't touched on. Would love feedback from other parents who've dealt with this space. The goal is to protect children and empower parents with tooling that's transparent and effective.
Re: Ask HN: What Are You Working On? (April 2026)
#339I've been building an AgentRegistry. Right now it is mainly based on A2A Agents that run in Docker containers. There's an auto-register module that watches the Docker system event log (I'll add support for K8S eventually) and if it sees a container spin up with the right labels, it fetches the AgentCard from the Agent, then registers an Upstream and Route with APISIX, then updates the 'url' field in the AgentCard, and stores the AgentCard in the Registry.
The Registry in turn has two interfaces: one REST, and one A2A itself. If you hit /.well-known/agent-card.json on the Registry server, you get the AgentListerAgent, which supports searching for Agents by various criteria. Or you can search using the REST interface. In either case, you get an AgentCard that points to the correct APISIX endpoint to talk to the desired Agent.
Besides adding K8S support, other plans include adding support for other proxy providers (including Istio for the K8S case), supporting Agents that are not based on A2A and, allowing Agents to register themselves using the Registry API, and... uh, well, that's the main stuff I have in mind right now. Aaah, wait, I might do something along the lines of integrating an MCP Registry as well, not sure yet. Heck maybe I'll get bored and make it an all-out API registry for all sorts of endpoints... could integrate a UDDI server and bake in WSDL support for good measure! (Don't count on that last bit happening anytime soon).
Anyway, no repo to share right this second, but I do intend to make it open source. I'm just committing the cardinal sin right now of wanting to "make it presentable before releasing the code".
Re: Ask HN: What Are You Working On? (April 2026)
#340[dead]