[00:00:13] No I tend not to look at the user page that often This is to ensure that I can give then the confirmed permission [00:00:22] I don't understand exactly what you're trying to do [00:00:26] they'll get autoconfirmed though [00:00:41] Well that's good new for me πŸ™‚ [00:00:43] if your wiki is not private and assuming you haven't changed any permissions, any registered user will be able to edit [00:01:00] (or even anonymous users) [00:01:13] What wiki is it? [00:12:17] @Sario, I believe his wiki is `fakemediacollabwiki`, iirc [00:12:28] (or something similar) [00:13:22] dmehus: thanks [00:13:27] Sario, np [00:13:43] s/fakemediacollabwiki/fakemediacollabwikiwiki` [00:13:43] dmehus meant to say: @Sario, I believe his wiki is `fakemediacollabwikiwiki``, iirc [00:13:48] Sario, ^ [00:14:02] ack [00:14:57] @Soda11pro!, looks like you have `edit` assigned to the `*` group, so as long as you don't have `$wgEmailConfirm` set to `true` or have the EditSubpages extension enabled, even anonymous users can edit on your wiki [00:20:14] You mean this wiki https://fakemediacollabwiki.miraheze.org/wiki/Main_Page [00:20:15] [ Atrocious nonexistent media Wiki ] - fakemediacollabwiki.miraheze.org [00:20:31] Well I want people to edit it! [00:20:53] just so you know your main page isn't protected, might want to change that [00:21:02] well, they can. whether they want to is more of a philosophical question [00:21:50] How do I protect the main page? [00:22:01] Under the More tab, select Protect. [00:22:04] use the dropdown menu on the top bar and select protect [00:22:22] I'd recommend protecting it at autoconfirmed to start, but you could go straight to sysop protection [00:24:56] How all I need to do is to wait until someone edits my wiki! [00:27:23] I saw your message on the #cvt channel. Those spambots have been so persistent as of late. [00:27:46] yeah it's really annoying [00:28:14] actually went ahead and did a local filter to immediately block them [00:28:20] Well, it's only a matter of time before they are eventually locked. [00:28:51] you mena ip blocked? [00:29:47] No, I mean locked. The IP blocks do come in between. [00:30:44] ah [00:32:10] But they come in a form called global blocks. [00:32:49] I know [00:32:56] thats why I assumed you were talking about an IP block [00:51:29] I'm testing an abuse filter on `testwiki` that will block spambot usernames that follow a certain pattern from account creation. I want to ensure there's no false positives across a representative sample before rolling it more broadly. I'm very grateful to `newuesopediawiki` for sharing it with me :) [00:51:58] So far no false positives, but it's only had 4-5 hits so far [00:53:30] dmehus: you mind if I test that out on my wiki too? [00:54:17] @chrs, sure, but let me ask Schwarz first if we can use it on other wikis, as they only gave me permission for testwiki or as a global filter [00:54:31] I'll ping you on my message to Schwarz [00:54:38] πŸ‘ [00:57:35] @chrs, https://newusopedia.miraheze.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85%E3%83%BB%E3%83%88%E3%83%BC%E3%82%AF:%E3%82%B7%E3%83%A5%E3%83%B4%E3%82%A1%E3%83%AB%E3%83%84#Anti-spambot_abuse_filter_164 [00:57:35] looks like your account might not be attached yet, so you probably didn't get the ping [00:57:36] [ εˆ©η”¨θ€…γƒ»γƒˆγƒΌγ‚―:γ‚·γƒ₯ヴゑルツ - γ‚¦γ‚½γƒšγƒ‡γ‚£γ‚’ ] - newusopedia.miraheze.org [00:57:50] got the ping [00:58:16] oh the on-wiki ping [01:12:06] I could make use of that filter at some point. Heh heh heh. 😏 [01:31:23] @chrs, yeah on-wiki, heh. I don't think they come through if your account isn't attached yet, or do they? [01:32:13] DarkMatterMan4500, yeah I'd be happy to deploy it on `crappygameswiki` for testing purposes as CGW does generate a lot of spambot attention, if Schwarz okays [01:32:32] @Doug Okay. [01:32:43] but would need to be a private filter (not visible to non-sysops), so spambots don't alter their username patterns [01:32:58] yeah it didn't come through [01:33:09] chrs, ah yeah, that's what I figured [01:33:10] thought of the discord relay bot ping for some reason [01:33:16] ah [01:33:33] and this won't stop the random dictionary word spambots, like Llamagoat7 [01:33:42] though those seem to be less prevalent [01:34:56] it does seem like most of the spambots follow this pattern though [01:35:08] chrs, if you get a chance, would you mind taking a look at the userRightsManagerTW gadget on TestWiki? I can't seem to get it to work for adding additional user groups, like `interface-admin`. Not sure what I've missed [01:35:12] chrs, yeah [01:35:19] sure [01:35:30] I'd say probably 80% of them [01:35:32] thanks :) [01:36:46] there's some code in there that actually scans the requested right [01:38:21] going to set it to trigger if it contains the word "interface", should get it [01:40:47] @dmehus it should be working now [01:40:57] just give it a bit for the cache to update [01:41:12] and then probably do a test or two [01:43:56] chrs, oh, great, thanks :) [01:44:29] ah, yeah, was that the issue, it wasn't recognizing "Interface Administrator" in the section header? [01:44:40] and getting confused with "Administrator"? [01:45:22] so the way it checks for this is by looking to see if the phrase "crat" appears in the "Requested group/permission: " line [01:45:34] needed to be updated to look for the phrase "interface" [01:46:04] otherwise it just assumes it's for sysop [01:46:35] ah [01:46:41] interesting [01:46:47] Naleksuh, you around? [01:48:16] * dmehus wants Naleksuh to request `interface-admin` on `testwiki` so he can test it out; makes sense since he does maintain Twinkle [02:37:55] dmehus : Oh I see [02:38:09] I had interface admin, but I removed since on the grounds that if I need it again I can give it to myself [02:38:13] But now bureaucrats can't grant it anymore [02:38:30] That said, I don't use Test Wiki for testing Twinkle, it's a copy of Twinkle that is used on Test Wiki [04:19:06] Hello VictorRocks! If you have any questions, feel free to ask and someone should answer soon. [04:20:08] Hello. I just asking. Do you know were you can make User tools tab and the background color. [04:35:26] @chrs, looks like you can use that anti-spam filter from `newuseopediawiki`...just keep it marked as `private` [04:35:36] It's on TestWiki [08:08:33] is there in discord any bot to check a miraheze user? [08:09:13] What do you mean by check? [08:11:12] something like the user page, in my wiki is a new user, and i want to check who is and other wiki with the same user [17:46:09] @Doug these anti spam filters are global, by the way? [17:46:48] I noticed that some wikis targeted by spam did not even created a single filter on AbuseFilter, but 99% of the spambots are blocked automatically [18:22:48] @Lake, yeah, we've got two main global anti-spam filters that block (most) spam. The ones that aren't blocked are where they don't use external links, but still create spammy user pages. My theory is those are the "smart" spambots whose objective is to build up enough edits to become `autoconfirmed` [18:23:07] but thankfully, we do catch them before that were to happen [18:24:04] @Lake, https://meta.miraheze.org/wiki/Special:AbuseFilter. #14, #18, and #19 are the principle anti-spam global filters [18:24:06] [ Abuse filter management - Miraheze Meta ] - meta.miraheze.org [18:26:48] dmehus: I see, but I can view the Filter 18 and 19 [18:26:51] it's protected [18:29:58] @Lake, yeah those are private, so only stewards, Meta sysops, and global sysops can view them. #18 blocks certain repeated HTML tags commonly used by spambots. #19 blocks alll external links, other than a few safe websites (i.e., social media or Miraheze, for example), and a few other exceptsions, by non-autoconfirmed users [18:31:37] s/exceptsions/exceptions [18:31:37] dmehus meant to say: @Lake, yeah those are private, so only stewards, Meta sysops, and global sysops can view them. #18 blocks certain repeated HTML tags commonly used by spambots. #19 blocks alll external links, other than a few safe websites (i.e., social media or Miraheze, for example), and a few other exceptions, by non-autoconfirmed users [18:31:43] so the html tags are really that common [18:31:58] @chrs, yeah [18:33:08] Should mention that #19 only applies to User namespace pages [18:45:31] talking about userspace... [18:45:44] is there a way to prevent users from using specific templates on user pages? [18:46:01] (or specific functionality of a certain template) [19:00:15] either abusefilter or checking the namespace from the template [19:00:23] depends on what you're trying to do [19:11:21] it's because I have a lot of templates storing data to Cargo tables. I wish users would not be able to use these templates on their userpage [19:11:30] (plus also, a lot adding categories as well) [19:18:29] Hrm, if they are allowed to update the templates I can see why that can be a problem.. [19:19:16] Er.. not update the templates, I mean the cargo tables. [19:19:31] So you get junk entries in the tables? [19:19:48] you could include a check in the templates for if they're in userspace [19:20:18] take a look at the code for https://en.wikipedia.org/wiki/Template:User_other [19:20:18] [WIKIPEDIA] Template:User other | "" [19:20:27] yeah, I'm planning to query some specific things, then in the middle there's random user pages, lol [19:20:57] oh I thought of that, I don't remember how it works exactly on Cargo, but I will check it [19:21:31] Hello neoweb! If you have any questions, feel free to ask and someone should answer soon. [19:21:33] So you just use that template anywhere in the template? [19:21:40] how do i donant [19:21:42] donate [19:21:50] i just requested a wiki, do you know how long will take? [19:22:07] though there's a decent change it won't work since cargo uses parser functions [19:25:07] Having the entire cargo store within the other page part might not work? [19:25:17] donate* [19:25:34] found it [19:25:36] https://meta.miraheze.org/wiki/Donate [19:25:37] [ Donate - Miraheze Meta ] - meta.miraheze.org [19:25:44] πŸ™‚ [19:25:48] you mean a separate page for the #cargo_store and #cargo_declare? [19:26:08] neoweb: request time depends, it can take from a few minutes or a few hours [19:26:49] (usually, of course, sometimes, it can take more than that because wiki creators are not available for a variety of reasons) [19:27:19] k [19:27:22] No I mean like {{user other | User page text | Having the entire cargo store here }} [19:27:22] Thanks! [19:27:39] would that even work [19:28:05] it'd probably not work, since both arguments will still get parsed [19:28:20] Even on user pages? [19:28:21] don't know enough about cargo to know how it reacts to that [19:28:58] yeah both arguments to the template would be parsed and then fed to the template [19:29:43] So what it returns and what it actually does wouldn't matter I suppose? [19:30:52] well, I think there should be already a default way to disable certain features on userpages [19:39:28] Can you use namespace in an if statement somehow? [19:41:07] I think a switch works with a magic word [19:41:45] Was thinking if you could have the cargo store within switch or if or whatnot.. [19:41:54] or if that would still get parsed. [19:42:10] Unless there is a better solution. [19:42:27] πŸ€” I don't know exactly, I know that the pipe characters with Cargo's transclusions have a different behaviour [19:43:22] I think, of course, I never investigated this too far [19:44:30] Worth checking I suppose if you regularly see people using the template on user pages and having that add junk entries to the database(s) [19:44:47] Or enough that it becomes an issue. [19:46:05] I mean testing a template in a sandbox is one thing, but you'd generally don't want that to add stuff to the database. [19:47:57] I will ask on the MW server to see if anyone knows something [19:48:15] best of luck [19:55:22] If you come up with anything useful please do share. I'm reading what is posted on the mediawiki discord though. I do test templates in my sandbox sometimes, but if it's one using cargo I think I rather make a copy of the template and remove the cargo stuff from the test template. [19:55:49] We started using cargo in one template yesterday. [19:56:53] The plan is to use it in more places. [20:06:52] @Blackwolfe I also asked on the Cargo talk page to see if there's a way to just disable the storing for certain namespaces [20:07:08] That would be great if that was possible. [20:07:19] https://www.mediawiki.org/wiki/Extension_talk:Cargo#Disable_storing_on_User_namespace [20:07:19] [ Extension talk:Cargo - MediaWiki ] - www.mediawiki.org [20:31:43] yeah, no.. couldn't get it to work properly [20:44:14] Or wait, perhaps I did.. [20:45:21] It did generate an entry from a test page.. but not from using the same template in my sandbox. [20:46:30] But if I remove the entire ifeq it does generate an entry from my sandbox [20:47:10] This was using {{#ifeq:{{NAMESPACE}}|User|| before cargo store [20:47:22] @Lake [20:47:55] (and ending the ifeq with }} naturally after cargo store) [20:47:57] πŸ€” interesting [20:48:01] I will test this later [20:55:59] It didn't work at first because.. I thought.. because lol.. I accidently used the original template instead of the test template.. so the entries were added to the regular database πŸ˜› [20:56:27] instead of Databasetest [21:20:59] apparently it's also possible to query data for specific namespaces [21:21:05] only for* [21:55:37] Oh [21:55:40] Well that's useful. [23:52:04] Hello Anjiru! If you have any questions, feel free to ask and someone should answer soon.