[01:08:52] [1/2] I’m trying to style my slideshows (with inspect element first cause yes) but my icons just seem to become a bit transparent for some reason, anyone know how to fix that? [01:08:52] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1404270308378153011/IMG_2930.png?ex=689a9423&is=689942a3&hm=b6807a1129ba1368cf9b5141b5af94c796f57534f9afc178544084f66893e495& [01:10:30] opacity 1 somehow doesn’t work 🤷 [01:11:43] does anyone know if theres an equivalent to Featured ('starred') articles on Miraheze? an extension or somesuchh? [01:27:02] neeeevermind I got it [01:27:04] heeheee [01:33:31] That system is implemented in wiki by modules and such, it’s not an extension [01:33:41] It’s definitely possible to add [01:33:44] ooo okay [01:33:48] do you know of any modules that do it? [01:35:21] not off my head, but I may know a wiki that does it [01:35:53] But also [01:37:33] It depends on what exactly you want [01:37:43] is your goal just the star thing? [01:37:54] pretty much [01:37:59] just some way to show that articles are featured on the article page itself [01:39:17] https://mediawiki.org/wiki/Help:Page_status_indicators [01:41:07] https://en.m.wikipedia.org/wiki/Template:Top_icon https://en.m.wikipedia.org/wiki/Template:Featured_article Honestly, seems pretty easy [01:48:40] oh i had no idea was a thing in MW [01:48:42] thats awesome, thank you [01:55:29] [1/3] Pissing me off, when I put it in inspect element it works perfectly fine but when I put it in Common CSS it becomes transparent again what the hell 🥹 [01:55:30] [2/3] https://cdn.discordapp.com/attachments/407537962553966603/1404282042283196436/IMG_2931.png?ex=689a9f11&is=68994d91&hm=57329067ef022e38932e721f2d9fa54eea40e5491c3a0035736c0c3b6fd0f88f& [01:55:30] [3/3] https://cdn.discordapp.com/attachments/407537962553966603/1404282042664882186/IMG_2932.png?ex=689a9f11&is=68994d91&hm=e4ef1b6482ba7af5dbed505a40f31fb1f94174d993d8c550fec724c91f2157bf& [01:56:04] [1/2] Can one of y’all check if it’s transparent or solid [01:56:04] [2/2] https://blockstarplanet.miraheze.org/wiki/User:Progeest?debug=2 [01:56:52] [1/3] sweats [01:56:52] [2/3] i've never gotten this error b4- [01:56:52] [3/3] https://cdn.discordapp.com/attachments/407537962553966603/1404282388166606868/image.png?ex=689a9f63&is=68994de3&hm=3586096fa0409a49951cbfc34c0a03c92d2c343544cd74640f844749a1b3b810& [01:57:07] I had it once too [01:57:13] After a few reloads I believe it fixes itself [01:57:35] [1/2] this is the other error im receiving [01:57:35] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1404282571315085462/image.png?ex=689a9f8f&is=68994e0f&hm=9272466c018a40fef7eed6b61642444f8c656811c5642cf3122aa1f0a40a718a& [01:57:55] what the hell [01:57:56] course [01:58:13] i also forgot lol, i checked enwiki to see how its done [01:58:42] i'm not using a vpn btw, so i don't know why it's doing this,, [02:00:48] Try clearing your cache and cookies [02:01:35] that worked! weird tho, i have a thing that should be clearing my cookies regularly but oh well [02:28:36] [1/2] what's the snippet that changes this part of the wiki? [02:28:36] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1404290375123734640/image.png?ex=689aa6d3&is=68995553&hm=7c06ebb4c30cda6baa39da093063e3616b90feea71c48549e742b3b0f2db4535& [02:28:41] on the timless skin [03:11:12] I usually go into my browser's DevTools and figure out what goes into where, and it helps at times. [03:14:41] it's called wordmark, there's a setting for it now but if you don't like outcome then css comes in [03:16:41] How do I use universal language selector? [03:18:07] I have it enabled but I am not sure how to actually use it [03:51:40] is this functional for vector skin [03:51:42] [1/2] Wait for cache to clear. You should see a menu like this. [03:51:42] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1404311286325448806/image.png?ex=689aba4d&is=689968cd&hm=0628c2193217f8878a4ca5953c0ea29f37ed0d3e70d8c46e248a4c4929705c00& [03:52:04] [1/2] I love styling 😻 [03:52:05] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1404311381666168862/IMG_2937.png?ex=689aba64&is=689968e4&hm=18d6681e917ac406237016d10dcb1728b279e86b1323087d4b513060dd8968bd& [03:52:06] Opinionsssss [03:53:07] [1/2] The text/description is following in-game style btw [03:53:07] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1404311643869020191/IMG_2938.png?ex=689abaa2&is=68996922&hm=60d42f64a5d6303fbdb03a5635674ba5087b3861a8519559e333735cbba0d6f4& [03:53:45] I would add a like and comment icon but it’s just not needed cause well… that doesn’t exist on Miraheze lmfao [03:56:26] Is this just on all pages? [04:10:05] How do you access the VisualEditor? When I click on "edit" it does not show me the option to switch between source editing or visual editing. [04:12:08] Yes. It's on all pages by default. [07:31:30] [1/2] Eh huh [07:31:31] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1404366605168672849/Screenshot_20250811-143050.jpg?ex=689aedd2&is=68999c52&hm=8ffa4800fbc1911f7b0ea435b1c94f730169127489dc575ac2a50aed102bb397& [09:20:13] Fixed [09:20:38] I'm kinda surprised that no one fixed it in the past 2 hours. [14:24:48] [1/2] Guh... [14:24:49] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1404470614688927835/Screenshot_20250811_162319_Chrome.png?ex=689b4eb0&is=6899fd30&hm=b3c038d00cbf729931efeae330705bf9e1d16d57cf534b0b656d386ec4b69ed1& [14:28:32] you'll probably find Switch to work better with that function [14:51:06] OpenAI broke the reviewer [15:00:16] My private wiki will be to document a fangame I wanna make and also help me remember everything I got and actually write it down ksksjkss, so I'm waiting till I got some more assets and references done for it [15:12:21] wassap guys hows it hanging [15:12:39] was wondering if anyone would know why my wikis visual editor seems to work randomly [15:12:51] source editor always fine but visual editor will only work when it feels like it [15:12:58] https://mapping.miraheze.org/wiki/Main_Page [15:13:07] tried a priv window and refreshing my cache and cookies [15:17:28] visual editor is buggy asf [15:17:50] sometimes disabling and enabling it again fixes it [15:18:19] source editor is THE real one for mediawiki, visual is an add-on [15:25:42] lemme ask them to try cheers [16:12:16] 💔 [17:09:42] this happens because the VE extension comes in from your custom domain (mappingwiki.org), but isn't loaded since it violates the CSP policy [17:12:59] [1/2] I don't think we have a way to tell CSP "the custom domain is us too" (pinging @rhinosf1 to confirm) , so your options are basically to not use the miraheze domain [17:12:59] [2/2] Your bureaucrats can also make a request on [[Phorge]] to redirect the miraheze domain to your custom one. [17:13:00] [17:13:10] Thank you so much lemme report back to them and keep yall posted [17:16:17] are u fr [17:16:22] The original Miraheze domains are not designed to be functional for editing [17:16:26] man [17:16:50] Once automatic custom domain removals are in place, they will be redirecting automatically [17:17:07] It's only there so you have basic functionality if your domain fails [18:08:54] hi [18:09:04] i think i already said this a week ago [18:09:13] But our wiki still isnt loading some images [18:12:52] https://discord.com/channels/407504499280707585/407537962553966603/1399516231442370761 [18:31:11] [1/2] Same thing. It's obviously a parser bug with how `#` is handled. [18:31:12] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1404532618510209195/image.png?ex=689b886f&is=689a36ef&hm=7da621b59675b1136bf532b63cef4e6bd5a6024d2aa2c731e213d8df40ba4e4c& [18:39:41] [1/3] Hi, everyone! I'm trying to persuade a wiki to move away from Fandom, and since they're a music wiki it looks like their only options are either self-hosting or Miraheze. Since I don't know the singular administrator's circumstances, I want to help them move here! I have reached out to him on Fandom, but have not received a response about if he'd like to move. However, I am cons [18:39:41] [2/3] idering making a wiki on the topic on Miraheze anyway if he decides they won't move, which would just mean I'd be working without his assistance and without assuming their prior work. Our wiki's topic & scope would be the same, regardless of whether or not the wiki is made as a move from Fandom. So, I wanted to start the process of requesting the wiki now in order to "get ahea [18:39:41] [3/3] d" of the queue... but the checkbox `This wiki is moving or forking from an existing wiki` is a box that I don't know whether I can tick or not yet until he gets back to me. Is it possible for me to move forward (and if so, how) - or should I wait for his reply? [18:53:20] [1/3] Discussing forking on Fandom itself can be problematic because of its strict forking policy. If the admin is aware of it, they would be very reluctant to respond to you on the site itself. [18:53:21] [2/3] You most likely can assume their prior work. If the original wiki is licensed under some variant of the CC license without the ND clause, you can simply fork all content to Miraheze (volunteers here canhelp you). Note that if you don't have much wiki-editing experience, fixing all the things that will be broken after the fork can be challenging. [18:53:21] [3/3] IMO you can check the box to say some members of the original wiki are moving, but I'm not a wiki creator, so I can't say for certain. [18:54:10] I would wait for a reply. Creating the wiki without consideration for the already established wiki is gonna cause a rift in the community and is a really bad idea imo. Forks should only happen if there's a general consensus to do so [18:55:14] true yeah [18:55:20] both of these messages [18:55:39] as a music wiki admin may i ask which wiki is that? 👀 [18:56:24] Apparently this is a MediaWiki parser bug that has existed since 2008: a 17-year-old bug... [18:56:34] Also I'd say it's pretty unethical to do an unofficial fork regardless of the law, you're practically stealing people's hard work [18:58:17] I wouldn't say harsh things about it. It might make people very sad because they don't understand what the CC license means, but when they edited the wiki, they have already given consent to let other people do whatever they want with their work as long as license terms are followed. [18:59:17] If you wanna look at it at a technicality then yeah, but it would be pretty rude. I certainly wouldn't be happy if someone were to take all my hard work and move it somewhere else [18:59:33] Forking unofficially is very common in the software world and usually don't make the original authors upset, though in the MW world things might be different. [19:00:33] I think for software it's pretty different. Wikis you sit down and write, you create templates, you summarize, you create themes, etc. [19:01:27] Yk for communities to read [19:01:29] I should clarify I would only have based the Miraheze wiki off of the work on Fandom if they agreed to move (at which point the Miraheze wiki would replace the Fandom one). Otherwise, I would have worked on it from Miraheze from scratch - but then that gets into the community rift you brought up. But yes I agree with this mostly [19:01:42] Thank you all for your input ^_^ I think I'll wait for now [19:01:56] Gotcha, just making sure :DoneMH: [19:05:01] idk if you don't want people (including those you might not like) to expand upon your work, then perhaps you should consider a license other than CC [19:05:13] (not directed towards anyone) [19:06:07] I can DM you [19:07:46] ok [19:14:37] I mean I'd be fine with people expanding upon my work, but creating a dupe wiki on another platform with all my content without asking permission is where I'd draw the line [19:15:49] If someone asked first I'd probably be fine with it LOL [19:18:08] Yeah, beyond questions of licenses, wikis thrive best when there's an active community behind them working to help build and expand on existing content. Forking without the community behind the project is a hard road to travel. [19:20:22] Eh, it’s just fundamentally not stealing. Permission is granted with the license itself. It’s not just a technicality it’s just how it is. The majority of images on Wikipedia are photographs taken under the similar license. [19:26:04] [1/2] I'd personally say it's the letter vs the spirit. You can, but the intent is that they know "hey, this came from somewhere else, and this is where it came from" so the person reading knows your work is based on something and not entirely your work. Most of the outrage would come from those statements living in the fine print where people won't re [19:26:05] [2/2] ally find it easily (parallel example: did you know existed? I was only able to find it in the Discord marketing website footer) [20:39:33] That's older than some of our volunteers [20:39:40] And nearly an adult [20:39:56] Bugs old enough to drink in the UK are not okay [20:40:08] Bugs old enough to drink in the US need fire setting to them [20:42:04] that's nuts [20:56:32] They better not have this bug in parsoid... [21:25:46] Bugs 🐛 [21:25:54] When we all move on [21:26:03] There’s gonna be that one 50 year old bug [22:38:36] We love the WMF. Instead of fixing bugs, just sunset the entire thing and rewrite it from scratch with less functionality! [22:38:41] Every developers dream [22:53:14] [1/2] how is ts still in review [22:53:14] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1404598565439012894/image.png?ex=689bc5da&is=689a745a&hm=d1a22f3148d5a4c4d5363a903eb175ce57cb8f31b6345a58b15873b32371cd95& [22:53:19] 🤷 [23:00:01] Also it’s just been a day [23:05:10] Understood. [23:05:15] I didn't read that mb 😭 [23:12:42] Not a worry. Our usual timeline bounces between 1-3 days for human review, so as you might imagine this much of a backlog is incredibly painful for us as well. Nobody likes waiting, and nobody likes looking at a virtual 'to-do box' so full of pending work. 😭 [23:16:15] True... true. I understand your struggles and I hope the problem is fixed soon, especially with the amount of wikis needing to be created 🙏 [23:22:03] So using wikibase is there any way to run SPARWL queries on it? [23:32:44] Not as far as I've heard , though there's some orb-pondering on what the future state might be looking like re: SPARQL and MH [23:42:12] Table colors again I see [23:42:32] I did recently ask for ColorizerToolVE to be installed on my wiki so I don't have to fiddle around with doing the colors in source editor [23:43:26] [1/2] Hello! Yes, I did leave the Fandom Discord server shortly yesterday, as I will be moving my home wiki to Miraheze due to a large majority of reasons. That, and I feel more at home with Miraheze than on Fandom. Sure, I'll be dropping out of some functional JavaScript tools, but it had to be done. I've already made a full database dump of my home wiki a [23:43:27] [2/2] nd downloaded all the images I don't have on my computer, so I'm pretty much good to go. [23:43:47] and I've already done a fork of Mongrels Wiki on Fandom to Mongrelpedia on Miraheze [23:44:05] the content in the show itself is just too much for Fandom which is why I made the fork in the first place [23:45:32] welcome [23:46:10] Thanks! 🩷 [23:48:18] [1/2] Same thing with me and the My Life as a Teenage Rabbot Wiki, as I've been busy downloading all the media from said wiki to my computer after making a full database dump. When the automated review tool comes online, I'll upload the full dump to my Google Drive head of time, since I think MediaWiki would time out, since the full extracted dump is 1.6 giga [23:48:18] [2/2] bytes in size. ``:Miraheze_pain:`` [23:48:55] ngl we need a miraheze pain emoji [23:49:06] :moonch: [23:49:18] What the heck is that [23:49:51] I don't know, but it's the custom emoji that most closely resembles a miraheze pain. 🙂 [23:49:57] Since the Fandom server has pain emojis, we might as well have our own. [23:50:33] I think a dis/misassembled miraheze logo [23:51:48] it's hard to misassemble the logo [23:55:35] That would be nice, or the times when MediaWiki decides to go oof.