Hello @maxberger I've been checking your latest commits and have verified that it is correct. The device ID is added. However, right now, the only way to verify the bot is by opening two external sessions and verifying them manually. However, over time, errors such as WRN Failed to verify self-signing signature error="invalid signature" and WRN One-time key has invalid signature from device are received in the log, and also if u doing that when receive a notification every minute appears more errors.
According to the Mautrix Go documentation, would it be possible to implement SAS verification to be able to verify the bot by emojis, for example, and thus verify the bot?
Thanks 😉
Hello @maxberger I've been checking your latest commits and have verified that it is correct. The device ID is added. However, right now, the only way to verify the bot is by opening two external sessions and verifying them manually. However, over time, errors such as WRN Failed to verify self-signing signature error="invalid signature" and WRN One-time key has invalid signature from device are received in the log, and also if u doing that when receive a notification every minute appears more errors.
According to the Mautrix Go documentation, would it be possible to implement SAS verification to be able to verify the bot by emojis, for example, and thus verify the bot?
Thanks 😉