Announcements

A while ago someone wrote in with a question that looked simple: What does Active Sites (##/30) mean? And if I reach 30, will it stop saving? Two questions. The first one was easy. The second one was the problem — because the honest answer was yes. Once Form Recover had drafts saved on 30 different sites, the 31st site was refused. You could open a form there, type a long reply, and nothing was kept. An extension whose entire job is not losing your work was quietly deciding not to do its job.

There’s a version of Form Recover that works exactly as it’s supposed to: quietly, invisibly, accumulating drafts in the background so that when disaster strikes, you’re covered. The problem? It works too well. After a few weeks of active use, your vault fills up. GitHub issues, Reddit comments, support tickets, long-form emails. And suddenly, finding the one draft you actually need becomes a chore of its own. That’s the problem v0.2.2 solves.

It’s finally here. After roughly 90 days of “keluh kesah” (struggles), countless late nights, and hundreds of browser tabs crashed intentionally for testing, I am beyond excited to announce that Form Recover v0.1.0 is officially live on the Chrome Web Store. The 3-Month Journey When I started this project, I thought, “How hard can it be to save some text from an input field?” Famous last words. I quickly realized that the modern web is a chaotic place. Between complex Single Page Applications (SPAs) like React and Vue that manage state in ways that bypass traditional “value” attributes, and the “Nightmare of Iframes” found on many support portals, the development was a constant battle against edge cases. There were times when I thought the “Ghost Icon” would never align correctly, or that the recovery engine might miss that one crucial comment on a forum.