Skip to content

Migrate from messenger.com to facebook.com/messages with bug fixes and new features - #2379

Open
bankjaneo wants to merge 3 commits into
sindresorhus:mainfrom
bankjaneo:development2
Open

Migrate from messenger.com to facebook.com/messages with bug fixes and new features#2379
bankjaneo wants to merge 3 commits into
sindresorhus:mainfrom
bankjaneo:development2

Conversation

@bankjaneo

@bankjaneo bankjaneo commented Feb 24, 2026

Copy link
Copy Markdown

Fixes #2374 #2361

Summary

This PR migrates Caprine from messenger.com to facebook.com/messages to address Meta's discontinuation of messenger.com on April 15, 2026. Includes pre-migration improvements and comprehensive post-migration fixes.

Migration

  • Domain migration: Switch from messenger.com to facebook.com/messages
  • Updated selectors for new UI structure
  • Added Facebook Messenger notification sound (messenger-notification.mp3)

Pre-migration Improvements

  1. macOS draggable area - Moved from top of chat panel to top 24px of the app
  2. Windows jump list - Added Windows taskbar jump list feature
  3. Dock conversation limit - Limited to 10 items on macOS
  4. Theme switching fix - Fixed dark→light theme bug when using system-based theme
  5. AGENTS.md - Added documentation for agentic coding agents

Post-migration Fixes

  1. macOS traffic lights - Repositioned to top-left of conversation list area
  2. Chat profiles - Open in default browser instead of in-app
  3. Notifications & dock badge - Fixed after facebook.com/messages migration
  4. Notification sound - Refactored to use native tools on all platforms (PowerShell on Windows, afplay on macOS, paplay on Linux)
  5. Chat links - Open in external browser, images stay in-app
  6. Conversation menu actions - Fixed Mute, Archive, Delete
  7. Notification features - Fixed message preview, unread badge, and mute notifications
  8. Internationalization - Use non language-specific selectors for full language support

- For macOS, move draggable area from top of chat panel to top 24px of the app
- Add Windows jump list feature
- Limit dock conversation list to 10 items on macOS
- Fix dark→light theme switching bug when using system-based theme
- Add AGENTS.md for agentic coding agents
- Update package-lock.json, conversation-list.ts, and selectors.ts
…n fixes

Migration:
- Migrate from messenger.com to facebook.com/messages

Post-migration fixes:
- Reposition macOS traffic lights to top-left of conversation list area
- Open individual chat profiles in default browser
- Fix notifications and dock badge after facebook.com/messages migration
- Add Facebook Messenger notification sound
- Refactor notification sound to use native tools on all platforms
- fix: open all chat links in external browser, keep images in-app
- Fix conversation menu actions: Mute, Archive, Delete
- Fix notification features: message preview, unread badge, and mute notifications
- Use non language-specific selectors for full internationalization support
Notification & Tray:
- Fix muted conversations still showing notifications and badges
- Fix tray icon updates on unread state transitions
- Eliminate race condition in tray icon state management
- Reuse notificationCheckbox selector for sounds toggle
- Remove outdated TODO for muted conversations
- Add optional unread count on titlebar

UI Icons:
- Fix SVG paths for Preferences, Archive, and Delete menu items
- Fix SVG paths for GIF, Sticker, Attach Files, and Search buttons
- Update icon paths to match Facebook's current Messenger UI design

Build:
- Add RPM package building with native rpmbuild
@zygimantasc

Copy link
Copy Markdown

Is the project dead? 😢 This is a major change that has to be introduced into this project.

@RedDragonWebDesign

Copy link
Copy Markdown

Is the project dead? 😢 This is a major change that has to be introduced into this project.

Doesn't look dead (there was a commit 3 months ago fixing a bunch of stuff), just inactive. Sometimes something major breaking is a good way to trigger some maintainer activity in a repo. Lol.

Although I do agree it would be good to get this patch reviewed BEFORE everything breaks :)

Good general tip for the future: smaller PRs are easier to review. If this were one of my repos, I'd ask for this PR to be split into just the change to facebook.com/messages, and then all the other fixes should be their own PRs.

@zygimantasc

Copy link
Copy Markdown

Is the project dead? 😢 This is a major change that has to be introduced into this project.

Doesn't look dead (there was a commit 3 months ago fixing a bunch of stuff), just inactive. Sometimes something major breaking is a good way to trigger some maintainer activity in a repo. Lol.

Although I do agree it would be good to get this patch reviewed BEFORE everything breaks :)

Good general tip for the future: smaller PRs are easier to review. If this were one of my repos, I'd ask for this PR to be split into just the change to facebook.com/messages, and then all the other fixes should be their own PRs.

I do understand, that the project was originally created by one creator, but maybe we should have automatic LLM based PR approval system in solutions like these ones? Why creating multiple forks, PRs that are never reviewed and merged? Such projects are golden, that should kept alive - I do think we need to have as much automation as possible, so it would be always up to date and few steps ahead of "Meta". Not sure how my ideas correlate with a broader community.

@RedDragonWebDesign

Copy link
Copy Markdown

If robots are both writing and approving the PRs, then we might as well just not have human developers anymore at that point :P Sounds like an AI slop quality nightmare.

The ability of open source to fork repos works around the very real problem of maintainer bandwidth/burnout. Someone already forked and fixed this repo; the link is in one of the threads somewhere.

Personally I am going to wait a bit and see if a hotfix gets released for Caprine official once things break.

@bankjaneo

Copy link
Copy Markdown
Author

Hi there, the reason for big PR is because the maintainer himself gives me an advice on the previously closed PR for easy review and another reason is by just changing the URL is not making the app works. In fact, almost all features break and UI is also horrible with Facebook top bar. So there are some works to be done before it reaches the usable stage.

I believe the maintainer is currently busy with other projects and he'll review or make a migration himself once he's ready 😀

@MatthewMenze

Copy link
Copy Markdown

Are we expecting this to be merged in by the switchover date from facebook? I'm fine switching to the fork of this project if needed, but I'd prefer if it just merged in as an updated release.

At any rate, I just wanted to pop by and thank @bankjaneo for this fix, Caprine is such an important part of keeping in touch with friends and family since the messenger app went away, and generally an upgrade in my opinion.

@monomon

monomon commented May 19, 2026

Copy link
Copy Markdown

I would just like to report that I have been using the fork for a few days, and it works great! Thanks for putting it together.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Messenger discontinue on April 15

5 participants