Community noticeboard

SVG thumbnails are rendering very blurry
I noticed that the past several SVG files I have uploaded to my wiki, are rendering thumbnails at extremely low resolution. Clicking through to the original svg file display the file properly within the browser window, but basically ALL the rendered PNG files, even when being rendered on a page, are blurry and basically unusable. Is there an issue with my wiki install? Is there a work-around? – Mitchell Gore (talk) 08:38, 2 July 2020 (UTC)
 * I'm having this exact issue over on companybumpers.miraheze.org. See my post about 2 sections up. Hb1290 (talk) 00:12, 3 July 2020 (UTC)
 * I think I found a working solution. I switched the SVG converter from “ImageMagick” to “Inkscape” in the wiki setting, and it seems to now render the SVGs in nice, clear, crip quality at all sizes. This is done by going into the Special:ManageWiki/settings page on your wiki, clicking on the "media" tab, then selecting the “Inkscape” in the “SVG converter” menu. – Mitchell Gore (talk) 14:13, 15 July 2020 (UTC)
 * It looks like you've found a working solution. See also this thread at the bottom of this noticeboard, in which I moved your duplicate post from the Meta administrators' noticeboard. AN is really only for local Meta problems or to request local rights on Meta only. If ever in doubt where to post as we have a few noticeboards, you can never go wrong with the community noticeboard. It's like a catch-all for community questions. Having said that, we have an active community and Miraheze staff on IRC and Discord and I have seen this question asked there...it was either paladox or RhinosF1 who answered the question, I think, but am not certain exactly as to the precise cause/solution. So you may wish to consider joining either (or both) of the IRC and/or Discord channels as often an answer is just minutes away (especially for quick answers to known problems/questions). Dmehus (talk) 16:09, 15 July 2020 (UTC)
 * Hi, just tried this solution to no avail, or does it take a while to fully take effect? EDIT: Nevermind, It's working nowHb1290 (talk) 05:06, 17 July 2020 (UTC)
 * Does the problem still persist? An resolved identical problem reported in Miraheze Phabricator Hispano76 (talk) 22:34, 22 July 2020 (UTC)
 * I haven't had issues with rendering since I switched my wiki over from using “ImageMagick” to “Inkscape” as the rendering engine. However, I did post another topic on the board here, about seeing if not rendering the SVG at all on the server side, and serving the SVG file up to be rendered natively by the browser has ever been done/implented on a Miraheze hosted wiki? (haven't gotten any response from anyone)
 * This would allow a lot more functionality (as well as avoiding any SVG rending issues) such as clickable elements within an SVG graphic, and other SVG interactive functionality, which gets totally lost when the SVG is rendered as a PNG. It has always struck me as very bizarre that MediWiki implements PNG rendering for SVGs in the first pace, which kind of defeats the whole point of vector graphics. – Mitchell Gore (talk) 01:49, 23 July 2020 (UTC)
 * Thumbnails now working like a charm. Hb1290 (talk) 12:47, 23 July 2020 (UTC)

Why do we have to request wikis?
Why do we have to request wikis on here? Can't we have a tool that users can use to create the wikis themselves, like FANDOM does? Tali64³ (talk) 19:41, 6 July 2020 (UTC)
 * The primary reason is to make sure that our Content Policy is being adhered to. The second reason is to prevent a massive flood of wiki creations that could crash the servers. Amanda Catherine (talk) 20:16, 6 July 2020 (UTC)


 * Why not hire more volunteers to close wikis that violate the Content Policy? Or upgrade your current servers? Or get more servers? Tali64³ (talk) 15:49, 7 July 2020 (UTC)
 * I would say that crashing the servers doesn't seem likely by simply creating wikis. As for the suggestion of closing wikis that violate the policies that would be difficult as we can't monitor everything. We are currently working on an artificial intelligence system that will allow more wikis to be created automatically, however. Reception123 (talk) ( C ) 17:00, 7 July 2020 (UTC)
 * I tried to understand this (and the dormancy policy) a while back but have yet to recieve a convincing explination for either of these. I really think that they are problems Miraheze has created for itself unecicarily. ~ El Komodos Drago (talk to me) 17:02, 15 July 2020 (UTC)
 * Speed bumps are occasionally good things. :) DMBFFF (talk) 22:11, 16 July 2020 (UTC)

