Since we are talking cats here, let me plug my CatBench vector search playground app, intended to learn and demonstrate in a visual way how (PyTorch + ViT) image embeddings and (Postgres) vector search work together with your regular OLTP transactional data. I implemented a toy version of a purchase recommendation system based on “cat customer” image similarity and “cat fraud detection” building block too:
Once launched, Posturr runs in the background and displays a brief "Claude Mode Active" notification.
I haven’t checked the code yet, but what does the “Claude Mode” mean? Is it a poor naming choice? It implies that the local app is somehow connected to Claude (?)
Right now I'm using a vision library to detect head height which was good enough. I went down a tangent where I hooked it up to my Claude Code instance to take a screen shot and have Claude Code assess how bad my slouch was. Claude would watch a folder for screen shots, read it in, and if it detected bad posture, write to a file the program was watching to adjust blur.
I did this weird work-around so I could use my Claude Code subscription as opposed to the API.
Anyways, it was too slow and Claude was a bad judge of slouchiness. Head height works well enough!
Cool, thanks for the clarification. Indeed it's a good and practical idea for a small app. As other comments have said, (some) people might happily pay for this app.
I luckily won't need such feedback loop anymore, had some mild lower back pain show up over 10 years ago and bought a chair without a backrest that, after 3-4 weeks of struggling, trained me to sit up straight. Now I have some random cheap office chair with a backrest, but I rarely lean back to it. Funnily, I was going to give up using that "backrestless" chair after 2 weeks of inconvenience, but decided to give it one more week and then the magic happened :-) Mild lower back pain automatically gone.
Care to share an example of this backrestless chair? Is it like a regular chair just without the backrest, or has some other differences? Does it have armrests for example, and if not - does it bother you?
I went with an overkill approach at first (as I often do :-) and bought some expensive nicely designed "active chair" / stool that was adjustable high enough so that I could lean on it even when using my desk as a standing desk. It was interesting, but not a game changer at all for me. I don't use standing desks now at all.
Just don't assemble the backrest at first. If sitting up straight, I just lean wrists on my keyboard wristpad and part of forearms on the desk, no armrests needed either.
Edit: I still use my height-adjustable standing desk, but now it's value is that I could adjust it for the perfect height for my sitting-up-straight position (so no chair armrests needed) and it's been fixed at that height for the last 7 years...
Not sure which one the parent was referring to but personalizing I've been using one of these for more than a decade at this point (I'm sitting on it right now) https://www.varierfurniture.com/en/products
The one I have does have a backrest but because of the way it's shaped you don't actually use it to slouch. It's more there to support when you lean back and want to take a break from typing or something like that.
A codebase search for "claude" only has 1 hit in the code (the markdown that you referenced) and 4 commits which include the word in the commit message, or one commit includes .claude/ in the git ignore. See https://github.com/search?q=repo%3Atldev%2Fposturr+claude&ty...
I also wrote a little Python tool that iterates through syscall tracepoint declarations in debugfs (/sys/kernel/debug) and lists available syscalls and their arguments available in your currently running system:
And with eBPF iterators you can bail out early and move to next if you see a non-interesting item (or one that should be filtered out) instead of emitting textual data of all items and later grepping/filtering things out in post-processing.
I use early bailout a lot (in 0x.tools xcapture) when iterating through all threads in a system and determining which ones are “active” or interesting
The internals document looks pretty great too. It actually talks of internals and goes pretty wide and deep. Saved for reading later once the coffee kicks in!
I never got to comparing the exec plans between PostgreSQL 16 and 17. The latter ran much faster, if you (or anyone) have time, please test on 16 and 17 (and 18) with explain (timing=on) and put it through some online plan explainer (and write a post about it).
https://github.com/tanelpoder/catbench
Also, a simple browser-only page for visually demonstrating what embeddings/vectors physically are, for explaining this to database & storage folks:
https://tanelpoder.com/catvector/
(Initial load of the vector heatmaps may take a few seconds when you click on a pet type)
reply