Clojurians Log v2

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

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

They're being fixed 🙂

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

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

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

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

I can try.

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

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

I used the legacy token thing for work.

I'm very happy with weeslack

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

@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

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

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

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

testing thread reply

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

halo

i am testing

nice

reactions are fun too

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

testing Emacs ERC via the IRC bridge on
              <http://clojurians.irc.slack.com:6697|clojurians.irc.slack.com:6697>                             [12:54]
&lt;dominicm&gt; halo                                                         [12:55]
&lt;dominicm&gt; i am testing
&lt;noisesmith&gt; nice
&lt;dominicm&gt; reactions are fun too

IRC doesn't work with threads does it?

I suppose not, considering how old the protocol is.

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.

they covered this is the announcements article I think

Hmm, no.

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

I just ran into a weird thread bug in weechat though

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

wuut

never had that

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