--- Day changed Thu Nov 29 2018 03:14 <@provoostenator> @instagibbs: I'll try PR 66 with a Trezor T 03:15 <@provoostenator> I didn't intentionally set anything to invite-only, but I'm an IRC n00b so who knows. Thanks @sipa for fixing. 03:18 <@provoostenator> I lost ops myself too a few days ago, and had to do "/chanserv RECOVER ##hwi" to get it back. Let me know if I need to issue any incantations... 03:22 <@provoostenator> Maybe it's just a ZNC misconfiguration. I'm impressed by how high the barrier to entry for IRC remains in 2018 :-) 03:32 -!- grubles [~grubles@unaffiliated/grubles] has quit [Ping timeout: 246 seconds] 03:34 < arubi> provoostenator, setting 'recover' on the channel is what did it then :) 04:17 <@provoostenator> Interesting, so that creates some kind of hostile-takeover mode? 05:45 <@instagibbs> yeah bouncers are somehow still pretty not great in 2018. I think the "best" solution is tmuxing into your machine... 07:40 -!- grubles [~grubles@unaffiliated/grubles] has joined ##hwi 08:25 < arubi> provoostenator, yep. the line in my log says '*** ChanServ sets mode: +imo provoostenator' and that looks like what it says 'recover' should do in chanserv's help. probably "/MSG chanserv op ##hwi provoostenator" would've restored just the +o 08:32 <@provoostenator> Ok, I'll try that next time 09:48 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Ping timeout: 264 seconds] 10:03 -!- achow101 [~achow101@unaffiliated/achow101] has joined ##hwi 15:26 -!- arubi_ [~ese168@gateway/tor-sasl/ese168] has joined ##hwi 15:27 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 256 seconds] 17:45 -!- arubi_ [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 17:46 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined ##hwi 22:22 -!- grubles [~grubles@unaffiliated/grubles] has quit [Quit: Leaving]