"You are about to publish an event signed by [Flowey]. You are currently logged in as [�����] Are you sure?"
Is this a @Keychat issue or a problem with logging in with NIP-07 on multiple accounts within the same client?
In older versions of Keychat, users had to log out from the virtual Home button before they could sign in with a new ID. In the current Keychat, you can simply log out directly inside a Mini App — no need to log out from the Home button first.
However, using **Jumble** as an example: if a user signs in with multiple IDs inside Jumble and then switches IDs within Jumble, the error you encountered will appear. **NIP-07 was never designed with multi-ID support in mind**, so this issue shows up. We’re now reaching out to the Jumble team about it.
Yes, I like the current method because it allows me to log into another account without having to log out of the first one, but it's confusing to be logged into one account and have a subscription to another.
If the client passes the pubkey when calling signEvent, the signer should be able to tell which account the client wants to use. Seems like an easy approach that doesn’t break the current spec.