[02:00:09] POV: its 10 PM and you should go to sleep to get used to the timezone [02:00:21] [1/2] me: [02:00:21] [2/2] https://cdn.discordapp.com/attachments/615786602454581249/1226350823068401714/nz4rE05.png?ex=66247334&is=6611fe34&hm=a9bacb28b02abeae275c1f9ec06302adf5efb1d0797e952f8b86020684d4361d& [02:40:49] https://cdn.discordapp.com/attachments/615786602454581249/1226361006436122644/image0.png?ex=66247cb0&is=661207b0&hm=edfe4e6727a93ac847b6c57fa60e9da906db4b0355cb19d1a6170f912a5b26e2& [02:40:56] lol [04:56:32] <.labster> This wiki has to be peak Miraheze: https://autisticcharacters.miraheze.org/wiki/Autistic_characters_wiki [05:24:16] @han.0000 yo [05:25:22] it's your baby [05:32:05] Lol that's cool [07:58:58] [1/2] A while ago I shared a mediawiki tool I made that relied on the Widgets extension. Well I just made a version of it on my own site so anyone can use it for their own wiki without installing anything on their respective wiki. Should work for anything that isn't overly massive :) Example: [07:58:58] [2/2] https://cdn.discordapp.com/attachments/615786602454581249/1226441073870504067/image.png?ex=6624c742&is=66125242&hm=e8f7c323a2c697ea25e5c4afc20a082bb48034816a125d84db7b536247556c86& [08:31:56] <.labster> Wait, are you running widgets on your own site, and using that to access the Mediawiki API? [08:38:16] Not widgets no, just my own JavaScript. ^^ [08:38:55] The widgets on MediaWiki hosts do run way the API queries way faster though lol [12:20:22] [1/2] I just spent like 10 minutes trying to figure out what the right way to include this class was [12:20:22] [2/2] https://cdn.discordapp.com/attachments/615786602454581249/1226506854738300968/DgZiz1N.png?ex=66250485&is=66128f85&hm=960a168ff3cd7f294a6a4deac2cf0216322957ab66dee8d13216c3613b84213d& [12:20:23] kill me [12:20:37] wheres that pig for throwing across a room [12:21:04] okay i feel better now back to work [12:21:23] My window is probably fine that crack sound is normal [14:51:36] are you seriously using vscode in a wsl ubuntu in windows [15:06:48] yes how did you know [15:07:08] theres also docker in there [15:27:16] What are you mkaking? [15:31:15] trying to make a simple barebones version of fandoms theme designer [15:31:27] to do stuf like change link color without CSS [15:36:04] Oh, meat [15:36:52] I have never made an extension [15:37:16] so its half prod project and 3 halfs stumbling through bs [15:45:53] so um how does one like load js on a special page [16:36:46] Welp..... [16:36:58] Rest in Peace Miraheze [16:37:22] @notaracham wait does the new board minute mean im gonna need to remake all these discord role icons? [16:38:57] Discord Admins will determine how we want to proceed w/ icons, tbd, but please do raise the topic in the upcoming meeting tomorrow if you're able to attend [16:39:03] [CryingAboutIt](https://cdn.discordapp.com/emojis/1000063458651422861.webp?size=48&quality=lossless&name=CryingAboutIt) [16:39:31] i may pop in a wee bit but ill be in school so :/ [16:39:40] I'll make sure it gets raised, then [16:39:43] I am surprised there was no RfC on this. [16:39:58] I would have expected this to be a community decision. [16:43:13] can we at least keep the support one, its way easier to theme a icon after the mediawiki flower with the heze then wikitide [16:43:30] I actually made a version that looks more like a flower I never got to sending [16:43:35] This won't be unilateral, there'll be some discussion about it both through the next meeting and an RfF on the general thought [16:43:57] RfF? [16:44:25] My impression from the minute was it was a fairly set in stone decision. [16:45:41] Not entirely [16:46:09] [1/2] ```The Board of Directors resolves: [16:46:09] [2/2] 1. To rename the Miraheze project to WikiTide.``` [16:46:18] We already discussed this with elected volunteers and SRE beforehand [16:46:18] The board has approved a rebrand to take place + timeline for it, which is different than a decree that it will take place. [16:46:29] We are now in the community consultation period [16:46:34] That.. should be clarifed [16:46:45] Which is what tomorrow's meeting is for [16:47:28] The official resolution text says the board resolved to rename, not the board approves if the community is for it. Can def be misleading [16:48:07] I’d agree there. I know the intention is for community consultation, as it was discussed prior and will be discussed in the future to have community approval, but can see how it’s a bit confusing. [16:48:21] The rest of the resolution further reinforces that [16:48:24] Again, board notes = legal text, not for general consumption [16:48:25] `Announcement of intent to rename the project to the community during the Miraheze Meeting` [16:48:32] True. [16:48:34] 💯 [16:48:52] Rest assured, the Board would not take such major decisions without community input. [16:48:57] I mean I am probably the only person who would bring it up this quick [16:49:19] Anyway, let's leave this topic alone for now, idiomatic cart before the horse and all that. [16:49:32] ❓ [16:49:38] Never heard that onw before [16:49:42] We're getting ahead of ourselves, is what I mean [16:49:57] I have a doctered in getting ahead of myself [16:50:00] [sorry](https://cdn.discordapp.com/emojis/925148611354968114.webp?size=48&quality=lossless&name=sorry) [16:57:31] what I missed [17:11:04] I only went for a walk round the lake [17:11:56] We seem to be a little slow [17:12:30] Link to these minutes ? [17:12:47] And yes we're a tad on the slow side [17:13:00] https://meta.miraheze.org/wiki/Board_of_Directors/Meetings/20240404-Minutes [17:13:06] [1/15] ``The Board of Directors resolves: [17:13:07] [2/15] 1. To rename the Miraheze project to WikiTide. [17:13:07] [3/15] 2. To designate WikiTide as the primary project of the WikiTide Foundation. [17:13:07] [4/15] 3. To maintain as policy that wikis that were created with miraheze.org subdomains may remain at such subdomains indefinitely, provided that individual wikis may consent to adopting a new wikitide.org subdomain. [17:13:07] [5/15] 4. To authorize the President to take action as needed to effect the name change according to the timeline below. The President may deviate from the timeline with notification to the Board. [17:13:08] [6/15] The Board of Directors approves the following timeline to implement this resolution: [17:13:08] [7/15] * April 8, 2024: [17:13:08] [8/15] * Announcement of intent to rename the project to the community during the Miraheze Meeting [17:13:09] [9/15] * Written announcement posted to Miraheze Meta the same day. [17:13:09] [10/15] * Deployment of footer logo around this time. [17:13:09] [11/15] * Beginning April 16, 2024: [17:13:10] [12/15] * Ongoing renaming of other Miraheze-branded pages to WikiTide, where relevant and not historical. Transitioning social media accounts and URLs of official wikis and websites (i.e. Phorge), GitHub URLs, and mediawiki.org pages. Expected to continue to roughly May 1. [17:13:10] [13/15] * April 18, 2024: [17:13:11] [14/15] * Announcement to the broader general public during the MediaWiki Users and Developers Conference [17:13:11] [15/15] * Deployment of brand assets to primary entry points, including landing page URL and identification, Meta wiki identity, and primary policy pages. Domain name changes for these wikis.``` [17:13:33] was it a unanimous vote? [17:14:24] You know what that means... [17:14:42] Pardon? [17:17:17] Read the minutes [17:17:17] If we're a little slow \:P [17:17:30] Ddos? [17:17:35] Yep [17:17:41] Ffs [17:17:47] For FUCK sake [17:17:48] hey! [17:17:52] UH? [17:18:01] for the record i was typing that message before rhinos sent his [17:18:03] ol [17:18:33] Humans confuse me [17:19:11] https://cdn.discordapp.com/attachments/615786602454581249/1226582058231533578/EBCbvb5.png?ex=66254a8f&is=6612d58f&hm=c2779ce1f656771f587f279e6ad663f3d1852d2b993c405636c74b34ca1625be& [17:19:15] mw182 [17:19:32] I will be like 10-15 minutes late to tomorrows meeting [17:19:47] I'll shut up on the meeting until then [17:21:51] 151/152/161/182 are taking a bigger hit [17:25:33] Just noting that I am opposed to any form of rebranding Miraheze as a whole; Miraheze already has an extant brand built up over the past 8.7 years, and it would be unwise to discard that unless required by law for whatever reason [17:27:36] As a human, I agree. [17:27:43] true [17:27:51] As maybe a human I concur [17:30:17] How do you not know some of the users here are not Large Lanage Models? 🙂 [17:31:28] (I am obv joking) [17:31:30] I've seen GPT talking about miraheze or mediawiki 🤣 Miraheze [17:32:03] Really? Does chatGPT know about Miraheze? [17:32:30] Try [17:32:32] Oh, they do know about it. Smart GPT [17:32:42] Someone asked it for help with mediawiki [17:32:48] it spouted grade A BS [17:32:54] funni [17:33:01] does it knows about wikitide [17:33:09] lol [17:33:19] [1/11] " [17:33:19] [2/11] Miraheze is a nonprofit organization that provides free hosting for wikis, similar to the popular platform MediaWiki. It was established in 2015 by a group of volunteers who were originally involved in managing various wikis on the now-defunct Wikia platform (now known as Fandom). [17:33:20] [3/11] Miraheze's mission is to democratize access to wiki hosting, allowing individuals and organizations to create and maintain their own wikis for various purposes, such as documentation, community collaboration, knowledge sharing, and more. The platform is open to anyone, and users have full control over the content and administration of their wikis. [17:33:20] [4/11] Key features of Miraheze include: [17:33:20] [5/11] Free hosting: Miraheze offers free wiki hosting with no ads or paid plans. This makes it accessible to individuals and groups with limited resources who want to create and maintain wikis. [17:33:21] [6/11] MediaWiki software: Miraheze runs on the MediaWiki software, which is the same platform used by Wikipedia. This allows users to benefit from the familiar interface and functionality of MediaWiki, including editing, formatting, and organizing content. [17:33:21] [7/11] Community support: Miraheze has a community of volunteers who contribute to the platform by providing technical support, documentation, and assistance with wiki management. Users can seek help and advice from the Miraheze community forums and other support channels. [17:33:21] [8/11] Customization options: Users have the flexibility to customize their wikis according to their needs and preferences. This includes choosing themes, installing extensions, and configuring settings to suit specific use cases. [17:33:21] [9/11] Open source: Miraheze is built on open-source software and operates transparently, with its codebase and infrastructure publicly available for inspection and contribution. [17:33:22] [10/11] Overall, Miraheze offers a valuable service for individuals and organizations seeking to create and host wikis for collaborative content creation and knowledge sharing. Its commitment to openness, accessibility, and community-driven development makes it a popular choice among wiki enthusiasts." [17:33:22] [11/11] - ChatGPT [17:33:38] That is what chatGPT knows about Miraheze [17:33:43] I asked it once and it claimed that WikiTide was about oceans; that may have changed, though [17:34:17] ChatGPT seems to know nothing about WikiTide [17:37:07] "WikiTide was a wikifarm created by a former Miraheze board member, which aimed to provide a platform for collaborative editing and sharing of information similar to other wiki hosting services." [17:37:14] Guess it did change [17:49:13] https://cdn.discordapp.com/attachments/615786602454581249/1226589612441469030/image0.jpg?ex=66255198&is=6612dc98&hm=bcb4a6687f247828920bc0d72d0635d77c587e0310ffe4cba8742446a6ff3dd8& [18:02:23] (late to the party but ahh!! that's my child! thank u Miraheze for providing me with a space to infodump <3) [19:44:56] [1/2] "WikiTide is the organization behind Miraheze, which is a free wiki hosting service that offers wiki creation and hosting for free. WikiTide provides the infrastructure and support for Miraheze, allowing users to create and maintain wikis on various topics without the need for technical expertise or financial resources. Miraheze hosts a w [19:44:56] [2/2] ide range of wikis covering diverse subjects, from educational resources to fan communities and open-source projects." [21:20:47] huh https://meta.miraheze.org/wiki/Requests_for_Stewardship?curid=4268&diff=386016&oldid=385634 [21:21:58] Rolled back [21:26:35] post-closure commentary can be alright although that certainly didn't add anything [21:26:57] noted [21:27:01] thou so much for "The following discussion is closed. Please do not modify it." [21:27:35] Actually advising use of the talk page would have been good [21:28:00] Should I leave them a message on their user talk to discuss if they wish on Talk:RfS? [21:30:59] I honestly wouldn't encourage them to drag it on much... a response may be to clarify the closure on their talk page and hold that discussion on their home turf [21:31:09] The whole RfS could've been rolled back tbh [21:31:22] very well could have, I think reception had thought of it [21:31:58] Noted [21:33:38] They thought of it on their own [21:40:18] I looked at this and left it as raidarr said concerning post-closure comment despite agreeing it was unnecessary and added nothing of value. [21:40:42] well, fine as it is now [21:40:57] we thought alike at about the same time replying to him on talk page [21:41:23] he has some very deep misconceptions, linking a random independent wiki to demonstrate local rename capability when that wiki is not at all affiliated with miraheze [21:42:05] [1/2] huh [21:42:06] [2/2] https://cdn.discordapp.com/attachments/615786602454581249/1226648219136692304/zV8KOGF.png?ex=6625882d&is=6613132d&hm=626b7f1a2ae88618c1056459ec9c289c8420688e3b67721749c42df45a9d7ad7& [21:42:16] didnt even think to check that at first lmao [21:42:32] wait this dont mkae sense without context do it [21:42:41] this is on the list of meta patrollers [21:45:58] this is a user who was hit by a gdpr request [21:46:07] or some such related; could be cosmicalpha [21:46:19] what [21:46:28] a request to remove that user from the patroller list would be in order since there is no way that account will be doing patrolling for sure [21:47:04] what happened to CA [21:47:09] could be someone else but the point is you don't know anymore :p either way that account certainly can't patrol anymore and should have its rights stripped [21:47:24] CA at one point requested to be GDPRed, that was my guess although it's possible some other patroller did it too [21:47:27] I'll make a AN ig [21:47:34] No this is recent [21:47:40] really [21:47:40] I didn't see it before [21:47:46] I think so at least [21:48:03] at the VERY LEAST since I became a patroller but way after as well [21:48:59] oh I understand now [21:49:10] ok [21:49:21] I know who it is, I'll drop the subject for privacy's sake [21:49:30] yeah, just have a removal request and that should take care of it [21:49:34] Yeah I saw [21:49:39] On it [21:49:58] Unfortunate. [21:50:05] IIRC CA did get GDPRed and created a new account after the WikiTide merger [21:50:12] it's not ca [21:50:26] I taught he just up and left the farm today for a sec lmao [21:50:44] within the half an hour since i talked to him [21:50:45] but yeah, that was the highest profile gdpr and without looking I assumed maybe there was a residual right there [21:51:01] and it become widespread knowledge to everyone but me lmaoooo [21:51:13] that would be massive news tbh [21:51:21] no I critically misunderstood how recent this was [21:51:27] is this AN or now M:RfP? [21:51:46] AN I would say as just a clerical removal even though it could technically fit M:RfP [21:51:52] AN it is [21:51:58] but M:RfP is a long/bureaucratic way to achieve it so I recommend AN [21:52:16] I hate that even though its AN and not ANI I mentally pronounce it an-e [21:53:36] What are M:RfP ANI and AN again? [21:54:48] RFP - request for permissions (m specifying meta), AN/ANI administrator's noticeboard [21:55:13] AH yes [21:56:53] ANI is on enwiki Administrators Noticeboard/Incidents [21:56:57]