raucao
commented
7 years ago I had another thought about this topic: we should aim for sane defaults in selecting which notifications to show in the first place, trying to maximize the signal-to-noise ratio. There are tons of notifications from just GitHub alone, and in an active project they can quickly add up and clog a channel.
It'd be trivial to implement e.g. GitHub organization webhooks ending up as content in a channel, but we need a good design first. I think it should be half-generic, half-custom.
What I mean by that is that we need a generic design for "[user/actor] [verb] [object] [repo] [...] [url]", e.g. "Garret created a new pull request in 67P/hyperchannel: https://...". But I think it should contain custom icons based on the action and/or object, like in this case an icon for pull requests. These can be the same icons across services, of course (i.e. same for GitHub, GitLab, Bitbucket and any other code/repo hosting service).
Another example would be wiki edits, like "gregkare edited page Kredits Development ("summary/description"): https://...". Or kredits actions. Or app deployes. And so on, and so forth.
I find other chat applications lacking in the customization of these messages, as they're all 100% generic, and the only differences between messages are usually user/service avatar and color strips. And maybe there's even a better approach than what I outlined. This is a greenfield issue really.