Community noticeboard

Request for feedback: Restricting ability to modify certain core groups without assistance
A perennial issue which pops up every few weeks (both on Discord and on wiki) is someone reporting that they've deleted the bureaucrat or administrator group and have now lost their access to ManageWiki or even worse, locked themselves out of their wiki (in private wikis, it is actually completely possible to 100% lock yourself out if you delete the administrator group). In fact, if you look on the Stewards' noticeboard right now, you'll find 2 requests asking for the bureaucrat group to be recreated because the bureaucrat accidentally deleted the bureaucrat group.

As such, SRE wants users opinions on potentially restricting bureaucrat's ability to delete the bureaucrat and administrator group without the assistance of Stewards. This is mainly a safeguard against bureaucrats and administrators deleting the group without even knowing what doing that does, just for the sake of it because they can. Over the history of Miraheze, there have probably been over 100 requests for the bureaucrat and/or administrator group to be recreated because users accidentally deleted it. I don't see much net benefit in allowing users to delete them but if they want to, that's fine but we want to add a safeguard against these sorts of accidental deletions. We want to hear your thoughts on this and what you think so please let us know what you think about this. Thank you! Agent Isai Talk to me! 02:35, 16 December 2022 (UTC)
 * One thing I remember is someone said it's not possible to remove read from sysops to avoid locking yourself out of private wikis. This doesn't do much if you can just delete the group entirely. Also, I'm not sure HOW it's possible to delete any group bundled with core, much less why. So this would be sysops, bureaucrats, bots, and interface administrators. As for whether or not it's a good idea, I really don't like the idea of rigidly implementing things like auto-created pages, but in this case since it would be doing what core already should be doing anyway, it makes sense. Naleksuh (talk) 06:43, 16 December 2022 (UTC)
 * Per discussion w/ Agent over other channels and their relayed conversations w/ technical folks, while this isn't possible today it is within the realm of possibility.
 * If other technical folks agree with this assessment, removing the ability to self-delete core groups would be a good idea given the number of new admins with limited administrative experience we have joining from otherwise-turnkey platforms like FANDOM. --NotAracham (talk • contribs • global) 07:18, 16 December 2022 (UTC)
 * Since this discussion initially happened, in the last two weeks alone we've had no fewer than 5 instances of deletions that were completely unrelated to restoration activity.
 * Fixing these is a bad use of steward time and clearly demonstrates the need for this to be implemented --NotAracham (talk • contribs • global) 21:51, 2 January 2023 (UTC)
 * Not all wikis use the standard bureaucrat -> administrator -> everyone else setup, if we're going to introduce something like this it's very important we give them the ability to change this in the future.
 * While it'll take some time to make something like this, one thing that can be implemented quickly is a warning when deleting a group that has the  permission. Perhaps something like this next to the "Delete this user group" checkbox:
 * Warning: You're about to delete a group with permission to access ManageWiki. Deleting this group may lock you out of ManageWiki! Are you sure you want to do this? OrangeStar (talk) 10:21, 16 December 2022 (UTC)
 * Per the proposal, the main goal is just to make sure that users don't delete the group accidentally. Stewards would still delete it if requested, provided that a replacement group exists, one with ManageWiki rights. Agent Isai  Talk to me! 14:00, 16 December 2022 (UTC)
 * As long as the option exists, I agree with this change. OrangeStar (talk) 16:37, 16 December 2022 (UTC)
 * I would prefer the suggested avenue of clear warnings as compared to restricting the feature to require third party intervention outright. --Raidarr (talk) 13:13, 24 December 2022 (UTC)
 * The proposed warning message above that appears when you're trying to delete any groups/user rights that has ManageWiki permission should not be ignored (but be aware that some users might ignore this warning and they risk locking them out of ManageWiki unless a restriction that prevent the user that has a right with ManageWiki permission from deleting the group that the user have). This might or might not solve this perennial issue and I have to wait to see this. TF3RDL (talk &#124; contribs &#124; FANDOM &#124; Wikipedia) 04:45, 30 December 2022 (UTC)

Hi
Is my companyball wiki pages and my old userpage on companyball wiki gonna restore after companyball wiki got fixed and back to normal? ★ Commander Xiaochan ⚡ (Talk to me for fun) 06:47, 20 December 2022 (UTC)


 * Yes.Data was taken from db141 discs.Your wiki will be restored by using it if you make a request. by Buel ·Talk·e-mail 06:54, 21 December 2022 (UTC)

