[03:13:22] <__mangone__> is it possible to have a clickable gallery similar to fandoms galleries? I don't like that it takes you to the page of the file as opposed to just viewing the image larger on the same page [03:28:14] you need to enable media viewer extension, it will work like on Wikipedia [03:29:53] <__mangone__, replying to theoneandonlylegroom> it didnt do anything [03:30:08] <__mangone__> do i gotta change something on the pages? [03:30:57] no [03:31:05] you sure you enabled correct one? [03:31:17] MultimediaViewer [03:31:26] <__mangone__> yup [03:31:32] also it takes a bit of time for extensions to start working [03:31:41] try to purge cache too [03:31:48] <__mangone__> how do i do that again? [03:31:53] <__mangone__> f5 or smth [03:32:26] ctrl + F5, or purge button near edit [03:32:39] also maybe check this setting [03:32:52] I believe it's enabled by default [03:33:05] <__mangone__> yeah its enabled [03:33:09] <__mangone__> purged cache and it did nothing [03:33:15] <__mangone__> ig ill just wait a minute [04:08:42] Ctrl F5 force purges your browser's cache, purge action on the page forces the MediaWiki server to parse a new version, to my understanding [04:09:16] So a little different in outcome, but both are relevant when testing changes. [05:05:00] <__mangone__, replying to theoneandonlylegroom> the mediaviewer only works properly on some images [05:05:28] <__mangone__> like the gallery images take you straight to the file page but the character sheet images show the mediaviewer screen [05:06:27] you mean gallery vs file:/thumb syntax? [05:06:40] <__mangone__> i have absolutely no idea [05:06:48] <__mangone__> basically [05:06:55] <__mangone__> this brings up media viewer [05:07:06] <__mangone__> these dont [05:07:14] portable infobox, alright [05:07:21] <__mangone__> ohh [05:07:23] <__mangone__> yeah thats the template [05:07:28] lemme check my wiki [05:09:43] hmm no, works fine on my wiki [05:10:05] [06:26:18] how do I make pr tho <:ThinkingHardMH:769233180799795221> [06:27:30] I guess wame will go to my other recent task [08:24:55] I've reopened the task. I'm not happy with that close. [08:25:52] do feel free to send a PR [08:26:06] I'm with family today. I can look tomorrow. [08:26:11] I'm trying to navigate through the almost 200 Phabricator tasks, quite a challenge [08:26:30] a crash team as suggested by Raidarr may yield fruits there [08:27:45] key word "how" cus github honestly confuses me to no end, or I should open an issue? [08:28:03] @theoneandonlylegroom issues shouldn't even be enabled [08:28:09] ah [08:28:31] I'm afraid to touch gh because of accident fuck up lol [08:28:34] https://github.com/miraheze/mw-config/compare is how to create a PR [08:28:48] But if you're not sure, we can do it for you [08:29:09] I'm not happy with asking users to do technical stuff [08:29:57] your assistance in helping sift through Phabricator configuration requests would be most welcome and appreciated then [08:30:59] Probably going to be new year before I can do too much [08:31:23] 162 tasks is what I count at the moment [08:31:32] this only includes tasks with medium priority and up [08:33:18] Ok [11:49:13] [1/2] @orduin kindly check inbox [11:49:13] [2/2] Would appreciate that 🫡 [15:05:43] [1/2] hi, our wiki is still inaccessible because of the expired ssl cert \:( [15:05:43] [2/2] can someone point me to the right direction to solve this? [15:06:09] its becoming a showstopper to our community [15:52:17] could a multilingual wiki work on miraheze/mediawiki? [16:16:04] yes, with the Translate extension [16:16:24] installed it, it's so confusing lol [16:16:37] especially when you have html all over the place [16:17:00] i have to place inside every span, div etc [16:17:14] yeah, unfortunately it's not the easiest/nicest extension to use [16:17:17] because the translators don't know how to handle wikitext [16:17:36] at least it can be done :) [16:18:52] you made phab request? [16:27:39] hi! no, not really familiar with that [16:29:06] [1/2] [[phabricator]] [16:29:06] https://meta.miraheze.org/wiki/phabricator [16:29:06] [2/2] as I understand, you want to remove custom domain from wiki now? [16:29:07]

