20:57 <denon> happened to stumble on this channel after some conversation logs ... so not sure if it's the right place ...

20:57 <denon> but is anyone familiar with a way to make slack stuff not auto join all the channels on connect?

20:57 <denon> doesnt seem to support JOIN 0 to leave them all again (or .. any kind of PART?)

20:59 <Liothen> slack stuff?

20:59 <denon> sorry, the irc.speck.com gateway to slack

20:59 <denon> er, irc.tinyspeck.com

21:00 <denon> sorry if this chan is totally unrelated, I just some some related conversations come up in searches

21:01 <Liothen> this channel is for https://github.com/cinchrb/cinch

21:01 <Liothen> which is an irc bot framework written in ruby

21:01 <denon> ahh gotcha, makes sense

21:01 <denon> sorry for the distraction

21:02 <denon> looks like the conversations were just disgruntled that their ircd doesnt act normally

21:02 <denon> so the bot didnt behave well

21:08 <leftylink> PART's behavior on slak's irc gateway is: you stop receiving messages on that channel, but other users do not perceive you as having left - the reason for that is that "some clients PART all channels before disconnect and we don't want that to happen to our users"

21:09 <leftylink> (paraphrased)

21:09 <leftylink> as for not auto joining all channels on connect, uh

21:09 <leftylink> leave the channel through some non-irc means

21:10 <leftylink> slack's API would possibly work for that, and yeah it sucks tha toyu have to do it through non-irc means but them's the breaks

21:10 <leftylink> since obviously PART via irc won't work, and I infer JOIN 0 wouldn't either

21:11 <leftylink> should HL

21:12 <leftylink> denon: (summary, see other messages) you'll have to leave the channel through non-IRC means, possibly through slak's API, because their ircd has "unusual" PART semantics

21:13 <leftylink> the upshot of "other users do not perceive you as having left" means "you didn't actually leave, you just stop receiving messages for that session despite still being in the channel, which is super confusing but apparently that's how slak wants it to be", and since you are still in the channel you will auto join it on connect

21:14 <denon> yeah ...

21:14 <denon> that's kind what I gathered too

21:14 <denon> I wondered if there was a config somewhere that could be set

21:14 <denon> "dont autojoin me"

21:14 <denon> havent found one though

21:14 <leftylink> now that would be interesting

21:14 <denon> the whole thing looks like it was written by a preschooler

21:14 <denon> I have no idea why they made some of these design decisions

21:14 <leftylink> should ask slak support... anyway from slak support is where I have confirmation about the PART semantics

21:15 <leftylink> and why I know that the reason for it is "some clients PART all channels and we think that would be disastrous for our users"

21:16 <denon> sigh

21:16 <denon> why makes an ircd gw if you arent going to honor any ircd things

21:23 <leftylink> thanks for the idea (a config option)

21:24 <leftylink> they already support one config option https://get.slack.help/hc/en-us/articles/201727913-Connecting-to-Slack-over-IRC-and-XMPP so I'm wondering if they would be willing to support another

21:25 <legit> TIL .help is a TLD

21:34 <leftylink> I didn't even notice that when looking at that url :o

22:02 <dominikh> leftylink: best thing is trying to leave unleavable enforced auto joined channels. You keep getting all messages. But no indication (e.g. JOIN) that you are still in the channel

22:03 <dominikh> You could part normal channels in the past, couldn't you?

22:04 <dominikh> Anyway, stay away from their irc gateway if you can. It's broken in so many more ways, even for normal users

22:05 <dominikh> Back to sleep.