Weechat install script6/22/2023 ![]() ![]() Slackcat is a utility you can use to upload files or snippets to Slack or even just post from your command line. However, if you are using a terminal with a Solarized Dark colorscheme, changing the _line setting to darkgray is a pretty bad idea. Follow the instructions in the Github repo to install it. It pulls the recent history of any channel from the Slack server whenever you join it. Slacklog is a plugin created by the folks at Thoughtbot. With a few tweaks and plugins we can replace most of the functionality we lost by moving from the native app to WeeChat. If you have a ‘vanilla’ install of WeeChat and would like a bit of insight in where all your channels are, refer to the WeeChat docs to find out about installing the plugin. If you are connected, you are automatically joined to all channels you are a member of. A blog on weechat in Docker is coming, though. 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" 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. If ($Source -like '\\wsl$\*' -or ($Source).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. ![]()
0 Comments
Leave a Reply. |