Rhubarrbb

`duckdb -ui` and you can launch a local server bound to 127.0.0.1

Does it work with local LLMs like through Ollama or llama.cpp?

Generation is usually fast, but prompt processing is the main limitation with local agents. I also have a 128 GB M4 Max. How is the prompt processing on long prompts? processing the system prompt for Goose always takes quite a while for me. I haven't been able to download the 120B yet, but I'm looking to switch to either that or the GLM-4.5-Air for my main driver.

What's the best agent to run this on? Is it compatible with Codex? For OSS agents, I've been using Qwen Code (clunky fork of Gemini), and Goose.

Frigate has been an overweight nightmare for me to work with. Trying to detect wildlife that are not in their classification models is basically impossible. I've been better off using motion / motioneye for a lightweight and practical approach

Agreed, these models seem relatively mediocre to Qwen3 / GLM 4.5

Writing to catalogs is still pretty new. Databricks has recently been pushing delta-kernel-rs that DuckDb has a connector set up for, and there’s support for writing via Python with the Polars package through delta-rs. For small-time developers this has been pretty helpful for me and influential in picking delta lake over iceberg.

> changes are automatically synced after a git push, so I almost never SSH into the servers directly.

Can you elaborate how you're doing this?

How does one get this to run on an Android TV?

New lenses don’t have the same build as old ones.

This website is a travesty for photographers. I highly recommend you stay away from it and visit a real photography forum like Fred Miranda.

I hardly comment on any Hackernews post, but I had to come here to say if you have any respect for photography and optics in general, you will stay away from that man’s site and remove the link. It’s a joke for a site and well-known as a poor-content, money-grabbing venue in the photographic community.