How long will the wikis be down?
My wiki, which is about the 1996 video game Super Mario 64, was down today due to the restoration. What I wanted to know is, how long can I expect it to be down, or other wikis for that matter? Revolution64 (talk) 12:30, 21 December 2022 (UTC)


 * about 4-6 weeks? ★ Commander Xiaochan ⚡ (Talk to me for fun) 16:24, 21 December 2022 (UTC)
 * Where did you get that info? I don't think it will be that long, since they on the Tech:RSE noticeboard they say they already have the servers back. Freighttrain (talk) 03:34, 22 December 2022 (UTC)
 * Maybe a week or two. Tali64³ (talk) 16:26, 21 December 2022 (UTC)
 * Yeah, the SRE will see SetsunaKnowsTheMatrix (talk) 19:14, 26 December 2022 (UTC)
 * I think maybe too many weeks PrincessTricktyy197 (talk) 20:07, 21 December 2022 (UTC)

Why does Miraheze have constant technical problems?
Some of those problems are minor (like 50x errors which only last a short time) and others are major (like the db141 thing), but why do they happen that commonly? In other platforms like FANDOM that doesn't happen. FtosorciM (talk) 21:03, 21 December 2022 (UTC)


 * Money. That's all. A free platform that pays no one and makes no profit cannot compare to the money hungry behemoth that is Fandom with their millions of dollars and hundreds of shareholders all seeking ways to cash out even more. The db141 issue though was a very unfortunate incident that was caused by a faulty drive but performance is due to the above. Agent Isai  Talk to me! 21:12, 21 December 2022 (UTC)
 * If I had to guess, it's because of not enough money and volunteers at SRE. Backups weren't being done at the time db141 happened because doing them put a lot of strain on the servers (I don't have a source for this, look for the initial post at the CN or one of the old revisions at the SRE Noticeboard), and they probably couldn't afford to bring down any one of them in fear of slowing the entire farm down. Miraheze is a CentralAuth wikifarm, which already isn't exactly trivial to even setup, keeping everything running smoothly, securely, and being up-to-date, while keeping backups of everything to prevent stuff like what happened requires both a lot of technical expertise and a lot of money. FANDOM can afford those things by virtue of being a for-profit with paid employees (which is undeniable an incentive for people to work as sysadmins there) financed via ads, but here in Miraheze we don't believe in ads, so it was decided back when this farm was setup to not have ads. OrangeStar (talk) 21:17, 21 December 2022 (UTC)
 * Money wouldn’t help PrincessTricktyy197 (talk) 22:33, 21 December 2022 (UTC)
 * That's just your opinion, I have but a limited understanding of how Miraheze's backend is setup, but I can definitely see how they would appreciate some extra money at the bank. More money means more everything: servers, database servers, everything. This means less 50x errors and better performance. More money also opens the door to proper regular database backups instead of XML dumps at archive.org. OrangeStar (talk) 11:23, 22 December 2022 (UTC)
 * Platforms like fandom are sponsored by hyper-aggressive advertising and being a commercial enterprise. Other wiki hosts substantially lack management options, flexibility, overall performance outside of issues, extensions/skins/features and upkeep (being relatively up to date) and support (a technical team that will actually address said problems). Or, they simply cost money. So to mirror what has already been stated and add a little more; you have a very idealist platform that makes very limited money, has a very limited technical volunteering force which is mainly able to just keep lights on as is and take out fires with little time to actually make the system more robust, and you have a platform that you cannot find with equivalent offerings for its scale (miraheze is ever growing but its resources tend not to grow in proportion). Recent issues have been a stacking of cataclysmic incidents that on their own are supposed to be quite rare, happening at a time which is bad for everyone involved between holidays and life in general. This year has been unusually subject to the recent issues, plus the growing pains of upgrades and concurrent changes intended to keep Miraheze alive in light of its growing audience. --Raidarr (talk) 02:40, 22 December 2022 (UTC)

Concerns about DOL Wiki?
Hi, After contacting stewards, they suggested I post here. Anyone else concerned about the content of the Degrees of Lewdity Wiki? The disclaimer seems extremely flimsy to me and the characters seem to be minors in basically every way. Not to mention the bestiality and the trauma meters that get filled by molesting these characters. The steward said that if there was enough concern expressed here, they could take action, but as DOL people have argued that their characters are over 18, it isn't against the Content Policy.

Thoughts? If I'm missing anything, feel free to chime in. Corvidae (talk) 05:49, 22 December 2022 (UTC)


 * I believe some discussion about this was held on the Miraheze Discord server in August 2022. I'm not sure exactly what happened, but I'd recommend giving it a read. --Blad  (talk • contribs • global) 11:05, 22 December 2022 (UTC)

If db141 is now fully restored, can you please add interwiki entries for companyball wiki
(1) https://companyballwiki.miraheze.org

★ Commander Xiaochan ⚡ (Talk to me for fun) 11:56, 22 December 2022 (UTC)


 * Wikis on db141 will not be available for a few more days. SRE is still working on restoring them. Tali64³ (talk) 15:42, 22 December 2022 (UTC)
 * db141 is fixed, can anyone or you add interwiki entries for companyball wiki ★ Commander Xiaochan ⚡ (Talk to me for fun) 00:51, 28 December 2022 (UTC)
 * Wow nice! PrincessTricktyy197 (talk) 01:16, 28 December 2022 (UTC)
 * This is now ✅ --  Joseph  TB  CT  CA   09:03, 30 December 2022 (UTC)

My infobox templates say "Lua error in package.lua at line 80: module 'strict' not found."
Some infobox templates on my newly-created wiki have the following error message: "Lua error in package.lua at line 80: module 'strict' not found." Does anybody know how to fix this? GenO (talk) 14:23, 22 December 2022 (UTC)


 * You'll need to change references in those Module pages (probably Module:Infobox) or one of the helper modules from require('module:strict') to require('module:No globals') and then copy over the no globals module from wherever you found the original templates. example link for 'no globals' module on wikipedia:
 * Root cause here is that a lot of wikipedia templates are using the Strict keyword from the bleeding-edge newest version of lua parser, we haven't upgraded to that version just yet. --NotAracham (talk • contribs • global) 16:57, 24 December 2022 (UTC)


 * I don't see any references that say require('module:strict') in the Module:Infobox page, but I did find one in Module:Infobox military conflict (which is one of the infoboxes I'm trying to use), and it seems to have fixed the problem (though the message about 'module strict not found' still persists). The problem I'm having now is that the borders of the infobox don't show up, and I can't get rid of some attached text that says "  " --GenO (talk) 17:54, 24 December 2022 (UTC)
 * Templates based on the infobox module often call other modules that will have similar dependencies baked-in, which is why this error is likely still appearing. You can also use the "Purge" function to force the server to render a new version of the page, which might remove the error too.
 * The borders-not-appearing issue is related to missing CSS. This is either stored in a /styles.css subpage off of Module:Infobox on wherever you borrowed this template from, or might be in the wiki's MediaWiki:Common.css page.
 * --NotAracham (talk • contribs • global) 18:23, 26 December 2022 (UTC)
 * Thank you. I managed to import the Common.css page from Wikipedia and it fixed the border issue. However, I used the Purge function and haven't noticed any change: there's still transcluded(?) text in the template that reads "  ". The page Module:Infobox military conflict/styles.css exists on my wiki, having been exported from Wikipedia, but I'm not sure if there's something else I need to do. I'll keep looking. --GenO (talk) 03:44, 27 December 2022 (UTC)
 * This text indicates that the TemplateStyles extension needs to be enabled on your wiki. --NotAracham (talk • contribs • global) 03:52, 27 December 2022 (UTC)

