[00:31:32] as arawynn is going with not seeing a basis to decline, I also see no basis where it is something we cannot or distinctly should not host; if that is the form that works for them and they are aware of the limitations (this alone would be cause to message about and have them affirm before approval), then I see no reason not to proceed [00:31:45] it is indeed not the optimal medium but hey [00:32:20] have mused about an essay of mediawiki alternatives for more distinct use cases where a wiki might not be the solution people are looking for [00:32:24] It's actually less of a burden/nuisance than global user page micro edits [00:33:08] leafy, na and the next top five all deciding to go wild on login edits at once [00:33:13] (to best of my understanding, and yes I did test when we were patching that performance issue) [00:35:38] Also should go without saying, but don't attach your account to a bunch of wikis just to do it for fun [00:35:47] [1/2] Eh? Better then my micro edits last time that caused skye to add an ratelimiter? [00:35:47] [2/2] That is unexpected [00:35:51] It has some very unpleasant side effects on multiple things [00:36:04] heh, [00:36:07] What side effects does it have [00:36:19] I wasn't aware of it [00:37:06] Try pulling me up on centralauth, it's very instructive [00:37:29] for some reason i discovered on centralauth i'm blocked on some random private wiki [00:37:57] Yep, it happens [00:38:09] People see an action from a global volunteer and say, oh no, it must be a hacker [00:39:34] Yep, the patch improved performance on that, now we're not spooling up 2-12 jobs for each wiki the person is attached to every time they make an edit on their page on loginwiki [00:40:07] It's a little sad because I would think that I wouldn't be blocked anywhere but oh well [00:40:21] The more wikis one is attached to, the longer things that require hitting centralauth take. [00:40:36] Attaches, logging in, adding user rights, anything that vets against global groups [00:41:15] I will sometimes get errors just because it takes too long for a task to complete. It does eventually go through, but it also means I usually need to check the work [00:43:11] well no, we are, it's just that previously it was every wiki, not just every wiki the person is attached to [00:43:25] Yeah I get it, if I saw my wiki get edited by someone unauthorized without other info, I would think the wiki host got hacked lol [00:43:28] meant to press reply to this one [00:43:41] Oh dang, I thought we also reduced the count of jobs created per-wiki [00:44:09] maybe we did but I thought the main performance thing was only updating it on wikis you're attached to [00:44:13] We did [00:44:18] Every wiki??? No wonder skye wanted me off so bad [00:44:22] Yeah, that was definitely the biggest saver - not hitting every wiki [00:44:38] We prevented it hitting every single wiki rather than ones just attached I think. [00:45:39] But yeah it still hits all wikis you are attached to. [00:45:50] I was once blocked with the only reason given being 'scary' [00:46:02] That was fun [00:46:11] Which is funny, because can't you unblock yourself anyway? [00:46:12] That would be funny [00:46:33] Wait can you unblock yourself lol [00:46:37] Oh, absolutely. They didn't understand who I was or the level of access I have. [00:46:43] We got it sorted in the end. [00:46:54] I wouldn't arbitrarily unblock myself though. [00:46:58] Yeah. Since I can block everywhere [00:46:59] Yeah you have all access to all MW interface [00:47:05] Including the scary CheckUser UI [00:47:31] @notaracham also what do you prefer, Investigate or CheckUser feature in the CU UI [00:51:13] Assuming you're allowed to say it [00:53:30] Oh, that's not NDA bound at all. [00:53:43] (UI preference) [00:54:04] I primarily use CU, mostly because it has a few niceties investigate doesn't. [00:54:21] I also appreciate a quick and easy CIDR rangefinder that affords me easy copy and past [00:54:42] I should give investigate some more testing though [00:54:57] PixDeVl has been a fan of it [02:44:26] [1/2] I usually end up using both, I start with Investigate and use Check when I wanna dig more or expand my search, since Investigate makes it easy to rapidly expand your search to related IPs and users to draw a really big list of connected things, and you can quick add items that the search brings up to the query, but you can't add arbitrary entries (like say a r [02:44:26] [2/2] ange based off the data), so for that I open a CheckUser page [03:19:04] is it just me or is https://meta.miraheze.org/wiki/Steward_requests/Restricted_changes messed tf up [03:21:46] It needs some TLC, yes [03:22:02] [1/2] Unclosed template? [03:22:02] [2/2] https://cdn.discordapp.com/attachments/1225560610628964423/1549258968969384016/image.png?ex=6aaa0b5a&is=6aa8b9da&hm=350b48e0dd2e450c961d5cacd1ae841c3359d3779cd42fcfb97b34eb41b79851& [03:22:28] [1/2] Yeah BeeBot messed this one up [03:22:29] [2/2] https://cdn.discordapp.com/attachments/1225560610628964423/1549259080361840750/image.png?ex=6aaa0b74&is=6aa8b9f4&hm=9aa7644aabd0a902ecae06690387e04dfc7ccce43b93bbb7c42a9ef1184b60cf& [03:22:31] Diving into the count code, I seem to remember it looks for pending, on hold and a very rowdy version of open [03:23:46] Oh, yeah, beebot isn't great at handling extremely malformed situations [03:24:44] this page makes me cry [03:26:01] [1/2] I think it's also showing me outdated pages. Like I made a response to this request but I'm only seeing it sometimes when I refresh/purge the page. [03:26:01] [2/2] https://cdn.discordapp.com/attachments/1225560610628964423/1549259969726124172/image.png?ex=6aaa0c48&is=6aa8bac8&hm=0e06708ee36ae9c105b8e7ac305690717056ad986d8725a362d28918dc34a426& [03:26:17] i think we should jsut [03:26:21] burn it to the ground [03:28:37] Burn it with tons of Wiki Gasoline™. [04:38:16] 😱 [10:29:19] no just the entire page got duplicated [12:30:28] Oh now I see it lol. No one noticed and just kept piling onto it. [18:05:34] [1/2] I feel like CU is more like targeting suspects individually, and Investigate is where multiple users is possibly the main suspect imo [18:05:34] [2/2] I hope I explained this right [18:06:47] this has gotta be the joke of the year...the game name is limbus company not whatever that gibberish is... [18:12:36] The Limbus Company wiki is on wiki.gg, that's a different game. [18:14:54] Ohhh, I see so it's a different game [18:15:43] The name is very suspicious similar in spelling but I won't comment more on it [18:55:12] [1/2] Could I get feedback on these practice request numbers please? 15, 17, 18, 19, 21 [18:55:12] [2/2] https://meta.miraheze.org/wiki/User:Amanda_Uranium-Explosion/Practice_Wiki_Requests#12_September_2026 [21:10:44] [1/2] I'm interested in becoming a reviewer, so I poked through this to see generally what form the practice reviews might have, and I had a question relating to PR20: [21:10:44] [2/2] Documenting music is clearly something that a Miraheze wiki would be allowed to do (otherwise the music category on the request form would be rather odd). Documenting music by one creator is too narrow but clearly trying to document all music (or even just music in a genre) would be too broad, so what would an acceptable topic/scope be? [21:13:06] depends on artist. e.g. [[mh:ayeshaerotica]] exists [21:13:07]

