First of all: the new bridge function is really awesome!! I have successfully tested it with XMPP. Connecting to Nextcloud Talk with my XMPP clients is my big vision :smile:
For daily routine, I think it would be helpful if messages in Nextcloud Talk wouldn't appear as from the bridge bot and prefixed with "protocol ", but as from the user itself (if such a mapping exists).
This would also allow to reply to the correct user instead of the bot.
Possible solution: If a user has configured their XMPP id (JID) in their personal talk_matterbridge settings, XMPP messages from this JID shouldn't be posted from the bot with "xmpp jid@example.com" prefix, but from the specific user without any prefix.
Possible security implication: If someone enters the JID of someone else, it would be possible to impersonate the other user in the chat. So maybe the JID should be verified; or the mapping could be set system-wide by admin for the beginning?
Work is currently going on for this here: https://github.com/nextcloud/spreed/pull/5667
Oh whoops, you meant on the sending side. That would be a change in matterbridge, not our implementation of it.
First of all: the new bridge function is really awesome!! I have successfully tested it with XMPP. Connecting to Nextcloud Talk with my XMPP clients is my big vision :smile:
For daily routine, I think it would be helpful if messages in Nextcloud Talk wouldn't appear as from the bridge bot and prefixed with "protocol" , but as from the user itself (if such a mapping exists).
This would also allow to reply to the correct user instead of the bot.
Possible solution: If a user has configured their XMPP id (JID) in their personal talk_matterbridge settings, XMPP messages from this JID shouldn't be posted from the bot with "xmpp jid@example.com" prefix, but from the specific user without any prefix.
Possible security implication: If someone enters the JID of someone else, it would be possible to impersonate the other user in the chat. So maybe the JID should be verified; or the mapping could be set system-wide by admin for the beginning?