31–40 of 55 posts
Reminds me of http://quassel-irc.org/ which is not really a beauty but is working good enough for me at the moment. (I'm just a user, not related to the project in any way)
Reminds me of http://quassel-irc.org/ which is not really a beauty but is working good enough for me at the moment. (I'm just a user, not related to the project in any way)
http://bugs.quassel-irc.org/projects/1/wiki/Stylesheet_Galle...
I use DarkMonokai: https://gist.githubusercontent.com/Zren/2779042/raw/DarkMono...
The default is not pretty ugly though, I agree.
Does anyone know how this compares to WebIRC [0]? [0] https://github.com/pavben/WebIRC
Earlier quoted context omitted.
And https://www.irccloud.com One obvious difference is that IRCAnywhere is a discontinued product!
Another is that irccloud is not free!
Earlier quoted context omitted.
Personally I run weechat on a small home server I have and run it in tmux and just ssh into it.
I run it on a small dedicated server (kimsufi) in tmux. But instead of sshing into that, I connect to it with Glowing Bear which feels much nicer to me. I also like the mobile support (I use it a lot on my Android phone and my iPad). For Android, we even have a "native" app (using cordova). It's very convenient to have IRC on the go, with synced read marker states and a pleasant interface.
Why doesn't the project owner look to pass it onto a new maintainer to move it forward?
Earlier quoted context omitted.
Another is that irccloud is not free!
well, there's a free tier that lets you keep 2 connections + irccloud's server. you just have to keep a web browser open somewhere to avoid the 2 hour timeout. but yea ive always felt their $5 / month plan was a little overpriced. for mobile irccloud's app is fantastic. i dont know if any of these solutions mentioned here even has one
Someone learned their business model from 90's shareware. :)
I am all for using an open source alternative to Slack. But IRC is not it. What we need is a modern, open standard for persistent group chat ala Slack, with security features. I am not saying sit down and draft papers, writing code that can become a standard is fine. Maybe Mattermost is it, I don't know.
Totally relevant to this post.
Why doesn't the project owner look to pass it onto a new maintainer to move it forward?
This was previously discussed in the IRC Channel on Freenode. None of the people that have contributed have shown interest in taking over the project. And the majority of the community we have don't know their way around JS/Node outside of installing it on their server.