T3s|4
o/ dr|z3d - not sure if this is a weechat quirk, but since I began running weechat 4.0.0 yesterday #saltR never transitions to #saltr after successful identification - as it always had previously. Both laptops, same behavior since yesterday
dr|z3d
nothing to do with I2P+, T3s|4. check weechat configs.
T3s|4
np dr|z3d - but I didn't change any of my ~/.weechat configs, so perhaps something changed in the new code
dr|z3d
nothing new in the code.
T3s|4
no, I mean in the new weechat 4.0.0 code
dr|z3d
oh
dr|z3d
then probably.
dr|z3d
in other news, ETA to -45+ approx 2m.
dr|z3d
try adding explicit /joins on server connect, perhaps.
dr|z3d
-45+ uploaded.
T3s|4
thx, I'll grab it soon
T3s|4
I already autojoin channels, and attempting to `/join #saltr` fails / does nothing. #saltR works fine for me :D
dr|z3d
strange.
T3s|4_
D
dr|z3d
\o/ T3s|4!
T3s|4_
still unsure why weechat <=3.8 logged me into #saltR, and then 'flipped that' to #saltr usually within seconds
dr|z3d
code change, obviously it's no longer accepting uppercase in channel names.
T3s|4_
that makes sense :D
dr|z3d
code change or bug. :)
T3s|4
hmmh...it seems unlikely that weechat stopped accepting any uppercase in channel names, as 4.0.0 still logged me in correctly to #saltR, but the new code stopped 'auto flipping me' into #saltr within seconds once identified as previous versions of weechat always had. In any event, a truly minor nit :D
dr|z3d
you could always try reporting the issue.
T3s|4
dr|z3d: been a long time - Was the original distinction for #saltR for unregistered nicks to view what was being said on #saltr, but they were prevented from speaking?
dr|z3d
registration required, and voice, to speak in channel.
dr|z3d
short answer, "yes" :)
T3s|4
got it, thanks