Why does nobody listen to me
I want to known how people can’t respond to my questions?㊗️⚽️Μπέλα2006⚽️㊗️ (talk) 20:54, 11 July 2020 (UTC)


 * Some people are more inactive for some days. Also, some people take a lot of breaks. 14:16, 12 July 2020 (UTC)
 * Summer time. DMBFFF (talk) 22:15, 16 July 2020 (UTC)

Vote
Okay, ladies and gentlemen, I have a question for you: should we have a wiki on here like the Wiki Gazetteer on FANDOM? Put your vote in the headings below! And remember to sign your posts with ~. Tali64³ (talk) 20:33, 16 July 2020 (UTC)

Yes

 * 1) Why not? This would not be a bad idea for someone looking for a specific wiki. --TFFfan (talk) 21:57, 16 July 2020 (UTC)
 * 2) per  InspecterAbdel (talk) 21:16, 26 July 2020 (UTC)
 * 3) I strongly support this because we can find more specific wikis.  CircleyDoesExtracter  ( Circley Talk  |  Global   |  Email the Cloud ) 21:31, 26 July 2020 (UTC)

Discussion

 * 1) I'm currently been slowly working on a similar idea over the past month or two just documenting wikis: the Wikiverse. dibbydib 23:38, 22 July 2020 (UTC)

Native SVG file handling
Currently SVG files are rendered as a ONG when used as an image on a wiki page. However this defeats many of the reasons why creating graphics in the SVG format are better than pixel-based images. It also precludes any of the interactive aspects that can be put into an SVG fit (mouse-overs, clickable links when clicking on a part of the image, etc.).


 * Is there a way to bypass SVG rendering into PNGs and simply display/deliver the image as the SVG file itself and let the browser do the rendering?

I read a little bit about the Extension:NativeSvgHandler over on MediaWiki and this appears to be what that extension is and does.


 * Has this ever been installed into a wiki hosted here on Miraheze?
 * If so, what (if any) issues, etc. came up?

I am hoping that this is a viable solution, as I have some complex map SVG files I have created for my RPG gaming wiki, that have a bunch of interactive elements in the (mouse over legends of map locations, links to other map files, etc.) that would all really need to be displayed/delivered natively as SVGs instead of displayed as rasterized PNG images. – Mitchell Gore (talk) 21:01, 16 July 2020 (UTC)

Question about the commission election
Is it possible to nominate other users to be code of conduct commissioners? DeeM28 (talk) 07:41, 17 July 2020 (UTC)

Template help
I’m in need of importing some templates. I’m worried tho, is there any gnarly css and modules to import this?

Template on:

https://commons.miraheze.org/wiki/Main_Page

You know, that little image carousel thingy

Thanks

•• Fair0002 • Bureaucrat and Administrator of Crazybloxian Empire Wiki 07:57, 18 July 2020 (UTC)
 * delving into the source of that page, here is the code you'll need:


 * Obviously sub in your files where the .jpgs are and write captions as needed. The only template you need is this one. Neccessary CSS and Javascript can be found here and here. Put those in Mediawiki:common.css and common.js respectively, unless you want to use gadgets. Hb1290 (talk) 11:05, 19 July 2020 (UTC)

New Account Permissions/Notification on a Private Wiki
My wiki is a private wiki (as it needs to be) but I want to have a better understanding of how I can set up notifications of new user accounts when they are created, so that I can control and easily process, said new accounts. With a private wiki, accounts need to be “members” in order to actually view and edit pages. On a private wiki, accounts that are not made “members” can only view the main page.

As the “admin” and “bureaucrat” for my wiki, what's can I do to be notified when a new account is created, grant it the needed “member” status, etc.?

