Formalize callerid

[Mikaela]

2015-12-07 12:47:00+0200 < AttilaM> thats interesting, i think that if clients implemented callerid properly (with a gui etc) then more clients would use callerid and avoid harassment altogether
2015-12-07 12:47:13+0200 < AttilaM> which is the better solution
2015-12-07 12:47:25+0200 < AttilaM> er, more users would use callerid
2015-12-07 12:48:57+0200 < Mikaela> they won't do it unless IRCv3 requires it and there are many networks that don't support it at all. I have opened two issues about the notificatons being almost invisible so I haven't known to /accept people who I want to be able to PM me.
2015-12-07 12:49:06+0200 < AttilaM> in other words, i want to concentrate on "how to avoid harassment" not on "how to have a conversation about harassment after it happens"
2015-12-07 12:49:22+0200 < kaniini> the original problem was a certain user who used to PM people on freenode and +g themselves to avoid taking the heat back
2015-12-07 12:49:41+0200 < AttilaM> making callerid more popular helps the former goal, auto /accept etc helps the latter goal
2015-12-07 12:50:28+0200 < kaniini> both are worthwhile though
2015-12-07 12:52:54+0200 < Mikaela> Is it within the scope of IRCv3?
2015-12-07 12:53:05+0200 < AttilaM> formalizing callerid is surely within the scope of ircv3

[sdaugherty]

Possible extensions for ACCEPT

• special entry to accept from any channel op in a common channel
• special entry to accept from any user sharing a given channel

Use cases:

• Messages from channel ops frequently concern channel policy (stop pasting, or I'm going to kick you) and are unlikely to be spam.
• Users on a given channel with close friends or coworkers might want to blanket accept from anyone on that channel, without dealing with individual ACCEPTs, and still benefiting from CALLERID blocking random messages.