Before adding this issue, make sure you do the following to make sure this is not a duplicate:
Search through the repo's previous issues
Read through the readme at least once
Search the docs for the feature you're looking for
Just describe the feature
Is your feature request related to a problem? Please describe.
One of the biggest causes of instabilities and high consumption of RAM by the library is the synchronization of statuses posted by clients.
Messages exchanged in conversations use little RAM, as it is just text, while the statuses are all videos, therefore, a cell phone that has, for example, 5000 saved contacts, receives an avalanche of statuses as soon as it connects, throwing RAM resources there on top and consequently bringing instability to the library.
Describe the solution you'd like
It would be interesting to add an option at client startup to choose whether or not to synchronize statuses.
If you do not want to synchronize the statuses, you must make the following deletions:
As soon as you connect the chip, you should not pull the statuses during the initial synchronization;
When the chip is already connected, it should not receive the new statuses that contacts are posting;
It is important to maintain synchronization of the statuses that are posted by the connected device, because if a contact responds to that status, and it is not synchronized in the library, it will not be possible to link that the message received is the response to a status.
Describe alternatives you've considered
It is necessary to follow the criteria stated above.
Additional context
In another library, this mechanism was implemented to suppress the receipt of status from contacts, receiving only data relating to messages responded to statuses forwarded by the connected number.
Before adding this issue, make sure you do the following to make sure this is not a duplicate:
Just describe the feature
Is your feature request related to a problem? Please describe. One of the biggest causes of instabilities and high consumption of RAM by the library is the synchronization of statuses posted by clients.
Messages exchanged in conversations use little RAM, as it is just text, while the statuses are all videos, therefore, a cell phone that has, for example, 5000 saved contacts, receives an avalanche of statuses as soon as it connects, throwing RAM resources there on top and consequently bringing instability to the library.
Describe the solution you'd like It would be interesting to add an option at client startup to choose whether or not to synchronize statuses.
If you do not want to synchronize the statuses, you must make the following deletions:
Describe alternatives you've considered It is necessary to follow the criteria stated above.
Additional context In another library, this mechanism was implemented to suppress the receipt of status from contacts, receiving only data relating to messages responded to statuses forwarded by the connected number.
If you want to consult, the activity is at this link: https://github.com/wppconnect-team/wa-js/issues/981