-
-
Notifications
You must be signed in to change notification settings - Fork 548
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How does it compare to Messenger Desktop? #1321
Comments
Caprine is open-source, has privacy features, is more customizable, and also supports Linux. |
Here is my opinion on this. I get the privacy stuff but its running faster and better than Caprine (cause its official) |
I would like someone who is knowledgeable on UWP to chime in on how private the official app must be. Afaik UWP doesn't allow apps to know anything outside of it's container |
Does it support Linux? I can't find a way to install it. |
No it doesn't.. For linux Caprine is the only solution |
I have the opposite experience. The official app is slow on mac. Try cmd + w and then open the app again. It takes 1-3 seconds to do so, while it's instantly with Caprine. The UI is better on Caprine. You can reply to previous messages by clicking a button; you need to right click to access the option in the official app. I'll still use Caprine for now. |
You can reply by double clicking outside of the message (on the same row). That's actually kinda smart instead of having lots of buttons. Also you can react by long pressing the message |
I had to switch to the official simply for the lower memory usage. As @1nikolas pointed out it's not Caprine's fault, the official messenger app just gets to use the mobile interface & APIs which are faster. As I speak right now the official messenger app is using 57 mb RAM, while Caprine is at ~570 mb. Still love & appreciate Caprine and all the dev work that went into it. |
Caprine has some features that I like to use, but I switched to the official simply because of two reasons:
But yeah, Caprine was awesome while I use it apart from the two issues. |
Messenger is also an Electron app so it's definitely not a silver bullet. And it also has its share of issues. I, personally, can't migrate to it for now. |
From my experience with the app, I think it uses Electron only for calls. Everything else seems to be native |
Hmm they could have made it native. Anyway point is that it doesn't use the website directly so it doesn't lag that much like Caprine. But still it has some bugs |
@rtpHarry Caprine has the same problem. Caprine and Messenger are essentially a heavy html page which never refreshes, so everything you do (send/recieve messages, load images, or maybe going a few messages back) is loaded on the ram. Restarting the app is a quick and easy fix |
fair enough... I guess I'm just a bit rooting for it to suck as caprine has had so much development and i don't want it to be bested :P in just over one day its gobbled up 3gb of ram. I have noticed Caprine chugging ram but no more than anything chrome related. This seems like a bug to me, but I'm not an expert: |
Hmm you might be right |
Yea I had the same hope, recent copy paste bug into the windows client causing crashes made me switch :( Hope Caprine matches! Rooting for it :) |
Okay its been a few months using the official app and I have to say that it has become worse. It lags a lot and it freezes most of the time for like a second periodically (despite me having a better PC than I used to have). I don't know how they managed to make it worse, but they did. So I'm switching back to Caprine |
This comment has been minimized.
This comment has been minimized.
Look on the comment above yours |
I found Caprine chugging 6gb of memory and heavy disk usage so back to official for me I tend to copy paste images into my chats... combined with me keeping it open 24/7 on my desktop |
@CaptainYesz |
I just got offered the desktop messenger. Was it not available for Windows before? Is it any good? Caprine right now has issues due to the re-design of messenger.com. It tends to hang and not update anymore. And there are no alerts. |
I noticed the native messenger app for Mac has completely broken search. It will hang and freeze. If I try to scroll up enough in a chat, it'll eventually just leave me with a spinning wheel. This doesn't happen when using the web messenger, and ultimately I'm using Caprine because the search/indexing is just borked on facebooks native mac app. Also Facebook still hasn't released an update that follows the UI guidelines of Big Sur, and the corners of the window aren't rounded lol. Even though Caprine is a little slower then the FB native Mac app, at least Caprine is getting updates. It doesn't feel like Facebooks put an update into their Mac app forever. |
But then why am I still seeing suggestions and ads on Caprine to download Messenger Desktop? Don't want to see these. |
Where are you seeing these suggestions/ads? Version 2.53.0 removed the banner at the bottom of the conversation list and in the preferences modal window (#1621). If you could include screenshots and system info, that would help us track down these objects (and remove them). |
I had to flip back to Caprine as the official app doesn't seem to support logging in via Messenger only account without facebook. The desktop app reactivated my facebook account twice and deactivating seemed to log out the app. Caprine supports a deactivated facebook account with 2FA without requiring my facebook account to be active. |
Sorry to necro this thread, but it seemed like the best place to ask my question. Does Caprine support E2E Encryption like the desktop app? |
Messenger Desktop (on PC) refuses to send files or even images, while Caprine has no problems with them. On the other hand, Caprine cannot write anything, the only possibility is to use a browser (which is very uncomfortable). As long as the saving function is not added to Caprine, I will have to use both programs at the same time. It is frustrating... |
Now that it's out, how does Caprine compare?
The text was updated successfully, but these errors were encountered: