seamus_c

Joined 10 years ago

Karma
51
Submissions
9
Member since
Jan 25
Developer at bronto.io
View on Hacker News

Recent submissions

Comment · 1 month ago
Yeah it's a great combo of capabilities, decent as an ereader with Crosspoint too, similar to Xteink, etc.
Comment · 1 month ago
Fair ofc :) This is more intended as a tech demonstrator and a bit of fun, although we have been using it for the weekly shop..
Comment · 1 month ago
You can sort the aisles manually in the app, and there's a (hacky) route to use AI to categorise new items into an aisle. It shouldn't be too hard to use AI to sort the aisles I'd guess
Comment · 1 month ago
Yeah, it is clunky tbh. but it does work. That was the motivation behind the web UI. I also stuck a basic MCP in front of it, we sometimes use AI to help plan out meals for the week, etc.

Why keep it simple when you can massively over engineer it ;)

Comment · 1 month ago
That's a cool idea! There are small 1.54" e-ink screens, I wonder would it be possible to add an NFC chip and have them completely passive? (i.e. powered from the writer)
Comment · 1 month ago
That was part of the motivation here: If I can think it up, can AI actually build it, even when it's outside my day-to-day experience? (and can it do it without frying the hardware somehow)
Comment · 1 month ago
Honestly it's pretty good, but it's too new to give you an actual number. I haven't had to think about it so far. As a LoRa Meshtastic node the device ran for days and still had plenty of battery.

In normal operation battery life is by how often you do a refresh, the rest of the time it's in deep sleep. I think for this application I could build in a refresh schedule tied to when the house is active (mornings, evenings, weekends) to reduce the number of refreshes. It syncs on touch if it hasn't synced in the last 5 minutes (and there's a button for when your feeling impatient)

Comment · 1 month ago
I stuck with the recommended full refresh every 15 interactions and partial otherwise. There's also a full refresh when moving from the settings screen back to the main list. Honestly though it probably makes sense to only do a full refresh when unticking (which is rare) or changing screens. The typical use cases are (1) glancing at the screen to make sure something is one the list and (2) ticking things off as they go into the basket. Neither really require a full refresh imho. Some ghosting is acceptable in general use I think

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton