-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
More subtle join/leave messages #906
Comments
I like this idea. I just change timestamp to before the name. |
👍 |
@AdrianoCahete That was what I had in mind at first, but my concern is that it makes it harder to 'scan' over the names in chat and find somebody in particular, as the nicknames for messages are at a different (horizontal) position than those for joins. I'm not really sure which solution is better, or how much this would matter. |
Definitely an @rcaferati UX issue. Perhaps even 'bubble burst animated away' after a minute, collapsing other message flows? Kinda like some Vegas / Monte Carlo slot machines. |
👍 |
I think a very simliar style was proposed for /me |
@geekgonecrazy IMO |
@nahtnam problem with that is its exactly the same as _ message _ IRC would be the inspiration :) That's where it came from :) |
? |
Related to #661 |
you can see it working at https://threads-qa.rocket.chat |
A small UX proposal. Right now, the join/leave messages are taking up a ton of space in the room, making it hard to follow conversation over a longer period of time.
My proposal would be to make join/leave messages into smaller, 'inline' messages instead, like this:
This would make it easier to 'scan' over them while following a conversation. On multiple subsequent joins/leaves, they could be grouped together with less margin inbetween, like this:
The exact spacing inbetween entries would be up for discussion of course, but as a general proposal. I think it'd really help to focus more on the conversation, rather than on room state.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: