@blockchainstudio, thanks for the great feedback.
We will look into making your authorised account default on first sign-in, whew, so much to do still!
Regarding the Keychain request it is unlikely to change in the short-term Tokenbb is geared towards ease of use for our users, things should just work. Keychain would introduce subtle problems we can't mitigate in our own backend, retries, co-ordination with our database and even policing beneficiary reward status.
Witness of the people, by the people, for the peopleHi @thecryptodrive, thanks for your reply! Not many PO reply to users feedback sadly :) I actually didn't know you're in this project. To be honest, I always wonder why thecryptodrive is on the top witness list, now the mystery is resolved. If you haven't seen, you may find interest in my recent post:
ps. Regarding your answer, I got it if you need it in your backend. But I still don't understand why that backend logic is needed, maybe some efficiency? For instance, to me so far, steempeak works quite seamlessly with keychain without posting right authorization. I has retry feature for instance. While I agree that steemconnect style's posting right authorization has been a dominant way, but unless it's absolutely needed (e.g., voting automation, scheduled post), that should be avoided.
Anyway, tokenbb is actually very awesome project, and I'll try to contribute on GH too. Thanks!