Open 14mRh4X0r opened 9 years ago
There's deeper places that this should be handled.
Notably, pIRCbot is hard-coded to say that v
means +
and o
means @
.
Second quick check: how well does the IETF document line up with http://www.irc.org/tech_docs/005.html ?
I'll update this pull request later with an implementation on a deeper level. The IETF document matches the irc.org doc as far as I can tell, but the latter does provide more information about real-world implementations.
I'd like IRCService to be able to tell what the ISUPPORT blocks state. This way, we can strip out the nick prefixes (and handle things like the absolutely strange $foo channel type that I encountered)
As my local version is now, PircBot has a Map<String, String> getISupport()
. It requires more rewriting than I anticipated.
Also stores the ISUPPORT parameters in an easily accessible HashMap and fixes a slight parsing bug with IRCv3 message tags