HN user

scosman

3,926 karma
Posts81
Comments803
View on HN
news.ycombinator.com 9d ago

Show HN: Biscotti – on-device meeting transcription for macOS

scosman
1pts1
github.com 27d ago

Show HN: Create animated explainer video from a prompt

scosman
2pts0
imgur.com 1mo ago

Kagi adds Hacker News conversation under links

scosman
5pts0
github.com 1mo ago

Show HN: Cursed Browser – a VLM reads the HTML and hallucinates the page

scosman
7pts1
github.com 2mo ago

Show HN: Videowright – we made our launch video with Claude Code (open source)

scosman
1pts0
kiln.tech 2mo ago

How we made our launch video with Claude Code (and open-sourced the tool)

scosman
3pts0
kiln.tech 2mo ago

Git-Backed SaaS: SaaS Without a Service

scosman
2pts0
github.com 2mo ago

Cursed Browser: web rendering engine using visual-LLMs

scosman
8pts1
github.com 4mo ago

OutClaw: Manage parallel OpenClaw instances in Docker

scosman
1pts0
github.com 4mo ago

Show HN: OpenAPI 2 Skill – progressive disclosure of OpenAPI specs for agents

scosman
2pts0
news.ycombinator.com 4mo ago

Ask HN: Does Window's "Set Time Automatically" feature require the correct time?

scosman
2pts1
github.com 4mo ago

Vibe Crafting: spec and test-driven agent development

scosman
2pts0
github.com 5mo ago

Show HN: Give Agents Isolated Linux Sandboxes via MCP [Kilntainers]

scosman
1pts0
huggingface.co 6mo ago

GLM-Image

scosman
5pts0
twitter.com 6mo ago

Flappy Bird clone that uses folding phone as the controller

scosman
2pts1
github.com 6mo ago

Show HN: CLI to share secrets using one-time public keys

scosman
4pts0
www.theverge.com 7mo ago

Tested: Budget 5K Monitor for macOS

scosman
2pts0
scosman.net 7mo ago

Animating SVGs with LLMs

scosman
1pts0
lancedb.com 7mo ago

RAG Isn't One-Size-Fits-All - Here's how to Tune It

scosman
5pts0
news.ycombinator.com 8mo ago

Vercel.com: Do not use Vercel

scosman
8pts6
docs.kiln.tech 8mo ago

Show HN: Synthetic data generation for evaluating RAGs

scosman
2pts0
github.com 8mo ago

Pelicans Riding Bicycles

scosman
1pts0
tailscale.com 8mo ago

Mail your parents a tailscale node

scosman
3pts1
news.ycombinator.com 11mo ago

Show HN: Breaking IDE silos with MCP for prompts and dev-tools

scosman
1pts0
news.ycombinator.com 11mo ago

Show HN: SecretShare – Easy, secure one time secret sharing CLI

scosman
3pts2
getkiln.ai 11mo ago

Eval-maxing an AI FFmpeg command generator

scosman
6pts0
news.ycombinator.com 11mo ago

Show HN: Give coding agents MCP access to lint/test/format with 1 YAML file

scosman
2pts0
github.com 11mo ago

Show HN: Kiln – AI Boilerplate with Evals, Fine-Tuning, Synthetic Data, and Git

scosman
10pts1
getkiln.ai 1y ago

I wrote 2000 LLM test cases so you don't have to: LLM feature compatibility grid

scosman
2pts2
news.ycombinator.com 1y ago

Ask HN: LLM for Browser Inspector/DevTools/DOM?

scosman
1pts1

Go mobile definitely supports building libraries. It will package up an xcframework for iOS and something else for Android (I forget details). It doesn't need to be the whole app. You get nice(ish) language bindings.

That said, a pure c framework is probably a cleaner way to go.

GPT‑Live 14 days ago

ChatGPT has had this for over a year too. This is a better model.

The top of my ~/.claude/CLAUDE.md:

