-
Notifications
You must be signed in to change notification settings - Fork 61
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
Distinguish between OMEMO for 1:1 and MUC #234
Comments
We could also take a lighter approach und list two tickets (one for 1:1, one for MUC) in the existing column. I am not so sure if ordinary users would really care about a more extensive feature matrix or if that is something mostly of interest to developers. |
I know what you mean, but it's highly subjective – even for "non ordinary" users. I've been using Jabber since 15 years and never had the urge or need to join a MUC 😁 As for the table, I could imagine something that hides a lot of the confusing details by default and let's you drill down into the details if you need to. |
@ritzmann would you like to create a PR? |
I can give the expandable table with CSS a try. It's quite a bit more effort than I had expected, i.e. it will take me a while. |
@ritzmann I would probably tackle this as a part of #122 via something like https://www.datatables.net, since youu want proper filtering and sorting mechanisms. I also don't want to get rid of the simple list on the home page that gives a quick overview so people aren't scared away from the full blow feature / comparison matrix. At any rate, I feel this whole discussion is better kept in the original ticket #122, so I am going to close this one. Please make sure you follow the other issue so you can participate in the discussion over there. |
I found that quite a few clients support OMEMO in 1:1 chats but not in private MUCs. That is an important criteria for me when selecting a client. Would it make sense to add another column? I could submit a pull request but would like confirmation first that I am not doing the work for naught.
The text was updated successfully, but these errors were encountered: