[00:19:59] this seems like a case for that content to be removed from the destination if it does not comply with the original license, but I'm not sure the case is made to proceed to unilateral removal. It would depend on the exact places and circumstance though, worth presenting at least be it on wiki or in confidence via email if you prefer [00:31:12] Asked over the wiki, it can eventually be moved to email if necessary though, yeah? [00:36:30] https://cdn.discordapp.com/attachments/407537962553966603/1443400055833890837/image.png?ex=6928ee8e&is=69279d0e&hm=907ba10ad95061960b4c108c295e6b75261da30c4641ca6f0317335b8a07d8db& [00:36:35] 😔 [00:36:41] y'know i was about to post something like that [00:36:55] we all died 💔 [00:37:15] It is known [00:37:51] 1 second without miraheze is hell [00:38:07] every single time i go to do ANY work it goes down i stg its out for me [00:38:31] It's up the vast majority of the time, to be fair. [00:38:43] we need a hero [00:38:44] to save us [00:38:49] No [00:38:55] man im just trying to learn miraheze wiki stuff since im kind of new 💔 [00:38:55] Well, we can practice on being Patient again 😄 [00:38:56] We need proper uptime tracking [00:39:08] (First of all, welcome) [00:39:12] I thought that was what Grafana was? [00:39:21] hai there [00:39:27] pix does miraheze have a public uptime % [00:39:31] Grafana tracks the nerdy metrics for this stuff [00:39:32] Yes [00:39:33] But it’s [00:39:34] Uh [00:39:56] also down 😛 [00:39:57] https://wikitidestatus.net/history [00:40:04] https://cdn.discordapp.com/attachments/1156734890537140256/1443115604054904967/cat-gato.gif [00:40:09] You can see the problem [00:40:13] I would say we have an uptime of about 97% [00:40:16] So earlier someone said we’d never get SPARQL. Would you be willing to try to add it if I joined and tried to work on it. [00:40:54] Who was the person involved in looking into SPARQL, do you knows [00:41:05] And why did they say that [00:41:18] There’s a task I think [00:41:19] [1/2] Something went wrong [00:41:20] [2/2] If this keeps happening, let us know. [00:41:21] I do not know who that was this was a while ago [00:41:31] I think it was Rhinos [00:42:38] [1/2] ive never seen this one before [00:42:38] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1443401599220449452/image.png?ex=6928effe&is=69279e7e&hm=e8236fd389d0894b41d4033dea02b1ae597d5777d315478c88944c1603afa156& [00:42:57] https://discord.com/channels/407504499280707585/407537962553966603/1407112545566855209 [00:43:46] Wow, dusty much https://issue-tracker.miraheze.org/T13728 [00:44:14] Sorry Addshore…. [00:44:29] @rhinosf1 someone should probably poke this sometime huh [00:44:30] dead again [00:44:33] Maybe over the holiday freeze [00:45:02] Im literally having a gateway error right now [00:45:09] Known issue [00:45:11] so are all of us [00:45:37] https://tenor.com/view/rabbids-lost-as-a-rabbid-gif-10119628982440016968 [00:46:02] there should be a bot that automatically tells users when miraheze is down [00:46:13] its up [00:46:15] we r alive [00:46:17] I’ve proposed adding a sticky Bot here before [00:48:22] Cooked?? [00:48:22] That would be more than 20 hours of downtime per month. I'd say we're doing better than that. 99% maybe? [00:48:42] Main issue with Blazegraph is that it’s a significant memory commitment. Even a small database can require a few gigabytes of RAM, which adds up very quickly. However, QLever now supports streaming updates AND has a smaller memory footprint. Maybe it should be considered. [00:48:52] 98.9? Im not confident enough to say 99 [00:49:35] My VM that I dedicate to the Wikidata Query Service has 320 GB of RAM [00:49:41] Most Wikibases aren’t that big [00:49:42] We should be back [00:49:59] I think we used to do a lot better. It seems that the hardware is no longer overpowered enough to cover for software issues. [00:50:33] Honestly I think its a growth issue, we’ve outgrown our hw [00:51:03] This was not caused by traffic [00:51:16] I'm pretty sure none of our recent outages would've been solved with better hw [00:51:30] If db171 has a load of 600 something else is wrong [00:51:32] yes [00:52:17] This is only like the second outage we've had since we've solved the db issues we've had previously [00:52:31] A couple of weeks ago we've had a db freeze every day [00:52:47] I propose we solve the problem by removing the database [00:54:06] [1/2] (for reference this is the load on db171 if we exclude the outage a few days ago) [00:54:07] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1443404485132161085/image.png?ex=6928f2ae&is=6927a12e&hm=0a573c65043a4a55dbdb51f2b4c0c98a3b4b1a429b2d0421bc088be9a43f4f5a& [00:54:41] Wait, what's the load on db161? 👀 [00:56:02] [1/2] hard to tell because of the four spikes [00:56:02] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1443404970132111453/image.png?ex=6928f322&is=6927a1a2&hm=8d31cde7aa829a36c6c96229468a220acaac6461e864c8e55cabec1bf71959da& [00:56:07] [01:00:30] Oh thanks [01:11:04] The Yu Gi Oh Wiki approach [01:14:52] Wait… [01:22:31] No SQL no problems. 🙃 [02:12:49] Sounds like something I'd do on a weekend, but can't this weekend [02:12:54] Can't break things that don't exist. [03:59:58] how to make carousel in miraheze? is there any example? [04:00:06] or do i have use css [05:30:29] Try enabling [[mw:Extension:JavascriptSlideshow]] on ManageWiki [05:30:29] [05:31:55] [1/2] Vanilla CSS (no JS) also works if you want more customization. Here's one that I made for Vocaloid Lyrics Wiki. [05:31:56] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1443474400816005211/Screenshot_2025_1127_123104.png?ex=692933cb&is=6927e24b&hm=6ad81d96428626d40ea86ffbe69a9a5daeb1e0acdef0cb797bc42caca1cd7a97& [05:44:23] does anyone use DRUID infoboxes here? [05:45:38] they recommend (but do not require) [Extension:OpenGraphMeta](https://www.mediawiki.org/wiki/Extension:OpenGraphMeta) and [Extension:ParserPower](https://www.mediawiki.org/wiki/Extension:ParserPower). what are the consequences on the infobox if you don't install those [05:46:11] oh wait parserpower is on MH [05:46:43] but yeah, question applies to opengraphmeta which is on miraheze too but... seems to be something to do with facebook like buttons? [05:47:15] I'd rather not install it if it doesn't provide a significant improvement [05:50:56] Not familiar with DRUID infoboxes, but OGM seems to be doing things that [[mw:Extension:WikiSEO]] can do [05:50:56] [05:51:23] awesome thanks [05:51:30] hmm ok [06:03:24] help why is the background not loading [06:03:25] https://excaeliscientia.miraheze.org/wiki/Sandbox [06:58:40] `mw.loader.load("https://cdn.jsdelivr.net/gh/lihaohong6/MirahezeDevScripts@dist/dist/BackgroundImage/gadget-impl.js");` [07:01:27] but note this script uses single color stop of linear-gradient so it's unlikely working on a browser older than half a year old [07:36:23] LOL fr frrrrr [07:49:02] Oh that's good to know. I should change it then (and maybe remove the blur since it affects performance) [07:49:34] Accommodating Citizen is also on my todo list since the current support is minimal. [07:50:17] https://caniuse.com/single+color+stop i'd never use something with even less than 70% global coverage [07:51:50] at least not rely on such. it means most readers cannot see them [09:19:02] hello fancy infrastructure specialist [10:47:49] im trying to contact a guy who had a wiki on miraheze but migrated to selfhosting, but i can't find his userpage on meta or request for wiki in the queue :ThinkerMH: [10:48:06] wonder if he's still here in irc [10:48:11] musicanimal [10:48:15] thats funny [10:48:53] wanted to show spcodex as example of music wiki but im getting domain error [10:49:09] wondering what's happened to wiki [10:50:53] ah, typo [10:50:57] musikanimal [10:50:59] ? [10:52:12] https://meta.miraheze.org/wiki/Special:RequestWikiQueue/11295 ? [10:52:56] yeah i found lol [10:53:11] but not sure if he'll response to meta talk page [10:53:17] was hoping for irc [10:53:42] eh [10:54:11] also not being sp fan i wouldn't never guess that it had completely different subdomain [11:01:36] isn't he a wikimedian? suggest checking their discord server/irc [11:27:00] He's still active on https://shinto.miraheze.org/wiki/Special:Contributions/MusikAnimal [11:27:29] You could contact him on Shinto [11:33:02] [1/2] ah right, i can't login lol [11:33:02] [2/2] yeah, it's not that urgent anyway [11:36:44] You atleast know where he's active [13:33:36] hi fancy donor [13:48:57] Who we have totally never seen or interacted with before [13:50:05] I've seen mooncloud [13:50:08] idk where but ye [13:53:17] Never seen a moonclod in my life [19:39:18] I cannot for the life of me figureout how to edit a skin in this wiki [19:39:29] i just want to change some colors and fonts but nothing seems to be working [19:39:47] i have next to no programming expirence and theres no tutorials on how to do this that i can find [19:48:36] Most CSS goes in "MediaWiki:Common.css" (Replace Common with the name of your skin) [19:53:09] which skin tho? [19:58:35] euidite [20:01:08] [[mw:Skin:Erudite]] yeah this one is rare case [20:01:09] [20:01:56] for newbies i commend Cosmos, it's a replica of old Wikia look, it offers color and background settings, works on mobile alright too [20:02:42] but in general, changing look of skin w/ CSS involves poking the page w/ browser's inspect element tool [20:03:01] like here https://discord.com/channels/407504499280707585/407537962553966603/1319311694979403849 [20:03:54] you make changes in console, see what works or not, then add those changes in, your case, MediaWiki:Erudite.css [20:04:16] ofc basic understanding of CSS is needed, gonna be hard w/o it [20:06:58] Erudite is a complicated skin. I wouldn't start with that either. [20:10:38] gotcha [20:26:51] why is it so complex? [20:28:06] ok now its giving me an error saying @import wont work use [20:32:30] While the design is visually clean, users have reported issues with the placement of navigation and settings links and the complexity of getting the skin to work with other installed extensions. [20:37:29] See also https://www.mediawiki.org/wiki/Skin_talk:Erudite [20:37:58] It might give you an idea of other users struggling with it [20:38:05] i wish there was a 1:1 oasis replica [20:38:15] is there anyhthings simlar to it? cosmos... I dont like [20:38:22] not enough width [20:39:02] Oasis = Cosmos* [20:52:30] there's a setting to change its width too, and hide the right rail thing [20:53:56] i cannot find any of the settings [20:54:03] its just a blank css page [20:56:38] look into Administration - there will be Additional settings link [20:56:48] then go to Styling tab [20:57:07] as you scroll down you'll see Cosmos related settings [20:57:09] ohhhh found it [20:57:18] yeah no settings showed up for euridite lol [20:57:34] yeah well [20:58:01] cosmos is the only one atm that offers settings for such things [20:58:49] even independent wikis don't usually poke inside skin, they go w/ css [21:28:00] tfw you lost custom domain and now google index your wiki [21:28:27] * BlankEclair punts google [21:30:19] [1/2] holy shit!!! one page!!!!!!!! /hj [21:30:20] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1443715589041553632/1764279014324.png?ex=692a146b&is=6928c2eb&hm=eaceb237bd1ea2c341839238f8fdfee2ae6e685fb3bca4e65ae983ab48516503& [21:30:44] it's the main page lol [21:31:05] [1/2] no fuking way lmao [21:31:06] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1443715782423871539/Screenshot_20251128_003045.png?ex=692a1499&is=6928c319&hm=55cd6e3cdc4cd469894cb1cb2060fe2fceb00cb34b700b274ad938302daa996c& [21:31:31] in incognito [21:49:57] [1/2] is this how linux users see out shit? (also incognito) [21:49:57] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1443720526949519360/Screenshot_20251128_004928.png?ex=692a1904&is=6928c784&hm=d7ddf5518afe018dc64e31a6e112639e2aa4187290a5a6ab1d15122d351fffd5& [21:55:28] [1/2] not all [21:55:28] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1443721915654209546/1764280523321.png?ex=692a1a4f&is=6928c8cf&hm=90b8896bffedf132abba9f423ae9533676f9828e1113039e101435da6cbb19c0& [21:56:16] what causes this ... [22:03:52] [1/2] Legroom [22:03:52] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1443724029990273145/Screenshot_from_2025-11-27_22-03-42.png?ex=692a1c47&is=6928cac7&hm=c5918e34e2254857748e7cfffead1d5fc5c375ed7e7470f3071ca4a35cd894fa& [22:04:43] https://cdn.discordapp.com/attachments/407537962553966603/1443724245124518040/Screenshot_from_2025-11-27_22-04-37.png?ex=692a1c7b&is=6928cafb&hm=f078f2b38ca2444ae56500fbaf0044bad28ff243265c7e567708d16a7e8e9dd1& [22:05:18] Fonts maybe? That's the kind of width I'd expect from a CJK font. [22:05:18] Ubuntu Linux, Cinnamon Desktop, Google Chrome (outdated) [22:05:54] but fonts appear normal in usual session [22:16:01] No CSS on Timeless for meww [22:22:44] cursed to forever use vector legacy [22:34:32] [1/2] nyarch linux, ungoogled chromium [22:34:32] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1443731749455528140/1764282871901.png?ex=692a2378&is=6928d1f8&hm=f2265d2b02ea0978a5af2db10edee7a4bb4266f06ab8cb75f8f1a4e0de0eba4e& [22:43:00] [1/2] yo are we all posting linux screenshots [22:43:01] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1443733880870801590/image.png?ex=692a2574&is=6928d3f4&hm=7265dd13428ba19917f3329fba367f1ed5255f87409359a750fa01d16fea5319& [22:44:07] lmao [22:44:28] okay, i guess i should feel paranoid about mangled css [22:44:40] *not [22:44:45] Wow, what set up is that [22:44:49] Also respect Zen [22:45:17] i3 [22:45:21] using mint [22:45:36] only installed it like 3 weeks ago [22:48:05] I kinda wanted a setup where content is maximised but without using fullscreen, so it works really well with i3 [23:36:52] IDK why Pizza Tower on Timless looks bad for me [23:38:11] first looks like custom css disabled [23:38:33] second looks normal except for theme toggler