mirror of
https://github.com/42wim/matterbridge
synced 2024-11-07 09:20:23 +00:00
.. | ||
.travis.yml | ||
builtin.go | ||
cap_sasl.go | ||
cap_tags.go | ||
cap.go | ||
client.go | ||
commands.go | ||
conn.go | ||
constants.go | ||
CONTRIBUTING.md | ||
ctcp.go | ||
doc.go | ||
event.go | ||
format.go | ||
handler.go | ||
LICENSE | ||
modes.go | ||
README.md | ||
state.go |
girc, a flexible IRC library for Go
Status
girc is fairly close to marking the 1.0.0 endpoint, which will be tagged as necessary, so you will be able to use this with care knowing the specific tag you're using won't have breaking changes
Features
- Focuses on simplicity, yet tries to still be flexible.
- Only requires standard library packages
- Event based triggering/responses (example, and CTCP too!)
- Documentation is mostly complete.
- Support for almost all of the IRCv3 spec.
- SASL Auth (currently only
PLAIN
andEXTERNAL
is support by default, however you can simply implementSASLMech
yourself to support additional mechanisms.) - Message tags (things like
account-tag
on by default) account-notify
,away-notify
,chghost
,extended-join
, etc -- all handled seemlessly (cap.go for more info).
- SASL Auth (currently only
- Channel and user tracking. Easily find what users are in a channel, if a user is away, or if they are authenticated (if the server supports it!)
- Client state/capability tracking. Easy methods to access capability data (LookupChannel, LookupUser, GetServerOption (ISUPPORT), etc.)
- Built-in support for things you would commonly have to implement yourself.
- Nick collision detection and prevention (also see Config.HandleNickCollide.)
- Event/message rate limiting.
- Channel, nick, and user validation methods (IsValidChannel, IsValidNick, etc.)
- CTCP handling and auto-responses (CTCP)
- And more!
Installing
$ go get -u github.com/lrstanley/girc
Examples
See the examples within the documentation for real-world usecases. Here are a few real-world usecases/examples/projects which utilize girc:
Project | Description |
---|---|
nagios-check-ircd | Nagios utility for monitoring the health of an ircd |
nagios-notify-irc | Nagios utility for sending alerts to one or many channels/networks |
matterbridge | bridge between mattermost, IRC, slack, discord (and many others) with REST API |
Working on a project and want to add it to the list? Submit a pull request!
Contributing
Please review the CONTRIBUTING doc for submitting issues/a guide on submitting pull requests and helping out.
License
Copyright (c) 2016 Liam Stanley <me@liamstanley.io>
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
girc artwork licensed under CC 3.0 based on Renee French under Creative Commons 3.0 Attributions.
References
- IRCv3: Specification Docs
- IRCv3: Specification Repo
- IRCv3 Capability Registry
- ISUPPORT Specification Docs (alternative 1, alternative 2, relevant draft)
- IRC Numerics List
- Extended WHO (also known as WHOX)
- RFC1459: Internet Relay Chat Protocol
- RFC2812: Internet Relay Chat: Client Protocol
- RFC2813: Internet Relay Chat: Server Protocol
- RFC7194: Default Port for Internet Relay Chat (IRC) via TLS/SSL
- RFC4422: Simple Authentication and Security Layer (SASL EXTERNAL)
- RFC4616: The PLAIN SASL Mechanism