[21:14:53] in what way does it depend on the artist? [21:15:55] if the artist has enough writable content I guess? I'm basing this off of some youtuber wikis I've seen, where if they actually have enough lore then a wiki is reasonable [21:47:40] a clear body of work is the simplest way I can put it [21:48:13] in limited examples I do think a genre would be fine [21:48:40] music in general the problem with that to me is mainly that it stands a very high risk of just being aimless in terms of how it does the coverage [21:49:06] but each of these can touch on distinct things that do not conflict and are reasonable topics to get into given confidence in the presentation [21:51:33] [1/2] in general elevated scrutiny should be to acquire that confidence or to suss out known problematic approaches, and this is a feel that realistically only comes over time despite efforts like [[Help:Restricted Wiki Topics]] spelling out many aspects and ongoing work to cover others which are not restricted but do have caveats which I've started to cover in [[User:Raidarr/Request wik [21:51:33] [2/2] i primer]] (hope the link works). I do want to add a bit more to restricted wiki topics to distinguish wikis on content creators in particular, and to highlight the 'body of work' element [21:51:34]

[1/2] [21:51:34]

[2/2] [21:51:44] alright it was wrong lets see what I named it [21:52:53] there we go [22:09:23] I recommend using https://vylet.wiki/Vylet_Pony_Wiki as the go-to example for music wikis unless you want to throw people off with R17.9 content lol. [22:17:05] [[mh:vyletpony]] [22:17:06]

[22:17:28] yeah that's easier to recommend lmao [22:23:37] yeah, I did not look too closely at the link and was caught off guard