What are best practices in setting up and managing such issues? – Mitchell Gore (talk) 17:06, 18 July 2020 (UTC)
 * Special:Log/newusers is probably the best way to monitor new user creations, or attachments, for your private wiki; however, I would strongly encourage you not to locally block users who merely visit the public Main Page of your wiki as their accounts are attached just by clicking through to your wiki. I don't get the idea you were going to do this, but just wanted to point that out for other private wiki owners. Regarding Special:Log/newusers. there's no Atom feed for that log page directly, but what you could do is transclude it as, optionally parsed by a "date since" and then every month or so, just update the "date since" to declutter the transcluded page. This would allow you to monitor the Atom feed for that page. It should be quick and easy to set up. Dmehus (talk) 17:20, 18 July 2020 (UTC)
 * “however, I would strongly encourage you not to locally block users who merely visit the public Main Page of your wiki as their accounts are attached just by clicking through to your wiki.” –


 * Correct, I wasn't looking to do this. I was mainly asking what best practices are to set-up/maintain processing any new account so that I can grant them “member” status when they sign-up. Currently, someone could go the front page of my wiki, create an account, but since there is no way that I would be notified the account was created, it would just sit there in limbo. That new account would only be able to see the main page, but not see or do anything else. But since by default there is no notification that a new account was created, as an admin I would not know about it in order to rectify that situation by granting “member” status.


 * I'm not sure I fully understand what you are suggesting about transcluding the  page. Simply putting   on a page (like my user page) simply makes it a link to the log page. Which is handy as a quick link, but doesn't really solve the issue of notification of a new account being created.


 * Granted it isn't a case of a many people coming to my wiki and creating accounts at this point. But setting up a proper workflow/system to have me be notified, so I can process new account permissions in a timely manner would be helpful. – Mitchell Gore (talk) 17:56, 18 July 2020 (UTC)
 * It's more or less a quick and easy way to transclude the recent user creations onto an actual page of your wiki that has a built-in Atom feed you can monitor from any RSS/Atom feed reader. There's probably an easier way, and you could probably have a miraheze IRC sub-channel or Discord feed set up for your wiki, though this would include all wiki activity and would have to be customized in some way for certain logs, pages, etc. Are you on Discord or IRC? Probably the easiest way for either of those options would be to ask a system administrator for assistance in setting up a Discord bot for wiki or for setting up a miraheze sub-channel for your wiki on IRC. Dmehus (talk) 18:02, 18 July 2020 (UTC)
 * Except  doesn't actually transclude anything. It simply renders as a link to the log page. As for the RSS/Atom feed stuff, that's talking right over my head. – Mitchell Gore (talk) 18:34, 18 July 2020 (UTC)
 * Well, it actually is transcluding something; it's transcluding the contents of that special log page into a normal page on the wiki. The wiki software is configured to display only a certain number of log entries per page (usually defaults to 50) depending on the user's set preferences, so whatever the system default is set to is what should be transcluded on that normal page. As for RSS/Atom feed readers, essentially, it is type of structured data that allows the content of a webpage to be read various software packages and rendered in a myriad of formats, constantly updated in (near) real-time. The content of a page, blog post, wiki page, etc., is sectioned off into various elements, and those elements are how the various software packages read the content and notify the user of updates. Hope that helps. Dmehus (talk) 18:49, 18 July 2020 (UTC)

URL Shortener does not work
Wiki: custom domain:vedopedia.witches-empire.com / magic.miraheze.org / Error: There are problems with some of your input. _https://vedopedia.witches-empire.com/wiki/Заглавная_страница_ Links to the following domain may be shortened: vedopedia.witches-empire.com URLs to domain vedopedia.witches-empire.com are not allowed to be shortened How that could be solved ? Thanks. Затейник (talk) 16:06, 20 July 2020 (UTC)
 * Custom domains must be whitelisted in the settings for it to work. I've done so and it should be working now. Reception123 (talk) ( C ) 05:32, 24 July 2020 (UTC)

Wiki logo showing grey

 * 1) Go to https://vt.miraheze.org/wiki/Main_Page
 * 2) Look at the top left

It should show the logo that I configured.

