I built a small tool that makes one cleanup commit at a time, keeps it only if tests pass, and moves on. The article is about how it grew from that basic loop into taste files, staged migrations, and a way to keep repos getting a little cleaner in the background.

Been tinkering on my personal site and wanted to add some AI features without being the one paying for tokens on every visit. So I went looking at how close browser-side inference actually is to practical. Closer than I expected.

The post is less a tutorial and more me walking through what it felt like. Kicking tires on random models, getting one to actually run, then doing the small unglamorous work to turn "demo" into something I'd put in front of a reader.

Related: https://news.ycombinator.com/item?id=47851111

I added live translation to this site, wrote about the weird edges, then made this little playground to mess with them directly. Proper nouns, tags and markdown syntax were always coming through weird, so this helped me investigate.

TranslateGemma was one of the few models I tried. Something interesting I noticed is that each model has a different expectation of interface (fields passed in, naming of those fields and such.)

HN Post of Article:

https://news.ycombinator.com/item?id=47808030

Been tinkering on my personal site and wanted to add some AI features without being the one paying for tokens on every visit. So I went looking at how close browser-side inference actually is to practical. Closer than I expected.

The post is less a tutorial and more me walking through what it felt like. Kicking tires on random models, getting one to actually run, then doing the small unglamorous work to turn "demo" into something I'd put in front of a reader.

This tool is not just used for safety. ;)

You can spoof or disappear a mashed file. You can trigger vulnerabilities by breaking internal assumptions of a program.

I just downloaded and I'm presented with a seemingly required google login.

I really appreciate that this is free, but I do feel like the privacy-first approach is incompatible with requiring google login.

edit: FWIW, I bought MacWhisper and would buy this if it didn't require the Google login.

Yes, I can remove the login. I only use your email for communication such as news, updates, and bug fixes (I’m not collecting any additional data)

I’m curious, if you already have MacWhisper, what makes you interested in Scripta? What motivates you to buy it (Am I right we are talking about lifetime payment or you are ready even for monthly subscription)?

I am only trying it out for now. But what I'd love is for things to be quite automatic. I join a zoom, get a prompt "what do you want? record, record+transcribe or record+transcribe+summarize (or use some custom prompt)"

Fully agree to this. I find the cost of cloud providers is mostly driven by architecture. If you're cost conscious, cloud architectures need to be up-front designed with this in mind.

Microservices is a killer with cost. For each microservices pod - you're often running a bunch of side cars - datadog, auth, ingress - you pay massive workload separation overhead with orchestration, management, monitoring and ofc complexity

I am just flabbergasted that this is how we operate as a norm in our industry.

No.

What the commenter is saying pertains to the _decision_ to use Android. That is why this is happening. That is NVidia.

Such decisions cannot be reversed on a whim.

I look at this as the equivalent of writing a MUD as you ladder up to greater capabilities. MUDs are a good educational task.

Similarly AIs are just putzing around right now. As they become more capable they can be thrown at bigger and bigger problems.