Community noticeboard

Archives:
 * Archive 1 (23 July 2017 - 25 November 2017)
 * Archive 2 (1 December 2017 - 3 March 2018)
 * Archive 3 (3 March 2018 ~ 11 June 2018)
 * Archive 4 (10 June 2018 ~ 29 September 2018)
 * Archive 5 (29 September 2018 ~ )

Wikia Uncyclopedia
In response to Wikia's decision to cease hosting the original Uncyclopedia, editors are now voting among four new candidates for a new home. I advocated Miraheze but this got no traction (Uncyclopedia Admins apparently wanting an anxious sales pitch from Miraheze Stewards) until The Pioneer followed up. In the voting discussion, the current site notice stating that capacity is low and "updates will fail" has been cited as a reason not to choose Miraheze; also the deteriorating state of finances. 10:49 15-Mar-2019
 * Well, unless people donate there is nothing we can do, we are a non-profit and that is how this whole site lives, from donations. Where is the discussion page? Reception123 (talk) ('C' ) 05:53, 16 March 2019 (UTC)
 * Found it! Will comment. Reception123 (talk) ('C' ) 05:57, 16 March 2019 (UTC)
 * Yes, thanks for doing so, and for clearing up misperceptions. There are people in that discussion from the other three candidate webhosts actively advocating for themselves.   17:14 16-Mar-2019

I've asked some questions relating to this here on Talk:Miraheze. I should probably have posted them on this noticeboard instead. Flyingcat (talk) 23:56, 16 March 2019 (UTC)
 * Probably Stewards' noticeboard, as it is more for wikifarm management than for the community.  00:53 17-Mar-2019

Decision looms
Repeating, the end of the month is the apparent date at which Wikia closes the original Uncyclopedia. Some there continue to argue that lack of money and lack of storage space would mean that relocation to Miraheze would be a dead end. asks at Talk:Miraheze whether, in the case that it is a dead end, it is a dead end that leaves in place an abandoned copy of Uncyclopedia for new imitators to reside in.

Inadequacy of storage and of funding are real issues to a few voters. I think that, in the more numerous cases of members of competing wikis who are kibitzing in the debate at Wikia, it is an excuse.