It shows a grey rectangle in the place of the logo. Daily5 (talk) 09:49, 21 July 2020 (UTC)
 * I think that the size of the set image is too large. The ideal logo image is 150x150px. See also MediWiki's FAQ. --そらたこ (talk) 11:47, 21 July 2020 (UTC)
 * Thanks!

Polls are not working properly
I'm admin of Giantess Wiki.

A few months ago I had noticed that the polls had "restarted" (i.e. their vote counter had returned to 0). I had overlooked it thinking that they would manage on their own and that the votes would come back in time. However, I have noticed that polls suffer from strange behavior: The vote counter ranges from 1 to 4, and when a new vote is added, the results are altered at random. In short: polls are suffering from a glitch.

I don't know if this is happening with the other wikis as well, but with Giantess Wiki it is happening with the old and new polls.

Aurumargelium (talk) 21:48, 21 July 2020 (UTC)

Error while creating blog entries
There is a problem with creating new blog entries, when you want to create a new one, you get an error message saying.

'''Error: There is already a blog post with that title. Please choose a different title for your blog post.'''

Someone would think that there is a blog post with that same name (when in fact it didn't exist previously), but in reality, the blog post is created, but to access it you have to go to "Recent Changes" and search through the new editions as if it were a newly created post.


 * Sample from Giantess Wiki: https://giantess.miraheze.org/wiki/File:BlogPostE1.png
 * Sample from Cappy Games: https://giantess.miraheze.org/wiki/File:BlogPostE2.png

This error is annoying because it would make someone believe that they can't create blog entries.

Aurumargelium (talk) 23:09, 21 July 2020 (UTC)
 * Since this is an error with an extension, would you be so kind as to post this on Phabricator so that we can track it better? Thanks! Reception123 (talk) ( C ) 05:30, 24 July 2020 (UTC)
 * Done! Aurumargelium (talk) 06:20, 24 July 2020 (UTC)

Happy Birthday Miraheze!
Happy Birthday/Anniversary/whatever you want to call it! (I completely forgot about this until I saw the 5-year page in recent changes). Congratulations everyone. 🎊 🎉 – AmandaCath  ( talk ) 00:10, 22 July 2020 (UTC)

How you do it?
Sorry but how do you see the number of visitors on your Wiki by phone? Francesc 25 (talk) 09:05, 22 July 2020 (UTC)
 * Special:Analytics#mw-section-devices on your wiki. Reception123 (talk) ( C ) 05:29, 24 July 2020 (UTC)

Hosting Custom Font (bumped)
(bumped from archive)

I have created a custom font face that I want to use (as a web font) for my RPG gaming wiki. Is there a way to upload the .woff (and/or the other format font files) and then utilize it as part fo the custom css for my wiki?

As this is a font face I have created form scratch, licensing of it is not an issue as I am the rights holder for the font.

What are the steps I need to take to actually get my custom font uploaded and/or installed and then referencing it within css as a web font for use across the entire wiki? — Mitchell Gore (talk) 06:58, 5 July 2020 (UTC)

@Mitchell Gore: Hi, you would need to upload the file via Special:Upload and then use @import css in MediaWiki:Common.css. If you need any help with this please let me know. Reception123 (talk) (C) 17:03, 7 July 2020 (UTC)
 * I can't seem to upload any of my custom font files, because the file types are not allowed in the default set of allowed file types on a wiki here on Miraheze. How do I go about changing my wiki settings to allow the various web font file formats (.wof, .ttf, etc.) to be uploaded and used?
 * In addition, what specific steps do I need to do, once the .wof file(s) are uploaded, in order to use them as webfonts with my wiki's CSS?
 * I have used Google web fonts on another wiki in the past, where the @import url tag is used on the common.css definitions, then called in the vector.css page definitions as any other font css element deceleration. If someone could give a precise run-down of what needs to be done when uploading and hosting the .wof webfotn oil (and if any other custom file file formats need to be generated and uploaded) and what css coding needs to be done on the various css mediawiki pages, that would be a huge help. Thanks in advance. – Mitchell Gore (talk) 02:01, 23 July 2020 (UTC)

Request for Comment/Global Rollback group
A RfC on the possible creation of a Global rollback group has been posted here Sario528 (talk) 03:32, 23 July 2020 (UTC)

Customizing sidebar of, adding chat to, adding border to, and adding infoboxes to wikis
How do I customize the sidebar on a wiki, how do I add chat to a wiki, how do I add a border to an infobox, and how do I keep that infobox on the right and have text wrap around it, and how do I change a wiki name and subdomain?
 * 1) The sidebar can be customised by editing MediaWiki:Sidebar on your wiki. 2) Not sure what you mean by chat, but there are chat extensions available in Special:ManageWiki/extensions (you can use Ctrl+F "chat" to find them). 3) Infoboxes are quite tricky so I would not be able to help in that regard (cc ). 4) the wiki name can be changed in Special:ManageWiki, the subdomain can only be changed by sysadmins and must be requested on Phabricator. Reception123 (talk) ( C ) 05:28, 24 July 2020 (UTC)

