[09:48] <tomreyn> is everyone gone or are you just hoping they'll stop?
[09:49] <EriC^^> somebody kick wtflol he's posting malicious commands that are obscured using base64, thanks
[09:54] <tomreyn> everyone gone then, sad. :-/
[09:55] <Unit193> Hi, thanks.  It's been delt with.
[09:55] <tomreyn> tx
[09:55] <tomreyn> i mean: thank you
[09:56] <Unit193> Sure thing.
[09:56] <tomreyn> is there a way to gain this power and if so, which policies need to be followed?
[09:57] <tomreyn> we have a couple regulars in #ubuntu-discuss with what i 'd consider a good take who'd be happy to help out.
[09:58] <tomreyn> doesn't need to be kline, maybe just muting or kicking or channel ban.
[09:58] <tomreyn> i don't mean to blame, but it occasionally takes 'too' long to get a reaction.
[09:58] <Unit193> Was elsewhere too.  There's a few good pages to read.
[09:59] <Unit193> https://wiki.ubuntu.com/IRC/IrcTeam/OperatorGuidelines
[09:59] <Unit193> !canibeanop
[10:00] <tomreyn> things like "Next team meeting (details): Wednesday, September 9, 2015 1800UTC" (a quote from https://wiki.ubuntu.com/IRC/IrcTeam/OperatorGuidelines ) could make people wonder whether this is still an active process
[10:00] <tomreyn> thanks for the links, though, i'll have a look.
[10:01] <Tm_T> tomreyn: it's somewhat still alive, someone just should remember to take care of those wiki pages and whatnot
[10:06] <tomreyn> looks like this is going to take 1 or 2 hours to go through. :-/
[10:07] <Tm_T> tomreyn: that's the easiest part
[10:07] <tomreyn> Tm_T: how does it get harder then?
[10:08] <Tm_T> tomreyn: I've spent weeks dealing some users, with power there's responsibility
[10:08] <Tm_T> there's reasons why process to get new responsibilities is somewhat rigorous
[10:10] <tomreyn> there's reasons why it shouldn't be. i'd be happy to help, i think i have opk ethics, i'm happy to be put to the test to ensure we have the same take on things. but i'm not really willing to spend hours on paperwork.
[10:10] <tomreyn> i do have irc operator experience on a small network.
[10:11] <tomreyn> anyways, i guess it's a non-match then, and i'll just keep on watching people spam #ubuntu
[10:11] <tomreyn> thanks for your help, though.
[10:14] <tomreyn> i thnk this is the typical case of processes becoming so convoluted that it gets very hard to keep the process alive (you seemed to agree that it has half failed) and new applicants, even those you'd want to join, will be turned off.
[10:15] <tomreyn> it would take jumping over your shadows and allowing reestablishing process with simpler rules. usually, this does not hapopen, resulting in only grey wolves remaining in power. which would be sad.
[10:18] <tomreyn> part of the process requires editing the wiki. i requested permission to edit the wioki half a year ago, never heard back.
[10:19] <bazhang> grey wolves
[10:19] <bazhang> hehe
[10:19] <tomreyn> i don't mean to blame anyone, i'm sure you're all very busy, as well as the other groups who manage the community resources. it's just that it doesn't seem to work out, which is sad, wso i'm providing an outside perspective on this, which can maybe serve to initate a discussion on how to get more open again.
[10:19] <bazhang> Tm_T, is not that grey!
[10:20] <tomreyn> so they joined recently,? ok, then it's still possible, that's good. but the overall response time is not nearly as gfood as it could be IMO.
[10:21] <tomreyn> (and without loosing aything)
[10:21] <bazhang> it's way better now than before
[10:21] <tomreyn> glad you made improvements.
[10:22] <tomreyn> i've wanted to say this for a while. i hope it doesn't feel like i'm blaming anyone, i have th ebest of intentions.
[10:22] <bazhang> I was around as a helper for around three plus years before they even considered me as a n op
[10:23] <tomreyn> well, i dont decide on the policies, but personally i wouldn't make people wait this long for an all volunteer driven group.
[10:23] <bazhang> how long have you had to wait so far
[10:24] <tomreyn> not at all for irc ops, i never brought up the topic before. around half a year for the wiki access.
[10:25] <tomreyn> have a nice day!
[10:26] <bazhang> same to you
[19:28] <genii> Meh, missed all the excitement
[19:40] <tomreyn> also, i got this, any idea what it is about?
[19:40] <tomreyn> -Sigyn- Your actions in #ubuntu tripped automated anti-spam measures (your sentence matches temporary blacklisted words), but were ignored based on your time in channel; stop now, or automated action will still be taken. If you have any questions, please don't hesitate to contact a member of staff
[19:43] <genii> Possibly you triggered the !ops too many times in a given period. But as indicated, it was ignored
[19:46] <tomreyn> right this would explain it, although i factually triggered it once (recently) only. so the pattern matching seems to be incorrect
[19:49] <genii> tomreyn: https://paste.ubuntu.com/p/8rq2JWQMjB/
[19:50] <tomreyn> genii: right, so at :26 i wrote: !ops Guest19225
[19:51] <tomreyn> this lacks the pipe character, thus didnt trigger the warning, i think. after all, ubottu told me it doesn't know what this means
[19:51] <tomreyn> which is why i'm saying the pattern matching is not perfect.
[19:52] <krytarik> Well, it'd be valid in #debian, for example.
[19:53] <tomreyn> oh ok
[19:53] <tomreyn> haven't used this one in years
[19:53] <el> sigyn is the network anti-abuse bot, not ubuntu's so ubuntu ops are not likely to have any idea what it triggered on or any way to change it. #freenode-sigyn is the channel for sigyn discussion.
[19:54] <tomreyn> i have a certain impression that there is a not too small overlap of both groups
[19:54] <el> i'm sure you do, but despite being staff i have no idea what that triggered on
[19:54] <tomreyn> but thanks for clarifying. i guess we already worked out that this can't be improved upon easily, though.
[19:55] <tomreyn> thanks for the explanations, el
[19:55] <el> np
[20:03] <tomreyn> 176.33.224.87 is back again, will likely spam more again