[05:30:15] Why doesn't the create talk permission still requires a moderator to approve the message? [06:59:24] how would I use a custom font on my wiki's skin? [07:06:32] [1/6] ``` [07:06:32] [2/6] body.mediawiki { [07:06:32] [3/6] font-family: ...; [07:06:32] [4/6] } [07:06:33] [5/6] ``` [07:06:33] [6/6] The same way you'd load fonts in CSS. [07:06:42] thank uuu!!!! [07:07:40] do I change it in Common.css? [07:10:45] Yes. [07:11:31] Note that different operating systems have different sets of fonts available out of the box. Hence the long list you see on guides like https://meta.miraheze.org/wiki/User:PetraMagna/Why_you_should_use_language_attributes. [07:16:38] So if your desired font is not available on some OSes, you'll need to load it first. Which could be time and bandwidth-consuming. [10:35:35] [1/2] I wanna punch my monitor everytime i see this [10:35:35] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1412023073850396813/fx6KN0Y.png?ex=68b6c876&is=68b576f6&hm=f2b35b0b410ab5e355d0989ca1db07e2fa031141124a60209a3550968516f6a9& [10:41:49] you know you can disable miraheze/wmf commons [12:51:03] [1/3] Hot take: we should disable WMF Commons by default for new wikis and move template dependencies of the dev wiki to MH Commons. [12:51:04] [2/3] Even hotter take: we should disable both commons by default and instruct users to enable them when needed on the dev wiki. [12:51:04] [3/3] On a more serious note, I find it hard to justify enabling both commons by default: the main reason would be ease of importing templates from dev, but the amount of headaches on all the wikis without such a need seems to outweigh the benefits. [12:58:29] Why? [13:01:25] most wikis on miraheze don't have a strong need of commons [13:02:22] worldbuilng wikis are fully on their own, wikis about works like games rely on assets [13:02:35] and forks bringing up everything over [13:03:12] i use WM Commons on my wiki for flag icons [13:07:22] other than the above, WM commons makes VisualEditor's image search unusable unless you use custom JS to suppress the results [13:11:43] [1/8] I would love to back up my speculation with some data. Unfortunately ManageWiki's api is being weird. [13:11:43] [2/8] https://meta.miraheze.org/w/api.php?action=query&list=wikiconfig&wcfwikis=metawiki|strinovawiki|ukbwiki&wcfprop=settings [13:11:43] [3/8] Both strinovawiki (a wiki that I contribute to) and ukbwiki (a random newly created wiki) don't have any mention of commons in their settings, yet the former has both commons disabled while the latter does not. [13:11:43] [4/8] Meanwhile, Meta does have [13:11:44] [5/8] ``` [13:11:44] [6/8] "wgUseQuickInstantCommons": "", [13:11:44] [7/8] "wgMirahezeCommons": "", [13:11:45] [8/8] ``` [13:12:23] I'm guessing managewiki has some hidden attributes which track settings that are set to false. [13:13:09] [1/2] Not sure how to find this out with wikidiscover either. [13:13:10] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1412062729140699156/image.png?ex=68b6ed65&is=68b59be5&hm=97372296251ede107548ef66e369b50e77cd4295349af31c0b040199349d09f9& [13:31:06] On UT/DR I disabled Commons because fetching files from Commons kept failing over and over and files on our main page and all soundtrack pages became redlinks and it didn't look great [13:31:19] So I just reuploaded the few logos we used locally [13:32:26] Did this happen recently? WMF made a few changes on their side [13:33:07] I disabled it mid-July [13:33:31] hm then it's probably not related [13:34:06] I know there was some stuff about QuickInstantCommons on Miraheze but that wasn't what we were using [13:34:11] But WMF requires a user agent now (or will require soon? not sure on the exact timeline) for requests like this, and they only fixed QuickInstantCommons/InstantCommons recently [13:34:30] ah [13:34:58] I mean maybe it's related [13:36:33] But I've had math formulas fail on me for years prior so I'm not particularly surprised about Wikimedia's web services being unreliable when used outside Wikimedia [13:42:57] Hi. Tell me, how do you adopt a wiki that is inactive and private? [13:45:05] the only thing you can do w/ private wiki is to contact admin (you can find on Meta's wiki creation queue) and ask for position [13:47:32] Okay, thanks [13:53:41] Yeah that should definitely be standard if it exists at all. [13:57:49] How do I request deletion of commons images? [13:58:46] Oh does wikimedia commons override miraheze commons? [14:02:21] you can't "delete" commons images. images on your own wiki will override them automatically, or you can disable commons images altogether in Special:ManageWiki/settings#mw-section-media [14:02:48] idk whether wikimedia commons or miraheze commons takes priority [14:20:10] [1/2] Miraheze Commons takes priority over Wikimedia commons. But Local wikis can upload the images on their wiki, and they overwrite both Wikimedia Commons, and Miraheze Commons. [14:20:10] [2/2] If you get a warning on your local wiki, you can safely ignore it. [15:02:33] You need &formatversion=2 in the API to get false values back from the API [15:02:46] It returns an empty value for false otherwise iirc? [15:03:10] Or maybe that's 1 and 0 instead idk I know there's some weird handling of booleans from the API if you don't use formatversion 2 [15:04:05] That worked. Thanks! [15:47:32] [1/2] the footer is covering the tools options in the main page, how to fix it? [15:47:33] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1412101581280645160/image.png?ex=68b71194&is=68b5c014&hm=33dfbd1014e50ebc4eb4a5ff71d12373950e191e08884d13a8f200fb0cc579e8& [17:46:28] "An unknown error occurred in storage backend "miraheze-swift"." [17:46:35] what is happening? [17:46:56] nvm [17:47:00] got it working [20:30:58] Hi, whenever I try to log onto Miraheze I keep getting the error message `No active login attempt is in progress for your session.` [20:31:19] I looked it up and a common suggestion to solve it is to clear your cache. I did that and the error still shows up [20:34:17] and cookies [20:34:25] failing that, try logging in incognito as well [20:39:05] hi, is there any fix for the bug that logs you out on file pages? [20:39:10] cleared cookies and it worked. thanks [20:39:19] it's used for site logins so i don't usually clear them [20:39:51] since clearing cache didn't work i also didn't believe that that would've worked [22:27:32] cookies is also a cache too [22:29:38] what? [22:29:59] cookies are an entirely different, intentional system meant to allow your browser to save data from websites. cache is just temporary files that your browser uses for multiple purposes [22:30:07] mainly speeding up page loading [23:10:40] What… [23:10:49] Cookies have nothing to do with cache [23:11:03] You can have one without the other [23:13:14] [1/2] Cookies are a small block of data created by a web server while a user is browsing a website and placed on the user's computer or other device by the user's web browser. [23:13:14] [2/2] Cache is website data like images and scripts locally on your device to speed up future visits to the same site [23:13:19] Not even remotely the same [23:24:29] I mean, you could cache data in cookies [23:24:32] i guess [23:27:33] that is what we collectively call "a bad idea" [23:27:44] <-- still wonders if it's possible to store a whole mediawiki database in cookies [23:27:44] depends [23:28:16] Thats a bad idea [23:28:23] Thats a worse idea [23:28:26] i know [23:28:28] but like, imagine [23:28:39] each user having their own copy of the database [23:29:06] Until you factor XSS, Injection [23:29:16] that's only self-xss :) [23:29:38] and you need to figure out how to set cookies on the victim [23:29:47] Not if for some reason the copy that a user gets includes something that would then be used to compromise them [23:32:00] fair [23:32:15] this is my compromise between having mediawiki entirely run in the browser [23:35:27] girl, having mediawiki run on your mortal human body is somehow a better idea than putting the whole db in cookies [23:36:30] injecting you with mediawiki [23:43:14] [1/2] # help! [23:43:14] [2/2] my wiki got raided - how do i make it so people can't edit it anymore?? [23:44:16] genuinely help [23:44:19] this is urgent [23:44:23] how do i lock it down [23:44:39] You can either change the permissions via Special:ManageWiki/permissions, or use the ProtectSite extension and go to Special:ProtectSite (which is probably easier as a temporary solution) [23:44:57] You can enable ProtectSite at Special:ManageWiki/extensions in your wiki [23:45:36] oh my god thank you so much [23:45:40] absolute lifesaver [23:45:50] Also I'd recommend you to consult [[CVT]] in #cvt so they can take appropriate action [23:45:51]

[23:46:16] [1/2] each user having their own copy of the database [23:46:17] [2/2] Isn't this actually a thing though? [23:46:22] wait what? [23:46:25] [1/2] uhm [23:46:25] [2/2] how exactly [23:46:33] I could've sworn there are apps out there that store databases in the browser for offline viewing [23:46:44] probably should move the cursed mediawiki talk to #offtopic though [23:46:47] look man i'll show you what they did to the wiki and then ill [23:46:48] yeah [23:47:00] its reversible probably yeah [23:47:01] but [23:47:15] Just send a message in #cvt with links to your wiki or relevant log pages and ping the CVT role [23:50:54] [1/2] uhm [23:50:54] [2/2] help [23:50:57] how long do i wait [23:50:59] please [23:51:11] who else do i ping?? [23:51:18] genuinely help [23:52:41] dude please