davegoldblatt

7 ms·

1.
by davegoldblatt 7mo ago
Fair critique. The methodology doc covers this: both pipelines agree on the high-confidence clusters (security vulnerabilities, bubble predictions) even though they disagree on edge cases. The repo is public specifically so people can spot-
2.
Marcus AI Claims Dataset(github.com)
64 points by davegoldblatt 7mo ago|52 comments
3.
by davegoldblatt 7mo ago
lol
4.
by davegoldblatt 7mo ago
Opened a design issue for this if anyone wants to follow along or weigh in: https://github.com/davegoldblatt/total-recall/issues/2
5.
by davegoldblatt 7mo ago
Nice, just looked at dory. Cool to see different takes on the same problem. The write gate and the manual curation approach converge on the same insight: the model shouldn't necessarily decide what's permanently important.
6.
by davegoldblatt 7mo ago
Thx! Also, interesting approach on your end. The screen-context angle solves a different problem than what I was going after, but I agree they're complementary. Curated project memory and broad ambient capture serve different retrieval
7.
by davegoldblatt 7mo ago
The global vs. project-specific split is the right question and has real tradeoffs. You're right that preferences, identity, and coding style don't change between repos. Right now Total Recall is project-scoped, so if you're
8.
by davegoldblatt 7mo ago
Agree on human pruning piece for the most part. The system is built on the assumption that the model shouldn't necessarily be trusted to decide what's permanently important. Remove-gates are a good extension of the same philosophy
9.
by davegoldblatt 7mo ago
Just pushed a rewritten README with a quickstart and usage walkthrough. Appreciate the nudge
10.
by davegoldblatt 7mo ago
Two good questions. Concurrent sessions: it's a real edge case but the blast radius is small. Daily logs are append-only by convention, so two sessions writing at the same time would mean interleaved or lost entries at worst. Registers
11.
by davegoldblatt 7mo ago
Also, let me know if this lands: How It Works Think of it like a kitchen with four storage areas: Counter (CLAUDE.local.md): The stuff you reach for every day. Loads automatically, every session. Kept small on purpose, around a page of text
12.
by davegoldblatt 7mo ago
just updated, thanks for the feedback!
13.
by davegoldblatt 7mo ago
roger that! good point on the readme, was aiming for velocity of shipping. will re work
14.
by davegoldblatt 7mo ago
great to hear! lmk if you have any feedback
15.
by davegoldblatt 7mo ago
thanks! lmk if you have any feedback
16.
by davegoldblatt 7mo ago
done https://github.com/davegoldblatt/total-recall/commit/152ab12
17.
by davegoldblatt 7mo ago
Good catch. I agree the safe default is to ignore memory/ since it can contain personal notes, people context, and daily logs. I’m updating the installer to add memory/ to .gitignore by default (along with CLAUDE.local.md and .cla
18.
Show HN: Total Recall – write-gated memory for Claude Code(github.com)
67 points by davegoldblatt 7mo ago|32 comments
19.
by davegoldblatt 6y ago
WOAH, this solves a huge problem. I'm in the early stages of building my newsletter, and the biggest problem is getting subscribers. Having a way to actively get current subscribers to be invested in getting me new subscribers is aweso
20.
by davegoldblatt 7y ago
You're welcome! Hope it's useful :D
21.
Free Gift for the HN community from a YCSUS S2019 grad, thanks for being awesome
6 points by davegoldblatt 7y ago|2 comments
22.
by davegoldblatt 11y ago
https://www.youtube.com/watch?v=xuQNt45Cjkc