This feature is currently only working for keychain users, and is not yet developed for HiveSigner users
I'm curious, what's the difference? I mean, what exactly makes logging in with Keychain or HiveSigner different in order to access these features?
Completely different libraries with different instantiation, file includes, operational processes like one doesn't use a browser extension, its linked out to a totally different website while the other is built into your browser via an extension. My site has to talk to them and listen to them in completely different ways. Times five for all five or so popular key management tools. Which is why Im going to swap them all out and go to AIOHA which solves that by giving MY software one tool to talk to, and users use whichever of the key services they want inside AIOHA which in turn keeps up with speaking five tools interfaces and response platforms.
For every task:
Login
Vote
Post
Comment
etc
I would have to write ALL the auths out separately, switch through them programmatically for the one the user is choosing to use, auth them, confirm stuff and then pitch the chain request in the tools preferred ingestion format and method. It sucks. See my keychain poll post for some pseudo code that explains all this visually. as well as details about what AIOHA is and how it solves it via mention of it there and in this post via its link as well.
Ah ok, I see. Well, then let's wait a bit until AIOHA is full integrated within your site and you can get rid of a lot of headaches. :)