[02:04:35] https://horriblevyonderswiki.miraheze.org/wiki/Special:Log?type=comments&user=&page=&wpdate=&tagfilter= Thanks for deleting that, @Zppix. Can you also revision delete those offensive edit summaries in the above comments log page? [02:04:36] [ Comments log - Horrible Vyonders Wiki ] - horriblevyonderswiki.miraheze.org [02:05:53] @doug done [02:06:43] > [ Comments log - Horrible Vyonders Wiki ] - horriblevyonderswiki.miraheze.org @Zppix, thanks. 🙂 [13:05:56] $log deleted a page on atrociousyotuberswiki for threats and personal attacks [13:06:01] Saved item "deleted a page on atrociousyotuberswiki for threats and personal attacks" [17:06:35] Welcome wm-bot3159. If you need to report spam or abuse, please feel free to notify any of the voiced (+v) users, if it contains personal information you can pm them, or email us at cvt [at] miraheze.org [17:55:26] Do we need wm-bot3 in here? [17:58:41] @QuIRC, what's @wm-bot3's purpose? [17:58:52] QuIRC: does anyone use it [17:59:08] QuIRC: oh ye, here is logged [17:59:08] .help wm-bot3 [17:59:08] dmehus: Unknown command "wm-bot3" [17:59:15] dmehus: it's a bot [17:59:25] I don't know why it's here, it auto rejoined [17:59:32] @RhinosF1, what's it do, though? Where its help file? [17:59:40] QuIRC: Here has always been logged by it [17:59:41] I am running http://meta.wikimedia.org/wiki/WM-Bot version wikimedia bot v. 2.8.1.0 [libirc v. 1.0.3] my source code is licensed under GPL and located at https://github.com/benapetr/wikimedia-bot I will be very happy if you fix my bugs or implement new features [17:59:41] @help [18:00:04] QuIRC: tbh, logging is one thing I do want to bring under our control [18:01:03] Maybe we can use Void-bot until MirahezeBot is capable of logging in here? [18:01:39] QuIRC: void-bot doesn't do public logs either [18:01:44] A lot of its commands are duplicated by @MirahezeBot; the only potentially useful ones might be the RC feeds, but Wikimedia has separate channels for those one can join. [18:01:57] I'd personally vote to kick it, at least from the -cvt channel. [18:02:15] dmehus: we can do per wiki RC feeds [18:02:59] @RhinosF1 yeah, exactly, for Miraheze or Wikimedia wiki FC feeds, so there's not really a lot of need for this bot, I think. [18:03:21] dmehus: i'd say it can go as soon as we build public log stuff [18:03:37] Only person I can think maybe that might use it might be Revi, but assume they're in many of the Wikimedia channels already. [18:03:48] @RhinosF1 yeah that sounds reasonable [18:05:04] dmehus: my only concern is disk usage [18:05:13] tell Voidwalker I wonder if you might be interested in merging the @Void-bot codebase into @MirahezeBot in a future release? Its logging functions are very similar to MirahezeBot. [18:05:20] .tell Voidwalker I wonder if you might be interested in merging the @Void-bot codebase into @MirahezeBot in a future release? Its logging functions are very similar to MirahezeBot. [18:05:20] dmehus: I'll pass that on when Voidwalker is around. [18:05:49] dmehus: they aren't yet, that'll be 9.0.0 of MirahezeBot [18:07:07] @RhinosF1 Ah, you mean version of 9.0.0 of MirahezeBot will use a similar logging functionality to @Void-bot? [18:07:07] Regarding the disk usage point, do you mean that having @wm-bot3 in here adds to the disk usage? [18:07:38] Wow, the bot has grown so fast :D [18:07:48] I think using wm-bot3 reduces the disk usage of MirahezeBot [18:08:04] dmehus: no and I mean whether we can cope with the added disk usage properly [18:08:15] and i don't even know our disk size [18:09:31] * hispano76 gives out cookies to everyone who has helped improve the bot [18:09:58] Size Used Avail Use% Mounted on 26G 8.6G 16G 36% / [18:11:26] meh, the actual logs are only 23M now [18:12:34] @QuIRC and @RhinosF1, thanks. And thanks to @hispano76 for handing out cookies. *wonders if he received a cookie for his bug spotting* [18:12:48] you do [18:12:54] okay, cool :P [18:14:32] dmehus: my quick maths shows my only concern is how much we would last storing logs [18:14:42] Uncompressed they'd take up quite a lot of room [18:16:23] Maybe optionally delete the logs that are more than one year old to leave space or not? [18:18:32] hispano76: I'd have to see, there's stuff we can do to make it take less room but it's also then how much ram and disk space we'd need extra [18:19:20] I'd say once we get logging running, we give it a month to see real world usage before we worry about size management [18:19:41] :) [18:19:55] @RhinosF1 Ah, yeah, that makes sense. Could we write a quick script that gzips and archives the old log files at regular intervals? [18:20:01] QuIRC: yeah we'd need to monitor a lot [18:21:09] Right now I just don't see a need to worry about a problem we don't even know the full shape of yet [18:22:02] yeah [23:00:29] ^ @RhinosF1 @MirahezeBot didn't tell @Voidwalker the message I left for him at 11:05 AM (UTC -07:00) timestamp. [23:00:43] watch this! [23:00:44] Voidwalker: 2020-08-14 - 18:05:20UTC tell Voidwalker I wonder if you might be interested in merging the @Void-bot codebase into @MirahezeBot in a future release? Its logging functions are very similar to MirahezeBot. [23:02:04] @Voidwalker Do you have a custom preference set to require your intervention to have MirahezeBot recall for you any messages users left? [23:03:04] no, it only works once the user actually drops a message in a channel the bot is inhabiting [23:10:13] @Voidwalker Okay, I'm just wondering why you didn't automatically get the message, though, when you rejoined this channel, as is normally the case. Wondering if maybe it's an MH bot bug? [23:14:44] Not a bug, just not how the bot works. Bot doesn't monitor joins/parts, only messages [23:15:17] So the bot doesn't realize that a user is there until they say something