[00:47:25] Many people have been telling me that they're having trouble when accessing into the [AliceSoft Wiki](https://alicesoft.miraheze.org/wiki/AliceSoft_Wiki:Main_Page). Somehow it's working fine for some people, myself included, but for several users, the images are not loading [00:47:55] Ever since the CSP update [00:48:05] How do I fix this? [01:11:31] Seems fine on my end? If you purge the page it should be back to normal. [01:16:05] [1/2] Purging + a hard refresh should fix them. Otherwise simply wait for the cache to expire. [01:16:06] [2/2] If it is a widespread problem, tech can do a mass purge for you. [01:17:35] I'm sorry, I'm not a tech guy. What does purging mean? Is a hard refresh different from pressing F5 on my keyboard? [01:18:40] The head admin of the wiki isn't online atm so I'm trying to solve thing on my own 🙏🏻 I usually just write guides and stuff [01:19:09] Be patient with me 🥔 [01:19:17] It’s happening on all pages of the wiki as far as I can tell [01:19:17] [1/2] It's this button on the page. [01:19:17] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1488346915731935353/image.png?ex=69cc7294&is=69cb2114&hm=e1f4825b0b3b4fb6bec060927f8819bb780f675e51534c6b9c042ffc43558d14& [01:20:39] Oh, I see, thanks 😄 Is it me who needs to press it, or the users who are having issues? [01:20:46] Because the pages always loaded fine for me [01:20:54] It's just other people who've had this problem [01:22:06] If it loads fine for you, then the user who is having issues should try to do a [hard refresh](https://en.wikipedia.org/wiki/Wikipedia:Bypass_your_cache). If it doesn't work, press the on-wiki button to refresh the page. [01:22:32] I see. Thank you very much! I'll let them know. [01:26:41] [1/2] uhh [01:26:41] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1488348779093557299/image.png?ex=69cc7451&is=69cb22d1&hm=da4427a980a23f4042018ab473f858e2e5301cf3a198890ee7e77ffa186fc697& [01:26:50] Somehow I do not see any recent traffic for this wiki in the past 2 hours. Are you stil getting this issue? [01:29:30] still gotta do it per page tho. is that expected? [01:29:41] I'm gonna ask the other guys if they still have this issue [01:31:13] I just thought of a way to mass purge main namespace articles. One sec. [01:31:33] please do templates and modules as well [01:32:53] Purge done. Lmk if it worked. If not there is another option. [01:33:48] it appears solved. thanks! [01:38:59] [1/2] Sitll happening. I've been experiencing since this morning & have cleared my cache [01:38:59] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1488351872677974228/image.png?ex=69cc7732&is=69cb25b2&hm=727ee98e5daf7b29c27c767007096499c509befda72a7879997e21c841ff78af& [01:41:03] [1/2] I had support & it looks like this page was purged but images still breaking for me: [01:41:03] [2/2] https://fashiondreamerwiki.miraheze.org/wiki/Camper_Dora [01:42:40] I just purged, the images popped back up, but they went back to being broken after I clicked away 😅 [01:43:58] i recommend making the infobox accessible for dark mode [01:44:41] How would I do that? I did make the template [01:45:49] [1/2] use Vector 2022 variables instead of forced-in colors [01:45:50] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1488353594439897199/image.png?ex=69cc78cd&is=69cb274d&hm=3d245298ec13c608b85870b37ea738547e482cc5aa5940416e641cd282976e7b& [01:46:51] What would the vector variable be for this change? [01:47:18] The guy seems to be having to refresh each page manually [01:47:38] It sounds like they're having a similar issue to me! [01:51:57] I purged all main namespace pages on fashiondreamerwiki and alicesoftwiki pages with [jswikibot](https://dev.miraheze.org/wiki/jswikibot). [01:52:26] If that doesn't work then I can purge the Varnish cache. [01:53:02] It seemed better but the images broke after few clicks for [01:54:09] It seemed better but the images broke after few clicks for me [01:58:03] This is not a CSP issue. You are being blocked by Cloudflare for making an excessive amount of image requests. [01:59:44] [1/2] I can reproduce it after clicking around as well. [01:59:44] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1488357097354559549/image.png?ex=69cc7c10&is=69cb2a90&hm=d5726e5b6945dbfa975830f80698b17448951e4bbb27fc4eb56501da69edd08f& [02:01:20] [1/2] Pages like https://fashiondreamerwiki.miraheze.org/wiki/Influencer_Rank make more than 1000 requests to the server, so you are almost guaranteed to hit the ratelimit if you click around. [02:01:21] [2/2] See https://discord.com/channels/407504499280707585/1482131098942177382/1482131098942177382 [02:10:23] Going to try to do this for our wiki - it's just a null edit to the main namespace pages with jswikibot, right? [02:13:05] I think purge works too? Since purge is faster, I would do it first before null editing. [02:14:31] Ah gotcha - thanks! I haven't opened it in a while and didn't know mass purge was a thing 💃 [02:35:34] okay nvm it still happening [02:35:57] https://cdn.discordapp.com/attachments/1006789349498699827/1488366212198043658/image.png?ex=69cc848d&is=69cb330d&hm=a2d6ea043f07fe96e5ff06f06bde9824275ac383105f975721cd97b3470db484& [02:45:06] [1/2] Not sure if it's helpful, but I was able to reproduce some loading errors after purging all main namespace and template pages (this was on a fresh incognito session) after loading a page, pressing the back arrow, then clicking the link again. Not too worried about it since a refresh fixes it, but just in case it's helpful for troubleshooting. [02:45:07] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1488368514703036528/image.png?ex=69cc86b2&is=69cb3532&hm=62b7d1fbef019708a0eb1b6ff23ad64fa4a7a5c2b5a529cf95217b3d5d422f63& [02:50:08] Thanks for the info. To me this looks like MediaWiki is occasionally failing to apply the CSP directive and falling back to the Varnish version, which is why the issue recurs hours after being fixed. [02:50:48] That makes sense to me! I know that the Varnish cache takes a while 😤 [02:51:27] [1/2] idk where to post this here, when i try to upload a file it says this, can i fix it? [02:51:27] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1488370110896013422/Skrmbillede_2026-03-31_040720.png?ex=69cc882f&is=69cb36af&hm=8b58b85f5ddd1f2cbca8dc801a803290202eff8d653631a92a60dc16fcab35ef& [02:57:31] What site is this? Doesn’t seem like one of ours [02:58:42] i don't even know, my guess was miraheze cuz someone had the same problem as me and like someone for 4 years ago had an invite link to here and to ask here for help [03:00:09] [1/2] Task: https://issue-tracker.miraheze.org/T15157 [03:00:10] [2/2] PR: https://github.com/miraheze/puppet/pull/4835 [03:06:07] [1/2] Since the Varnish fallback CSP should not be appearing in the first place, the immediate band-aid would be to at least make sure images can appear properly when the fallback CSP is applied. [03:06:08] [2/2] After that we can investigate why MW is applying the CSP inconsistently. [03:11:54] [1/9] https://battlecats.miraheze.org/wiki/Battle_Cats_Wiki Most of the Battle Cats Wiki pages, for me, do not work properly and most if not all of the images don't load properly. [03:11:54] [2/9] What I've tried: [03:11:54] [3/9] - Ctrl+Shift+R [03:11:54] [4/9] - Just... Waiting. [03:11:55] [5/9] It's been like this for 3-4 hours now, and has just progressively gotten worse. [03:11:55] [6/9] https://cdn.discordapp.com/attachments/1006789349498699827/1488375255121789168/image.png?ex=69cc8cf9&is=69cb3b79&hm=4cb6b1607bb1af709f330c9c26aabb96073759d576e7076d0c03dfe090dc0e9a& [03:11:55] [7/9] https://cdn.discordapp.com/attachments/1006789349498699827/1488375255457071325/image.png?ex=69cc8cf9&is=69cb3b79&hm=fd44c616cd06fc8d3f1c3a1d2b508864764e1be32ed29eb184a99f256ead04ef& [03:11:56] [8/9] https://cdn.discordapp.com/attachments/1006789349498699827/1488375255906127994/image.png?ex=69cc8cf9&is=69cb3b79&hm=c9523d38e17b93f20a938164591f06de03209bb184c29d85a2d0dc3af1438239& [03:11:56] [9/9] https://cdn.discordapp.com/attachments/1006789349498699827/1488375256254251128/image.png?ex=69cc8cf9&is=69cb3b79&hm=d4cd7b657e681f28301e4fb221f74ef5f2ddab8b1f90d0388d00360d60d9b8ca& [03:15:05] @Infrastructure Specialists Pinging infra because this is randomly making images failing to load across the whole farm. [03:18:12] I think I might know what's going on. When not doing a hard refresh of the page, Varnish returns 304 Not Modified. And since MediaWiki does not apply a CSP, the fallback CSP goes into effect and overrides the one in the original HTTP response. [03:19:05] So the solution is to either remove the fallback CSP completely from Varnish or figure out a way so that Varnish only inserts the fallback CSP when it truly needs to. [03:21:00] At least this is one way that I'm consistently reproducing the fallback Varnish CSP. Maybe there are other factors as well. [03:33:32] [1/2] Thanks Agent! I'm seeing `*.wikitide.net` in the fallback CSP response now, so the image outage issue should subside. If any wiki is still having issues please ping me. [03:33:32] [2/2] Gadgets and scripts that make connections outside the fallback CSP will still be affected, though. [06:26:36] it is slightly different issue, but on my iPad on Safari i can no longer access any miraheze.org domain, and i get the same logo with orange exclamation mark. clearing history (and cache?) did not solve it [06:27:50] Very different issue [06:27:55] Screenshot? [06:28:19] Also what iPad? What OS version? [06:30:43] [1/2] 7th gen, 15.4.1. The url for any wiki becomes miraheze.org [06:30:43] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1488425290198810684/IMG_0878.png?ex=69ccbb92&is=69cb6a12&hm=91fab836fbf9b57bc358ae80c61f4e25b54d17464d5bc8c1a3c26160446f5274& [06:32:09] That is unusual [06:32:19] This showed up two weeks ago, and I thought it was a server issue, but still can’t browse. Might be device specific [06:33:58] is it possible to have TLS v1.2 override support on https://battlenations.miraheze.org so I can use AWB? [06:33:58] Can you update? [06:35:00] Like you're not even running the latest version of 15 [06:35:09] Never mind the latest your device supports [06:37:49] let me see, i have a 18.7.7 OS update that i can do that never notified [06:38:00] I can't see us having logged any error on the Cloudflare side from a Tablet running Safari on https://battlenations.miraheze.org/ [06:39:21] Oh wait I can but only a handful [06:40:26] https://cdn.discordapp.com/attachments/1006789349498699827/1488427738657198161/IMG_0879.png?ex=69ccbdda&is=69cb6c5a&hm=70d864f6f4a84ca032566b49c1bb4306797ab23bbbc61537858de87095d45643& [06:40:30] Done [06:41:54] What country are your requests coming from [06:43:23] i'm in the US but idk if that means my requests also are. how do i check? [06:44:26] Not seeing much [06:44:32] Try updating first [06:46:06] i'll get back to you tmrw and lyk if post-update it fixes things, gotta sleep soon :bceSleepPeaceful: [11:22:50] @originalauthority how many cups of tea for you to replicate fandom's social features [11:23:36] 1 and a choccy digestive [11:24:04] deal, upon completion of work I can comp you the costs of purchasing them [11:24:28] What social features in particular [11:24:49] mainly the yapping ones, comments and message walls [11:25:02] compatibility with forks from fandom would be amazing [11:25:43] (i dont use it enough to know if there's more, i think there was a feed for the yaps?) [11:26:19] i was /srs here btw [11:26:57] like it is such a popular thing that fandom refugees cry for, i think we really need something to offer them [11:27:25] I already made an article comments extension but didn't OSS yet (mainly because there's some stuff like Post history and reporting still to do and I'm kinda dog fooding in production). [11:28:13] The main issue with bringing over stuff from Fandom is that I don't think article IDs are consistent when forking? So it would require some funky workaround to know what comment goes where [11:28:59] weren't the IDs included in xml dumps [11:29:04] could read them from there [11:29:19] I forgets you know let me check that [11:29:27] would mean changing the import script or running two scripts but its worth it [11:29:42] That would solve the issue yeah (as you can see I did a lot of investigation for this 😭) /j [11:30:24] actually wasnt there the legal issue of fandom not having the comments be under CC [11:31:17] [1/2] FUCKING CUNTS [11:31:17] [2/2] > Content submitted to discussions or chat on communities are not licensed under the CC BY-SA licenses. As set forth in our Terms of Use that content is subject to a separate license grant to Fandom, Inc (only) which allows Fandom, Inc to utilize such content as it sees fit. [11:33:51] LMAOOO [11:35:01] if anyone ever needed an example of what a scummy company Fandom is there you have it [11:36:01] [1/2] Yeah there were some discussion in the WG server about this as well. I think Warframe Wiki imported these anyway and they haven't gotten into trouble (yet). [11:36:01] [2/2] This will be another Fandom image situation where we cannot officially support anything like this. The forked Yappin does have an import feature available to sysops by default. [11:36:42] images, unlike comments, are licensed under CC or others, and we 200% can display them [11:36:55] having comments is a legal liability [11:37:24] but, like you said, they are yet to play that card [11:38:01] would the individual wikis or miraheze as a whole be accountable [11:38:37] common legal recourse would be DMCA takedown but I would not like the risk of them coming at us with something worse and wider [11:39:09] [1/2] I mean, Fandom ToU only state that you grant them an license to do what they see fit – grant of this license doesn't automatically remove ownership of the poster, so theoretically, there would be no legal issues if the comment poster gave permission for the content to be copied (since they still own the copyright to their content) but that would rely on getting permission f [11:39:09] [2/2] rom every single comment author which is not really feasible [11:39:13] tl;dr fuck fandom [11:40:07] (Alas their restriction doesn't seem to extend to message walls in any case, though?) [11:40:20] wonder what a lawyer thinks of allowing comments under archiving or whatnot [11:41:31] also wonder what @wikitideharej and @notaracham think [12:06:54] Are they if you use Weird Gloop's grabbers? [12:07:19] ¯\_(ツ)_/¯ [12:07:34] whats wrong with wikiteam3 [12:07:58] or ig i should rather ask whats the difference [12:08:00] [1/2] Sans Undertale [12:08:00] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1488510171167719474/image.png?ex=69cd0a9f&is=69cbb91f&hm=264cd5b74543d67e888c84410db3ccb8edc8842fd58699fde8af8df0ebbf1337& [12:08:56] The difference is that WGL's grabbers transfer the accounts and the logs and file history I guess [12:09:10] And stuff like revision IDs are left intact [12:09:20] I don't know what wikiteam3 does [12:16:57] i guess the main issue on our side is centralauth being a bitch [12:17:44] Oh yeah lol [12:18:32] other than that we probably could do revids but beyond ensuring diff links and such keep working as they should, i dont really see a reason to bother at this time [12:18:52] bigger fish to catch [12:19:03] Yeah it's not that big of a deal [12:20:03] also it seems like the grabber scripts directly yoink from a fandom wiki, that's also a big uhoh for us [12:20:59] automation is a nono according to their policies so we can't really use them [12:21:49] we can however use archives from IA that someone has kindly decided to upload [12:23:01] SQL archives obtained through normal means and definitely not grabber scripts [12:23:44] (i think falling them WGL grabbers is a bit misleading since they were written by Ciencia but alas I digress) [12:24:04] Yeah sorry it's WGL's fork of Ciencia's grabbers [12:24:05] hello it is me jane totallyahuman doing a bazillion requests to your servers i am not a scraper [12:24:16] https://github.com/weirdgloop/mediawiki-tools-grabbers/tree/weirdgloop/master [12:24:47] https://cdn.discordapp.com/attachments/1006789349498699827/1488514396799107233/image0.gif?ex=69cd0e8f&is=69cbbd0f&hm=2809b6bb0d16d910af27a10f49e5a8e6543e2c039dba2dbf3191c18673d1d36e& [12:25:24] That last commit is so funny [12:25:40] fandom-auth be darned [12:25:56] Hello it is me com.android.chrome I swear I am not going to make a bazillion requests to your servers [12:26:30] lets pull a chrome 146 from a residential proxy on them /j [12:26:34] Oh yeah also deleted revisions I guess [12:33:48] Is Miraheze now the maintainer of DataMaps btw [12:34:50] I had some changes that I was wondering if I should submit upstream [12:37:23] wiki.gg is a bit eepy on their backend and idk if they'll pick back up again with their newest employee [12:37:37] Yeah that's what I was thinking too [12:37:42] alex himself has committed to our fork so take that as you will [12:37:52] Yeah [12:42:34] actually I should ask if we can throw collaborator rights at him [12:42:38] [1/3] I would assume that Miraheze tech (at least myself) is willing to do some minimal compatibility fixes so that DataMaps at least works for newer MW versions. [12:42:39] [2/3] Though if at some point @alex4401 wants to pick DataMaps up again I'd advocate for us switching over to his version. [12:42:39] [3/3] Btw, if Alex is willing to accept, we should give him write access to the Miraheze-forked repo so that it's easier for him to fix things whenever he has the time and interest again. Not sure if there is precedent of us doing that, but this seems like a reasonable thing to do. [12:42:49] lmao I was just about to [12:42:52] Exactly what I was thinking lol [12:44:20] we are 200% down to support a new home for the repo or write rights for you on our own [12:46:48] the only thing we'd really need to worry about is making commits that explode on our stack, but thankfully we dont autoupgrade extensions [13:05:13] I was considering moving DataMaps to gerrit [13:05:45] and forking ThemeToggle on gerrit as well, but I haven't had time for that yet [13:06:52] is it about time we ask for a miraheze group [13:06:54] And along with that I also plan to request a gerrit group to Miraheze so all tech team members can get +2 access in our repos (we also have 4 or 5 others on gerrit) [13:07:05] lol I was just typing my message about that [13:07:13] im so good at reading minds today [13:07:27] after i hit the shops i can do the bureaucracy of all that if you'd like [13:09:51] not sure how hard it will be to fork ThemeToggle since the gh repo still exists, we probably need to explain in the request that it's basically unmaintained [13:10:24] that oughta work [13:11:20] ideally CA should request the gerrit group as DTech and also because he owns a few repos (e.g. Monaco) the group should have +2 in [13:11:26] Interesting [13:11:40] Should we give a heads up to GG? [13:13:33] i'll review the bureaucracy and see what it says, but might have to bother him yeah [13:13:56] [1/2] "can you make this other person the owner of the group" [13:13:56] [2/2] "what are you smoking" [13:14:18] lol [13:15:34] is a precedent task, only 10 years old [13:16:11] only [14:03:28] i'm fine with write access on the repo and you can tag me on any issue tickets [14:04:09] @abaddriverlol can i get a +2 from you for ^ [14:04:54] do we have a policy regarding this? usually merge rights require shell access [14:05:02] it would be easier to just grant access on gerrit once we have moved the repo [14:05:15]