Fork me on GitHub
#community-development
<
2018-02-23
>
cfleming00:02:31

I agree, I suspect that it would be surprisingly complicated for them to implement.

mbjarland14:02:08

am I correct in assuming that the current archives do not have data for 2018 yet? (https://clojurians-log.clojureverse.org/clojure/index.html)

dominicm14:02:45

They're being fixed 🙂

mbjarland14:02:11

ok, no worries, just making sure I'm not smoking something untoward

noisesmith17:02:47

has anyone here successfully connected to this slack with wee-slack?

noisesmith17:02:35

perhaps there’s a plugin that needs to be installed on clojurians side before it works

dominicm19:02:42

I haven't to this slack, but I have to our work slack with no changes on the work slack side.

noisesmith19:02:48

I'm sending this message from weechat - the trick was to get a legacy token and store and use that, instead of relying on clojurians to integrate

dominicm19:02:15

@noisesmith that's what I was about to say. The OAuth application is very new.

dominicm19:02:26

I used the legacy token thing for work.

dominicm19:02:38

I'm very happy with weeslack

noisesmith19:02:18

yeah - it seems decent so far - haven't tried anything like threads yet though

dominicm20:02:41

@noisesmith I really like threads, I place them equal with native ones. The only things that bother me are : No notifications when I open weechat again No all threads page Naming a thread doesn't work with go.py

dominicm20:02:07

These are all fixable. If someone has the interest. Except maybe the last

noisesmith20:02:20

testing thread reply

dominicm20:02:20

i am testing

dominicm20:02:29

reactions are fun too

noisesmith20:02:44

interesting - so how do I start a thread from an existing message?

noisesmith20:02:55

n/m I RTFM and I figured out how to edit too 😄

gonewest81820:02:33

testing Emacs ERC via the IRC bridge on http://clojurians.irc.slack.com:6697

gonewest81820:02:54

So far, reactions and threads aren’t being recognized … not sure if that’s config related.

testing Emacs ERC via the IRC bridge on
                                           [12:54]
<dominicm> halo                                                         [12:55]
<dominicm> i am testing
<noisesmith> nice
<dominicm> reactions are fun too

dominicm21:02:17

IRC doesn't work with threads does it?

gonewest81821:02:09

I suppose not, considering how old the protocol is.

gonewest81821:02:18

problem being, I can’t even see that your comment was in this thread… Had I responded in IRC it would have been out of context in the main channel.

dominicm22:02:04

they covered this is the announcements article I think

noisesmith22:02:53

yeah, the slack UI is richer - eg responses, threads, edits - and since weechat hooks into those I can use and see them all from weechat, but to do it via IRC you'd need some interface to stack that on irc and it would look weird from a normal client

noisesmith22:02:23

I just ran into a weird thread bug in weechat though

noisesmith22:02:12

if I respond to this thread in weechat, I only see the message in the GUI slack, not weechat

dominicm23:02:28

never had that

dominicm23:02:38

I suspect wee-slack + clojurians may run into economies of scale issues.