Skip to content
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

IRC support #104

Open
hannesm opened this issue Nov 3, 2015 · 8 comments
Open

IRC support #104

hannesm opened this issue Nov 3, 2015 · 8 comments

Comments

@hannesm
Copy link
Owner

@hannesm hannesm commented Nov 3, 2015

would be great... now that multi-user chat is there... maybe using https://github.com/johnelse/ocaml-irc-client is sensible?

@sternenseemann
Copy link
Contributor

@sternenseemann sternenseemann commented Nov 3, 2015

You mean IRC support within a jabber client?

I don't know if this is beyond scope. On the other hand that would mean hassle-free OTR for IRC queries…

@hannesm
Copy link
Owner Author

@hannesm hannesm commented Nov 3, 2015

well, apart from XMPP I do use IRC (and am not too happy with my current client), and certainly abstracting over the underlying protocol would help to cleanup code..

@sternenseemann
Copy link
Contributor

@sternenseemann sternenseemann commented Nov 3, 2015

Why not then?

@cfcs
Copy link

@cfcs cfcs commented Nov 5, 2015

Hm. I thought everyone was supposed to move to XMPP and just use IRC bridges/transports? :-(

On the other hand I don't see people moving away from IRC any time soon, so why not.
Perhaps we should move to the clean React style first, or in the process of implementing this.
IRC would also require more UI things, so having the new UI lib in place before spending time on this would also be good.

@sternenseemann
Copy link
Contributor

@sternenseemann sternenseemann commented Nov 5, 2015

I don't see why anybody would quit using IRC. It does not require an account and MUC is a hassle, also there's no such thing as bouncers or anything for XMPP MUC.

@hannesm
Copy link
Owner Author

@hannesm hannesm commented Nov 5, 2015

@cfcs yep, definitively something for the rather far future (first, get the XMPP support up to speed)...

@lukasepple you don't need bouncers since XMPP provides server-side logging which a client can request..

@sternenseemann
Copy link
Contributor

@sternenseemann sternenseemann commented Nov 5, 2015

@hannesm all of the backlog? Found that feature implemented rather poorly in xmpp clients.

@hannesm
Copy link
Owner Author

@hannesm hannesm commented Nov 5, 2015

I don't know server implementations, but at least in the "specification" there's no limit https://xmpp.org/extensions/xep-0045.html#enter-managehistory

client implementation, such as jackline, are currently poor (jackline specifically because I rarely use multi-user chat and am not aware about which server supports which strategy; and what a user interface should be (automated pulling, manual request via command, ...) [unfortunately also currently busy with other things]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.