Reformulate
This commit is contained in:
parent
f77a8dcacf
commit
d85e5c12ca
1 changed files with 5 additions and 3 deletions
|
@ -83,7 +83,8 @@ attempts quite rapidly. To bypass this issue, the Messenger backend provides the
|
|||
using a *client pickle*, i.e. a serialized client that contains all of the cookies obtained during a single
|
||||
initial login procedure, so that further logins are not required any longer.
|
||||
|
||||
To generate your client pickle, run the following command:
|
||||
To use this method, *do not enter your password in Easybridge when configuring the Messenger backend*.
|
||||
Generate your client pickle by running the following command:
|
||||
|
||||
```
|
||||
./external/messenger.py create_client_pickle
|
||||
|
@ -91,6 +92,7 @@ To generate your client pickle, run the following command:
|
|||
|
||||
This procedure will ask for your email and password and attempt to log you in to Facebook.
|
||||
If it succeeds, it will print several dozen lines of data looking like `eJyVVlt....X9cgyfgY7mJaK`.
|
||||
Then, when configuring the Messenger backend in Easybridge, *do not enter your password*.
|
||||
Instead, enter the obtained client pickle string in the appropriate field.
|
||||
Then, when configuring the Messenger backend in Easybridge,
|
||||
instead of entering your password,
|
||||
enter the obtained client pickle string in the appropriate field.
|
||||
|
||||
|
|
Loading…
Reference in a new issue