Please see https://github.com/TkTech/notifico/issues/79
* > There is a difference between a NOTICE to a channel and a NOTICE to a user, every client should be able to correctly display notices to a channel. ~~ @Dav1dde
* > They should, but they don't. ~~ @Mkaysi
* > That's besides the point. There are a lot of clients that do handle it properly, and if they don't then that's not notifico's fault, that's their own fault. ~~ @sckasturi
* This is default behaviour with ZNC and some other IRC related applications.
* Users are often confused when the logs don't appear.
* The logs will less likely get lost if they are written immediately.
* Gribble is doing this too (but not by default).
The old format also included useless nick. I don't know anyone who has used the default meaning it and it annoys people and it just annoyed me.
> XX:XX:XX -: blah blah blaa (Mikaela)
private: False
* If #653 gets done, notices are much more easier to lose.
tellOnJoin: False
* Many people are using bouncers or running their IRC clients on 24/7 up server, so in many cases joins don't tell anything on are people really present, so it's better to just wait for them to say something.
Enable colours: most of people want them and they are supported by
all IRC clients used nowadays.
Show hostmask: that is standard behaviour of relaybots which I am seeing.
Punish other relaybots: Does this even need explaining? "Let 2009-11-24 <http://echelog.com/logs/browse/supybot/1259017200> be a lesson to you: turn *on* supybot.plugins.Relay.punishOtherRelayBots."
Don't join on all networks: I think that people mostly want to relay
specific networks, not all of them. This is also a method to evade
limitation of LinkRelay ( ProgVal/Supybot-plugins#11 ).
Use notices with nonprivmsgs: This is also standard behaviour and makes
it easier to see the difference between PRIVMSGs and everything else.
