GitHub Issue

Issues with metadata on markdown export

Discovered On Apr 8, 2026
Primary Metric open
Noticing a few issues with the new `md` command. # Missing Year in markdown file name The file name includes a post date, but it's only the month and year, which interleaves multiple years together # Unfriendly date encoding in file name The file name is including a date encoded in readable text instead of ISO format `Sat\ Mar\ 07-karpathy-i-packaged-up-the-autoresearch-project-into-a-ne.md` # Incorrect metadata The above tweet is metadata that cannot be possible. Specifically the `bookmarked_at` date is before the `posted_at` date - ```yaml --- author: "@karpathy" author_name: "Andrej Karpathy" posted_at: Sat Mar 07 bookmarked_at: 2024-11-20 category: tool domain: ai categories: [tool, research] domains: [ai] source_url: https://x.com/karpathy/status/2030371219518931079 tweet_id: "2030371219518931079" likes: 28298 reposts: 3646 --- ``` This looks like a deeper issuer before the `ft show --json` command also has incorrect data - ```json { "id": "2030371219518931079", "tweetId": "2030371219518931079", "url": "https://x.com/karpathy/status/2030371219518931079", "text": "I packaged up the \"autoresearch\" project into a new self-contained minimal repo if people would like to play over the weekend. It's basically nanochat LLM training core stripped down to a single-GPU, one file version of ~630 lines of code, then:\n\n- the human iterates on the https://t.co/3tyOq2P9c6", "authorHandle": "karpathy", "authorName": "Andrej Karpathy", "authorProfileImageUrl"...
View Raw Thread

Developer & User Discourse

afar1 • Apr 14, 2026
@johnrengelman — two follow-up PRs have landed on `main` that should address all three symptoms you reported, and I'd love a confirmation before closing:

1. **Filename month-only + unfriendly date encoding** (`Sat\ Mar\ 07-...`) — fixed by PR #63 (`fix: Format dates as YYYY-MM-DD in ft md exports instead of using raw string slice`, merged 2026-04-09). Filenames should now be `2026-03-07-...` format.
2. **`bookmarked_at` before `posted_at`** — likely fixed by PR #72 (`Fix GraphQL bookmark dates and fetch-media post assets`, merged 2026-04-11), which stopped fabricating bookmark dates from the GraphQL response.

Once v1.3.6 ships you can `npm i -g fieldtheory@latest` and rerun `ft md`. If your exports come back correct on all three counts, please drop a confirmation here and I'll close. If any of them still misbehave, let me know which specific ones and I'll reopen scope.
unsync • Apr 16, 2026
Hello @afar1
i did a full re-sync after deleting the `.ft-bookmarks` and see the same timestamp issue in v1.3.9:





```
---
author: "@Thom_Wolf"
author_name: "Thomas Wolf"
posted_at: Fri Apr 04
category: unclassified
source_url: https://x.com/Thom_Wolf/status/1908170645818536087
tweet_id: "1908170645818536087"
likes: 61
reposts: 12
---
```
johnrengelman • Apr 17, 2026
I also still see the same file name pattern and old encoding `posted_at` field -
```
% ft -V
1.3.9
% ls ~/.ft-bookmarks/md/bookmarks
Fri Apr 03-tom-doerr-obsidian-vault-for-claude-code-memory-https-t-c.md
Fri Apr 10-axel-bitblaze69-some-important-claude-code-security-settings-you-n.md
Fri Apr 10-coreyganim-the-clearest-explanation-of-claude-managed-agents.md
Fri Apr 10-danveloper-https-t-co-n2zjeizky4.md
Fri Apr 10-leopardracer-https-t-co-c4zi0vicnj.md
...
```
johnrengelman • Apr 17, 2026
@afar1 looks like https://github.com/afar1/fieldtheory-cli/pull/63 was closed, not merged.
ccage-simp • Apr 17, 2026
That's confusing. I thought he was using the code from #63 in another pr.