Dispatch: web-based IRC client in Go
github.com
github.com
https://github.com/thelounge/thelounge
It's a node based IRC client you can install on a server and then connect to with a web browser.
It essentially turns IRC into slack/irc cloud, it has inline images/video, URL prefetching, push notifications, themes and custom css, mobile support, and allows you to idle indefinitely persisting your connection to your favorite channels across numerous devices. You can even hook it into active directory if you wanted.
And the bit you fail to mention is that the client naturally adapts and works great on a phone. So the same chat logs and interface and channels go with me in my pocket.
Does an IRC client/webserver really need several hundred megabytes of ram? I then began just tunnelling hexchat. Only needed to bypass a firewall for irc
Two things I really missed from MacOS that I thought didn't have a good alternative in Linux were Colloquy and Sequel Pro.
The Lounge via Docker Container and https://applicationize.me/ :
docker run --detach \
--name thelounge \
--publish 9100:9000 \
--volume ~/.config/thelounge:/home/lounge/data \
--env THELOUNGE_HOME=/home/lounge/data \
--restart always \
-u "$(id -u $USER):$(id -g $USER)" \
thelounge/lounge:latest
solved my IRC itch, and it works even better than Colloquy.Still haven't found anything that comes close to Sequel Pro, though.
thelounge start
Welcome to modern js development.
* Colored nick-names
* Theme-ability, even if only through user-provided CSS overrides
* Nickname autocompletion when hitting tab, preferably with some logic such as "you talked to this user recently"
* A locked down mode in which only authorised users can connect
That said, I really like the fact that you can search the history right from the client. Since I am not using this in production, maybe someone with more experience can tell me about how well it scales?
Also I feel that the separation of channels and DMs with users is very sensible.
I personally use The Lounge (https://github.com/thelounge/thelounge) for my web IRC needs, which solves my main issues outlined above, but doesn't have searchable history nor separated users and channels (there might be a setting for this that I haven't found yet).
Yes it does: https://thelounge.chat/docs/server/users.html
If that's not enough, I'm sure you could write some CSS to make the difference stand out even further. There's a custom CSS box in settings that you can put your styles in easily.
By visual separation I meant for example a vertical line with all channels being above that line and all users below it. I realize I can rearrange them manually, but I frequently join/quit channels and message new users in some networks and have that happen automatically would be a "nice to have" feature for me.
Clearly this didn't bother me enough to actually implement it or even open an issue with a feature request, so please do take this with a grain of salt.
Thank you for working on this awesome project and responding to my feedback!
I realize I can achieve this by hand, but I frequently join/leave channels and open new DMs and it would just be a nice to have thing for it to happen automatically.
So far it hasn't bothered me enough to actually open a feature request, so take this with a grain of salt.
Conversations need to be able to referenced. Getting some logbot + archive going is way too painful.
The SSL checkbox shows up as two checkboxes (one regular, one fancy), the regular one way out in the middle of nowhere:
https://i.imgur.com/tFqN4HK.png
If you don't have a large monitor to test it on, you can use Chrome's dev tools to emulate a higher resolution.
My dotfiles are really disorganized, but here's my polybar config which I copied from some reddit post:
https://github.com/veggiedefender/dotfiles/blob/master/polyb...
You'll need fontawesome 4 and material icons
I'm often a little baffled when I try to get help with a project and it doesn't have a chan on Freenode!
Finally the language affects deployment. Given that it is Go I know it will be trivial to cross-compile a static binary.
Attracting contributors who are familiar with the language might be one of the reasons?