Template talk:Echo

1x
Extension Echo's name refers to its ability to link "event" to "involved user" by notification. The involved user gets an echo of the event. It is neither misnamed, nor confusing to the other extensions that use extension Echo.

But surely template Echo has gone too far here, because template names are both a function-indicating, like any intuitive keyword, and their pagenames. Let's not conflate echo-functionality with echo-naming in this widely disparate way — Template Echo's functionality with the naming choice of an extension, named by programmers on the software project, about "events" (not "content" of its parameter one).

{ {for | echo functionality | Template: 1x }} should not have to hatnote T:Reply/doc, but it should hatnote it. No?

. Nobody in the last 4 mos since the re-purposing discussion, since the 30 pp-of-use cleanup, is using it to {{template:reply to} }

I would vote to reserve the purpose of "echo"
 * as a template learning tool
 * extended variously? (to document markup?)
 * the Echo (command) way!
 * the MediaWiki way: &mdash;  Cp i r al &sect; Cpiral  02:47, 2 January 2017 (UTC)