You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in accounts.xml to sign in. Actually the only way I found to do this is manually editing the file on the server so at the moment two-factor users can not register to the transport.
Possible solutions I thought of:
add a form that picks the value of this field on the registration screen (would this be client indipendent? does it break transport standard?)
add the capacity to edit accounts.xml for purple backend in settingsadhoccommand.cpp
adding support for "purple request API", so that we can use normal telegram-purple solution.way of retrieving the password.
adding an exception in telegram-purple for clients not supporting "purple request API" not only for request_code but also for two auth password.
The text was updated successfully, but these errors were encountered:
When two-factor auth is activated,
telegram-purple
needsin
accounts.xml
to sign in. Actually the only way I found to do this is manually editing the file on the server so at the moment two-factor users can not register to the transport.Possible solutions I thought of:
settingsadhoccommand.cpp
telegram-purple
solution.way of retrieving the password.The text was updated successfully, but these errors were encountered: