[09:53:42] [discord] https://ysmwiki.miraheze.org/wiki/%E7%89%B9%E5%88%A5:%E6%9C%80%E8%BF%91%E3%81%AE%E6%9B%B4%E6%96%B0 The `ysmwikiwiki` is currently being riddled with IP vandals vandalizing pages. I've been effectively adding in rangeblocks, but they just keep coming. [09:53:45] [url] 最近の更新 - Ysmwiki | ysmwiki.miraheze.org [11:39:24] [discord] I'm no abusefilter expert, but I feel like you could create one that would be remarkably useful which a) targets a mass blank and b) checks some of the content that is posted in its place [11:40:13] [discord] I'd also reconsider IPs editing or how much they can edit freely, or if you leave it open seriously consider a more stringent AF [17:51:41] [discord] Okay then. [19:05:09] [discord] [[Special:CentralAuth/Emuritto]] - https://meta.miraheze.org/wiki/Special:Contributions/Emuritto - Showing some behavioral patterns that are reminiscent of Apex [19:05:09] https://meta.miraheze.org/wiki/Special:CentralAuth/Emuritto [19:05:10] [discord] [19:05:11] [url] User contributions for Emuritto - Miraheze Meta | meta.miraheze.org [19:05:13] [url] Global account information for Emuritto - Miraheze Meta | meta.miraheze.org [19:07:08] [discord] See also https://meta.miraheze.org/wiki/Special:DeletedContributions/Emuritto [19:07:09] [url] Permission error - Miraheze Meta | meta.miraheze.org [19:07:14] [discord] @raidarr if around ^ [19:09:41] [discord] Time to do a nuke block then, I guess. :/ [19:10:43] [discord] I nuked their created pages but would rather wait for a Steward to investigate this before issuing a local block that may be superseded by a lock [19:10:57] 👍 [19:11:09] [discord] Speaking of nuking, I nuked somebody's YouTube channel. [19:11:15] [discord] Speaking of nuking, I nuked somebody's YouTube channel today. (edited) [19:11:23] Hmmm? [19:11:31] How though? [19:12:05] [discord] I gave the user all 3 copyright strikes, and it caused their entire channel to get terminated. Something I've been plotting for a few weeks up until this point. [19:12:21] Ah [19:12:25] Sky [19:12:30] s/k/l [19:12:31] RhinosF1 meant to say: Sly [19:12:53] [discord] But anyway, were we just talking about ApexAgunomu again? [19:14:14] [discord] Also, the behavior from that account is pretty obvious it's her, even the IP range she's used earlier in the week just absolutely dogpiles it, eliminating any doubt here. [19:18:12] Yeah no can we just ban the IP [19:18:30] [discord] BrandonWM It's not that simple. [19:18:42] Let raidarr investigate first [19:19:39] [discord] Let's not rush progress here guys. I'm sure raidarr will eventually get word of Apex's latest sockpuppet account. [19:23:53] No I mean…wait actually nevermind [19:36:03] I'm sure agent can watch [19:36:40] If they cause trouble, we will be ready [19:42:12] [discord] [[Special:CentralAuth/Train tickets to tutu]] @CVT Oh look, -abigblueworld-, our repeat costumer has returned, with proof: https://okaymovies.miraheze.org/w/index.php?title=What_is_Long-term_abuse&oldid=2005 [19:42:12] https://meta.miraheze.org/wiki/Special:CentralAuth/Train_tickets_to_tutu [19:42:13] [url] What is Long-term abuse - Okay Movies Wiki | okaymovies.miraheze.org [19:42:14] [discord] [19:42:16] [url] Global account information for Train tickets to tutu - Miraheze Meta | meta.miraheze.org [19:42:49] Yeah [19:43:32] locked [19:45:04] Um [19:45:07] will note [19:45:21] emuritto has sysop on PTW [19:45:34] something to keep note of [19:45:45] [discord] BrandonWM, I take it that you didn't know about our "old friend", -abigblueworld-, have you? Well, to make a long story short, she's been an annoying, pestering user who would constantly abuse multiple proxies, and shit like that. Her modus operandi is her typical "FUCK THE RULES, I'M GONNA KEEP FORCING PEOPLE TO LOCK ME FOR MY DESIRED REASONS" motive. [19:46:06] [discord] [[Special:CentralAuth/What is Long-term abuse, what is it.]] And, she strikes again. Lovely. -_- [19:46:06] https://meta.miraheze.org/wiki/Special:CentralAuth/What_is_Long-term_abuse%2c_what_is_it. [19:46:07] [discord] [19:46:08] [url] Global account information for What is Long-term abuse, what is it. - Miraheze Meta | meta.miraheze.org [19:46:44] https://meta.miraheze.org/wiki/Special:CentralAuth?target=What+is+Long-term+abuse%2C+what+is+it. [19:46:45] [url] Global account information for What is Long-term abuse, what is it - Miraheze Meta | meta.miraheze.org [19:46:49] oh nvm already said [19:46:55] [discord] What is locking? [19:47:27] DarkMatterMan4500: No I wasn’t aware. That sounds like a severe issue. [19:47:48] I find therapy would be her right avenue, not Miraheze. [19:47:50] [discord] [[Special:CentralAuth/Tell me what L-TA and Long-term abuse means?]] And she's back again. [19:47:50] https://meta.miraheze.org/wiki/Special:CentralAuth/Tell_me_what_L-TA_and_Long-term_abuse_means%3f [19:47:52] [discord] [19:47:53] [url] Global account information for Tell me what L-TA and Long-term abuse means? - Miraheze Meta | meta.miraheze.org [19:48:06] too bad I don't have CU :( [19:48:06] block the IP for 24h [19:48:18] [discord] I've known that pest for over a year. [19:48:20] we should block locally to trigger an autoblock [19:48:26] Yep that [19:48:37] that’s what I was about to say [19:48:43] [discord] You think @Orduin might help us for the moment if he's not busy? [19:48:46] MrJaroslavik lock conflicted with me again! :P [19:48:58] no one can say the CVT team isn't active and quick anymore now [19:49:00] [discord] A global AF which prohibits the usage of any username containing the phrase "Long term abuse" should definitely be added [19:49:09] [discord] 100% [19:49:14] Agree [19:49:24] also Reception123 you’ll have CU soon enough lol [19:49:40] would assume it closes early next week [19:49:53] [discord] I've done this (autoblocks) in the past, but I don't know what IP they uses and if it's not unnecessary 🤷‍♂️ [19:49:57] [discord] IPs [19:50:05] [discord] BrandonWM Let's just wait until the Stewardship(s) close. [19:50:09] Wait [19:50:20] DMM you said they use proxies? [19:50:39] yeah autoblocks only work if they use the single IP [19:50:47] if it's dynamic then it's pointless without a rangeblock [19:50:48] [discord] BrandonWM Yes, I have. She has misused multiple service proxes from the likes of Amazon and other shit. [19:50:54] Btw [19:50:59] reception123 [19:51:01] [discord] Then they will use L-o-n-g-t-e-r-m-a-b-u-s-e and/or some other character than - [19:51:03] How is it L-TA like Ho [19:51:08] new user [19:51:11] [discord] [[Special:CentralAuth/How is it L-TA like Ho?]] And again. -_- [19:51:11] https://meta.miraheze.org/wiki/Special:CentralAuth/How_is_it_L-TA_like_Ho%3f [19:51:12] [discord] [19:51:13] [url] Global account information for How is it L-TA like Ho? - Miraheze Meta | meta.miraheze.org [19:51:17] yea [19:51:50] DMM auto block won’t work then [19:52:01] [discord] And if you don't know IPs in these cases, autoblock is useless, yeah [19:52:02] she’ll just switch [19:52:16] but [19:52:20] [discord] BrandonWM It's gotten so bad, that I even Qualitipedia-banned her from Qualitipedia due to her persistent disruption. [19:52:23] we can just rangeblock the proxies [19:52:40] [discord] She's even spread to other MediaWiki hosting sites, such as the Super Smash Bros Wiki. [19:52:41] thst way the block applies to logged in users [19:52:56] [discord] Or block all IPs [19:52:58] [discord] And not just Wikimedia projects. [19:53:10] MrJaroslavik: what do you mean? [19:53:20] block all IPs from editing service-wide? [19:53:50] no, all proxies [19:53:58] since they're banned by NOPP anyway [19:53:59] Oh well yeah [19:54:10] we should’ve done that a while ago [19:54:29] Need a steward though to check this mf’s IP [19:54:48] [discord] [[Special:CentralAuth/L-TA is not what L-TA is.]] And she just keeps coming. @Orduin, we might need you. [19:54:48] https://meta.miraheze.org/wiki/Special:CentralAuth/L-TA_is_not_what_L-TA_is. [19:54:49] we know, there's no need to repeat that here really [19:54:50] [discord] [19:54:52] [url] Global account information for L-TA is not what L-TA is. - Miraheze Meta | meta.miraheze.org [19:54:57] L-TA is not what L-TA is [19:54:58] new yser [19:55:08] jesus she just won’t stop [19:55:18] [discord] Or, MrJaroslavik could just obliterate it like the way he did, [19:55:21] [discord] Or, MrJaroslavik could just obliterate it like the way he did. (edited) [19:55:28] Wait [19:55:33] There's no need for peanut gallery comments here really, reporting is enough [19:55:45] can we just block account creation temporaily [19:55:47] for like an hour [19:55:48] [discord] @Reception123 Me, or BrandonWM? [19:55:49] [discord] Wdym? [19:56:00] block all accounts from being created [19:56:05] [discord] I meant that you locked it so quick. That's what I meant by obliterating. [19:56:09] it’s a way discord servers sometimes stop raids [19:56:21] they prevent any users from joining for a set period of time [19:56:27] we could try to employ the same technique [19:56:40] [discord] I'm afraid it's not that easy BrandonWM. [19:57:18] [discord] [[Special:CentralAuth/L-TA means make a new acc.]] Yep, she's not giving up yet. [19:57:18] https://meta.miraheze.org/wiki/Special:CentralAuth/L-TA_means_make_a_new_acc. [19:57:20] [discord] [19:57:21] Sure it is, we just prevent account creation from user groups [19:57:22] [url] Global account information for L-TA means make a new acc. - Miraheze Meta | meta.miraheze.org [19:58:07] [discord] BrandonWM That would we would all have to resort to rangeblocking and autoblocking, causing an en masse of issues (if I'm not mistaken). [19:58:15] [discord] BrandonWM That would mean we would all have to resort to rangeblocking and autoblocking, causing an en masse of issues (if I'm not mistaken). (edited) [19:59:11] BrandonWM: we aren't willing to block new people from joining just because an LTA is currently active [19:59:15] I’m confused [19:59:46] [discord] We shouldn't [[w:WP:BITE]] new users. [19:59:46] https://en.wikipedia.org/wiki/WP:BITE [19:59:46] [discord] [19:59:50] chrs: what I’m saying is if we temporarily ban account creation, the LTA may get bored [19:59:54] [discord] Noo, i am back where i was before :DDD [20:00:11] and leave since they don’t know when the account creation block will expire [20:00:17] BrandonWM: we aren't going to punish everyone else for a random LTA [20:00:23] this isn't discord [20:00:32] It’s an hour [20:00:35] we don't engage in collective punishment [20:00:40] It’s not [20:00:44] people can wait an hour [20:00:53] we have some amount of patience, right? [20:00:57] they shouldn't though [20:01:09] what will actually end this is when a steward gets here to checkuser them [20:01:13] [discord] BrandonWM Locks are ***NEVER*** supposed to be used as a superior form of punishment whatsoever. That's like sentencing someone to death just because they stole a cookie. [20:01:30] DMM you’re confused [20:01:32] not a lock [20:01:37] an account creation ban [20:01:40] .mhca What account l00ck am I bypassing? [20:01:40] https://meta.miraheze.org/wiki/Special:CentralAuth/What_account_l00ck_am_I_bypassing? [20:01:41] ^ [20:01:42] [discord] [[Special:CentralAuth/What account l00ck am I bypassing?]] And once again, she's back. [20:01:42] https://meta.miraheze.org/wiki/Special:CentralAuth/What_account_l00ck_am_I_bypassing%3f [20:01:43] [discord] [20:01:43] [url] Global account information for What account l00ck am I bypassing? - Miraheze Meta | meta.miraheze.org [20:01:52] People just simply can’t create new accounts [20:01:53] [discord] chrs We both conflicted. 😄 [20:02:29] Okay do you have a better solution? [20:02:44] because unfortunately all our stewards are away right now [20:02:56] [discord] Void's online you know. [20:03:13] If he was available to take care of this he’d have responded here [20:03:19] [discord] It was last comment instead of "LTA", sorry :DD [20:03:41] heh [20:03:56] [discord] I would've been better off locking the account just for "long-term abuse". [20:03:58] Account creation bans aren't going to happen, because they're not even technically possible due to common login [20:04:01] BrandonWM: if we cut off account registration because of an LTA, the LTA wins [20:04:10] Oh [20:04:16] There's really no need to speculate and propose here, there's only one solution: a Steward does a CU and performs a rangeblock [20:04:21] chrs: yes in the short term [20:04:21] and long-term proxy banning [20:04:23] that's it really [20:04:52] .mhca WHO’s yourself? [20:04:52] https://meta.miraheze.org/wiki/Special:CentralAuth/WHO’s_yourself? [20:04:57] [discord] [[Special:CentralAuth/Who's yourself?]] And again. [20:04:57] https://meta.miraheze.org/wiki/Special:CentralAuth/Who%27s_yourself%3f [20:05:00] [discord] [20:05:02] [url] Global account information for Who's yourself? - Miraheze Meta | meta.miraheze.org [20:05:08] Why’d it capitalize [20:05:23] [discord] Don't worry about Brandon. [20:05:35] JohnLewis: could you maybe have a look? [20:05:45] I love how we’re exchanging messages through account names and lock rationales now [20:05:46] they seem to be evading local autoblocks so probably a rangeblock is needed [20:05:56] and they really seem to be abusing account creation [20:06:01] actually tho it’s funny [20:06:22] [discord] JohnLewis has dealt with that pest once, and it was from nearly 7 months ago, dating back to December. [20:06:23] reception123: did we even attempt an autoblock [20:06:37] i don’t see anything in RC [20:06:50] an autoblock just happens when a local block is done, DMM did that [20:06:53] it obviously didn't work [20:07:04] [discord] [[Special:CentralAuth/Yourself is not L-TA. Who's yourself?]] Stay alert guys. [20:07:04] https://meta.miraheze.org/wiki/Special:CentralAuth/Yourself_is_not_L-TA._Who%27s_yourself%3f [20:07:04] [discord] [20:07:06] [url] Global account information for Yourself is not L-TA. Who's yourself? - Miraheze Meta | meta.miraheze.org [20:07:06] [discord] Who don't remember >> [20:07:09] [url] Stewards' noticeboard/Archive 29 - Miraheze Meta | meta.miraheze.org [20:07:11] .Yourself is not LTA. [20:07:16] oh whoops [20:07:19] BrandomWM: there are no local blocks actually, thus no autoblock [20:07:34] chrs: I thought @DarkMatterMan4500 did perform a local block on okaymovieswiki? [20:07:39] Reception123: not autoblock on Meta thoufh [20:07:53] [discord] @Reception123 I did block the user on the `okaymovieswiki`. [20:08:00] I believe they’re registering accounts through Meta [20:08:02] oh I guess you're right, it would have to be on Meta to prevent creations [20:08:06] yep [20:08:17] [discord] I still don't understand why there is not autoblock after block [20:08:19] i assume you can hammer that as a crat [20:08:38] MrJaroslavik: it’s because there was no block on Meta [20:08:49] locks don't create autoblocks [20:08:52] [discord] sorrryyyy [20:09:03] No need to apologize [20:09:04] [discord] i wanted to say "after lock" [20:09:06] [discord] I hope JohnLewis can read and see what's happening. [20:09:12] I've now blocked on Meta so that should fix that. I didn't think of that (that one wiki wasn't enough) [20:09:18] you see the amount of times I’ve screwed up in this convo alone? 😂 [20:09:30] thanks Reception [20:10:01] I can look in like 5 mins [20:10:12] Can you also lock the account with the bloxk [20:10:13] [discord] JohnLewis That's great. Thanks. [20:10:20] Thanks JohnLewis [20:10:26] hopefully there shouldn't be a need anymore since I just realised the autoblock had to be on Meta [20:10:35] [discord] BrandonWM, MrJaroslavik has locked the new account just now. [20:10:35] but either way the likely proxy being blocked would be a good thing [20:10:40] Well it’s good anyways to rangebloxk [20:10:44] *block [20:10:56] also, there's probably no need to ping people here multiple times per minute, we should calm down a bit [20:10:57] DMM didn’t see that, thank him for me [20:11:19] [discord] Me, or Brandon? [20:11:25] Probably both of us [20:11:34] ill chill [20:12:11] [discord] Excuse me for a moment. I have to take care of some business for just a ***few minutes***. [20:12:20] Yeah probably both of you [20:12:32] though I understand it can be frustrating to have an LTA create accounts every 30 seconds [20:13:04] Yeah [20:13:14] also John I’ve sent an inquiry to your DMs [20:13:24] CVT-related [20:14:35] Reception123 sent one to you as well [20:14:49] Discord though [20:15:01] Oh mb on the ping didn’t realize [20:15:34] will look though if it's not private it can always be asked here so that anyone can answer [20:15:43] oh I see, it is a bit sensitive [20:16:46] I'm here if admin tools needed but chatting with people about real life [20:17:06] Yeah it’s sensitive didn’t necessarily want to put it here [20:17:19] rhinos: how’s it been going? [20:17:41] you got here about 10 minutes too late for admin tools but always happy to chat about life [20:18:02] [discord] but not here [20:18:16] BrandonWM: just been sorting up meeting up with a mate before I move down south [20:18:20] We can chat in DN [20:18:21] DM [20:18:45] Ah okay [20:18:48] discord DMs [20:19:22] Ye [20:19:32] or in -offtopic, but please do keep this chat CVT reports only! [20:20:46] Absolutely [20:27:23] Reception123: proxy blocked [20:28:19] thanks! though it seems the autoblock done properly did the job [20:29:25] I wish autoblock for locks existed [20:30:05] Any way that could be developed? [20:34:21] yes, there's probably an upstream task [20:36:54] Okay [20:52:41] There's definitely tasks [20:59:14] [discord] Going to look into possible apex evasion and follow up with the lta this eve [20:59:24] [discord] Okay then. 🙂 [20:59:54] [discord] Both have factors that a simple range block will not solve [22:03:47] Raidarr what do you mean won’t solve? [22:40:46] [discord] what the heck is a range block [22:43:09] [discord] [22:43:09] [url] Help:Range blocks - MediaWiki | www.mediawiki.org [22:57:53] [discord] alright thanks [23:16:36] https://publictestwiki.com/w/index.php?diff=44780&oldid=44779&rcid=61023 [23:16:43] [url] TestWiki:Request permissions: Difference between revisions - TestWiki | publictestwiki.com [23:16:54] CVT note this diff and match against previous “I’m not apex” comments [23:34:18] [discord] I'm pretty certain it's apex, just going to gather technical evidence [23:34:50] [discord] same request reason [23:34:51] [discord] the problem with apex is that she uses wireless providers that are totally unaccountable in IP and unless we take heavy handed steps across say, verizon wireless in general, there's no easy way to deal with it at an ip level [23:35:30] [discord] the problem with abbw is that abbw is famously competent at finding new proxies to abuse, which will hopefully be mitigated by @Orduin's work in progress project [23:36:23] [discord] @raidarr may be worth an attempt to send abuse reports to verizon [23:36:24] [discord] abbw is still in action? [23:36:38] [discord] my experience is that abuse reports tend to be worthless to mobile providers [23:36:49] [discord] but if someone can testify otherwise I can give it a shot I guess [23:36:54] [discord] @raidarr I agree but if they get enough… [23:37:05] [discord]