Author Topic: Facebook protocol  (Read 162149 times)

0 Members and 1 Guest are viewing this topic.

Offline Myshor

Re: Facebook protocol
« Reply #795 on: 11 10 2019, 20:53:16 »
Started to work without any update. :D Maybe they were doing something with their API.

Fear my anger, fear my power.
I'm Dark Angel undercover.
 

Offline aekotra

Re: Facebook protocol
« Reply #796 on: 11 10 2019, 20:59:15 »
Started to work without any update. :D Maybe they were doing something with their API.

Confirmed!
 

Offline culinko

  • Newbie
  • *
  • Posts: 2
  • Karma: 0
Re: Facebook protocol
« Reply #797 on: 11 10 2019, 23:16:25 »
For 2+ months now, I have been updating Miranda after my daily session instead of the beginning of the day, so I wouldn't need to restart Miranda and reconnect to the Facebook protocol. This means that at the beginning of my day I started Miranda and declined if there was an update (so it wouldn't restart). Then at the end of my day, I would close Miranda and would start it again at the beginning of my next day, but this time it would have the updates from the previous day. I though the issue was gone, but today after 2+ months I received the suspicious activity e-mail forcing me to reset my password yet again.

The only things worth mentioning is that I am closing Miranda from tray after my daily session (I am not clicking on disconnect for the Facebook protocol). I also sometimes visit the Facebook page in my browser at the same time I have Miranda open. Maybe it's one of these things that Facebook don't like?
 

Offline riki

Re: Facebook protocol
« Reply #798 on: 21 10 2019, 18:40:50 »
Happened again today as soon as I started Miranda. Wrote another love letter to support. They don't seem to care at all.
 

Offline riki

Something needed for conversation archival
« Reply #799 on: 28 10 2019, 19:52:07 »
One important reason why I use Miranda is that I like to have all my conversation histories tidily archived. The Facebook protocol is giving me a hard time because some messages that I sent/received via web browser (often on a different computer) are skipped and never retrieved. Luckily, there's an option to load last messages on opening message window (EXPERIMENTAL). This function works most of the times (marked as experimental after all), but sometimes it fails to retrieve some messages.

My solution: "load history". This seems to get all the messages, but it goes back to the start of time and leaves a mess of duplicate messages. So I found a trick: I replace the key LastMessageID value with one from a previous backup, so next time I open the message window, Miranda retrieves messages up to the previous value (up to 99).

It's a bit inconvenient, though, and hit-and-miss. So I'm asking for some feature to help with my aim: having an integral store of my conversations, given that some messages get lost sometimes (never arrive). I think one of the following could solve the problem.

1. "Delete duplicate messages" feature, which used to be present but got removed.
This would enable the user to reload ALL history and delete duplicates. Problem solved (but big download in some cases, Facebook site might be unhappy).

OR

2. Exposing the MessageID in all messages (through "properties" in History++ maybe?).
This would enable the user to retrieve the last 99 (max) messages by replacing the LastMessageID key in the database with the key of a message before the missed ones.
Also, increasing the limit to more than 99 could help in some cases.

OR

3. Load history back to <date> with user-selectable date?

What do you developers think about this?
 

Offline ghazan

Re: Facebook protocol
« Reply #800 on: 28 10 2019, 20:12:09 »
First of all, I think that this protocol plugin is dead, cause it still causes account lockouts , so its further development doesn't look promising.

Second, all histories are retrieved and recorded using server-side message ids, so in theory it doesn't matter how Miranda loads unread histories. Right now Miranda stores last server id retrieved and tries to load everything else since that message id. I wonder how this mechanism could fail