How to import pages from zh.Wikipedia?
The import page of my wiki seems to be imported from en.Wikipedia by default, how to import from zh.Wikipedia? -- SailRain  Talk 09:02, 23 December 2022 (UTC)


 * Importing by using interwiki?If so,please enter . by Buel ·Talk·e-mail 10:31, 23 December 2022 (UTC)
 * By using .-- SailRain  Talk 10:51, 23 December 2022 (UTC)

a private wiki] I own, there's been a problem with special pages since November 2022, probably due to an accidental configuration. Pages in the "Special" namespace simply appear as "There is currently no text in this page. You can search for this page title in other pages, search the related logs, or create this page." (for some reason, even you can click "create this page" and add random stuff in special pages, like "test" in Recent Changes), and obviously this makes the wiki broken. Axolotel Ukraine (talk) 13:42, 23 December 2022 (UTC)

Request – adding interwiki entries


Ora &#38; D (talk) 16:00, 26 December 2022 (UTC)


 * +  is back. Ugochimobi Can you copy the whole table from   to  ? Or should I list it here? Ora &#38; D (talk) 20:59, 29 December 2022 (UTC)
 * @Ora & D hi, please list whatever you want here. --  Joseph  TB  CT  CA   21:19, 29 December 2022 (UTC)
 * ↑ first thing first. Ora &#38; D (talk) 21:33, 29 December 2022 (UTC)
 * @Ora & D I've added the above table for the three wikis, kindly list what else you want for smallvillewiki here, thanks. --  Joseph  TB  CT  CA   09:02, 30 December 2022 (UTC)
 * @Ugochimobi Please add to :

