-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shared roster groups #63
Comments
This issue will be closed within two weeks if the requested reproduction data is not provided. Please refer to this guide. |
Thanks @poVoq unfortunately, I'm not using eJabberd and the staging setup is based on Prosody, can you provide a |
An example for Prosody is in the original post. Prosody's support is much more limited, but you can make a |
Seriously, I don't want to spend my free time trying to figure out how to reproduce setup. I have already spent time to make a detailed procedure, and and no one cares... WHAT IS NOT CLEAR? |
Bad idea. As a user can be in more than one group, it will be too long. |
Sure, was just an idea. Thanks for looking into it! |
When I said "Bad idea", it was my UI proposal I was talking about 😉 |
Your second example is how ConverseJS does it. To me that seems like a good way to do it. |
Great! I let it as pull request for now, if you want some UI tweaks, let me know. |
ejabberd and prosody (via https://prosody.im/doc/modules/mod_groups) support configuring shared nested roster groups and it would be nice if the UI would support this by showing the roster categories as groups of contacts.
As xmpp-web doesn't do contact management by itself (for now?) I think this would be used often by linking these groups to LDAP for example.
The text was updated successfully, but these errors were encountered: