[00:02:51] it is a matter I would recommend pursuing via a request for feedback on the community portal, given previous rfc-backed discussion on the matter [00:22:50] could also try some better/more aggressive abuse filters [00:24:03] @orduin: decent idea [00:24:03] @raidarr: sure, I'll try drafting something [07:46:14] [1/2] Talking about Tali - he's still out there last time I heard [07:46:15] [2/2] o7 [07:47:56] o7 [07:48:03] such a shame [07:48:22] what's also annoying is that we now only have 1 global sysop, who isn't very active [07:48:25] I wonder is there "logged in users protection" settings? [07:48:36] Waki? [07:48:44] yeah [07:48:58] Yes [07:49:06] If I remember right, protection options are admin, confirmed, and user. [07:49:17] Or something along those lines. [07:53:35] I know waki probs has important irl stuff, but his last log actions as far as I can tell was in early May which is a lil in convenient [07:54:37] and that also means that for global locks, global sysops arent very relevant since the it's always stewards responding [07:54:53] but anyways, its not a super big issue and again, I'm sure he has like irl stuff [08:01:07] [1/2] waki has other projects as well [08:01:07] [2/2] the infamous "make a quote" stuff [08:01:30] i see quite a bit of people using it, so yeah...his time seems to be quite split [20:04:21] https://meta.miraheze.org/wiki/Special:CentralAuth?target=+User%3ANegga+ma+tregga [20:04:29] attempting to insert stuff into fisch wiki [20:04:34] created half an hour ago [20:42:29] @crystalite13 You wanna bet they're a repeat customer from last time? [20:42:52] Probably, from the other fisch wiki vandal [20:45:17] Reminds me of this one [20:45:22] I think the @Stewards should look into this anyways. It seems evident that it's an incredibly likely sock based on the abuse logs. [20:46:26] Maybe file a CheckUser report? [20:48:07] I already filed one against a different user not too long ago. [20:48:21] Alright [20:50:15] Yes, probably best to file them on SR so they don't get lost [23:34:21] @darkfawfulguy64, why a /16 block [23:44:19] I figured they would probably switch to a different IP on the same range. [23:45:01] /16 is an extreme range and I will advise you to not use it without authorization [23:45:20] /24 is typically broad enough if that, and the maximum assignment for the given vandal I gather was /21 [23:45:30] a /21 would be justified if bouncing is detected [23:46:20] Alright. Although, I was able to put in a 3 month block like you had advised rather than a 6-month block. [23:46:22] but only if it occurs in the same range since it might occur from another one entirely, while a /16 can either have no collateral or severe collateral and it is sometimes not trivial to tell the difference [23:46:31] it is good you have refrained to the 3 month line [23:46:45] I suppose I should make block ranges more explicit in the vd [23:47:13] Perhaps you should. [23:51:25] Sometimes, it's just better to be safe than sorry at times.