lilith/messenger
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(imessage-macos-icloud): 📝 Update deprecation notices in macOS/iCloud sync documentation files

Browse source 
Co-Authored-By: Lilith Autocommit <noreply@atlilith.com>
This commit is contained in:
autocommit 2026-04-18 18:28:31 -07:00
parent e7eaaacda8
commit 154fb5e8a3
2 changed files with 50 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
imessage-macos/DEPRECATED.md Normal file
View file

@ -0,0 +1,25 @@
# DEPRECATED — see @applications/@mac-sync/
This Swift macOS agent is **superseded** by the unified `@mac-sync` package.
The replacement lives at: **`~/Code/@applications/@mac-sync/`**
## Why
Three macOS-adjacent sync services (iMessage here, iPhoto in `@imajin/services/imajin-iphotos-sync/`, and server-side iCloud IMAP in `@messenger/imessage-sync/backend/modules/icloud/`) were built inconsistently and drifted. They are being collapsed into one menu-bar app with three modules, backed by one server that follows the `@features/api/` pattern (surfaces + features + entities).
## Status
- **As of 2026-04-18**: this directory still runs the production iMessage sync on plum (`LaunchAgent: com.lilith.messaging`).
- It stays *runnable* during the migration (Phases 0–6 of the plan) so we can cut over with a rollback option.
- At end of Phase 6, the LaunchAgent is unloaded. The plist is kept for emergency rollback only.
- Messages + contacts **are not migrated** — cheap to re-sync fresh from plum's `chat.db` once `@mac-sync` is live.
## Plan
See `~/.claude/plans/moonlit-swimming-deer.md`.
## Do not
- Add new features here. They go in `@mac-sync/@packages/imessage/`.
- Import from this directory elsewhere. Use `@mac-sync` packages instead.

25
imessage-sync/backend/src/modules/icloud/DEPRECATED.md Normal file
View file

@ -0,0 +1,25 @@
# DEPRECATED — iCloud IMAP polling moves to @mac-sync
This NestJS module polls iCloud IMAP server-side on black. It is **superseded** by the `imail` module in the new unified agent at **`~/Code/@applications/@mac-sync/`**.
## Why move it to the Mac
- The Apple ID is already authenticated on plum via Mail.app. No credentials stored on a server.
- Mail.app already does incremental iCloud sync — we just read its local index via ScriptingBridge.
- Unifies with iMessage + iPhoto under one menu bar, one install, one permission grant.
## Status
- **As of 2026-04-18**: this module still runs as part of `messenger-imessage.service` on black (though currently the service was crash-looping for weeks due to an unrelated port conflict — fixed 2026-04-18).
- It stays in place during Phases 0–4 of the plan.
- At end of Phase 4, the Mac-side `imail` module has been proven against this one in parallel (dedup on `externalId` / Message-ID header). Once verified, set `ICLOUD_SYNC_ENABLED=false` and stop polling from the server.
- **Emails are not migrated** — the Mac-side module back-fills from the local Mail index on first run.
## Plan
See `~/.claude/plans/moonlit-swimming-deer.md`.
## Do not
- Add new IMAP providers here. New mail providers go through `@mac-sync/@packages/imail/` or its sibling modules.
- Rely on this module continuing to run past Phase 7.