-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Would like to use ircdjs as a library; thoughts? #85
Comments
Hi, Can you give me an example of what are you trying to accomplish? |
That is what I had in mind, yes.
:(
I’d like to, for example, have a callback for when the client connects or, really, does anything, to verify that what I’m telling node-irc to do actually happens. But it sounds like this isn’t something that you’d be interested in supporting, unless I’m misreading? |
I'm interested in using ircd as a library. I know nothing about IRC, @sespindola why is a standard compliant ircd incompatible with being used programmatically? |
@sonnyp I don't think the point was that a standards compliant ircd is incompatible with programmatic use, but rather that ircd.js wasn't designed that way and thus doesn't support it. |
@apeiron got it, thanks |
Using ircd as a library would be pretty cool for adding IRC support for existing chat systems such as let's chat. Some websites like Ustream and I think Twitch allow IRC clients to access their chat and it's pretty useful. Another usecase are custom server extensions in similar to ChanServ. node-xmpp-server is a pretty similar project that supports being used as a library maybe you could adapt some of their project structure. |
Hi there! I just stepped up as a collaborator on irc.js and we are looking for an easy way to test that library. "Hey, let's look for an ircd written in node!" I thought, and I found ircdjs. Unfortunately, it doesn't appear that it was written with library usage in mind--there are no callbacks, there's no support for interacting with clients programmatically. I would like to extend ircdjs to support these use cases so we can test our code. If you'll accept pull reqs for this, I'm fine writing patches that do what I need. Thoughts?
The text was updated successfully, but these errors were encountered: