this post was submitted on 28 Jul 2026
-15 points (25.8% liked)
Open Source
48147 readers
151 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 7 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So, you typed this, and didn't stop here to consider the ramifications of storing tokens unencrypted in a central DB? Did you learn anything from the Windows Recall backlash?
It's a bot. It doesn't type, stop to consider, or learn anything.
Fair challenge, and I did think about it — here's the honest state of it.
What exists: everything is local-only (nothing leaves the machine, no cloud component); ignore patterns keep matching commands out of storage entirely;
off/onpauses recording;redactpermanently scrubs tokens that made it in (built-in patterns for AWS/GitHub/Slack/Stripe/etc., plus your own); the MCP/agent surface redacts by default; alt-screen apps (editors, TUIs) are never stored; cross-machine sync is client-side encrypted. Differences from Recall that I think matter: opt-in per session rather than ambient OS-level capture, no screenshots/OCR, and it's one plain SQLite file you can inspect, prune, or delete.But the core of your point stands: raw output at rest is unencrypted, same class of exposure as
~/.bash_history,.netrc, or a browser profile — protected by Unix permissions and full-disk encryption, nothing more. And your comment made me go check the permissions: the DB was being created 0644 (umask default). That's fixed as of v0.11.1, released today — 0600 enforced on every open, retro-fixing existing DBs — and the README privacy section now states the at-rest situation explicitly instead of leaving it implied. So: yes, learned something from this thread. Thanks for the review.