We've opened HB-1030 ("Making a "Session ID" available in log and via HB API, so user's know which BuddyAuth session to kill ") against this request.
Thanks a lot!
To me, its still unclear how the provided timestamp is ambiguous. Its very hard to imagine multiple bots being started within the same second, and if some were, it would not be very many. We've opened the issue, but the case is not strong, and the change control board may decide its not worth implementing or set the request to a reasonable priority, unless the argument can be made much stronger.
Specifically, having access to a session identifier within HB to compare against BuddyAuth is a critical benefit for me and hopefully many others. We've had requests for this in the general section over the years but none recently.
Regarding the timestamp on BuddyAuth, you are right, there isn't much difficulty in determining the correct session to kill when you remember the order you started them in and I wouldn't consider this a high priority but more of a convenience and usability factor. Many times I have closed the wrong session after HB or WoW crashes during a DungeonBuddy group because I wasn't sure exactly which session was tied to the one that crashed. I end up just closing all sometimes. Other times I would be in town or at work and have to close a session from my phone.
If it wasn't a security risk to include the character name & realm then that would solve all of those issues, at home or remotely. An alternative could be to use PID. Again though this isn't a considerable productivity boost like having a unique session identifier available to HB would be. Thanks again for your time.