When we start excluding unsigned devices then all users in a room, including bots, will need to verify their devices.
Some bots, e.g. mjolnir don't currently provide a way to verify their devices, and the underlying matrix-bot-sdk does not provide a way of doing this. The preferred way would be to supply a Recovery Key during bot setup, but without support in matrix-bot-sdk this would be quite a lot of development work to do.
So, we want an easier way of manually asserting that a device is verified. We think the simplest way would be for the bot to print out its ed25519 key on startup, so we can supply it to another client.
In Element Web, provide a dialog (probably in an "Advanced" section) that allows pasting in a client's ed25519 key to verify it.
When we start excluding unsigned devices then all users in a room, including bots, will need to verify their devices.
Some bots, e.g. mjolnir don't currently provide a way to verify their devices, and the underlying matrix-bot-sdk does not provide a way of doing this. The preferred way would be to supply a Recovery Key during bot setup, but without support in matrix-bot-sdk this would be quite a lot of development work to do.
So, we want an easier way of manually asserting that a device is verified. We think the simplest way would be for the bot to print out its ed25519 key on startup, so we can supply it to another client.
In Element Web, provide a dialog (probably in an "Advanced" section) that allows pasting in a client's ed25519 key to verify it.