Is your feature request related to a problem? Please describe.
In a very large group chat it is impractical to have /showkarma print out a list of each user with one user per line. If 1000 users each have karma then the result would be 1000 lines long and pollute too much space in the chat.
Describe the solution you'd like
After a certain number of users would be printed out, have the bot switch into an alternative publishing mode.
Potentially have the bot host the result of /showkarma on a link that users could press to see the results. Perhaps that is a static html/css file hosted in S3, or just a text dump on some website.
Describe alternatives you've considered
Being able to see /showkarma through 1 on 1 chats as in in issue #9 will somewhat alleviate the concerns. Perhaps after a certain group size users should no longer be allowed in invoke the /showkarma and instead only use /userinfo instead. Maybe instead /showkarma just does a statistical summary of the group and returns the results.
Additional context
In usability testing I've found that with small number of users /showkarma is fine but after a certain point users will become frustrated with the spam.
Is your feature request related to a problem? Please describe. In a very large group chat it is impractical to have /showkarma print out a list of each user with one user per line. If 1000 users each have karma then the result would be 1000 lines long and pollute too much space in the chat.
Describe the solution you'd like After a certain number of users would be printed out, have the bot switch into an alternative publishing mode. Potentially have the bot host the result of /showkarma on a link that users could press to see the results. Perhaps that is a static html/css file hosted in S3, or just a text dump on some website.
Describe alternatives you've considered Being able to see /showkarma through 1 on 1 chats as in in issue #9 will somewhat alleviate the concerns. Perhaps after a certain group size users should no longer be allowed in invoke the /showkarma and instead only use /userinfo instead. Maybe instead /showkarma just does a statistical summary of the group and returns the results.
Additional context In usability testing I've found that with small number of users /showkarma is fine but after a certain point users will become frustrated with the spam.