Conversations: MUC - Invitations process

Created on 16 Aug 2014  路  5Comments  路  Source: iNPUTmice/Conversations

If I invite someone (conversations users) to a conference they get joined to the channel without confirmation or even a notification on their side. They see this new conference only by - accidentially - looking at the list and cannot decline to join.

Is this the desired behaviour or is there something wrong on our side/server?

Most helpful comment

Besides of the UX problem where people don't notice they are in a group chat now, this also has security implications:

  • you can see the user's presence in the MUC
  • you can see the user's full JID if you are a room admin
  • you can send IQs to the user's client

It would be better to limit the auto-join in two ways:

  1. Only automatically follow invitations from people subscribed to your presence (that requires 'direct' as opposed to 'mediated' invitations)
  2. Only auto-join non-public rooms (not sure how to best implement this)

All 5 comments

This is expected behaviour. The reasoning behind is that I want to treat one-on-one conversations and conference-conversations as equal as possible. And one-on-one conversations will also pop-up or open without the user accepting them first.

Okay. What about a single notification when a new conference was joined? Otherwise users have to know that they need to highlight new users in the channel to trigger their attention.

On 16. August 2014 09:53:33 MESZ, Daniel Gultsch [email protected] wrote:

This is expected behaviour. The reasoning behind is that I want to
treat one-on-one conversations and conference-conversations as equal as
possible. And one-on-one conversations will also pop-up or open without
the user accepting them first.


Reply to this email directly or view it on GitHub:
https://github.com/siacs/Conversations/issues/358#issuecomment-52386789

There is one readon why you would want to avoid that behavour:
Someone challenges you, and your answer does go to him plus a bunch of other recipients - and suddenly you regret not having checked the audience first.

I think the code handling the messages schould be the same, but the UI must show the user clearly whom he is dealing with.

Besides of the UX problem where people don't notice they are in a group chat now, this also has security implications:

  • you can see the user's presence in the MUC
  • you can see the user's full JID if you are a room admin
  • you can send IQs to the user's client

It would be better to limit the auto-join in two ways:

  1. Only automatically follow invitations from people subscribed to your presence (that requires 'direct' as opposed to 'mediated' invitations)
  2. Only auto-join non-public rooms (not sure how to best implement this)

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

devurandom picture devurandom  路  3Comments

benjaminbischoff picture benjaminbischoff  路  3Comments

guy6498765413168978463153248 picture guy6498765413168978463153248  路  4Comments

jplitza picture jplitza  路  4Comments

andypl picture andypl  路  3Comments