[00:08:13] Good to know. [00:10:45] <⁦raidarr⁩#6550> realistically much of cvt activity concentrates around certain types of wikis or just individual wikis [00:11:28] Are most of the offenders you see LTAs? [00:11:56] <⁦raidarr⁩#6550> [1/2] leading venues are japanese speaking wikis with a unique group of dedicated vandals that we have a double whammy to deal with (language barrier and their determination), AVID (one of our most active wikis community wise with a particular series of repeat vandals) and reception wikis (though less so than before, also with a core of vandals, several of whom have returned to dorm [00:11:56] <⁦raidarr⁩#6550> [2/2] ancy) [00:12:12] <⁦raidarr⁩#6550> you'll notice the common theme is repeat vandals so yes, they are most common and most irritating to deal with [00:12:14] So that's basically a yes [00:12:56] Hmm.. Japanese vandals.. that's odd/new to me. [00:13:15] Yeah, most offenders are LTAs [00:13:31] one off vandals do exist but they're not a large number [00:13:38] <⁦raidarr⁩#6550> one-off minor cases requiring a lock or sanction are comparatively a bit rare; spambots had an uptick though as noted before agent likely destroyed most of their options. The spam thing comes down to our captcha troubles; the previous captcha system straight broke and the current one is so-so in effectiveness [00:14:14] <⁦raidarr⁩#6550> the japanese vandal group is one of the nastier ones and it's also a case where the ip work is tricky, taking them out effectively can wipe out huge regions [00:14:25] Yeah.. not surprised. [00:14:38] But when dealing with ranged blocks, you tend to run into problems regardless. [00:14:40] <⁦raidarr⁩#6550> though that's what it took to deal with an italian lta in the end [00:15:46] <⁦raidarr⁩#6550> yeah, I think that covers most of what cvt has to deal with at a given time [00:16:37] <⁦raidarr⁩#6550> comparatively the lta issue is lighter than it was last year I would say, at least some of the more prolific ones [00:16:55] <⁦raidarr⁩#6550> though a few are still determined as noted [00:17:24] No GIPBE group? [00:17:26] Interesting. [00:17:49] I guess with private wikis and everything it might not be as easy to implement that? [00:18:20] <⁦Agent⁩#3928> GIPBE does exist [00:18:26] <⁦Agent⁩#3928> [[GIPBE]] [00:18:26] https://meta.miraheze.org/wiki/GIPBE [00:18:27] <⁦Wiki-Bot⁩#2998> [00:18:28] [url] Global IP block exemption - Miraheze Meta | meta.miraheze.org [00:18:39] Huh.. I didn't find it in LGR so I guess I was looking in the wrong place. [00:18:52] Ah [00:19:12] [[Special:GlobalGroupPermissions]] is the global equivalent of LocalGroupRights [00:19:12] https://meta.miraheze.org/wiki/Special:GlobalGroupPermissions [00:19:25] Ah, I see. [00:19:39] I was using ListGroupRights which in the past I assumed covered that. [00:20:09] Christ.. only three GIPBEs? [00:20:20] Interesting. [00:20:30] Two could probably be removed tbh [00:20:36] or maybe even all three [00:20:43] Could definitely remove Revi's bot lol [00:20:58] No idea who added that but lol [00:23:21] SPF decided to step down a while ago it looks like. [00:23:52] yeah, unfortunately [00:26:07] While I'm at it, I'll take a look over all of the policies and see what's changed in depth. [00:27:17] <⁦raidarr⁩#6550> primarily you'll see changes regarding conduct and content and depth regarding practices which have been tuned to miraheze and not pulled right off wikipedia [00:27:21] [[Global policies]] lists all policies [00:27:21] https://meta.miraheze.org/wiki/Global_policies [00:33:42] Read it all. [00:34:02] Seems pretty straightforward, but there's a few things I find a bit.. weird. [00:34:13] Not sure why sharing accounts is allowed and uh [00:34:34] https://meta.miraheze.org/wiki/Global_Conduct_Policy#Sanctions [00:34:35] [url] Global Conduct Policy - Miraheze Meta | meta.miraheze.org [00:34:45] That leaves a lot to be desired when it comes to consistency. [00:35:00] <⁦raidarr⁩#6550> sharing is allowed I suppose because there hasn't been enough of a reason to deny that liberty [00:35:02] When it comes to global policy, it should be global. [00:35:24] It shouldn't be global with local administration discretion. [00:36:21] <⁦raidarr⁩#6550> gcp is a volunteer expectation for any role, local or global; in general it is preferred to deal with issues locally and global intervention only occur if strictly necessary [00:36:26] It ends up going from global policy to being "recommended community guidelines" which I don't think is necessarily great with the sanctions bit worded as it is. [00:36:49] That's the overall conduct policy, though.. not the one for volunteers? [00:37:12] <⁦raidarr⁩#6550> oh I see [00:37:35] <⁦raidarr⁩#6550> I was thinking of the volunteer policy and code of conduct, I tend not to think of 'gcp' much [00:37:37] Yeah, you can't make a document of policy like this and have it be wish-washy. [00:37:59] It's too open to interpretation and frankly I feel like that sanctions part should be amended if nothing else. [00:38:09] That's just a friendly recommendation after looking over it. [00:38:18] <⁦raidarr⁩#6550> always room for amendment [00:38:23] Of course :) [00:39:07] <⁦Agent⁩#3928> Ideally, local admins should enforce the GCP but Stewards and Global Sysops can and primarily do enforce it [00:39:32] <⁦Agent⁩#3928> The section for some reason doesn't reflect that Stewards/GS enforce it too [00:39:33] <⁦raidarr⁩#6550> well I have to admit I pretty much had forgotten about it as it's a bit of an odd extension of what is really stuff you'd expect from the code of conduct [00:40:20] <⁦raidarr⁩#6550> I'm pretty sure the reason is in part to deal with certain things that were happening both on the part of local functionaries and certain behaviors which weren't addressed strongly enough under standard coc [00:40:34] https://meta.miraheze.org/wiki/Responding_to_threats this seems okay [00:40:36] [url] Responding to threats - Miraheze Meta | meta.miraheze.org [00:40:43] I like how you all include resources [00:40:47] <⁦raidarr⁩#6550> that is a bit of an old one [00:40:57] but it could use an update [00:40:58] yeah [00:41:20] <⁦raidarr⁩#6550> yeah, copied from wp in 2020 and only subject to minor modifications since [00:41:37] threats to life, limb, property or regarding child abuse only [00:41:39] <⁦raidarr⁩#6550> to me 'old' is probably new since I came smack in the mid of 2021 [00:41:40] <⁦Agent⁩#3928> Patches welcome [00:41:46] do you all not handle DMCA? [00:42:04] <⁦raidarr⁩#6550> copyright comes through cvt typically, in certain cases directly to t&s [00:42:19] that should be tns-specific in my opinion [00:42:33] <⁦raidarr⁩#6550> t&s tends to defer non-urgent enforcement to cvt [00:42:41] hmm [00:43:03] <⁦raidarr⁩#6550> they tend to deal with serious cases from larger entities, which is a bit rare [00:43:10] is the t&s email a priority inbox? [00:43:13] <⁦raidarr⁩#6550> most commonly you have more informal reports [00:43:30] <⁦raidarr⁩#6550> it's reviewed on the regular by t&s, which currently consists of two people [00:43:37] generally CSAM should always be handled by t&s which it looks like you all go with [00:43:39] <⁦raidarr⁩#6550> agent is a responder and owen is the main shot caller [00:43:40] which is good [00:44:11] I mean.. two is two more than it was years ago when there were zero [00:44:15] <⁦raidarr⁩#6550> pretty sure it was the same way back when but you notice people overlap in roles significantly [00:44:23] <⁦raidarr⁩#6550> at one point it reached a whopping 3 [00:44:34] <⁦raidarr⁩#6550> but that was the transition period of one going out and agent just getting in mostly [00:45:03] I'm going to be honest, there should be more T&S responsibilities and less of that should be going to cvt [00:45:16] volunteer or not, some things require people with that kind of expertise [00:45:24] <⁦Agent⁩#3928> Like what, for example? [00:45:37] <⁦Agent⁩#3928> ts@ gets forwarded to our emails which get checked frequently [00:45:44] <⁦raidarr⁩#6550> t&s is sufficiently small and mainly just due to how it works, really just wants cvt to handle things - which, unless they have stronger legal implications, is typically done and done rather well [00:45:50] anything that is related to legal matters should be t&s and not deferred to cvt [00:45:54] <⁦Agent⁩#3928> I get my emails on my phone so I see them as they come in [00:46:05] <⁦raidarr⁩#6550> owen will still deal with any substantial legal matters which are quite rare in the ts capacity [00:46:19] <⁦raidarr⁩#6550> certain things like dealing with underage do go through ts exclusively [00:46:19] <⁦Agent⁩#3928> I think the only legalish thing CVT handles is copyright issues where the reporter isn't the copyright holder [00:46:32] <⁦raidarr⁩#6550> yeah, that's the most common thing and also the one easiest to delegate [00:46:33] cvt as it was initially implemented was only meant for vandalism/spam handling [00:46:38] hmm.. alright [00:46:41] <⁦raidarr⁩#6550> cvt has grown in role [00:46:59] as long as people aren't dealing with things out of their element [00:46:59] <⁦raidarr⁩#6550> first became old cvt plus lock, then some more proactive gs came along [00:47:05] <⁦raidarr⁩#6550> that doesn't typically happen [00:47:06] <⁦Agent⁩#3928> s\/CVT/Stewards [00:47:21] <⁦Agent⁩#3928> CVT doesn't handle copyright [00:47:23] <⁦Agent⁩#3928> Stewards do [00:47:26] <⁦raidarr⁩#6550> realistically anything with complexity is handled by stewards directly or in communication with them [00:47:35] <⁦Agent⁩#3928> CVT is primarily a vandalism thing still [00:47:38] <⁦raidarr⁩#6550> and yeah, stewards fire the guns on copyright [00:47:43] okay, stewards handling with copyright makes more sense than cvt [00:47:45] was about to say [00:47:45] <⁦Agent⁩#3928> proposals to expand it's scope have been rejected left and right [00:48:00] <⁦Agent⁩#3928> like the proposal to let them rename users or also be able to edit the interwiki table [00:48:07] I mean, when it's the same ~20 people, shit doesn't go anywhere [00:48:10] <⁦raidarr⁩#6550> gs does have a much larger range of theoretical scope than old cvt [00:48:20] <⁦raidarr⁩#6550> old cvt is basically what global rollbacker is now [00:48:42] pretty sure cvt had global blocks when it was created [00:48:49] at least I remember it having that [00:48:57] <⁦raidarr⁩#6550> I heard they either didn't have it or lost it at some point before GS was created [00:49:01] but take it with a grain of salt, it's been 6 years [00:49:21] <⁦raidarr⁩#6550> I might well be misremembering since that all happened before I came along [00:49:35] yeah, I'm talking about late 2016/early 2017 [00:49:51] <⁦raidarr⁩#6550> when I came in the 'picture' of stewards and cvt was far different from 2019-2020, let alone 2017 [00:50:04] <⁦raidarr⁩#6550> heck, it's different now than it was in 21/last year [00:50:05] well, sure [00:50:11] <⁦Agent⁩#3928> Yeah, I think original CVT didn't have the ability to lock [00:50:12] miraheze was extremely small back then [00:50:15] <⁦raidarr⁩#6550> quite a few radical changes in 2020 in particular [00:50:19] <⁦Agent⁩#3928> dunno about being able to globally block [00:50:26] we had global block I think but not locking perms [00:50:29] I can check [00:50:42] <⁦raidarr⁩#6550> might be what you were remembering? [00:51:52] nah, we had gipbe, not gb [00:51:57] jesus [00:52:08] granted [00:52:11] this was a long time ago [00:52:15] newly created group [00:53:20] https://meta.miraheze.org/w/index.php?title=Special:Log&logid=28436 [00:53:21] [url] All public logs - Miraheze Meta | meta.miraheze.org [00:53:32] <⁦raidarr⁩#6550> in terms of scope there's a big broadening between global rollbacker which is what you would imagine with the phrase cvt, global sysop which ranges from a higher powered cvt person to a backup admin with reach on a majority of wikis if required slightly outside of just vandalism, and steward which includes but of course is far broader than cvt [00:53:43] yeah, well [00:53:55] it's more akin to wikimedia now [00:54:14] <⁦Orduin⁩#1491> local group had lock perms [00:54:14] [url] local cvt group · miraheze/mw-config@861ffa6 · GitHub | github.com [00:54:16] <⁦raidarr⁩#6550> with important caveats, sure [00:54:31] I didn't say exactly like it [00:54:34] I meant more than it was haha [00:54:51] <⁦Agent⁩#3928> their layout is useful [00:55:12] christ [00:55:20] I never checked github, even back then [00:55:59] <⁦Orduin⁩#1491> Only real place to check for most restricted permissions [00:56:12] <⁦raidarr⁩#6550> lots to learn from wikimedia [00:56:42] <⁦raidarr⁩#6550> as long as we know where to stop and look at topically relevant places like fandom or other wiki farms, though fandom is really the only big inspiration (both for what to do and not to do :p) [00:57:08] honestly one thing I noticed that I would copy from fandom is bot-global when looking through [00:57:19] giving bots GIPBE instead is dumb [00:57:24] <⁦raidarr⁩#6550> any other wiki farm is either highly specialized or far more obscure / suffers significant drawbacks in comparison [00:58:00] have it for global sysops' bots and stewards' bots [00:58:39] <⁦Agent⁩#3928> I've thought about renaming the `global-flood` group to `global-bot` (as everyone in the group is technically a bot) and making an RfC to ask what the community thinks about community appointed global bots [00:58:58] not a bad idea [00:59:02] global flood is confusing [00:59:34] but either way you look at it, those bots should probably only be bots of stewards, t&s and maybe global sysops. [01:00:55] assuming bot permissions aren't flagged in countervandalism watch channels which I'm guessing they're not, it's an avenue for abuse and it can cause a lot of abuse unnoticed if given out like candy [01:01:21] to go unnoticed, even [01:02:00] <⁦Agent⁩#3928> not really many Stewards/GS/T&S bots though [01:02:07] @Agent But it only has flood and not other bot permissions [01:02:26] <⁦Agent⁩#3928> a global bot should ideally be a bot that many wikis use [01:02:35] <⁦Agent⁩#3928> not just a bot a few people use [01:02:36] I'm saying those people's bots are the ones it should be restricted to, not that they have them already. [01:02:57] Yeah if many wikis use it then just let it run around everywhere and WITHOUT RC! [01:02:58] It shouldn't be something that can be requested normally, at least in my opinion. [01:03:02] Global autopatrolled but worse [01:03:18] <⁦Agent⁩#3928> well obviously a global bot should only operate where it has permission [01:03:29] Then they can just add the bot group there [01:03:29] <⁦Agent⁩#3928> if it operates anywhere it doesn't then that'd be grounds for revocation [01:03:41] Yep [01:03:54] The only purpose of a global bot group would be to have a bot that runs everywhere without the permission of local communities [01:04:15] <⁦Agent⁩#3928> having a bot be flagged on multiple wikis that request it can be tedious [01:04:25] <⁦Agent⁩#3928> my bot has the `bot` flag on like 10+ wikis [01:04:49] Ticking one box can be tedious? [01:05:05] Also that's a GOOD thing because it signifies that 10+ wikis are allowing it to operate [01:05:06] <⁦Agent⁩#3928> if assisting new users, yes [01:05:13] Global bots would only be used on request of local administration, by t&s or to mass delete vandalism/remove spam. [01:05:25] It shouldn't be used often at all. [01:05:27] Auto granting it permission everywhere but still requiring local approval is the worst of both worlds [01:05:31] Pick one or the other [01:05:31] <⁦Agent⁩#3928> my bot has helped many wikis move over from other hosts and having to explain MediaWiki lore to admins is tiring [01:06:03] Requiring local approval for use outside of what's described above. [01:06:11] Not requiring local approval in general. [01:06:31] Honestly they shouldn't even be used outside of those conditions. [01:06:31] <⁦Agent⁩#3928> well typically spam is isolated to one wiki [01:06:40] <⁦Agent⁩#3928> I haven't really seen any huge cross-wiki spam [01:06:55] <⁦Agent⁩#3928> usually if I'm nuking spam, I rarely need to grant myself bot [01:07:10] Yeah, and having a global flag beats giving bot permissions per-wiki for bots dealing with CVT stuff. [01:07:49] Hmm.. I just realized that the groups that would use said bot would already have implicit permission, no? [01:08:03] I guess it's not as useful if that's the case. [01:08:31] I'm just saying that anything beats giving a bot GIBPE haha [01:08:47] It's absurd. [01:09:14] https://meta.miraheze.org/wiki/Special:GlobalUsers/global-ipblock-exempt [01:09:15] [url] Global accounts list - Miraheze Meta | meta.miraheze.org [01:10:33] at the very least renaming the global flood group might be helpful [01:15:12] I'm going to go do other things, it was nice chatting with you all. [01:16:10] <⁦Agent⁩#3928> See you 👋 [01:44:06] <⁦BWM⁩#6978> yay [01:44:59] <⁦BWM⁩#6978> <:InterwikiMH:945091223176228894> [01:53:50] <⁦BWM⁩#6978> @Agent shouldn't `botsphab` be removed from the interwiki table? [01:54:02] <⁦BWM⁩#6978> as it's now closed [01:56:03] <⁦Agent⁩#3928, replying to ⁦BWM⁩#6978> it can be removed once the project winds down officially I guess [01:56:14] <⁦Agent⁩#3928> but for now, their Phabricator instance is up and running [01:56:17] <⁦BWM⁩#6978> got it [01:57:49] <⁦Lake⁩#1494> <:ThinkerMH:912930078646730792> [02:01:22] What does that have to do with it? [02:08:31] <⁦BWM⁩#6978> what does what [03:24:02] <⁦Agent⁩#3928> but for now, their Phabricator instance is up and running [03:24:13] Arguably it never should have been added at all, but the shutdown is a convenient time to remove it [03:37:39] <⁦Legroom⁩#2748> morning, damn that's a lot to read [05:15:07] <⁦General Nuisance⁩#1200> [1/4] just got a message while trying to upload an audio file (solfege sung by a synthetic voice for an article) [05:15:07] <⁦General Nuisance⁩#1200> [2/4] "The database is currently locked to new entries and other modifications, probably for routine database maintenance, after which it will be back to normal. [05:15:07] <⁦General Nuisance⁩#1200> [3/4] [05:15:08] <⁦General Nuisance⁩#1200> [4/4] The system administrator who locked it offered this explanation: The primary database server is running in read-only mode." [05:15:14] <⁦General Nuisance⁩#1200> does anyone know what this might mean? [05:15:35] <⁦Agent⁩#3928> @Site Reliability Engineers db121 perhaps? ^ [05:18:41] <⁦Reception123⁩#2349> that soon? let me checkl [05:18:59] <⁦General Nuisance⁩#1200> I'm guessing db121 is a little bit of a problem child [05:19:09] <⁦Agent⁩#3928> indeed [05:19:14] <⁦Agent⁩#3928> it eats too much memory [05:19:16] <⁦Reception123⁩#2349> fixed [05:19:18] <⁦Agent⁩#3928> never satisfied [05:19:19] <⁦Agent⁩#3928> lol [05:19:38] <⁦General Nuisance⁩#1200> hopefully wav files that are abt ~20sec in length aren't TOO much of a server load? [05:19:47] <⁦Agent⁩#3928> shouldn't be, no [05:19:48] <⁦General Nuisance⁩#1200> I can switch them to MP3s if needed [05:21:58] <⁦Legroom⁩#2748> for dome reason I thought ogg is standard for MW [07:04:49] <⁦max20091⁩#7318, replying to ⁦Legroom⁩#2748> Ogg is the old standard for open source audio format [07:07:56] <⁦max20091⁩#7318> Opus should be the latest format now but Safari (especially iOS) is so bad that it can't run that file [08:37:36] <⁦Legroom⁩#2748> ah [08:38:28] <⁦Legroom⁩#2748> I remember now that some wikis on FANDOM had ogg files because mp3 wasn't allowed [10:49:49] <⁦Legroom⁩#2748> I forgot #ifexist is bugged and now I have red file links in wanted pages 🤦 [11:11:11] <⁦Legroom⁩#2748> fixed it, hope I won't forget solution again (use #ifexist as outcome of blank #if parameter, not opposite, then inside #ifexist default result can be used) [13:27:15] <⁦CZghost⁩#2894> [1/3] If I wanted to export my wiki from Miraheze in order to import it to Wikimedia backed servers, I suppose the license should be compatible? Like, there is an unofficial Interslavic Wikipedia currently hosted on Miraheze (I say unofficial, because Interslavic doesn't have an approved ISO code yet, which makes it inelligible to get an official language version approved by WMF - h [13:27:15] <⁦CZghost⁩#2894> [2/3] owever that might change in future, once the ISO code registration proposal is approved). The purpose of hosting it on Miraheze is solely to give some breeding ground for Wikipedia in Interslavic language. Now, that wiki is not mine (I don't actually have my own wiki on Miraheze), but if the ISO code registration is approved and WMF approves eligibility of this language for a [13:27:16] <⁦CZghost⁩#2894> [3/3] new official language version of Wikipedia, current wiki community on Miraheze might actually want to migrate to the official site. [13:51:51] <⁦Legroom⁩#2748> interesting [14:19:49] <⁦Agent⁩#3928, replying to ⁦CZghost⁩#2894> Yes, licensing should probably be compatible. You can change the license via ManageWiki [14:20:05] <⁦Agent⁩#3928> But that's cool to hear, a breeding ground for a future WMF project [14:28:21] <⁦CZghost⁩#2894> Oh, right. [14:28:29] <⁦CZghost⁩#2894> Thanks 🙂 [16:05:53] <⁦Ice Mace⁩#2538> [1/2] Hello. [16:05:53] <⁦Ice Mace⁩#2538> [2/2] Does anyone know how to remove extra metadata of an image? [18:42:17] <⁦Colleiflower⁩#2020> yes [18:42:30] <⁦Colleiflower⁩#2020> https://exifcleaner.com/ [18:42:31] [url] ExifCleaner - FREE Desktop app to clean image metadata | exifcleaner.com [18:46:41] <⁦Fiddlestix⁩#9401> quite a great tool [18:54:16] <⁦WellTemperedClavier⁩#3840> Question: I'm currently ranked as an admin for the DariaWiki. I'm thinking about stepping back from wiki management, and would like to be made a user. Is that something I can set myself, or do I have to do it through here? [19:00:26] <⁦Agent⁩#3928, replying to ⁦WellTemperedClavier⁩#3840> If you're only an admin, you'd have to ask a bureaucrat to remove your rights. If you're a bureaucrat though, you'll need to ask a Steward to remove your rights at [19:00:29] [url] Stewards' noticeboard - Miraheze Meta | meta.miraheze.org [19:00:39] <⁦Agent⁩#3928> If you're just a normal admin, you can also ask we remove your rights in the above link [19:25:14] <⁦WellTemperedClavier⁩#3840, replying to ⁦Agent⁩#3928> Thanks. I'll go ahead and ask the bureaucrat [20:22:57] <⁦Ice Mace⁩#2538, replying to ⁦Colleiflower⁩#2020> Thanks [20:23:19] <⁦Colleiflower⁩#2020> np [21:04:37] Good evening. [21:09:51] hi Samuel_. I saw your DM the other day but you left [21:09:54] will reply [21:10:03] Sounds good :) [21:18:24] <⁦Fiddlestix⁩#9401> congrats @BWM [21:35:58] Hello ExiledRival! If you have any questions, feel free to ask and someone should answer soon. [21:50:20] If anyone can help round up Reception, please tell him we're stuck between domains. [21:50:37] <⁦Agent⁩#3928> @Reception123 [21:58:08] <⁦Reception123⁩#2349> Unfortunately I must get going now. I have noticed that unfortunately but efforts to fix haven't seem to have worked. [21:58:29] <⁦Reception123⁩#2349> @Agent if you could perhaps it's best to try reverting the custom domain for nenawikiwiki to nenawiki.org [21:59:02] <⁦Agent⁩#3928> will look [21:59:59] <⁦Agent⁩#3928> What exactly is the issue? [22:00:07] <⁦Agent⁩#3928> kb.nena.org loads fine [22:01:20] It just started working. [22:05:46] <⁦Agent⁩#3928> Great to hear that [22:05:58] <⁦Agent⁩#3928> probably a cache issue it seems [22:12:42] Can you get to ndgkb.nena.org? [22:16:36] Wiki not found when I put in the URL. [22:22:33] <⁦Agent⁩#3928> MikeV: should work now [22:22:45] <⁦Agent⁩#3928> That wiki was still configured to use ndg.nena.org [22:23:06] it works now, yeah. [22:23:08] YES! [22:23:34] Thanks. [22:26:19] <⁦Agent⁩#3928> No problem [22:26:25] <⁦Agent⁩#3928> sorry for the delay [22:49:51] Did something happen to the Extension ReplaceText that I'm sure was previously installed on our sites? [22:53:37] <⁦Tali64⁩#9984> I think it was broken because $wgCompressRevisions is enabled, so it may have been removed [23:01:14] Oh, no! We changed domains and have lots of links to update. I was counting on ReplaceText to help. Is there a similar replacement? [23:07:35] <⁦Gummiel⁩#0001> The Extension MassEditRegex is pretty much the replacement (As the name implies you need to know at least basic regex to use it) https://www.mediawiki.org/wiki/Extension:MassEditRegex [23:07:35] [url] Extension:MassEditRegex - MediaWiki | www.mediawiki.org [23:09:03] <⁦NotAracham⁩#0009> [1/2] Thankfully a user on our site has written a guide to its use that helps demystify that a bit: [23:09:03] <⁦NotAracham⁩#0009> [2/2] https://discord.com/channels/407504499280707585/407537962553966603/1084963715314634923 [23:09:19] <⁦NotAracham⁩#0009> Sorry, wrong link [23:09:20] <⁦NotAracham⁩#0009> https://meta.miraheze.org/wiki/User:Dimpizzy/MassEditRegex_Guide [23:09:24] [url] User:Dimpizzy/MassEditRegex Guide - Miraheze Meta | meta.miraheze.org [23:10:47] <⁦Gummiel⁩#0001> Heh, yeah I geuss a discord post link isn't that usefull over the bridge 😛 [23:11:07] <⁦NotAracham⁩#0009> Yep. Clipboard picked up the wrooooong thing [23:18:49] <⁦raidarr⁩#6550> massseditregex appears to be the somewhat more involved/painful version to use [23:18:58] <⁦raidarr⁩#6550> wish replacetext wasn't defunct [23:19:04] <⁦CosmicAlpha⁩#3274, replying to MikeV> FYI, I am working on a ReplaceText alternative that uses searchindex (like Special:Search) instead of oldtext table, which is compressed, and why ReplaceText doesn't work. No ETA on the extension and I am a bit busy with other things lately, but I hope to be able to finish it, hopefully not to long. [23:22:06] Thanks for the feedback! [23:22:45] <⁦CosmicAlpha⁩#3274> Though, I only started it yesterday, as when I was working on another searchindex task, I realised this can likely use that for it. So still a little ways to go, but hopefully should be able to finish it. [23:54:11] <⁦NFMiraheze⁩#2978> How do I add licenses to the photos already uploaded [23:57:07] Hello EzriGamer26! If you have any questions, feel free to ask and someone should answer soon. [23:57:43] why is my wiki still in review [23:57:55] its been minutes [23:59:29] <⁦NotAracham⁩#0009> [1/2] The average time to approve is hours to days, though we've generally been faster in recent months. [23:59:29] <⁦NotAracham⁩#0009> [2/2] Wiki creation is 100% driven by volunteers who provide their time for free, we are not available for every minute of every hour.