caprine: Block chat seen option no longer working with new Messenger.com
The block chat seen option no longer works – my guess is that the change_read_status.php endpoint has been changed with the new Messenger.com update, but I can’t confirm.
To reproduce: enable “Block Seen Indicator” in the Caprine File menu, then open a chat, while looking on another Messenger.com instance, and see that the message will be marked as read.
Caprine 2.51.2 Electron 10.1.5 darwin 20.2.0 Locale: en-US
IssueHunt Summary
Backers (Total: $2.00)
aggelosm ($2.00)
Become a backer now!
Or submit a pull request to get the deposits!
Tips
- Checkout the Issuehunt explorer to discover more funded issues.
- Need some help from other developers? Add your repositories on IssueHunt to raise funds.
About this issue
- Original URL
- State: open
- Created 4 years ago
- Reactions: 16
- Comments: 22
Is it fair to list the “Privacy” feature on README if it’s broken since December?
Hi everyone and thanks for taking interest in this issue. So far, as you might assume, we’ve been overflown with issue reports about same issues over and over again with little to no investigation or details about how Messenger handles everything now. If anyone is interested in helping out or at least researching a bit more in depth this issue and how Messenger might be handling those “privacy” features (sending seen reports, typing reports and block delivery receipts), we’ll be very thankful. Right now because of the scale of the update of Messenger, we are basically building every feature from scratch and it might take some time until we get back on our feet.
@dusansimic I wonder if its okay to post this link here. But some developers have successfully made a new extension allowing the blocking of seen and typing receipts on the new Facebook. I’m linking it here, maybe it will help.
https://chrome.google.com/webstore/detail/facebook-block-read-recei/llbdoljkknpjgfcnbnoiehjcgancpjmd
@Amandaville your issue was closed because it’s a duplicate of this one. The new Caprine version that was released did not fix any of the privacy related features so it doesn’t matter if its targeted for a new version or a previous one. Here is the pull request that has a list of issues that are fixed/not fixed. The main reason we created a new release is to push out the dark mode fix and some other features. This one is harder to fix and will take some time.
Sorry for the lack of explanation while closing your issue. We are overflow by the issues being reported and a lot of features are broken due to new design. It’s not easy to fix them all at the same time but we’ll try our best.
It still not working - Tested with the release 2.55.2 on Linux
For those interested, I’ve made a pr for fixing this issue. Those who can, please test this out. If there are enough positive responses it’s possible that the fix will be available in the next release.
@dusansimic Thank you for the explanation. My apologies for not understanding that there were unfinished issues in the new release. Thanks for all your hard work.
@ammanley I think I’ve located where the hide read feature is implemented in the source code. I’ve tried to look into the network requests made when you read a message on the web client but can’t find any requests made to a link with
change_read_status, so it looks like they changed something about their API. I don’t know what the requests looked like before the update, though, so I’m not sure it’s relevant.Theoretically a few tweaks to this function might work, but would require a bit of investigation on the Messenger website.