Don't turn a one-off or area-specific comment into a durable memory without my explicit confirmation. You have a history of over-indexing on one-offs, and those memories end up getting cited to override well-tuned skills.

short answer: they mostly aren't

A few people are running highly quantized models with limited context windows. It's still impressive, but not the benchmark level intelligence. Very few people could afford a rig for reasonable local performance at a reasonable quant, at full context size.

The antirez example is 2.6bit quant, 32k context, and few tokens per second... on a ~$7000 MacBook M5 (new RAM pricing).

I dunno. I know a lot of software engineering experts. AI isn't always right, but neither are the people, and it's getting better and better.

Software is one domain where it excels because of structured training data and simulation environments, so I'm well aware it's better here than other areas.

Still there's somewhere balanced between saying every time it's "insufficient or incomplete or outright misleading" and "just trust AI". AI's a useful source of information/reasoning/research, but know you need to validate it's answers for important decisions.

This was copying many screens, composing layouts and many strings. not a "general look and feel" or one off utility string. Others found parts of the code copied (exact variable names). It would take a court to decide, but I think it's pretty clear cut copyright violation. They gave their agent had access to the EE code, and seemingly asked it to produce a copy. It's not a 1:1 copy, but there was a lot of copying. No clean-room attempt was even made.

If I take the first chapter of Harry Potter and write a new ending, it's still copyright violation. They took many parts.

It's not economic to run them locally. It's amazing for privacy, and fun hobby. But you're either looking at super slow CPU builds with $10k in RAM, $90k worth of GPUs, or a really quantized model that doesn't compare in quality.

I might build one for fun, but it's not going to change the economics alone. Still exciting it's possible.

My 8yo son plays with this any chance he gets. We've started building watches together as a result (simple "drop in movement mods", but aspirations of building our own movement). The author really made something special.

I think the point is: if every app chooses the best model for their use case, my phone is hosed (disk, memory swap, memory). A good-enough default might be better for the user than the each app having the best possible.

I think that's what they are trying to avoid. If you need on-device intelligence, their pitch was "The model the device already has is best", and if you need something more specific an adapter (aka, a fine-tune/lora) is best.

They were wrong when their on-device model was way behind. They still might be right in the long term.

While multiple app I use might need Gemma 4 E4B, I use dozens of apps and app devs can choose from hundreds of models. A shared cache might reduce size a little when there's overlap, but the core problem still exists. If each app chooses a model disk and memory-swapping explode.

Its probably be better for device manufacturers to bake in a default. I'm not proposing they limit you from using others, but one shared default might be best developer/user experience for 99% of apps.

- Being warm in memory is the single biggest perf speedup you can get, and a default is much more likely to be warm.

- "Best model" is usually "best model for this device" given both RAM and compute. A developer can't test every device but Apple can/will.

- Each model needs to be optimized for the hardware (what's running on ANE, what's running on Metal, what's running on CPU). The default gets optimized.

- If you need custom model, a Lora is probably best (30MB, benefits from all of the above)

You could say the default should be swappable, but that's more a linux ideal than an Apple one so I doubt we ever see that. Plus there are real downsides: intentional or not, prompts end up optimized to the model they are developed for, so swapping the default system model would degrade every app.

I had the same experience so started building my own. All problems are solvable, just working on the polish.

- crash recovery: part one is use ADTS aac (even if process crashes, audio is saved up until it does). Part two is isolating the transcription/summaries in separate XPC services.

- disk space: AAC 64kbps mono soles it. Could use Opus for further reduction but both are small.

- speaker bleed: macOS voice isolation processing solves this. It’s a nightmare to get setup, but works great once done.

- library: using argmax SDK - by a bunch of ex-Apple on device AI folks.

It it wasn’t for CoreAudio, I’d say it was easy to make. Argmax, Whisper, and llama.cpp - wrapped in the right architecture, mostly just work.

I’m having fun nerding out on the details like custom vocabulary (get the names of the people in here meeting right), inferring speaker names from transcript, calendar integration, nice UI, etc.