[00:54:06] [1/2] @janebuzjane – I can't replicate your bug with the soft hyphen hmmmm [00:54:07] [2/2] https://cdn.discordapp.com/attachments/615786602454581249/1491964459738988625/Screenshot_2026-04-10_at_01.52.45.png?ex=69d99bae&is=69d84a2e&hm=2f1663cc2bb47a5574d4b2c7cac1bddd0a4370e3bb4894a57ae532fc547cd5d8& [00:54:35] oh i used "" maybe thats why [00:54:57] hmm nope [02:05:41] [1/2] I gotchu - [02:05:41] [2/2] Watch it be something random with dpl again [02:06:20] [1/14] Relevant horrible code: [02:06:20] [2/14] ```{{#tag:{{#if:{{{notrack|}}}|div|table-progress-tracking}}| [02:06:20] https://meta.miraheze.org/wiki/%23tag:Template:%7b%7b%23if:%7b%7b%7bnotrack [02:06:20] [3/14] {{#DPL: [02:06:21] [4/14] |namespace = [02:06:21] [5/14] |uses = Template:Pet Infobox [02:06:21] [6/14] |category = Quaint Pets<&>Limited Pets [02:06:22] [7/14] |notcategory = Seasonal Pets [02:06:22] [8/14] |notcategory = Unobtainable Pets [02:06:22] [9/14] |include={Pet Infobox}:%PAGE%:image normal:obtained [02:06:22] [10/14] |table=class="article-table alignmiddle centerall sortable mw-collapsible mw-collapsed" style="width: 100%;",-,Pet,class="unsortable"¦Image,class="unsortable"¦Obtained«!-- [02:06:23] [11/14] |tablerow=--»\n¦-\n!scope="row" data-row-id="%PAGEID%"¦[[%%]],
[[File:%%|center|frameless|alt=%PAGE% thumbnail.|link=%PAGE%]]/span/center,%%«!-- [02:06:23] https://meta.miraheze.org/wiki/%25%25 https://meta.miraheze.org/wiki/File:%25%25 [02:06:23] [12/14] |resultsfooter=--»\n²{!}²-\n²{!}²+ Testing\n¦} [02:06:24] [13/14] }}|table-id=67956786785|header-label=Hat­ched|location=last}} [02:06:24] [14/14] ``` [02:10:08] If this does indeed happen to appear only when using this extension in ill-advised ways, please feel free to ignore it /gen [09:46:17] when pasting this into Special:ExpandTemplates I get `` [09:49:27] which means it might be an issue with `#tag:`? [12:41:47] rubs hands together who do I bother about THAT [13:10:45] I suppose you could resolve this by using the character instead of the related HTML entity...? [13:22:42] Maybe! This was just to report the bug. `­` works elsewhere in wikitext so most people would expect it to here. [13:49:05] https://tenor.com/view/fly-hands-guys-raised-by-flys-gif-11591198720050825009 [14:30:47] I suspect that `#tag` does that intentionally, using the character is probably the way to go [15:03:15] Ough I am so sneepy [15:39:05] A certain authority, that's original [16:20:42] Definitely appreciate the suggestions on what to use, my report was made a while back though so I've had time to mess around with solutions 💃 [18:03:31] [1/2] I spent over an hour making this [18:03:32] [2/2] https://cdn.discordapp.com/attachments/615786602454581249/1492223519872778250/Grand_Castle_Floorplans_10April2026.png?ex=69da8cf3&is=69d93b73&hm=41bd79ab3e36f4ae9974b4b0acc071f6eed3bc037a5672b2ce5810b5dfe2ba6a& [18:56:06] making what [18:57:07] A floor plan for a castle [18:57:21] send a screenshot [19:02:31] It is just a floor plan [19:36:35] Is there a overall issue with wiki.gg atm? [19:37:03] Yeah [19:37:37] alright thanksss [19:59:13] Guys can any of you help me decode something [19:59:19] Or find what it could be [19:59:28] I have tried everything I could [20:14:57] Ok don't worry it's partially solved thanks, I need something else to complete it [20:15:14] Hm? [20:38:27] The wiki Imagimedia, isnt active 🙁 [20:40:08] It's working fine for me. [20:40:17] Unless you mean it's not being maintained? [20:41:22] I dunno. Nobody sent any messages on their discord server and not many people have been editing [20:41:43] Its ok as I plan on making it active with my movement [20:43:18] It's had 12 edits just today, according to [its recent changes page](https://imaginationland.miraheze.org/wiki/Special:RecentChanges?hidebots=1&translations=filter&limit=50&days=7&enhanced=1&urlversion=2). [20:43:46] Thats good news at least [20:44:42] if enough miraheze users voiced that they wanted a certain wiki closed, would miraheze honor it or is it ultimately up to miraheze? [20:45:06] there is rather little precedent for that outside reception wikis [20:45:22] it would depend how that came out because it would be rather ugly [20:46:00] something like that would probably have to be a RfC [20:46:12] IBW [20:46:16] the predictable turnout of a meta-centric community could very well be outweighed if the entire body of italian brainrot or whtaever wiki caught wind of an attempt to shut them down and would easily outvote the matter, making it a shitshow, so I'd rather that be a policy and therefore enforcement issue rather than a direct community vote on a single community [20:46:24] ah, and ibw was just what I had in mind [20:46:52] their community volume would vastly outweigh meta turnout on average and they'd have a reasonable case to say ayo wtf and oppose [20:46:59] even if there might be a quality difference [20:47:22] i see [20:47:40] TS workload is like 90% IBW so I have no qualms over yeeting on that alone [20:48:08] plus they could make ads on tiktok like "save our wiki miraheze bad!!" and bring lots of non-wiki folks to complain. Too much trouble for the stewards imo [20:48:17] [1/2] Site users more broadly or the editing community of that specific wiki? [20:48:17] [2/2] My guess is that there would be procedures in place for if the maintainers of a wiki want it closed which are different from the community as a whole, albeit I'm not sure off the top of my head what they are in either case. [20:48:29] what made it successful for reception wikis was in part the fact a lot of senior and OG reception wiki voices were sick of the mess and supported the sanctions that did take place [20:48:53] I see. [20:49:01] still cant believe the things Reception123 did to wikis 😔 [20:49:08] so I would say an IBW case is something that would come down to volunteer level policy consensus if they feel the effort of supporting it is not worth it for a consistent problematic wiki [20:49:09] (/j to state the obvious) [20:49:09] my question was asked on a "can we all vote to remove italian brainrot wiki" basis [20:49:28] I really do think if you turned that into a vote you would be slaughtered by ibw turnout [20:49:35] (sorry, who is reception123?) [20:49:40] it is a weakness of the meta system [20:49:52] senior steward/tech volunteer since before the wikis were a thing [20:49:53] miraheze losing to an army of kids :( [20:49:56] A Steward, unless I'm thinking of someone else. [20:50:02] Ahh, got it [20:50:35] I have worried about this every time we had a huge niche bubble audience exist on the platform because meta isn't really designed in a way to cope with that unless stewards just said no f u and overrode it which would seem to defeat the point [20:51:00] Miraheze works fine [20:51:49] I do think we're basically fatally weak to a well executed sybil attack [20:52:02] I certainly can't see a way it could work unless something happened to move it within T&S jurisdiction, which I believe is a whole other kettle of fish. [20:52:49] on a different track I've been wondering what our options are against I don't know, vandalism on openclaw steroids [20:53:38] this definitely seems like a when, not an if [20:53:39] T&S does have the best case to unilaterally say no since they have such a heavy load from ibw in particular [20:54:06] imho, regardless of my personal opinions on brainrot wikis, that'd set a bad precedent. communities/wikis should be dealt with if they're too problematic or not abiding by the rules, but that's covered by the global policies [20:54:24] i think we could all benefit from not burning out NA twice as fast due to the great underage armies [20:54:45] if you want to make that a steward motion I can pass it on to the channel and badger for a vote [20:54:57] see what the room thinks [20:58:27] i assume theres no current plan of action in place in the event of an IBW uprising? [21:04:59] will ask the boss of 360 noscoping kids for his take and get back to you on that [21:05:30] mostly to see if there's any big concerns to doing so [21:10:11] if handled as a policy-level hey we can't support you anymore, then that will be it and any tantrum response will be accounted for [21:10:50] some of the folks who were really spicy and inclined to do something like that have already been ejected from this farm (and then several more in succession) [21:11:22] NO I MISSPELLED MY NAME SIGNING UP FOR WIKIOASIS [21:11:55] oof [21:12:30] NO I ACCIDENTLY MADE 2 ACCOUNTS [21:12:53] oh well i guess the other one can be my alt [21:15:29] don't think the account policy there is stricter than ours [21:15:38] @zipppee probably knows better off hand [21:16:05] would also be viable to put in for a rename on the original unless that's the new account you'd made [21:16:10] it’s more just don’t hide them or misuse them [21:16:16] basically ours [21:16:24] common sense is basically my view on taking action [21:17:26] up until common sense starts getting loopholes then a tighter policy will be introduced but as I see it common sense works for something like usernames and accounts [21:17:56] more strict can be warranted on a local level but at our scale more strict has not been required [21:18:09] the bar of are you using responsibly vs doing funny business has held up well [21:18:54] yeah there are legitimate reasons for it [21:19:13] and usually as long as there’s no vandalism, deception or abuse involved it’s moot [21:21:02] oh that’s fun I never realised rename jobs create localglobaluserpage update jobs [21:21:04] makes sense though [21:22:55] I don't principally even have a problem with a hidden low key alt that does nothing bad alongside a main account that is also in good standing [21:28:20] And policy backs that up