#WEECHAT ADD SERVER HOW TO#
#WEECHAT ADD SERVER INSTALL#
#WEECHAT ADD SERVER ANDROID#
#WEECHAT ADD SERVER VERIFICATION#
#WEECHAT ADD SERVER CODE#

#WEECHAT ADD SERVER INSTALL#

To fix it, install OpenSSL using Homebrew and then fix the gnutls_ca_file using: /set _ca_file '/usr/local/etc/openssl/cert.pem'ĭisclaimer: I personally run weechat on OSX in a Docker container, so I haven’t actually tested this. Update: Twitter user pointed out that on OSX you may run into the same issue. On my shellbox, running Debian Wheezy, the following fixed it: /set _ca_file '/etc/ssl/certs/ca-certificates.crt'

#WEECHAT ADD SERVER VERIFICATION#

If, like me, you get SSL verification errors when connecting, check if gnutls is looking in the right place for the CA certificates bundle. If you have WeeChat running, enter the following to add a new server for your Slack team: /server add SOMENAME /6667 -autoconnect -ssl -password=YOURGATEWAYPASSWORD -username=YOURGATEWAYUSERNAME -nicks=YOURSLACKUSERNAME -ssl_dhkey_size=512 If the gateway has been activated, you can find your gateway credentials at. The use of SSL can also be enforced there.

These Gateways are disabled by default, but can be enabled by a Team admin at. This ofcourse means that some of the added functionality will be removed or less easy to use. This way, you can use your IRC or XMPP client of choice and just connect to Slack using that. The guys at Slack have been so kind as to acknowledge that not everyone wants to use the native app or the web version, so they are offering so-called gateways for IRC and XMPP. OK, so now we’ve established the fact that the native Slack app has a massive usability issue, let’s look at a way to solve it. If I’m in the middle of a discussion about branching models, I won’t see that builds are failing, or that some AWS instance has decided to stop existing. That sucks, especially when you are using Slack for notifications as well as discussions. So basically, I have a modern native app that is not capable of doing what many old-school text-based IRC client were already capable of doing 20 years ago: showing multiple things at once. Splitting a window to show multiple tabs at once then? Nope. How about detaching a tab to make a new window? Not an option because, well, it’s a single-window app. In a world where every application has tabs, and multiple windows, the Slack app offers me just a single window, with tabs.

That’s right, I went back to a text-based interface because the modern and polished native app doesn’t have functionality I need. Yet, today I dusted off my trusty old IRC client, WeeChat, to solve one of the glaring shortcomings of Slack. They offer native mobile and desktop apps, centralized logging (so no need for BNC software), drag and drop filesharing, etcetera. Nowadays, however, IRC is losing marketshare to somewhat more modern alternatives like HipChat and Slack. This isn’t in any way a new concept, since IRC has been with us since 1988. Many development and ops teams rely on chat for communications.

#WEECHAT ADD SERVER HOW TO#

Powered by Gitea Version: 1.16.9 Page: 97ms Template: 5ms English Licenses API Website Go1.17.Using Slack in your terminal with WeeChat ←Home About Subscribe Using Slack in your terminal with WeeChat This blog explains why I decided to use WeeChat for Slack, and how to do it. Lith has a beta application that iOS users can use via TestFlight. There seem to be some client options but they aren't on the app store and hence require a local build or beta opt-in.

#WEECHAT ADD SERVER ANDROID#

In addition to being able to connect from your browsers, Android users can use the weechat-android application to connect on the go.

#WEECHAT ADD SERVER CODE#

You can save this code in /etc/nixos/weechat.nix, for example, modify it with the correct domain name, and then add weechat.nix to your imports list. Server configuration NixOS Moduleīelow, we'll specify a NixOS module that you can add to the imports list in your server's nixos configuration file (found in /etc/nixos/configuration.nix).įor example, the default NixOS-on-AWS configuration file looks like this: imports = Īnd you can add an import to it like this: Typeclasses has a detailed tutorial on deploying NixOS to AWS EC2.

You can deploy NixOS to a variety of hosting providers. We'll be assuming you're running NixOS on the server. We'll be using Let's Encrypt to generate certificates to help keep traffic between our server and clients secure.

We're going to set up a server that runs Weechat that you can connect to from your phone, tablet, or desktop machine. You can, however, achieve the same result using a few free and open source technologies. Some proprietary services, like IRCCloud, will keep you connected and provide you a cross-platform IRC interface. This is especially annoying when switching between mobile and desktop. One of the disadvantages of IRC is that you can't log in ('identify') as the same user on multiple machines. So much conversation in the Haskell and Nix ecosystems happens on IRC.

Weechat add server