Thank you! Ora &#38; D (talk) 09:18, 30 December 2022 (UTC)


 * @Ora & D It's ✅ now. --  Joseph  TB  CT  CA   09:29, 30 December 2022 (UTC)

Where I re-request creating wiki
The wiki I have is lost.Should I request on Special:RequestWiki or discord? by Buel ·Talk·e-mail 03:15, 27 December 2022 (UTC)


 * If your wiki is affected by the db141 issue, then all you have to do is wait for that issue to be fixed, hopefully before the new year. Tali64³ (talk) 03:49, 27 December 2022 (UTC)
 * Update: All wikis on db141 are now back up. Tali64³ (talk) 23:38, 27 December 2022 (UTC)
 * THAT WAS A GOOD JOB PrincessTricktyy197 (talk) 01:16, 28 December 2022 (UTC)
 * This is not a fully accurate statement, not all wikis are back.
 * All wikis that existed prior to the November crash are back online to their pre-crash state, with some exceptions -- those that were recreated have mostly been re-attached to the resurrected entries, but there are a few which are still displaying the unavailable error. Going beyond that, there's also a handful of wikis that have internal complications that are delaying their restoration.  See this list for the 20ish wikis impacted by this secondary problem: https://phabricator.miraheze.org/P475
 * For wikis initially created created AFTER the november crash that were also impacted by the december DB141 outage, reactivation is still pending. For ALL impacted wikis that had activity between November and December, if a backup was created on Dec 18, restoration of that edit history is ALSO pending.
 * More details here: https://meta.miraheze.org/wiki/Tech:SRE_noticeboard
 * --NotAracham (talk • contribs • global) 05:50, 28 December 2022 (UTC)
 * Your wiki falls into the latter camp (created after the initial november crash but also impacted by the december crash) that wasn't restored by today's activities.
 * We are working to get those wikis back online soon, this doesn't require you to take action, and you should hear more in the next few days, --NotAracham (talk • contribs • global) 05:51, 28 December 2022 (UTC)
 * It has been done.Thank you,everyone. by Buel ·Talk·e-mail 12:09, 28 December 2022 (UTC)
 * Your wiki falls into the latter camp (created after the initial november crash but also impacted by the december crash) that wasn't restored by today's activities.
 * We are working to get those wikis back online soon, this doesn't require you to take action, and you should hear more in the next few days, --NotAracham (talk • contribs • global) 05:51, 28 December 2022 (UTC)
 * It has been done.Thank you,everyone. by Buel ·Talk·e-mail 12:09, 28 December 2022 (UTC)

