Echo notifications at the moment can be sent as "web" (personal bar icons) and "email".
It would be nice to add a way to send a notification using Telegram.
At the moment it will be particularly useful for the Telegram bot at translatewiki (see T131664 and T62904), but can also be used for other things.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| WIP Sending notifications to telegram. | mediawiki/extensions/Echo | master | +80 -6 |
If this is absolutely needed, it should be an external tool that gets Echo notifications from MediaWiki API (if that is possible). It would be a bad idea to add an integration to an external proprietary service from MediaWiki. (This is not clear enough in the task.)
It should not be the only or even the primary way to get notifications, of course. It is needed for a project like T131664, where using Telegram is the whole point. Maybe in the future it can become an option for other kinds of notifications—but only an option.
it should be an external tool that gets Echo notifications from MediaWiki API (if that is possible). It would be a bad idea to add an integration to an external proprietary service from MediaWiki. (This is not clear enough in the task.)
Yes, that's more or less what it will be. MediaWiki will raise a minimal generic notification, and a hook in an external tool will take care of the rest.
It is comparable to IRC notifications, which were made long before Echo was around. Ideally, they should be converted to Echo, too.
Change 433995 had a related patch set uploaded (by Catrope; owner: Anna.d92):
[mediawiki/extensions/Echo@master] WIP Sending notifications to telegram.
I am going to raise a slightly philosophical point, so bear with me, and let's discuss a bit.
I think sending notifications to Telegram is awesome, but I would be more comfortable with a fix to Echo if it was more generalized. That is, we'd like to send to Telegram today -- but tomorrow, we might want to add IRC notifications, or Discord notifications, or hook it up to some other service.
I'd be more comfortable if we try to think about how to generalize this inside Echo so that the first iteration -- sending to Telegram -- uses some framework that also allows, in the future, to send to another service if/when needed. I think having a Telegram-specific code in Echo is not ideal at all given that.
We can see if this is possible using some hooks, similar to how GitHub allows for spreading its notifications through multiple services -- and then allow external tools or extensions to "hook up" to this method and utilize it.
@Catrope I'd love your input on this.