Miraheze management has taken the stance of passive welcoming. If it can instead give assurances that Miraheze is a good long-term host, it can acquire another website as notorious and active as All The Tropes. This should be of interest to a wiki farm that wants to be put on the map and perhaps even get a Wikipedia page that isn't immediately taken down. 17:08 23-Mar-2019
 * The vote's over. The people have spoken and Miraheze is a loser. Storage and money won't be enough to make them move to The Mirror Wiki or Miraheze to be with you. You were holding them back and everyone is happier without you. Accept it and move on friend. Alwam101 (talk) 05:56, 24 March 2019 (UTC)
 * The Pioneer declined the majority of the requests. There are a few (Arabic, Russian, Japanese), but the rest will either be hosted elsewhere or become defunct. Dysklyver (talk) 15:18, 28 March 2019 (UTC)
 * Italian (Nonciclopedia) did move here as I was not willing to accommodate some of Wedhro's more oddball demands, including the demand that the wiki be locked down so that no one can edit. There was also an attempt to move Polish (Nonsensopedia) here; that ended with the community not being satisfied with Miraheze due to a number of serious errors (including a mass-dump of Italian Nonciclopedia content into Nonsensopedia, which never should have happened). The main community is now at independent nonsa.pl, leaving me stuck with the awkward question of the fate of the nonsensopedia.org custom domain as that move has left the domain pointing to a fork, not the main project.
 * The Russian ("Olbanian") Uncyclopedia has also moved to independent hosting after encountering unresolved technical problems here.
 * There are four others (ar-beidipedia, eo-neciklopedio, id-tolololpedia and zh-cn.uncyclopedia) which were still planning to move here; so far, less than a quarter of the content which needs to be in these wikis before the Wikia versions go dead ("This wiki is closed", no redirect, no other explanation) is there and the import has slowed to a crawl. It is becoming rapidly apparent that the wikis will not be ready in time. See https://meta.uncyclomedia.org/wiki/Forum:Reorganization_of_the_whole_Uncycs#Deadline_is_near.2C_but_not_even_the_half_of_every_articles_are_imported
 * Miraheze was defeated in a vote on http://uncyclopedia.wikia.com/wiki/Forum:Hosting_options_for_Uncyclopedia_(wikia) on the fate of the original English-language project. That outcome could have been avoided had Miraheze done a better job of handling the other, smaller Uncyclopedia projects which had attempted to move earlier - such as Polish - and if they had deployed adequate infrastructure to handle the task (at 5.2 million revisions in database, en.Uncyc is not "All the tropes"... it's larger, and 100Gb virtual RamNodes are not going to fill the bill).
 * Ansaikuropedia (Japan) is not Wikia, was never Wikia, and is not closing down. The Pioneer had made a number of misleading posts a month ago, both on the meta.uncyclomedia.org thread and spammed across every Uncyclopedia-related Wikia on which the Wikia shutdown notice was posted, making false claims that I was shutting down my server or that projects which I am currently hosting were being moved away - effectively portraying this as a two-way choice between uncyclopedia.co and Miraheze. I'm not going anywhere. The Ansaikuropedia hosted on Miraheze is not the main project, it is a fork created by a minority of users who were objecting to one user on ansaikuropedia.org being a bit quick to issue broad IP rangeblocks in response to vandalism.
 * Many of the other projects, such as Uncyclopedia 2.0, are projects which have nothing to do with us but which are reproducing Uncyclopedia content, logos or branding without authorisation from the original creators or proper attribution.
 * The rest that Dysklyver wants to fork are already defunct; I've hosted them on my own server (so language xx: is xx.uncyclopedia.info) and the data is safe, but there appears to be no active community. I see nothing to be gained by duplicating the content again, if no one is actively editing. Why did you request these, again?
 * At this point, the time for discussion of the fate of the original uncyclopedia.org is long past. Miraheze needs to be doing some serious damage control to ensure that the handful of Uncyclopedia wikias which did choose to move here will be ready on time, as any site notices on the old sites saying "we've moved" need to be already running now. The whole Wikia mess goes dead on April Fool's Day and there will be no opportunity then to post anything on their side to say where the communities have gone. We've had a month to prepare and deal with this; I made my hardware upgrades and grabbed backups of everything weeks ago, why are you folks seemingly asleep at the switch? Carlb (talk) 21:48, 28 March 2019 (UTC)
 * Hmm. I'm going to poke the sysadmins on all of the import tasks. They really shouldn't be taking this long. -- Void  Whispers 22:19, 28 March 2019 (UTC)

DNS Redirect
Hello guys,

I have made a DNS Redirect from my OVH Hosted domain so that http:// or https://zw.fontainebleau-avon.fr redirects to zero.miraheze.org

In my browser, when typing http://zw.fontainebleau-avon.fr/, everything seems to be fine to navigate in the Wiki, but if I click on one link on the left menu below the logo such as "Recent changes" or any other one, a blank page is displayed. It sounds that it does not work for any Special Pages.

Does anyone ever tried to do this ? Is this a normal behaviour ? How can I change that so that anyone reaching my Wiki from zw.fontainebleau-avon.fr has a correct behaviour ?

Thank you for your help, Kevain (talk) Kevain (talk) 22:17, 22 March 2019 (UTC)


 * Hi, you need to follow https://meta.miraheze.org/wiki/Custom_domains . For the safety of you and other users you need to add a cname so that we can generate a ssl certificate. Also we set a variable that fixes issues with links. Paladox (talk) 22:53, 22 March 2019 (UTC)

What is the limit of erotic/nude/pornographic content?
I have read your Terms of Use, but they only say that you must not violate the laws of California or the Netherlands, in addition to the obvious prohibition of nudes of minors. But the limits of erotic images aren't explained.
 * 1) Is pornography allowed? What kind of pronography is prohibited? (Obviously, the child pronography is forbidden).
 * 2) Are nudes allowed? What types of nudity are not allowed? For example, those of Wikia FANDOM do not tolerate nudes, but they do accept artistic nudes and "doll nudes" (they are naked that do not have nipples or genitals, like dolls for girls).
 * 3) And what about the "hentai" (pornographic illustrations with anime/manga style)? And the "ecchi" (illustrations not pornographic but e'roticas in anime/manga style)? And the "lolicon/shotacon" (they are underages drawn, that is, they are not real people, but they are often drawn in a perverted way)?
 * 4) Is it possible to talk about erotic video games or h-games (hentai games)? For example, there is a wiki that deals entirely with an erotic game: https://cursedarmor.miraheze.org/

