On 5/29/21 9:27 AM, Christian Boltz wrote:
Hello,
Am Freitag, 28. Mai 2021, 21:48:20 CEST schrieb Neal Gompa:
On Fri, May 28, 2021 at 2:15 PM Christian Boltz wrote:
TL;DR: Here's your can of worms. [...] The first step is knowing the nicknames, and since Libera is a new network, people can register with any nickname they want. This means the Freenode IRC nicks we know (see connect.opensuse.org) aren't worth much when it comes to Libera.
Now to the worms ;-) [...]
However, my worm 5 was more to get the cloak applied to our members, which needs to be done for each nick separately. (On Freenode, this meant an openSUSE admin asked one of the freenode admins to do it. I guess Libera handles it in a similar way.)
Yes projects are trying to be nice and batch up there requests.
I'm inclined to say we should just do 'sed -e "s/Freenode/Libera.Chat/g" -i -' and call it good for connect-o-o.
OK, more Gagh for you ;-)
You assume that for all our members, Freenode nick == Libera nick.
I would be *very* surprised if this is true for all our 530 Members.
People might choose a different nick on Libera. Or they might choose not to register at Libera, and (if we just do a mass-cloaking based on the data in connect.o.o) someone else would get their cloak without even knowing what openSUSE is.
Believe me - I thought twice before I wrote that mail ;-) I also would prefer a simple[tm] solution, but I'm afraid this isn't that simple.
Maybe rather then trying to find a complex solution thats perfect we should aim for a simple solution thats going to work for most users most quickly. That could look like 1. Rename the freenode field (or just use it as is) 2. give people write access to that field atm (currently I can't edit mine). 3. Email all members giving them a week to update the field if they care about there cloak or wipe it if they explicitly don't want one as well as to register there nick on Libera Chat. 4. Give the people at Libera chat a complete list to process at some point when they have a chance. The obvious issues with this approach is I don't know how hard 2 is to implement. There is the potential that someone who is not a openSUSE member registers the nick an existing member used on freenode and accidentally ends up with an openSUSE cloak. I don't think this will happen enough that its a big issue. Obviously this wont handle the cases where people don't update there nick in connect or haven't registered there nick on the new network. But obviously these people will have had some warning and by not acting they are showing its not that important to them. We can come up with a process for them and now members in the future. But with minimal approach from all sides this would get most people sorted. Cheers -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B