***ChanServ sets mode: +o janneke
<oriansj>xentrac: the bootstrappable channel modes are: cnt :: c : Strip colour and formatting codes from channel messages.; n : Users outside the channel may not send messages to it. Keep in mind that bans and quiets will not apply to external users. and t : Only channel operators may set the channel topic. <oriansj>So the only thing that would be impacting you would be n; which only occurs if you exit the channel or try to send a message before rejoining the channel. <oriansj>Melg8[m]: well I don't really see how the two projects would benefit each other. <siraben>any updates on freenode? I'm getting reports that they're wiping everything <vagrantc>oriansj: i see mescc-tools 1.2.0 tag signed by an unfamiliar/new key ... what's my bootstrap path to find the new key? :) *vagrantc is somewhat surprised there is anything left of freenode <siraben>"Thank you for using freenode, and Hello World, from the future. freenode is IRC. freenode is FOSS. freenode is freedom." <vagrantc>is there a release tarball with the M2libc included? <oriansj>siraben: sounds like someone will have to claim and lock out freenode #bootstrappable again. with a message redirecting them to libera.chat <siraben>I have unregistered my nick, who is op there? <oriansj>siraben: well by the looks of it everyone was unregistered. <vagrantc>oriansj: ok, i got your new key from a pastebin ... certainly out-of-band but not sure how bootstrappable :) <siraben>anyone willing to venture out into the smoldering wreck! :P <clemens3>seems freenode dying quicker than anyone good have bet <siraben>janneke: please set #bootstrappable on libera to invite-only <janneke>siraben: done...but not sure what's been going on over at freenode <janneke>was it merely a netsplit that they cannot recover from? <janneke>all nicks got unregistered, all channel topics got erased ... <siraben>janneke: they are moving to a new daemon <siraben>they are deliberately bringing freenode to the ground <siraben>it's quieter now that north americans are asleep <janneke>i woke up this morning to find that freenode was empty <siraben>it's still ongoing, as you've noticed <janneke>so, the only people left were the occasional users and now they ask everyone to re-connect and re-register <janneke>luckily i finished the #lilypond registration yesterday :-) <janneke>siraben: so i probably set +i on the old split; not sure if i want to even log into the new freenode daemon/servers ***ChanServ sets mode: -o janneke
<siraben>I wouldn't bother, it's a free-for-all in terms of impersonating others at that point ***ChanServ sets mode: +o janneke
***dekenevs is now known as mitzman
***mitzman is now known as kitzman
<oriansj>siraben: fair, we just need to make sure to update our documentation to point to libera.chat instead of freenode. recently we updated the website and I think we finished updating the READMEs for the projects. (someone might want to double check) <xentrac>oriansj: yeah, I am thinking that maybe +c is not doing what it says in that sense. the other channels I'm on are +nt and don't give me that message (so I'm able to change nick from xentrac_ to xentrac without leaving and rejoining the channel) <stikonas>no, they are resetting all services from scratch <xentrac>I don't have to worry they'll compromise my password in the future <stikonas>well, I use different password per account <stikonas>so compromise wouldn't be that catastrophic <siraben>despite the amount of discussions and submissions it hasn't been frontpaged on the orange site yet ***terpri is now known as robin
<xentrac>I'm using the same password on libera that I used on the old freenode <oriansj>xentrac: that is a terrible idea; you really should have globally unique randomly generated passwords that are unique for each service you use. <oriansj>password managers like keepassxc are readily available <siraben>xentrac: I highly recommend you use a password manager and make all your passwords unique <stikonas>but even if I hadn't been using different passwords, in this particular case it would have been a good idea to change it <siraben>especially since IRC is essentially a plaintext medium <stikonas>siraben: password is TLS encrypted, isn't it? <oriansj>stikonas: depends if you connect on the tls port or the clear text port <oriansj>but anyone with access to the IRC servers in question will have the ability to collect the password used. So best to avoid password reuse when possible. <stikonas>indeed, so given that it was fairly hostile takeover by questionable people, it's best to change password <oriansj>As one doesn't want the compromise of one server to enable access to alternate servers. But then again, I am the sort of crazy who has a unique ssh keypair for each server I access. <xentrac>well, my logic was that libera wasn't "a different service" from freenode <stikonas>well, libera wasn't but you should consider old credentials leaked <stikonas>as old servers are not in control of 3rd party <xentrac>I thought I was the only one who did the unique ssh keypair thing <xentrac>do you also run unique ssh-agents for them? or do you just present all the keypairs to the ssh server and let it pick which one it wants to authorize? <stikonas>I think SSH stops checking after 5 or so? <stikonas>or maybe I'm confusing it with python's paramiko <stikonas>anyway, ssh key-pairs should be safer as long as public key cryptography is not compromised <xentrac>it depends on your threat model; public keys you use on github are actually public, so sshd can deanonymize you <xentrac>it was pretty disconcerting the first time I sshed to a host I hadn't used before and it greeted me with my github username