So inputs and outputs of LLMs are tokens. Inputs to Jev are state (arbitrary strings/tokens) and, depending on the type of query, either an assertion, options, or choices. (All of those are also arbitrary strings/tokens). Outputs from Jev are probabilities. If it's an assertion, the probability that it is true. For options and choices, it's probabilities for each one, basically.

Because Jev answers so quickly and inexpensively, it's a likely replacement for complex, best-effort functions like `isSpam()`, where up until now the only nondeterministic way of implementing that was an LLM, which is slow, costly, and may produce invalid/corrupt output.

I guess I'll focus mine more on the things Meta doesn't care about, like privacy and control.

Refresh rate is a solved problem for eInk as well, but it comes with energy tradeoffs and... might still be proprietary. But 60-120 fps eInk exists AFAIK.

The video preview I linked to only shows the rich maps and instrument modes. There's also a wireframe map view that is higher-contrast and much more practical for your gravel rides: https://i.imgur.com/lZF20Xz.png -- and I am still tuning of course, we can make the map smaller and the characters larger, etc.

Maybe follow @mholt6 on X for updates when I have them... whenever Apple will let me in.

eInk is the right display tech. I think this will do really well. It might need a UV filter.

That said, I don't love needing a separate device (hence, I don't own any bike computer). This is just my preference, but I really prefer to just plop my phone on my handlebars. So I'm building a bike computer app for iPhone: https://x.com/mholt6/status/2090529441944687087 (trying to get Apple to approve my developer account / business info, but they're hung up on my website of all things).

Phones are definitely not ideal in terms of display and energy use, but, I have found that with proper optimizations, energy use is a non-issue. To offset display problems, the app has several ride modes: a rich map display with 3D road or satellite view; a high-contrast wireframe map that looks great at both high and low refresh rates because it has no analog-style gauges; an instrument panel dashboard view; and a voice-only mode that has big touch zones for on-demand voice updates, using a state of the art mobile voice synthesis model. For connected radars, the app also renders radar data and has a screen like Tesla/Rivian's autonomy displays.

The app automatically manages thermals by switching modes to preserve battery life.

In my testing so far, by managing energy, making really good voice feedback, and using high-contrast screens (every mode other than the "rich" map), even a dimmed iPhone display is quite a usable bike computer in high-altitude sunlight.

But man, that eInk looks so clean and nice. Definitely the superior display! Nice work and I hope to learn some things from it!

EDIT: Woah, you got ANT+ support using BLE radio? I am not surprised that that is possible, but dang, that must have been a clever LLM.

Also, dust and hair at that scale looks hilariously huge, so you might want a cleanroom. :-/

The real heroes are the ones ambitiously raising the next generation while changing the world right now. That's what I aspire to be... and those are my role models. Not the ones who abandon their kids or wife to pursue their own dreams and make excessive amounts of money.

If you really can only muster enough time or energy to be ambitious about one thing, be ambitious within your home/family.

Sure. I'm not sure if I will actually publish this thing, but I can show you: https://x.com/mholt6/status/2074986102428139754

I wanted a phone app rather than yet another electronic device. Phones do not have great screens in bright sunlight, and they run hot, so it's not ideal for a bike computer in the first place. But I can't deny the convenience of the multipurpose tool that is my phone.

This app will have a few UI/UX modes. The default is the futuristic-looking HUD, but it has a low-power mode that's mostly monochrome on black, and an even lower-power "Cruise mode" that removes the map entirely and just shows you speed, approximate heading, and nav directions. Still very WIP and mostly for my own amusement!

(I am not an iOS developer, so getting something specific that I needed in a few hours/days was really helpful instead of spending months/years learning the language, APIs, etc.) (I am absolutely not "vibe-coding" Caddy btw, just tinkering with it for personal projects.)

I know a WDR typically would, but I don't think they perform an ignition for those.

We should probably take a break on these. It's probably more newsworthy now when GitHub is "up".