Skip to content

Improve chat experience #73

Description

@4nd3r

With many channels, things can quickly get noisy and confusing when trying to focus on a single channel or contact.

I propose a /mute command that mutes a channel at runtime (can be called in init too) and only displays its messages when it's focused on (with /to). For channels like #test, #wardriving or #bot, I don't really care what's going on most of the time. But when I do, it would be easier to quickly /to into it. Currently, I add a channel, monitor it, and then remove it again. Sure, it works, but it can be annoying - especially when I need to jump between multiple channels.

Secondly, I propose a /focus command, which works like /to but displays only the messages from that contact. Maybe having this as a configurable option for CLI behavior would be better, not sure. But I have moments when I'm in one channel and also want to monitor another, and then again I don't. Or maybe I'm overthinking. Having /mute alone would most probably already help a lot with many channels.

With these two additions, the CLI experience would be much smoother and somewhat similar to a graphical app, where it's possible to set notification levels and focus on one contact at a time.

What do you think, @fdlamotte?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions