Fork me on GitHub
#community-development
<
2018-03-14
>
gtrak20:03:06

hey, is it possible to install the wee-slack app integration here? I had been using the irc bridge, but that and xmpp are going down May 15. I use wee-slack for work, but would be happy to use another integration supported by weechat. Seems like matrix is a thing?

dominicm21:03:17

You don't need the integration

seancorfield20:03:00

See the wiki -- linked in the channel topic and details (in the sidebar) -- for various alternatives.

seancorfield20:03:31

Matrix bridges IRC and also bridges into a couple of channels here (but not the main #clojure channel from IRC).

seancorfield20:03:37

30-50 people are using Discord which doesn't bridge into anything. I think about 600-700 people have remained on IRC (and will likely continue to just ignore Slack once the gateway goes away). There are also a few small pockets of users on Gitter in various rooms.

seancorfield20:03:17

The number of people currently using the IRC gateway to Slack is very small (compared to the nearly 13K members in this Slack).

Alex Miller (Clojure team)20:03:36

IRC took a significant dip this year in the Clojure survey (and Slack is clearly the most used)

Alex Miller (Clojure team)20:03:03

(and yes, we plan to post that stuff soon - waiting on me at the moment)

gtrak20:03:58

I started using wee-chat to actually be able to keep all my slacks and IRC in one window. It's been pretty nice.

seancorfield20:03:17

I thought wee-chat used Slack's websocket API already and wouldn't be affected by the gateway shutdown?

gtrak20:03:34

it does, it just needs an oauth token

seancorfield20:03:34

@gtrak Are you already bridging into this Slack via wee-chat?

gtrak20:03:00

yes, via IRC at the moment, but I use the 'app' for my other slacks

seancorfield20:03:05

According to https://github.com/wee-slack/wee-slack all you need is to request an API token and put that into wee-slack locally and you're off to the races...

gtrak20:03:46

yes, I think the issue is, the oauth token is tracked as an 'app' in slack

seancorfield20:03:36

I don't see wee-chat or wee-slack in the Slack app directories so there's nothing to install from an admin p.o.v.

seancorfield20:03:03

Per that GH repo, it sounds like you need to request an API token from Slack...

seancorfield20:03:08

Looks like you can either request a test token or generate a legacy token.

gtrak20:03:34

yea, I wonder how slack knows about apps at all, maybe there's some link parsing or something. I think if I click 'request legacy token', you guys would have to approve it, which isn't a general solution. I'm not yet convinced that having one person try the normal wee-slack oauth will make it easier for the next person yet.

seancorfield20:03:07

We approve all token requests. @slackbot lets us know about them. We do not approve app requests tho'.

gtrak20:03:26

ah ok, well then I guess I'll do that 🙂

seancorfield20:03:36

And let us know how it goes.

seancorfield20:03:48

FWIW most people request test API tokens, not legacy tokens, but I granted your request anyway.

gtrak20:03:44

it worked, @seancorfield I don't see a way to get a separate 'test token', but thanks!

seancorfield20:03:12

Yeah, following their links for test API tokens seems to land you back on the legacy token page ... that may be a recent change?

dominicm21:03:56

Legacy tokens are what I use :)

dominicm21:03:17

They work almost everywhere.