CoCC election nominations
Hi everyone, in case perhaps it was missed or not noticed I would like to remind the community that nominations for the Code of Conduct Commission are currently taking place here and it would be nice to at least have five users that are nominated for the position. If you are interested in the CoCC and think you could help enforcing the CoCC feel free to nominate yourself, or alternatively if you know someone you think would be good for the position nominate them! Reception123 (talk) ( C ) 05:24, 24 July 2020 (UTC)
 * Nominations closed on July 21st 2020. So additional candidates strictly can’t nominate themselves anymore based on the precedence set out over the past 3 years. John (talk) 05:54, 24 July 2020 (UTC)
 * Oh, I did not notice that. In that case, should the vote for the candidates not be opened? And also, since the number of nominees is inferior to the number of commissioners, what would be the procedure to eventually fill up the 5th remaining spot (assuming that all the other four are elected that is). Reception123 (talk) ( C ) 06:01, 24 July 2020 (UTC)
 * The vote should be opened and no process exists for such a case. It was determined at the last election that the issue should be addressed in an RfC but it was never addressed. John (talk) 06:05, 24 July 2020 (UTC)
 * Okay, it should have probably been addressed in the other RfC regarding the CoCC. Since you began the election, will you open the vote or should I do it? Reception123 (talk) ( C ) 06:07, 24 July 2020 (UTC)
 * I was talking to about it earlier and he was saying any steward could probably officially start the vote, but thought maybe John might want to? We were thinking of maybe giving it until tomorrow or Saturday, and then maybe gently nudging John into opening it? But if you want to open it, sure, that seems fine, too. :) Dmehus (talk) 06:25, 24 July 2020 (UTC)

A community Developers wiki
I have a proposition for the Miraheze community. For a while now I have been debating whether or not to create a developers wiki for Miraheze. Unlike the template wiki, this wiki will include CSS and JS scripts that anyone can import using, it will allow anyone who wants it to use scripts built by the community in their own wikis and/or in their own personal global or local JavaScript or CSS files. After consulting with on Discord, I decided to get the communities feedback and/or support on this idea, therefore what does the Miraheze community think of this idea? 22:53, 24 July 2020 (UTC) ］ |
 * Yeah, though I don't think it's required to have a community discussion in this case, since it's going to be a community wiki for shared CSS and JavaScript files, among other things potentially, I thought it would be a good practice to have the discussion, especially if it proposes to use the name "Miraheze." Plus, I think it would be helpful for the community to (a) define the initial scope and purpose and (b) establish the founding bureaucrats for the wiki. From there, the local community can help to establish its local policies and further refine its purpose. In general terms, I support this as a community wiki as I think it is sufficiently different than the Template and Miraheze Bots + Tools wikis. I also think it could be useful at reducing the page load times of community-imported and -maintained user scripts, as opposed to always loading them from English Wikipedia and other wikis. Dmehus (talk) 23:17, 24 July 2020 (UTC)
 * yes, some of that is part of my initial thoughts for the reasoning of the wiki. As for using the name Miraheze in it, I think it should be called Miraheze Developers Wiki or something similar. As for bureaucrats of the wiki, any candidate recommendations? And I think a community discussion for this is a good idea. It gives the community a way to give input, and their own unique ideas in it as well. 23:39, 24 July 2020 (UTC) ］ |


 * As proposer I support this, but also because I know JS and CSS pretty well, and would love to have a wiki like this for the Miraheze community. 23:39, 24 July 2020 (UTC) ］ |
 * This is a great idea for a new wiki. I think that by doing this, lots of new coding things could be enabled, including possibly global modules and gadgets. Great suggestion. I also have no concerns for this proposal. --TFFfan (talk) 23:27, 24 July 2020 (UTC)
 * yes, I do believe that a wiki like this could be greatly beneficial in the long run, or at least I hope it can be. 23:39, 24 July 2020 (UTC) ］ |

