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
Maybe I miss something, but I believe once posting key is authorized to busy.app, users should be able to login with posting key. For instance, https://steemauto.com works this way: one-time authorization with active key and then login with posting key thereafter. Once it's set up, Steemauto does voting/posting(scheduled posting) on behalf of the user even without login. I think this is a right behavior based on the name "authorization" since the user already authorized the posting right.
I'd really appreciate if someone could explain why users still need to login with active key even after authorizing the posting right. Initially I thought this is for convenience (e.g., transfer without additional active key authorization), but still I have to reauthorize for transactions that require active key.
Actual behavior
Busy requires login with active key every time.
How to reproduce
This happens all the time.
Browser: Any
Operating system: Any
The text was updated successfully, but these errors were encountered:
Expected behavior
Maybe I miss something, but I believe once posting key is authorized to busy.app, users should be able to login with posting key. For instance, https://steemauto.com works this way: one-time authorization with active key and then login with posting key thereafter. Once it's set up, Steemauto does voting/posting(scheduled posting) on behalf of the user even without login. I think this is a right behavior based on the name "authorization" since the user already authorized the posting right.
I'd really appreciate if someone could explain why users still need to login with active key even after authorizing the posting right. Initially I thought this is for convenience (e.g., transfer without additional active key authorization), but still I have to reauthorize for transactions that require active key.
Actual behavior
Busy requires login with active key every time.
How to reproduce
This happens all the time.
The text was updated successfully, but these errors were encountered: