[01:42] hey I can't talk in #ubuntu for some reason [01:42] yeah, lets try cooling down for an hour [01:42] what does my temperature have to do with it? [01:43] sarnold: what does my temperature have to do with it? [01:44] hey I can't talk in #ubuntu for some reason [01:44] hey I can't talk in #ubuntu for some reason [01:45] it's this sort of behaviour that got you the +q in #ubuntu [01:45] what sort of behavior? [01:45] isn't this the channel to talk about not being able to talk in #ubuntu? [01:45] I don't even know why I have a +q, that's why I'm here [01:45] I gave you the +q because you were being abusive [01:45] abusive? What? [01:46] how? [01:46] i suggest re-reading the logs and try to figure out for yourself where the conversation went off the rails. I think it'll be instructive. [01:47] well I'm here 'cause I don't know what happened [01:47] so can you just tell me what abusiveness there was? [01:48] you were asked nicely to keep the ranting out of the support session [01:48] you continued to rant [01:48] when you were redirected to a more appropriate channel, you escalated [01:48] and then you insulted the people who are actually being helpful [01:48] I was not asked nicely or to keep "ranting out of the support session", at all [01:48] do you have a log? That never happened [01:48] this is a repeated pattern with you [01:49] when you're on your good behaviour you're nice enough and I like having you aruond [01:49] what, being denied an explanation? [01:49] I'm always in good behavior [01:49] but when you're acting childish, it's pretty obnoxious [01:49] and snaps are always a support issue [01:49] who's acting childish? You're an op and you won't even say why a person has been +q'd [01:49] suggesting to someone that they switch to a deb is fine [01:49] sure it is [01:49] being belligerant and abusive about it is not [01:49] well I've not been that [01:50] go ahead and show me the line where I was [01:50] disagree [01:50] "disagree" =P [01:50] Thu 09 01:40:46 < matsaman> suck an egg [01:50] Thu 09 01:41:18 < matsaman> arraybolt3: keep it to yourself! [01:50] "keep it to yourself" is something someone just said to me [01:50] and it's not abusive [01:50] nor is 'suck an egg', it's an age old expression [01:50] https://en.wiktionary.org/wiki/teach_grandma_how_to_suck_eggs [01:50] anything else? [01:52] yeah I didn't think so. IRC. 12-year-old ops at every corner, same shit different decade [01:52] later [07:29] I'm thinking of making a tool that might help the operators of the #ubuntu namespace channels be able to detect various forms of unacceptable user behavior such as ban evasions, spamming, etc. This tool would be made as an IRC bot that would log all events in the channels it was in and would then analyze those events to provide insight into what's happening. [07:30] For instance, it might be able to detect that a particular user is using a different nick than the last time they had joined the channel, but is likely to be the same user. [07:30] I would like to request permission to use the #ubuntu namespace channels to assist in developing this bot. It will only be reading information, never sending messages. It will, however, be logging all channel activity in the channels it is in. [07:42] I mean some of those features already exist in the bot. :P But we don't do database related tasks, so no tracking of users or something that could be considered privacy invasive. [07:42] Channel spam, asciiart, clones, etc. [07:44] Hmm. I guess what I'm planning could be considered privacy invasive. I just thought it might be useful for doing things like detecting if three different "people" who all troll and all behave similarly are actually all the same person based on ISP/IP address info. [07:45] All of the data is publicly available and at least WeeChat saves it all by default. It's just taking that data and trying to spot things in it. [07:45] There's been...problems in the past with bots that got too stalkery. [07:45] Understood. If that's not acceptable, I will either not develop the bot or find some other source of info to develop the bot with. [07:45] Can you read perl at all? [07:46] Not hardly :P [07:46] Current bot is perl. :P [07:46] My plan was to make the bot identifiable via CTCP VERSION so that unauthorized instances could be detected and banned. [07:47] That way the ops could use it, and I could use it for development purposes, but other people wouldn't be able to use it without it being noticeable. [07:47] I could also try to learn some Perl so that stuff like that could be added to the existing bot. [07:48] I see there's someone else here, and I think I already got my answer about the bot (that answer being "no, don't use our channels for that"), so I'll leave so as to not be intruding. Thanks for your time. [07:48] Not really, just telling you the histyr.. [07:48] Oh. [07:51] personally, while i don't do such analysis now, i could see its purpose and i was also wondering whether it would be an issue as long as i keep all data local on encryted file systems. personally i think this would not really count as privacy invasive. it's not stalking if its just analysis of public data. but sure, that line is slim. [07:51] He's in -irc [07:51] oh thanks