I know these questions are annoying, but I've seen in some wikis (most were Chinese) that had pornographic images. --PaladinDeGigantas (talk) 00:28, 23 March 2019 (UTC)
 * As long as it is legal in the both countries, it should be fine. Reception123 (talk) ('C' ) 08:56, 24 March 2019 (UTC)
 * I will note that drawn pornographic depictions of minors are generally illegal in the Netherlands since a 2011 law banning it. This differs from the US where I understand it is a grey area. Dysklyver (talk) 15:23, 28 March 2019 (UTC)
 * Hey Dysklyver, do you think that this gallery is illegal in Netherlands? It contains "doll nudity" (that is a nudity that doesn't have genitalia or nipple exposure, beacuse they are "deleted" from the drawing): https://brigadoon-marin-and-melan.fandom.com/wiki/Eternal_Green/Gallery --PaladinDeGigantas (talk) 17:09, 28 March 2019 (UTC)
 * If it's not pornographic in nature, I'd say it's probably fine. -- Void  Whispers 21:10, 28 March 2019 (UTC)
 * I concur with Void. Dysklyver (talk) 10:43, 31 March 2019 (UTC)

Translation of the Miraheze homepage
Translation from https://miraheze.org for more languages.--Eduaddad (talk) 15:47, 24 March 2019 (UTC)
 * Translators will handle this issue soon. --Anderlaxe (talk) 13:11, 6 April 2019 (UTC)

I'm waiting to translate to my language--Eduaddad (talk) 02:09, 7 April 2019 (UTC)

how to deal with "413 Request Entity Too Large" ?
I am trying to use Special:Import at my community and got the following error message:
 * 413 Request Entity Too Large
 * nginx/1.15.8

I am trying to import an XML file containing the data of a Wikia project's articles. It is 461.9 MB.

Does anyone know what the maximum import size is? Any way I can change the setting to include this?

I read at https://craftcms.stackexchange.com/questions/2328/413-request-entity-too-large-error-with-uploading-a-file and https://www.cyberciti.biz/faq/linux-unix-bsd-nginx-413-request-entity-too-large/ that for nginx you need to change something called client_max_body_size in "nginx.conf" but I'm not sure how to find that. Is that something any project owner can access, or only miraheze staff?

https://www.mediawiki.org/wiki/Manual:Configuring_file_uploads#Set_maximum_size_for_file_uploads mentions:
 * may require root access to the server. (If you are on a shared host, contact your server administrator.)

Who is the server administrator of the wiki? Can they give me a temporary boost to 500 MB file upload just to import this XML and then set it back to normal? Or perhaps could they upload it for me, or teach me to upload from the .7z file so it's compressed?

Compressed by default in a .7z file this was merely 14.9 MB but I was getting a different error "Import failed: Expected tag, got. " when I tried to import the compressed .7z version of the XML. Tycio (talk) 03:32, 25 March 2019 (UTC)


 * hi, that’s because we have a max upload limit set server side. The limit is 250MB. You can request us to import the dump at https://phabricator.miraheze.org/ Paladox (talk) 01:49, 27 March 2019 (UTC)

Is Patreon allowed at Miraheze?
I have read the Content Policy, but it does not specify if a Patreon project is allowed. What happens is that I would like to know if it is legal to ask for financial help from a Patreon project to be able to make more and better articles for a specific wiki. The money obtained will not be directly for me, since a percentage will be donated to Miraheze. This does not mean that I am going to convert a wiki into a restricted access only for those who supported Patreon, in fact, the wiki will remain fully open to the public. I would like to know if a project in Patreon like this counts as a limited fundraiser-type sales as was mentioned in Content Policy, since the main reason for Patreon's project will be to improve the wiki and its content. --PaladinDeGigantas (talk) 20:01, 26 March 2019 (UTC)
 * Here <-- I have noticed that several staff members were in favor of a Patreon for Miraheze, although they have not yet carried out that project. --PaladinDeGigantas (talk) 20:05, 26 March 2019 (UTC)
 * I'd say, since you are not selling anything through our services, it's fine to use Patreon to support your work on your project. And yeah, a Patreon for Miraheze is something that really should be on the table. -- Void  Whispers 22:29, 28 March 2019 (UTC)
 * I agree that we should definitely consider having a Patreon. Reception123 (talk) ('C' ) 06:38, 3 April 2019 (UTC)

Access rights: Wiki with limited editors but members can comment
Is it possible on Miraheze to have a small group of users able to create/write pages / articles, and a much bigger group wich can only post comments/ discuss on the page ? A bit like Atlassian confluence. It would be a collaborative way of formalizing projects where everybody have different ideas, and one is responsible for puting it "on paper". — Preceding unsigned comment added by Dmaugis (talk • contribs) 18:40, 28 March 2019
 * Yeah, it's possible, but depends a bit on how you do comments. However, the basics of what you'd do is use Special:ManageWikiPermissions to remove the ability to edit from the * and User groups. Then give the ability to edit to a special user group that you give to your editors. Then, you'd somehow allow users to comment (Extension:Comments may allow users to comment without being able to edit). And that's that. Alternatively, you could use Special:ManageWikiNamespaces/0 to require a certain permission to be able to edit the main namespace, and then setup an editor group that has this permission. -- Void  Whispers 21:00, 28 March 2019 (UTC)

How To Add Videos To Your Miraheze Page?
I need to know how to add videos to Miraheze pages. — Preceding unsigned comment added by JuriCon (talk • contribs) 03:23, 30 March 2019‎
 * You might be able to upload videos, but I'd recommend using the YouTube extension, which allows you to embed YouTube videos into your pages. -- Void  Whispers 03:39, 30 March 2019 (UTC)
 * There are a few ways to do this. Option 1 would be to upload a .ogg through Special:Upload and hope for the best. Installing the TimedMediaHandler is defiantly preferred if not a must have for anyone doing this. However video support is hard so unless their is something preventing you from doing this I would recommend following Void's advice.
 * ~ El Komodos Drago (talk to me) 12:39, 3 April 2019 (UTC)

Between the Brackets podcast featuring John
Since we don't really have a specific place for these kind of things, I thought this would be the best place to post this. For anyone who is interested, User:John (co-founder, sysadmin and steward here) recently recorded an episode of Between the Brackets, a MediaWiki podcast, where he discusses Miraheze-related topics. Check it out here :) If you have any questions about the points raised or feedback, feel free to comment on this post. Reception123 (talk) ('C' ) 15:06, 3 April 2019 (UTC)

Creating a public and a private section into the same wiki
Hi all. I am new here but collaborated as a volunteer in it.wikipedia and other wikis before. I have sent a request for creating a new private wiki for an organization. Actually, I would prefer to have in the same wiki two sections: one public (readable/editable for anyone) and one private (readable/editable just for selected users), as it happens on Wikipedia, where some pages are viewable only by administrators. Is it possible to do something like this with Miraheze? Do I have to change something at this regard in my request? Or have I open two separate wikis? Thanks in advance. --Daniele Pugliesi (talk) 13:51, 4 April 2019 (UTC)
 * You could take advantage of the fact that, by rule (see FAQ), even a private wiki's Main Page is public. You can give different classes of user different rights, but I don't know a way to give different pages different treatment.  Other people may have better answers for you.   17:14 4-Apr-2019
 * It's not possible to have a flexible system where you can have public and non-public pages on the same wiki. If you need to have public and private pages, you will need to use two wikis. Also, as far as I am aware Wikipedia does not have pages that are limited in visibility to admins only (excepting for special pages). -- Void  Whispers 20:55, 4 April 2019 (UTC)

Translate access
Hello. I can translate miraheze to persian. Please give me translator access for translate Miraheze. Thanks. Alireza Ivaz (talk) 18:38, 4 April 2019 (UTC)
 * ✅ -- Void  Whispers 21:12, 4 April 2019 (UTC)

Meta:Request for permission is locked
The title says everything. We can't ask for permissions as permissions ask page is locked. --Anderlaxe (talk) 15:38, 6 April 2019 (UTC)
 * The page is not locked, but protected for autoconfirmed users, in order to prevent new users from requesting permissions which will most likely not been granted. Due to the fact that autoconfirmed users do have the right to vote, and since the original protection was due to large amounts of requests from users not on Meta, I have changed the protection to just user. However, this can be again changed in the future on a temporary basis if necessary. Reception123 (talk) ('C' ) 16:53, 6 April 2019 (UTC)