How do I add a boilerplates dropdown like the one All The Tropes has?
I have a wiki I have created called Short Stories & Prompts (shortstories.miraheze.org), and I want to be able to make it so that users can load a boilerplate. One thing I need this functionality for is the fact that I am doing a contest involving answering 1 prompt every week for the year, and I want users to use a template for that. How do I enable the loading of boilerplates in the editor? Bauerbach (talk) 22:27, 27 December 2022 (UTC)


 * @Bauerbach Extension:Preloader or Extension:InputBox can load boilerplate text into the editor of a new page. If you mean adding boilerplate to an existing page, I'm not sure if Miraheze has an extension that can do that. Miraheze does have Extension:MultiBoilerPlate, but the documentation seems to say it replaces all text in the editor when you select a boilerplate. Extension:BoilerRoom can insert text within an existing page, but Miraheze doesn't have it. You may want to request on Phabricator that it be installed, as per https://meta.miraheze.org/wiki/Extensions#Disclaimers. Dimpizzy (talk) 15:39, 31 December 2022 (UTC)
 * @Bauerbach I should have looked at All The Tropes before answering. I'm not sure exactly which, but I think it uses one of the first three extensions I mentioned in the other reply. Dimpizzy (talk) 15:56, 31 December 2022 (UTC)
 * Most likely Extension:MultiBoilerPlate because I see they have a Special:Boilerplates page, which is associated with that extension. Dimpizzy (talk) 15:59, 31 December 2022 (UTC)

Realtime Preview Extension
The wikimedia wikis have a realtime preview feature. Is there a way to add this to my wiki? Aaron Liu (talk) 03:17, 28 December 2022 (UTC)


 * From special:managewiki. by Buel ·Talk·e-mail 10:14, 29 December 2022 (UTC)

What if I don't want the edits of my old wiki restored?
I feel like I've made more progress on the new version of my wiki created after the db141 error in November than I did on the old version prior so I don't feel like managing what was on the old wiki once it comes back online (ie dealing with pages with same purpose but with differing names and levels of completeness). Will there be an opportunity to decline having my old edits merged in favor of keeping my new wiki? Or is there nothing I can do about this and I'll have to deal with the old content? Marxo Grouch (talk) 16:21, 28 December 2022 (UTC)


 * You will be able to opt out if you don't want the old content merged into the wiki. Check Tech:SRE noticeboard periodically for any updates. Tali64³ (talk) 17:24, 28 December 2022 (UTC)
 * Thanks. Marxo Grouch (talk) 19:11, 28 December 2022 (UTC)
 * Never mind. My wiki is now back online, and I guess managing stuff shouldn't be too hard. Marxo Grouch (talk) 16:06, 29 December 2022 (UTC)

Can we bring back the November 30-December 19 version of Fohs archive?
We need it back! PrincessTricktyy197 (talk) 19:19, 28 December 2022 (UTC)

Thanks for all the hard work after the recent "restoration"
Medieval monks used to keep copies of important documents (mostly about which land they owned) to give them some insurance against fires and mice. Nowadays we can have "Name of the Rose" type catastrophes of a different nature, but which would still be familiar to a hypothetical "Walter of Stephenage". I do not see it elsewhere, so may I offer my thanks to the people who evidently worked so hard to restore things after the recent issues. 2A00:23C5:CE07:1701:3152:D6D2:648C:41BC 04:33, 29 December 2022 (UTC)

I've been waiting weeks for my wiki to be restored.
My wiki was private, created in December, and started with a B.

I was getting sick of waiting, and wanted my friends to migrate to another wiki I created until our old wiki's restored, but one of my friends is really stubborn, and refuses to use the spare wiki.

I even asked for a new wiki, and apparently the wiki creation's on hold until everything's finished.

I could not find another suitable wiki alternative, and I'm overall starting to lose hope if our wiki will ever be restored.

I hate to sound rude, but if all your work's been wiped, and you've been waiting weeks for a chance to recreate your work, and one of your friends refuses to cooperate, all my patience has run out. ThatOneTanko (talk) 13:55, 29 December 2022 (UTC)ThatOneTanko


 * Was it on the new db141 that was corrupted by hosting provider error? If so, that may explain it. Check Tech:SRE noticeboard periodically for any updates. Tali64³ (talk) 16:52, 29 December 2022 (UTC)
 * The reopening of post-november wikis is now underway, and I can confirm that yours has been reactivated. It's been a long stressful trip for us all and we thank you for your patience. --NotAracham (talk • contribs • global) 03:00, 30 December 2022 (UTC)

General Updates on DB141 Outage
Per updates added to Tech:SRE_noticeboard, we have now successfully reopened all wikis and are in the process of importing 18 December backups to wikis initially created after the first outage.

For those wikis that were recreated after the first outage, we have now opened requests for importing 18 December backups as well.

