Additional import adapters - Instagram / TikTok / Mastodon archive #121

New issue

Closed

opened 2026-07-15 19:53:43 +00:00 by claude-bot · 1 comment

claude-bot commented

2026-07-15 19:53:43 +00:00

Contributor

Feature idea (audit Phase 5, rank #4) · Effort: medium

Why
The user's notes span more platforms than Twitter/Bluesky. The adapter pattern (importWorker + lib parsers) is built for exactly this kind of extension.

Proposal
Add archive parsers for Instagram, TikTok, and/or Mastodon data exports behind the existing import-adapter interface, mapping each to entries with the appropriate source and source_id dedup shape.

Why it was likely missed
v1 targeted only the two platforms named in the spec.

Acceptance criteria

At least one additional platform archive imports with correct timestamps and dedup.
New parsers follow the existing adapter/parser separation.

Filed from the 2026-07-15 codebase audit. Full report: docs/.internal/report-2026-07-15.md (gitignored).

**Feature idea** (audit Phase 5, rank #4) · Effort: medium **Why** The user's notes span more platforms than Twitter/Bluesky. The adapter pattern (`importWorker` + `lib` parsers) is built for exactly this kind of extension. **Proposal** Add archive parsers for Instagram, TikTok, and/or Mastodon data exports behind the existing import-adapter interface, mapping each to entries with the appropriate `source` and `source_id` dedup shape. **Why it was likely missed** v1 targeted only the two platforms named in the spec. **Acceptance criteria** - [ ] At least one additional platform archive imports with correct timestamps and dedup. - [ ] New parsers follow the existing adapter/parser separation. --- _Filed from the 2026-07-15 codebase audit. Full report: `docs/.internal/report-2026-07-15.md` (gitignored)._

claude-bot added this to the v10.0.0 - Research workflow enhancements milestone

2026-07-15 19:53:43 +00:00

claude-bot added the

enhancement

label

2026-07-15 19:53:43 +00:00

claude-bot referenced this issue

2026-07-15 20:35:39 +00:00

[Scope] General reference-manager mode (PDF library, DOI/Zotero import, paper annotation) #132

claude-bot referenced this issue from a pull request that will close it,

2026-07-18 16:57:12 +00:00

v9.3.0 — OCR (#118) + import adapters (#121) + offline read cache (#122) #142

claude-bot closed this issue

2026-07-18 17:11:29 +00:00

claude-bot referenced this issue from a commit

2026-07-18 17:11:30 +00:00

Merge pull request 'v9.3.0 — OCR (#118) + import adapters (#121) + offline read cache (#122)' (#142) from feat/v10-utilities into main

claude-bot commented

2026-07-18 17:12:08 +00:00

Author

Contributor

Done — shipped in v9.3.0 (PR #142, merge c69897c).

Two adapters added behind the existing parser interface: parseMastodonOutbox (ActivityPub outbox.json — keeps Create/Note, skips boosts, strips HTML; sourceId = mastodon:<id>, published timestamps) and parseInstagramJson (caption from post/media title, creation_timestamp → ISO; sourceId = instagram:<ts> or content-hash fallback). New /api/import/{mastodon,instagram} routes + Import-page cards. Parser unit tests cover Create-vs-boost, HTML stripping, timestamp conversion, dedup id shape, and malformed-JSON handling.

Acceptance: ✅ two additional platform archives import with correct timestamps + dedup · ✅ new parsers follow the existing adapter/parser separation.

Done — shipped in **v9.3.0** (PR #142, merge `c69897c`). Two adapters added behind the existing parser interface: `parseMastodonOutbox` (ActivityPub `outbox.json` — keeps `Create`/`Note`, skips boosts, strips HTML; `sourceId = mastodon:<id>`, `published` timestamps) and `parseInstagramJson` (caption from post/media `title`, `creation_timestamp` → ISO; `sourceId = instagram:<ts>` or content-hash fallback). New `/api/import/{mastodon,instagram}` routes + Import-page cards. Parser unit tests cover Create-vs-boost, HTML stripping, timestamp conversion, dedup id shape, and malformed-JSON handling. **Acceptance:** ✅ two additional platform archives import with correct timestamps + dedup · ✅ new parsers follow the existing adapter/parser separation.