<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai on John Kuruvila</title><link>https://blog.akjohn.dev/tags/ai/</link><description>Recent content in Ai on John Kuruvila</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 16 Oct 2026 15:00:00 +0530</lastBuildDate><atom:link href="https://blog.akjohn.dev/tags/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Reverse Engineering My Dashcam's API, Mostly With AI</title><link>https://blog.akjohn.dev/blog/reverse-engineering-the-ddpai-z50-dashcam-api/</link><pubDate>Fri, 16 Oct 2026 15:00:00 +0530</pubDate><guid>https://blog.akjohn.dev/blog/reverse-engineering-the-ddpai-z50-dashcam-api/</guid><description>TL;DR The official DDPAI app never once connected to my dashcam, so I mapped the camera&amp;rsquo;s undocumented local Wi-Fi API and wrote a zero-dependency Python client for it — and found that the camera&amp;rsquo;s own settings API is far bigger than the app&amp;rsquo;s UI admits. The phone side turned into an Android app, because Android makes a dead-end Wi-Fi network surprisingly hard to automate. Almost all of the code here was written by AI agents working under my direction.</description></item></channel></rss>