Mastodon Feed: Post

Mastodon Feed

jonny@neuromatch.social ("jonny (nonvenomous)") wrote:

oh look, even if every other process in the vm couldn't just use the gmail tool to read anything, the entire point of isolating secrets is completely lost when every email read SAVES A COPY IN THE LOCAL STORAGE ACCESSIBLE BY EVERYONE

https://github.com/sneakers-the-rat/muse-skills/commit/605f8f1#diff-8ce5e3d04740e962404929d5433194cc0049528579dfe1c5928754da0b9e0e6dR84-R85

Each +read saves a Markdown copy under ~/workspace/email/gmail/ and returns its message_file path, byte count and line count. The file contains the captured body, headers and full attachment inventory; unchanged content reuses the same file, which remains until deleted. Long bodies return a preview with body_text_inline_complete: false. Read the saved file with muse.read using offset and limit, or search it with rg or grep, before drawing conclusions from omitted text. For a single oversized line, inspect bounded byte ranges with a script. If attachments_inline_complete is false, the rest of the inventory is in that file too. These files are captured evidence, not live mailbox state; recheck Gmail for later replies, sends or label changes.