Please see the FAQ section of the SRE noticeboard linked above for details on how to request integration of Dec 18 XML backups. NotAracham (talk • contribs • global) 06:11, 30 December 2022 (UTC)

request interlanguage for companyball wiki


★ Commander Xiaochan ⚡ (Talk to me for fun) 12:55, 31 December 2022 (UTC)


 * @Hyebun ✅; Happy New Year! :) --  Joseph  TB  CT  CA   00:41, 1 January 2023 (UTC)

Interwiki entries
Please add to : Ora &#38; D (talk) 14:38, 31 December 2022 (UTC)


 * @Ora & D ✅; Happy New Year! :) --  Joseph  TB  CT  CA   00:43, 1 January 2023 (UTC)
 * I've waited a year!
 * Happy new year. Ora &#38; D (talk) 09:51, 1 January 2023 (UTC)
 * @Ora & D Hehe, that can be true as you requested in 2022 and got attended to in 2023 :-) --  Joseph  TB  CT  CA   09:53, 1 January 2023 (UTC)

ReplaceText extension error
ReplaceText configuration error: Your wiki will not work with ReplaceText: Text replacements cannot be run if $wgCompressRevisions is set to true.

What should I do? Ora &#38; D (talk) 14:51, 31 December 2022 (UTC)


 * @Ora & D: ReplaceText might not be working anymore, but you might be able to use MassEditRegex as an alternative. Dimpizzy (talk) 19:22, 1 January 2023 (UTC)
 * That's too bad. Ora &#38; D (talk) 21:06, 3 January 2023 (UTC)

Fontpedia
I would like to request an import of Fontpedia backup as of 18 Dec to Fontpedia.

Wiki URL: http://fonts.miraheze.org

Silicona (talk) 15:55, 1 January 2023 (UTC)


 * Validated and added to task list, thanks! --NotAracham (talk • contribs • global) 20:45, 1 January 2023 (UTC)
 * All pages should now be reimported successfully, please let us know if there are any remaining issues. --NotAracham (talk • contribs • global) 16:54, 4 January 2023 (UTC)

Can we be sure that our wikis are safe here?
Just a general question. I know db141 has caused anxiety for several, and I'm glad the name has been retired. Thank you to everyone here for all your hard work over the past month and a half. I'm just asking because I still feel some of the weighted anxiety of losing months of work of possible subsequent database crashes. If it's a few days, that possibly count as unforeseen, sure, but I don't want to lose months of the hard work I've added into, let's say, Sega Wiki for example. Bawitdaba (talk) 17:13, 1 January 2023 (UTC)


 * SRE has been working in backups, see T8350 and the updated Backups page here in Meta. OrangeStar (talk) 18:05, 1 January 2023 (UTC)
 * You can download your own backups as well at Manage:DataDump, so you could be sure your data survives a Miraheze issue. I don't think it backs up images, though. (Although Sega Wiki may be too big to use DataDump, you might need to request it on Phabricator.) Dimpizzy (talk) 19:16, 1 January 2023 (UTC)
 * Yeah I got a lot of wikis to keep track of, so that's why I had hoped for automated backups. Looks like there's a proper plan in place, so that's good to see Bawitdaba (talk) 00:44, 2 January 2023 (UTC)

Import Dump maximum size
Is there any explicit upper threshold for the database size when importing an existing wiki? Sorry if this has already been discussed. Jack The Ripper (talk) 06:40, 2 January 2023 (UTC)


 * No. If it's smaller than 250 MB, you can upload the XML to Special:RequestImportDump, anything bigger than that, or if you want to import images, you can go to Phabricator. OrangeStar (talk) 11:48, 2 January 2023 (UTC)
 * FYI, the Phabricator link doesn't seem to be pointed at the right page. Dimpizzy (talk) 16:16, 2 January 2023 (UTC)

Share extension
Hello. I have activated the Share extension on my Satirapedia wiki, and I would like to know if there is a way to add Mastodon, Telegram and WhatsApp, and if the extension can be configured to appear in the Minerva skin (mobile version). Greetings. Anthony8IA (talk) 14:21, 2 January 2023 (UTC)


 * Hi there. I develop the extension so I can see if there's any way to implement a share button to other platforms. As for appearing on Minerva, that'll be harder to do but I'll check it out. Agent Isai  Talk to me! 17:36, 2 January 2023 (UTC)