Do I have to make an RfC for this?
I wanted to suggest some extensions (comments, flow, blogs, voteny and pollny, socialprofile), so I thought I can make an RfC, but I thought you can't make an RfC for a topic like that. InspecterAbdel (talk) 20:57, 26 July 2020 (UTC)
 * For extensions, you don't need to do an RfC for that. There's Extensions on Meta and, from there, there should be a link to the Phabricator feature request form for requesting new extensions or configuration changes to existing extensions. Hope this helps. Dmehus (talk) 22:06, 26 July 2020 (UTC)
 * Just noting that all the extensions you mention are already available and can be enabled via Special:ManageWiki/extensions. Reception123 (talk) ( C ) 04:47, 27 July 2020 (UTC)
 * I think meant to enable those extensions here on meta. I may be wrong though.  20:18, 27 July 2020 (UTC) ］ |
 * I meant add these extensions here on meta InspecterAbdel (talk) 20:28, 27 July 2020 (UTC)
 * Thanks, Universal Omega. Looks like you were right. In that case, consider this strong support towards adding Flow, though it should be only enabled after a brief community discussion on the talk page or noticeboard in Talk: namespace and upon request/on-demand in one's own user talk: namespace. Consider this support to either "voteny" or "pollny," if they can be used without SocialProfile, which I'd be either weakly opposed to or weakly supportive of (would only support if they can be enabled on-demand in own's userspace and if it is not made the default userspace page). I am not familiar with the other two, so will abstain there. Dmehus (talk) 15:03, 28 July 2020 (UTC)
 * I would say due to the extensions changing quite a bit a discussion is definitely necessary and possibly a local RfC could be chosen if you'd wish. I don't see what the purpose of the polling extensions on Meta would be, however. If you would want them for voting for different users in Requests for Permissions, that is not the way we do it around here as people should comment on why they are voting, not simply cast a vote. Reception123 (talk) ( C ) 16:40, 28 July 2020 (UTC)
 * Yeah, that's fair; if we were just wanting to enable Flow on Meta, then probably a short 5-7 community discussion on community noticeboard is all that would likely needed, based on my Discord conversations with you. With regard to the others, yes, I agree, we'd probably want to have either (a) a 21-30 day community discussion or (b) a full 30 day local RfC, eh? As to the polling extension, I've personally not used it, but could see it being particularly useful for these very community discussions. It is context-specific with community discussions as to whether one needs to !vote with a rationale or simply !vote. If they are voting in favour of a clearly defined proposal that is well articulated by the proposer, then it's strictly just a nosecount. Dmehus (talk) 16:49, 28 July 2020 (UTC)

A new wiki for the website's community
The Miraheze Community Wiki is a wiki for the community so people can get to know each other and welcome each other. I know Meta does that, but I think we need a wiki for that stuff.

Support

 * 1) I think we need a wiki for this kind of thing InspecterAbdel (talk) 22:44, 27 July 2020 (UTC)
 * 2) but not per any of the above or below, but because community noticeboard has become a catch-all for technical support questions, community discussions, and really anything. The organization is weak, and we could use a community wiki. I have no objections to it, but the main reason for my oppose  weak support here is because the purpose is somewhat vague and unclear. I appreciate  bringing this for a community discussion, though, and, since this wiki was simultaneously submitted for approval and created already, I think we should probably shift this wiki towards defining a clear purpose and terms of reference for its existence and the parameters by which the local   can be removed (via Community noticeboard) here on Meta. Dmehus (talk) 14:55, 28 July 2020 (UTC)  Amended. Moved from weak oppose to weak support Dmehus (talk) 15:31, 28 July 2020 (UTC)

