Wasn't the name "multisend" picked due to proposed feature to perform multiple s4c ? (More than 2).
David, correct me if I am wrong on this.
Also, I think "reaccuring" is only the nature of the function and should be undertood and expected by user, as it would continue to preform a set function untill changed by user again.
multisend was just a temporary name. Of course, we all know what happens to code name... they stick
multisend is an improvement of the current S4C but from the beginning, I named the whole thing
HyperSend, S4C being just a subset.
That being said, both multisend and recurringsend are correct: You can can to several persons at once and you can send in an automated way.
HyperSend
HyperSend is a generalization of the idea that first came up with Stake for Charity. [...] This can be used for a variety of purposes:
The above-mentioned well-known Stake for Charity.
[other examples]
So, just sticking to the original name HyperSend would make the most sense. multisending is just the latest improvement. Granted, we lose the "immediate understanding" of "recurring send" but we stay on the marque thing with "Hyper-*". as iantunc said, a "Feature name".
RecurringSend
Multisend
HyperSend - I vote for this one
