 |
This will be the last post specifically geared towards using Slack |
|
with IRC using wee-slack.py. This post will focus on some of the |
|
issues I had setting things up. Since there weren't that many of th |
|
this post will probably be pretty short. |
|
|
|
So, caveats and issues. Thankfully there were not many. The main is |
|
I had revolved around a bug that was, ironically enough, fixed just |
|
this morning. The commands `/slack channels` and `/slack users` wer |
|
broken (along with a few other less common ones) due to an issue wi |
|
a code refactoring that occurred back in July some of the `/slack` |
|
commands had broken. |
|
|
|
This post was originally going to outline a workaround I'd found. |
|
However, since the bug fix was merged to master this morning, there |
|
not so much to talk about anymore :) |
|
|
|
The only other issue I had was one that is self (or company) |
|
inflicted. One of the main reasons I want to inteface with Slack ov |
|
weechat is because I already have it open to hang out in IRC every |
|
day. Why should I have two chat applications open? Why not just |
|
combine them in to the same window? Unfortunately, you need a slack |
|
API key to access Slack with wee-slack.py and it seems like a bad i |
|
to store something that could provide someone access to sensitive |
|
company information on a server I don't control. So how do I fix th |
|
|
|
In my next post I will be leaving the topic of wee-slack.py to focu |
|
on how I manage to persistently stay connected to IRC while also |
|
connecting to my work chat server. It'll hopefully be a long one an |
|
packed full of great information that I hope you find useful in you |
|
own setup. |
