Relates to T5246.
In Slack you can set up integrations which will post messages and notifications to channels when things happen; i.e. when someone closes a JIRA task it'll post a message saying that a task was closed. Of course in this case it would be Maniphest, but it's a similar concept.
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T7569 Support Feed/Notifications in Conpherence | ||
| Duplicate | None | T5247 Allow Conpherence channels to be registered for notifications |
I can see why Slack has such a feature (though I am skeptical of the usefulness), but not clear to me why Phabricator (Conpherence) would given overlap in all the other notification channels. I would assume anyone wanting this information to just set up a Dashboard? Is there a problem we can instead solve with Dashboards we're not currently?
The use case tends to be when you're communicating with someone on a topic about work you're doing, usually something like:
chad: blah blah blah
hach-que: i've pushed my changes
hach-que: blah blah blah
Harbormaster: @hach-que Harbormaster build failed of commit rT37b7d9abc "Some changes I just pushed"
I'd imagine dashboards to be less accessible if you're on a mobile device (I'm presuming at some point Conpherence might have a mobile app or something for communication as the web browser on mobile devices isn't the best for real-time communications and doesn't deal with offline notifications, etc).
I could maybe imagine binding Conpherence threads to projects, and then pulling in project events or something like that.
I'm not sure how else this would work, offhand:
Even at our small scale, I think the feed notification handler in Phabricator was a spammy mess. This generally feels very redundant with real-time notifications, if we imagine a future world where most users have a browser window open most of the time to be in a Conpherence room.
I don't think this is technically difficult, I just worry it leads toward a product where you get two copies of every notification.
I could maybe imagine binding Conpherence threads to projects, and then pulling in project events or something like that.
That seems reasonable and makes sense to me. Basically each project would have a Conpherence thread which any member of the project could post to and where project-related notifications would be posted.
I don't think this is technically difficult, I just worry it leads toward a product where you get two copies of every notification.
I'd imagine this being much more useful when people are using Conpherence as a real-time messaging system. I don't think this is a very near future use case, given that that's dependent on real-time notifications. I do think that there are different contexts; e.g. leaving a messaging system like Conpherence open in the background vs. checking Phabricator every now and then.
I'm just going to merge this up into T7569, this doesn't have much of specific interest outside that task.