scenario: albert types /invite bonnie charles david

method 1: always assume last argument is a room

if room david exists,
then bonnie and charles are invited to room david

if room david does not exist,
then albert is told "unable to find room david"

method 2: check to see if every argument is a user

if user david exists,
then albert is told "invite them to which room?"

if user david does not exist, and room david exists, 
then bonnie and charles are invited to room david

if user david does not exist, and room david does not exist,
then albert is told "unable to find room david"

Neither method is perfect, since with multiple users that last parameter is awfully ambiguous. But I believe method 2 is perhaps more insightful in its error messages.

But I can think of one way to make this multi-user-invite completely un-ambiguous, and that would be to require the # in front of the room name.

So when albert types "/invite bonnie charles david" the system will correctly respond "invite them to which room?", regardless of the existence of user david or room david.

The correct usage of the invite command would then be, "/invite bonnie charles david #abcd".

This is consistent with how roomnames are displayed throught Jabbr - however it represents a big change in the invite command.

Thoughts?