[16:29:19] cc macfan if you are here [16:30:03] domain expired about a week ago [16:30:32] [16:54:37] Another idea is to make alternate pages or subpages with different languages and make custom link to direct readers to the subpages or alternate language pages [16:54:54] perhaps actually [16:55:07] the extension isn't working for nonadmins anyway [16:56:17] If the extension has an specific permission, you can make or search a wikigroup. Check if one exist, if not, you can make one group and that permission to that specific group [16:58:03] .miraheze.org/wiki/Special:ManageWiki/permissions [17:10:47] no, the domain ssl just expired, i just want it to be up again [17:12:30] Is there a way to wipe my wiki? [17:27:31] no, then it's not a wiki problem, you should renew domain by yourself [17:27:38] whenever you bought it [17:28:10] [1/2] delete or reset to blank state? [17:28:10] [2/2] either way can be requested on [[SN]] [17:28:10] https://meta.miraheze.org/wiki/SN [17:28:10]

[17:28:38] reset to blanks, alright. [17:28:39] . [17:37:36] [1/2] Hi, the domain itself is not expired, its the lets encrypt cert that didn't renew (which miraheze handled during wiki creation) [17:37:36] [2/2] the domain itself has other subdomains (hosted outside of miraheze) working just fine [17:40:59] If Miraheze is handling the cert via LE, it will need to be renewed by them. [17:48:19] Essentially, users see this very unfriendly warning on chrome, but the wiki can still be accessed if users click on "proceed to (unsafe)". But our community isn't very tech savvy so this warning turns them off 😅 [17:48:57] makes sense. so a phab task would be necessary, right? [17:50:02] its weird cuz our custom domain has been up for almost 2 years now, it just failed to renew letsencrypt just now [17:50:03] Yep 🙂 [17:55:13] okay sounds good, thank you! [17:56:47] I also have a wiki with a custom domain that expired in October; I haven't gotten around to filing a Phab task to remove it for various reasons [18:08:13] I've witnessed a fair share of hackers before. [18:09:27] I also had trouble designing conditionals with MediaWiki, since I mainly scripted using Roblox LUA. [18:18:26] [1/2] If you just need simple conditionals you can do it with some parser functions https://www.mediawiki.org/wiki/Help:Extension:ParserFunctions [18:18:26] [2/2] Otherwise Modules are just LUA (Though I know practically nothing about that language, so can't help with the specifics there, and the little I tried looking up once sounds so errorprone (like it makes JS seems resilient... which in reality is is not at all xD)) [18:26:37] [1/5] Hi, I'm fairly new to Miraheze and I'm afraid I've made a total rookie mistake. I added a friend as the first user for my wiki and assigned him to the members group. Unfortunately, when I tried to take away his rights to edit pages, the "members" user group disappeared altogether. Since the group is a preset group, I don't think I can create it manually in this form, can I? Can some [18:26:37] [2/5] one perhaps tell me if and how I can get my members group back? [18:26:37] [3/5] Unfortunately, I can't add anyone to user groups that I have created myself, as they are grayed out as options when I want to add users to groups. 😦 [18:26:37] [4/5] I know these are probably pretty noob questions, but I'm thankful for any help anyway! [18:26:38] [5/5] Best regards! [18:39:58] can i just uninstall the translate extension? [18:40:24] i've edited one page with it so if i rollback the translate tags everything should be back to normal? [18:40:50] and then we'll do manual translation with / [18:51:16] never mind i did it and it was fine [19:03:25] What’s your wiki? I can try and check logs for ya [19:05:46] You have to allow the "bureaucrat" group to assign other users groups you create yourself; you can also recreate the "members" group, as it's a group like any you create yourself [19:09:22] O [19:09:25] Elo Tali [19:11:45] Thank you so much! It is just called "DsA", the data base is called "dsakampagnewiki". [19:11:53] Thanks! [19:12:45] Ping me if what Tali said don’t work, I’ll try and check it out following my consumption of delicious sustenance [19:17:39] I forgot how to set up my wiki lmao iI'm sorry but what modules do I need to get started? [19:21:37] Depends on what you need, for example my wiki has no modules, I tried to install MBox but gave up in favor of a wiki text template [19:22:30] I want modules. It's what I've always used. it's for ns roleplay [19:24:27] Well, just install the modules you’ve used/you need. I don’t know what your wiki is, and every wiki has different needs [19:24:43] Main module I would think of it MBox and it’s dependents [19:29:30] they're wiki modules and I have so many on my main wiki I can't remember what the first one is called [19:41:23] Special:AllPages can help you figure that out (it provides a list of all pages on a wiki that can be customized to a specific namespace) [19:55:36] Or PrefixIndex [19:57:53] Hi, does anyone knows if I have to do something more to create a domain and point to my wiki? for the domain documentopublico.com.br I setup the name table with the url documentopublico.miraheze.org but it goes to the root miraheze.org... is that a webserver setup? I have opened the phabricator ticket is there anything else more? [19:59:36] you need to point it to mw-lb.miraheze.org and then make a [[Phabricator]] request asking that it be configured, otherwise the server doesn't know what wiki you're looking for [19:59:36] https://meta.miraheze.org/wiki/Phabricator [19:59:36]

