We currently don't in the plugin template. The downside with using one is that it would mean that the timerpoke event handler would have to be separate from the other event handlers (which means an additional function call). Either way we need to deregister from the timer to avoid a timerpoke.wb event for the selector being fired every 0.5 seconds (otherwise it would hurt performance).

I guess it is more of question of what has the greater performance cost:

Status quo: Continue to use "on" for "timerpoke.wb".
* Pro: Can be combined with other events to save a function call.
* Con: Handler is still attached so don't know if there is any performance impact for an unused event + selector (impact will not be felt on initial load)

Change: Switch from "one" to "on" for "timerpoke.wb":
* Pro: Plugin no longer listens for timerpoke.wb after the first event (don't know if that means any performance savings)
* Con: Requires "timerpoke.wb" to be split off into a separate "one" function which is known to have a performance impact (has an impact on initial load and it takes some cycles to remove the handler)

So I guess it depends upon whether leaving an unused handler in place has more negative impact than splitting off a new function. I suspect that the status quo would have better performance because there are less tasks involved, or at least it would have the least amount of impact on the initial load (although I have no evidence to back up my suspicion).