Could someone tell me how to remove the space at the bottom of my template?
This is done without removing this: The template in question: https://fiction.miraheze.org/w/index.php?title=Mod%C3%A8le:Citation Thanks in advance for your help. Darkrai18 (talk) 23:00, 2 January 2023 (UTC)


 * Would it work to not have a newline after ? Dimpizzy (talk) 19:20, 3 January 2023 (UTC)



Ora &#38; D (talk) 21:06, 3 January 2023 (UTC)


 * I had specified a condition above. Darkrai18 (talk) 21:24, 3 January 2023 (UTC)


 * You removed it, didn't you? By adding "margin-bottom:0px". Ora &#38; D (talk) 21:42, 3 January 2023 (UTC)
 * Thank you very much, it worked. Have a nice day/evening. Darkrai18 (talk) 23:22, 3 January 2023 (UTC)
 * Open its source to see the actual lines. ↑ (Remove &  ) Ora &#38; D (talk) 09:53, 4 January 2023 (UTC)

Request for Feedback: Requiring verified email to request a wiki
While not as common an issue as bureaucrats deleting the bureaucrat group, an issue which does occur every so often (and did today) is that a wiki founder forgets their password and is thus locked out of their wiki. What we currently recommend is that the affected user do is that they stage a local election where they run for bureaucrat and sysop on a new account in order to regain rights. For private wikis, we usually tell users that there's nothing they can do.

Both of these circumstances are inconvenient to wiki requesters so as such, we want to know what users think about potentially requiring a verified email in order to request a wiki. This requirement would only require wiki requesters to have a verified email before they request a wiki and wouldn't extend past there. What do you all think? Agent Isai Talk to me! 23:40, 2 January 2023 (UTC)


 * Miraheze is a bit of an anomaly for a service provider of this scale, requiring an email for signup (or Gmail/FB authentication via SSO) is virtually-mandatory anywhere else.
 * While it's not necessarily a must for a casual editor, IMO anyone requesting a wiki should have a path to account recovery as a condition for approval. --NotAracham (talk • contribs • global) 23:49, 2 January 2023 (UTC)
 * I was going to abstain on the grounds that this issues is not common enough to warrant the extra hassle to sign up for an email address, but I thought about it some more, and this proposal actually brings some unexpected benefits for users: with an email address, users can edit on wikis that require confirmed email addresses, recover their accounts easily, and even email other users. Additionally, they can now sign up for services outside of Miraheze that require an email. Tali64³ (talk) 02:19, 3 January 2023 (UTC)
 * I oppose, a user's account is their own responsibility, as I've said before. The most that would be a good idea is a warning but that's just about it. The only good argument for supporting would be that most websites make you verify your email to use the account at all, but that doesn't mean we should. Naleksuh (talk) 04:29, 3 January 2023 (UTC)
 * Another argument in favor I'd add is that by signing up to run a wiki on Miraheze, this is a commitment and responsibility beyond that of an average editor -- if the account with Admin/Crat permissions is lost either through forgotten passwords or malicious access by someone else, this can easily be the end of an otherwise promising wiki-project.
 * As email addresses are inexpensive (often free) and reasonably easy to establish compared to setting up a wiki, this additional requirement is of benefit to both the platform and the end-user for assurance of project security and stability. I'd like to understand more about your opposition though... what's the negative impact to the user in requiring a verified email in order to request a new wiki? --NotAracham (talk • contribs • global) 05:16, 3 January 2023 (UTC)
 * Because it's adding a new requirement? That's self-explanatory. I also don't like this trend of Miraheze telling users how to manage their own accounts. Naleksuh (talk) 05:39, 4 January 2023 (UTC)
 * This would be good idea ★ Commander Xiaochan ⚡ (Talk to me for fun) 05:34, 4 January 2023 (UTC)
 * I believe this limitation is necessary to prevent depletion of Miraheze limited database. --1108-Kiju /Talk 08:50, 4 January 2023 (UTC)

Add Interwiki entries for companyball wiki
★ Commander Xiaochan ⚡ (Talk to me for fun) 05:47, 4 January 2023 (UTC)


 * @Hyebun ✅ --  Joseph  TB  CT  CA   08:53, 4 January 2023 (UTC)