[20:01:49] There’s a guide on meta wiki [20:52:53] ok thank you... I have request Task ManiphestT11556...but I dont know if its right [21:04:48] [1/4] WikiTide people: [21:04:48] [2/4] Has your Board said anything officially about the proposed merger? [21:04:49] [3/4] What about UO? I only see a few messages from him here. Did I miss anything? [21:04:49] [4/4] You say disputes between you and MH "staff" have been resolved. What exactly does that mean and why couldn't it have been done instead of leaving MH? [21:09:04] Sorry I haven't been to involved in the matter, mostly because the others have answered everything decently, and I am currently on vacation for the holidays + sticking to technical work when around right now. I am however open to any questions anyone may have for me. [21:09:32] What’s the latest RfC scores? [21:11:18] The 4th option would be death for Miraheze and the number 4 is said to mean death in some parts of the world. Hmm… [21:11:42] Still option C winning by a landslide [21:11:49] OK good! [21:13:27] @mrbradlerz You need to /auth to post links [21:14:32] Ah, I was thinking about the holidays, too. I just thought you would know before this was posted hence the question. [21:14:52] OK thanks! I left the server and rejoined, so i guess i need to “re-auth” now! I guess the bots don’t “remember” members who left as it would take up additional space on the host? [21:16:09] Could you answer the 'why fix stuff now' question, please? [21:19:44] [1/4] To answer some of the other questions: [21:19:44] [2/4] * Our board was consulted before the RfC went live. The language of 1C was created with our input, and we'll be holding a special session to approve merger discussions shortly to speed things along should 1C pass [21:19:44] [3/4] * Regarding disputes, that's something that doesn't happen overnight in any case, we've been making those amends in private discussions before there was any discussion or thought to a merger proposal and have already started collaborations with MH tech folks where appropriate on projects of mutual interest. [21:19:45] [4/4] Even if 1C were to fail, this collaboration is something we'd continue doing anyhow -- we like* the remaining MH folks and enjoy working with them, despite differences of opinion [21:21:25] [1/2] I have been following the merge discussions closely... if I felt a need to say anything I would have the others just handled everything good and since I am busy with other things I've stuck to that. There just hasn't been a need for me to jump into anything yet. If there is, I definitely will, and like I said I am open to any questions anyone may have for me [21:21:25] [2/2] as well. [21:28:37] [1/3] Re disputes: [21:28:37] [2/3] Of course but the reason I am asking this is because another dispute will surely kill the new organisation and this time there very likely won't be a fork for users to flee to. I guess what I am really trying to ask is why spend so much time and energy now trying to salvage everything when, perhaps with cooler heads you could have not ended up in this mess to [21:28:37] [3/3] begin with. But I don't think you (just so we are on the same page: this is plural) can answer that. So I really just want an assurance that the community should not expect something like this again. [21:28:58] [1/2] Re everything else: [21:28:59] [2/2] 👍 [21:31:31] 1st choice supports for D are sad [21:31:50] I need to make my other votes when I'm not drunk [21:35:49] There's a problem with Module:Documentation/styles.css [21:38:10] [1/5] I like to think we are able to learn from our history and move on into a stable environment, and not have the same issues ever occur again. I'd like to think things can move in a civil manner in the future and regardless of disagreements work through them for the betterment of the community as a whole. The last thing we want is a damaged community, and for th [21:38:10] [2/5] e good of the community we need a stable internal environment and I believe we can achieve that. [21:38:11] [3/5] I speak in the "I believe" tone because I can't possibly know for sure nothing would happen again, but I give you my personal assurances I will always do my absolute best to avoid another situation as has happened in the past. I will always try to keep a cooler head. I respect this community and the last thing, I think any of us want is for anything to happen [21:38:11] [4/5] to it. So I do think we can all work together and put aside whatever happened in the past for the good of the community and not let what happened before happen again. In my personal opinion I believe a merge to unify the platform again would be the best for everyone on both platforms, and the volunteers to not be stretched so thin by unifying it again. [21:38:11] [5/5] To be clear, while I can't possibly know nothing would ever happen again, I do 100% honestly believe that this will be avoided from ever happening again in the future. [21:39:37] These past few months have given us time to reflect and to see how we can avoid situations like the June incident and also other incidents which contributed to the general stress that was felt in the air. I believe with this newfound insight and many developments over the past few months, we will overall be far more resilient against such issues in the future [21:40:00] I second that as well. [21:40:52] From talking to a lot of those involved in C over the last few days, I feel a lot more confident and like it's the right move compared to June [21:41:31] Seconded. Words are just words, but the situation on the ground and the people in play are materially different than they were 6 months ago, too. Only time can prove out how much of a change that is, but I'm excited for what that experience can bring to bear under a combined team. [21:41:33] I know, right? Why would people act like they’ve lost all hope for Miraheze? [21:42:07] You've answered your own question. They feel like they've lost hope. [21:42:28] Some folks just want to watch the world burn, and it looks like we've found a selection of them. [21:42:28] I really do hope this isn't our curtain call [21:42:42] And it does look like C will be approved come the end of the year [21:43:22] That’s terrible when you feel that way. Especially when you post it somewhere that would affect the future of the best free wiki host out there! [21:44:37] The RfC is a big decision for everyone voting [21:44:51] Which is why I spent a long time considering B v C [21:48:47] As one of the people who supported D, I can assure you not once in my life did I expect to be in that crowd but all the stuff that happened really unsettled me. [21:49:15] But I really wish it doesn't come to that. [21:49:24] Do you not believe that B/C have any reasonable prospect of success? [21:49:32] Like that's at least worth a chance [21:49:46] Because an unconditional support for D is a vote for the end [21:55:48] I hear you on that, and I hope we can reach a point where enthusiasm for the project feels warranted for you again under B or C. [21:57:38] My support isn't totally unconditional. I just think that SRE needs more people and B just can't fix that issue as nicely as C. But then again, C can fail in the same way the Premium Offerings RfC did (which is why I asked what I did today). So if B and C both fail in terms of implementation, I want D. [22:00:10] Anyway, thanks for the answers. I hope for the best for this farm regardless of which path we take. [22:00:40] Did the premium offerings RfC fail? [22:01:50] whats the difference between wikitide and wikiforge functionally? [22:02:05] Is that supposed to be rhetorical? Because it doesn't sound like that. [22:02:33] Oh no, I'm actually asking. I think I understand what you mean though, failed in that it wasn't implemented, right? [22:02:34] I think there was a confusion in what the meaning of it failed was. [22:02:42] yes, I thought you meant failed as in the vote failed [22:03:32] Oh, no, I actually meant failed in the sense that the implementation never happened. [22:04:15] I'm not sure I quite read that from your vote [22:04:21] Your thinking aligns with me [22:05:13] Your vote reads like D is preferred over C [22:05:18] Which confused me [22:05:28] what're y'all even taljking abt lol [22:05:39] I do agree that B feels like less of a chance of success than C [22:05:59] Whether to shutdown, transfer or merge Miraheze [22:06:06] https://meta.miraheze.org/wiki/Requests_for_Comment/Reorganization_of_Miraheze [22:06:17] Oh, maybe I will clarify that tomorrow once I get some sleep. [22:06:22] See RfC link in Announcements (and linked by Rhinos) for more details/context [22:06:32] wdym shut down [22:07:02] [1/2] My micro-summary from yesterday: [22:07:03] [2/2] https://discord.com/channels/407504499280707585/407537962553966603/1188717427123564674 [22:07:45] In the case that there isn't a transfer of operations to B or C, an orderly wind-down of service would take place, but that's the least-likely to happen at the moment. [22:08:03] Cease all operations effective a to be decided date [22:08:28]