Abstain

 * 1) I really like to have a community wiki for new users to gather, although we have a Community noticeboard.  CircleyDoesExtracter  ( Circley Talk  |  Global   |  Email the Cloud ) 17:09, 28 July 2020 (UTC)

Oppose

 * 1) . No, we don't need such a wiki.  This page ("community noticeboard") is exactly for this kind of thing.  I don't want to have to check both this page and a dedicated wiki to find out what is happening on the wiki farm, nor learn how such a wiki is organized.   04:25, 28 July 2020 (UTC)
 * 2) Per Spike. There is already not enough engagement and usage on Meta, so another wiki is really not what we need. We should focus on Meta. Reception123 (talk) ( C ) 06:08, 28 July 2020 (UTC)
 * 3) . We DO NOT need a community wiki is needed at this time. We already have this page, the community noticeboard, and Requests for Permissions, requests for global rights and requests for stewardship. It seems that it would serve the same service as as most of this meta wiki, and I just see no possible usage for this. I also agree with the comments that has made about having to go back and forth between meta and a community wiki. Sorry, it is just not going to work. --TFFfan (talk) 15:10, 28 July 2020 (UTC)
 * I'm hoping you'll consider amending your !vote, per my comments above, as I really don't think 's goal was for this wiki to replace Meta. The problem with this request is that (a) the wiki shouldn't have been created without a community discussion (not, technically, a requirement, as far as I'm aware, but good practice) and (b) it should've had a clearer purpose, scope, and defined parameters, as we are doing with Dev Wiki and have done with Template Wiki and Miraheze Commons in the past. No community proposals or discussions, or even drafts of such proposals, would've occurred on this wiki. Rather, as I saw it (though vague and unclear), this wiki was meant to be a user collaboration and social connection wiki that would've actually sought to deepen community participation. Participation in this community wiki would've been completely voluntary and not participating would not have meant the user would "miss out" on important community discussions, as I don't think that was ever the intent behind 's good-faith proposal. Dmehus (talk) 15:27, 28 July 2020 (UTC)

Comments
InspecterAbdel (talk) 22:44, 27 July 2020 (UTC)

The content model of Module documents is Scribunto
I found that, in rs.miraheze.org, the content model of Module documents ( or  ) is currently Scribunto instead of wikitext, which makes it abnormal to create module documents unless I use Special:ChangeContentModel to change it. --SolidBlock (talk) 08:08, 28 July 2020 (UTC)
 * Is this occurring on just that wiki, or on all wikis? If the former, you should be able to change this in . If the latter, this is likely a global configuration issue, and should be changed globally with a Phabricator request. If no one else notices this thread by tomorrow morning, I will investigate further, and submit a Phabricator ticket if required. Dmehus (talk) 14:47, 28 July 2020 (UTC)
 * I don't know if it's former of latter. But I failed to change that via ManageWiki, because I can only change the content model of whole namespace. --SolidBlock (talk) 15:08, 28 July 2020 (UTC)
 * Ah, that's helpful, thanks. We may need to file an upstream Phabricator ticket, then, with Wikimedia's Phabricator. I'll follow up here tomorrow. Dmehus (talk) 15:38, 28 July 2020 (UTC)
 * The default content model for Module is Scribunto InspecterAbdel (talk) 22:04, 28 July 2020 (UTC)
 * I found that it's occurring on almost all wikis, including meta, 10b10t, 343151, 8848 wiki and so on——I just randomly tested some and found that they are all Scribuntos. --SolidBlock (talk) 03:57, 29 July 2020 (UTC)