Community portal

Add topic
From Miraheze Meta, Miraheze's central coordination wiki
(Redirected from Community noticeboard)
Community portal
This noticeboard is community discussions, generally global in nature, or which relate to specific wikis or users. For requests that require Steward or Global Sysop intervention, please use Steward requests. If in doubt, please try here first, and you will be directed there if the matter requires a Steward. For discussion pertaining to Meta only, please visit the Meta Community portal.

On the Community portal, you can:

  • Start a community discussion, typically global in nature or which relates to specific wiki(s).
  • Solicit volunteers' assistance to help maintain or write content for your wiki
  • Ask questions with both the global community and system administrators about either Miraheze or some technical aspect of MediaWiki on your wiki
  • Request changes to your wiki's local interwiki table, including change(s) to locally override one or more of the global interwiki table (located on Meta) prefix configurations

If you would like to request:

To add your request, type in a concise title in the box below, then click "Add topic".

Archives of Community portal [e]   



  1. For some reason, the bold text on the left of the infoboxes that state what type of information is being shown is being centred. If you don't know what I mean, see the Abkhazia and Abkhazian War of Independence pages. In a previous thread, Tali64³ told me to add text-align: left; to the CSS page, but nothing changed.
  2. These templates do not work for some reason.
  3. The native name template that is used on this page isn't working for some reason.

Money12123 (contribs | CentralAuth) 04:23, 24 February 2024 (UTC)Reply[reply]

@Tali64³: Money12123 (contribs | CentralAuth) 01:17, 2 March 2024 (UTC)Reply[reply]
@Tali64³: Hello? Money12123 (contribs | CentralAuth) 03:52, 9 March 2024 (UTC)Reply[reply]
#1 appears to have been resolved. The other two I honestly have no idea how to fix; you may be able to get an answer by joining the Miraheze Discord server. Tali64³ (talk | contributions) 04:00, 9 March 2024 (UTC)Reply[reply]
@Tali64³: #1 is not resolved, take a look at result on the Abkhazian War of Independence page. Money12123 (contribs | CentralAuth) 04:36, 9 March 2024 (UTC)Reply[reply]
@Tali64³: Hello? Money12123 (contribs | CentralAuth) 20:52, 14 March 2024 (UTC)Reply[reply]

How do I add templates like the ones in wikipedia[edit | edit source]

Wikipedia has some templates like this one https://en.wikipedia.org/wiki/Mars, It shows Mars adjectives, name, image, symbol and technical information about the planet, is there any way to do something like this on Miraheze? If so, could someone teach me, please? Zibelina (talk) 03:23, 28 February 2024 (UTC)Reply[reply]

@Zibelina, I think you're looking for Infoboxes. That page has information on how to get started making them. Labster (talk) 05:04, 28 February 2024 (UTC)Reply[reply]
@Zibelina As a rule of thumb, never import from Wikipedia if you have a choice, it'll only become a tangled mess of dependencies and suffering. More often then not, Dev wiki or some other source will have a simpler version to use. Or, like Labs said, with infoboxes, the guide does a good job. ╚pixDeVl╝ (T|C) 11:14, 28 February 2024 (UTC)Reply[reply]
In Wikipedia, you need Special:Export page.
On your wiki, you need using Special:Import upload the .zip file.
Template:Infobox can found on dev wiki. Gongxiang01 (talk) 11:59, 11 March 2024 (UTC)Reply[reply]

Choosing templates to be preloaded for new wikis[edit | edit source]

Following the "closed" RfC and the convo at Miraheze's Discord, as suggested by Agent, I want to know your idea on what kinds of templates did you wants to have preloaded by default. Mine includes:

  • The bare bone PortableInfobox template, with PI enabled by default
  • Citations templates (from Dev Wiki)
  • Article status (from DW as well); and
  • Licensing boxes for image licensing (from DW too).

Tell me what you think about this. Questions and comments are welcomed! Pisces (talk) 16:27, 1 March 2024 (UTC)Reply[reply]

* Reflist
* Message box templates but with explanation of the cryptic names
* PortableNavbox
* Disambiguation
* Stub
* Delete because
--Rob Kam (talk) 18:00, 1 March 2024 (UTC)Reply[reply]
* Sfrac
* Color
* Background color
--Rob Kam (talk) 13:36, 11 March 2024 (UTC)Reply[reply]
Hm, the dev:Template:Hatnote and some default wrappers(like main, for, see also, etc) could be good. I'll talk more about this in the Phorge task but I personally think it would be awesome if we could select groups of templates to fine tune and not have unneeded bulk. ╚pixDeVl╝ (T|C) 01:39, 2 March 2024 (UTC)Reply[reply]
Agree with @Rob Kam Gongxiang01 (talk) 12:38, 11 March 2024 (UTC)Reply[reply]

Special:RequestSSL gives ArgumentCountError error[edit | edit source]

Greetings. I just submitted a custom domain name application on Special:RequestSSL. And it gives me an `ArgumentCountError` error. Could anyone please troubleshoot this issue?

[0cd0d84eeb92554fbc961c31] 2024-03-03 11:55:01: 类型“ArgumentCountError”的致命异常
 机智的小鱼君 (talk) 12:00, 3 March 2024 (UTC)Reply[reply]
Hi. This issue has been fixed in RequestSSL's latest updates, however Miraheze is not currently running the latest version. I've put a request for SRE to update the extension in Miraheze, they'll get to it soon. Thank you for your patience. OrangeStar (talk) 12:04, 3 March 2024 (UTC)Reply[reply]
❤️❤️❤️ 机智的小鱼君 (talk) 12:09, 3 March 2024 (UTC)Reply[reply]
@机智的小鱼君: Since it seems it is going to be a while before that is upgraded, I recommend requesting your custom domain at Phorge using this form. OrangeStar (talk) 09:09, 6 March 2024 (UTC)Reply[reply]
Thank you for your reply. Just filed a ticket: https://issue-tracker.miraheze.org/T11937 机智的小鱼君 (talk) 12:00, 7 March 2024 (UTC)Reply[reply]

Problem logging into wiki[edit | edit source]

I'm trying to log in Universopedia, but am not able to. When I try to log in, an error occurs. The error page has the following format (without the cursive, and the bold text being the title):

Database error
A database query error has occurred. This may indicate a bug in the software.
[string of random charachers] YYYY-MM-DD HH:MM:SS: Fatal exception of type "Wikimedia\Rdbms\DBQueryError"

I've tried cleaning my cookies and cache, but that hasn't worked.

What's funny is that this issue is exclusive to that wiki. I tried logging in Random-ness Wiki Incubator+, and even a closed wiki, and was able to. El meerahezedista (talk) 00:11, 4 March 2024 (UTC)Reply[reply]

mh:universopedia seems to be working; I did not get an error going to Main Page or other pages; --- Imamy (talk) 04:57, 4 March 2024 (UTC)Reply[reply]
I reviewed your bug issue again and think perhaps I may have misunderstood. I did not try logging in because I am already logged in, so had no trouble accessing mh:universopedia; However, if the error keeps happening, perhaps report to phabricator mh:phabricator? --- Imamy (talk) 05:07, 4 March 2024 (UTC)Reply[reply]
Imamy (un)Funnily enough, trying to log in Phabricator, it tells me my user info is "incorrect". I logged out of Meta and logged in again to confirm my info was correct, and, in fact, it is. Tried logging in again, and it continues to tell me user info is "incorrect"... El meerahezedista (talk) 02:34, 9 March 2024 (UTC)Reply[reply]
Go back to that page.
Don't enter username
Don't enter password.
Look around for a white button that says something like "Log in or Register" or blue button that says "Login"
--- Imamy (talk) 20:54, 9 March 2024 (UTC)Reply[reply]
Click on the White Button that says "Log In or Register" and you should be able to get into Phabricator
--- Imamy (talk) 20:56, 9 March 2024 (UTC)Reply[reply]
If you still don't see the option for "Log In or Register", look at the bottom of the page. The white button is below the blue "Login" button.
--- Imamy (talk) 21:04, 9 March 2024 (UTC)Reply[reply]

Miraheze app?[edit | edit source]

Are you interested in Miraheze app for Apple and Android devices? Wikipedia and Fandom already have these. Miraheze app will have similiar features to Fandom app, plus there will have a Contribute section.

If so, I'll create a RfC about this. Silicona (talk) 17:52, 5 March 2024 (UTC)Reply[reply]

This doesn't need so much an RfC as much as someone willing to make the app, honestly. OrangeStar (talk) 18:26, 5 March 2024 (UTC)Reply[reply]
This unfortunately proves the points made against you at Meta:Administrators' noticeboard. Agent Isai Talk to me! 18:37, 5 March 2024 (UTC)Reply[reply]
Well this is progress, seeking input before straight up creating an rfc. That, or going ahead anyway with slim or generally negative input would indeed validate the concern.
Anyway per OS this would strictly need a volunteer's time and passion, an rfc would be moot and out of scope as a technical matter. The idea has come up before, it needs a creator & maintainer. Beyond that I'm not sure a straight mira app is ideal as we have a more diverse nature than wikipedia or fandom. --raidarr (💬) 19:34, 5 March 2024 (UTC)Reply[reply]
I created a prototype of Miraheze app using PowerPoint:
I expect the technical requirements to be:
  • Android 9.0 or later (can be expanded to 8.0, 7.0 or 6.0 through discussion)
  • iOS 16 or later (can be expanded to iOS 15 through discussion)
  • Apple M1/M2/M3 Macs support likely (like Fandom app)
  • Apple Vision Pro support likely (like Fandom app)
  • Approx size of thirty (30) to ninety (90) megabytes (MB)
  • Offline reading support
What do you think of this prototype and these technical requirements? Silicona (talk) 09:42, 6 March 2024 (UTC)Reply[reply]
@Silicona: I've thought about this before and I think this is a good idea. The design in that prototype is also very good and I don't have anything to nitpick with it. I am concerned about how the app will handle extensions like SocialProfile and others that make a lot of changes to the frontend because it will likely require some manual implementation (I don't think anybody is going to want just a web browser that only loads *.miraheze.org so we'd need to be actually implementing some things ourselves) I'm not too up-to-date on the latest devices but isn't iOS 16 rather modern? A lot of people have really old and crappy devices, so I think it should work on devices earlier than iOS 16.
As for how the app should be written, I propose writing it in the only civilized way: making a local HTML5 site that's designed for mobile devices and then the mobile app loads it (React Native, Ionic, etc.)
I'd like to suggest that the Miraheze app let users add other wikifarms like Telepedia, Fandom, Wiki.gg, and ShoutWiki in addition to the defaults, because these are all fairly popular wikifarms, and the Netpedia network is scattered across Telepedia, Miraheze, and ShoutWiki. Collei (talk) (contribs) 09:53, 6 March 2024 (UTC)Reply[reply]
Okay, you crafted visual prototype, but again - who is going to actually develop that? Second, what is "trending wikis" in Miraheze environment? Some ideas about pushing "best wikis" to some sort of spotlight were thrown around but nothing coherent was made yet. Also Collei makes a good point about how extension will behave, but the most sensitive part here is - how wikis will keep their identity in mobile map environment? Are they going to be forced to unstyled Minerva? Or you want all wikis to go and set up mobile frontend? And templates, are we going to nerf them to unstyled tables and block like Fandom does in their mobile mode? Legroom (talk) 10:27, 6 March 2024 (UTC)Reply[reply]
I'd be willing to develop this if it was actually something people are interested in, but the other problems are going to require more thought. Also, yeah, I don't think the idea of "trending wikis" would really work so it should be removed. 1) It's useless because Miraheze wikis are usually at the same level of activity and nobody really needs it for anything, and 2) I don't know how it could be implemented from a technical perspective because there's nothing in the API that I'm aware of that would let us just fetch a bunch of wikis and see which ones are the most popular (I guess you could go through literally every wiki in Special:WikiDiscover, but that'd send thousands of network requests)
I suppose for how wikis will keep their identity in mobile map environment? Are they going to be forced to unstyled Minerva? Or you want all wikis to go and set up mobile frontend, the UI is very important to think about, I'm not sure what to do for this. Should it just display the site as-is, but maybe with some things like meta viewport being automatically added in to enforce mobile compatibility? Or are we going with wikis being styled by the mobile app in some way? If so, this should probably be dnoe on a skin-by-skin basis - for skins that are inherently broken on mobile, maybe it could be forced to Minerva, while others could be looked at more selectively (Cosmos works fine on mobile for example). There could also be an inbetween on this, like stripping out some styles while keeping others, or forcing proper color contrast, but I'm still not sure how well that would work for allowing wiki freedom and for being practical to implement. If a wiki has MobileFrontend set up, I think the app should just show MobileFrontend how it normally would.
And templates, are we going to nerf them to unstyled tables and block like Fandom does in their mobile mode? Probably not, but we'd have to look at how exactly templates could work because most are designed for desktop users, browsing wikis on the normal mobile site has always been a pain for me already, which is a problem that needs solving but is a different issue. This ties into the second paragraph of whether the wikis should preserve their normal identity, be restyled by the mobile app, or some kind of in-between.
I invite Sillicona to provide their thoughts on this. Collei (talk) (contribs) 11:15, 6 March 2024 (UTC)Reply[reply]
I meant “Follow wikis” not “Trending wikis” Silicona (talk) 11:20, 6 March 2024 (UTC)Reply[reply]
That sounds like a good idea, but the other problems still need some thought. Collei (talk) (contribs) 11:23, 6 March 2024 (UTC)Reply[reply]
“App optimisation” would be a great idea as a ManageWiki setting, as it can tweak the design and styling of wikis to be optimisable for apps on mobile and tablets
The default styling for all wikis, which can be changed, will be:
  • Width of tables forcefully set to 100% for mobile (less than 600 dpi width)
  • Only color, background, width (each row or columns, entire table for larger devices), height and text effects/styles can be set in tables.
  • Default font for headings will be Ubuntu and for body will be Google Sans Text.
  • CSS font family cannot be overridden except serif and monospace.
  • The background will be very light gray (#fbfaf9) for Apple devices and a very light tint of Material You color for Android.
  • CSS can forcefully be set on elements using force-css-app in class selector in HTML.
Emulation devices would be great. I would like to preview the changes on the emulated devices like Samsung S24 Ultra and iPhone 15 Pro right on a browser. Silicona (talk) 12:16, 6 March 2024 (UTC)Reply[reply]
This does not sound like a good idea, wikis are supposed to have their own customization, perhaps users of the app should be able to choose if they want to override customization but forbidding customization goes against Miraheze principles. Collei (talk) (contribs) 12:20, 6 March 2024 (UTC)Reply[reply]
Monodesign and the decidedly fandom-esque nature of most suggestions that would come up are a large part of why this project is problematic.
The most useful form I could imagine for this would be as a power user tool. Offline saves, 'follow' wikis, some sort of spruced up wikidiscover, a mechanism to promote engaging with meta if you have any advanced interest in the platform (say, sysop somewhere), and being an incredibly lightweight app otherwise that cannot possibly be considered bloated (though react isn't a great start for that) and is above technical reproach (you'd trust it like you'd trust a custom browser). But the sort of person this concept would appeal to is probably very niche and would not be worth the time it takes to develop these features, most of which would have to be developed independently for an app to properly utilize them and so way beyond a reasonable demand for Miraheze SRE to pull off. And anything less or which promotes a monodesign or miraheze branding above all, like a certain massive competitor, pretty much completely defeats what Miraheze is on about. In which case better to imagine ways for wikis to enhance their own designs, such as their own app if they feel they're large enough for that. Then at least you're not trying to shove what you (and I mean you as in Miraheze) want down a wiki's throat. --raidarr (💬) 12:28, 6 March 2024 (UTC)Reply[reply]
I don't agree with the proposal to remove wiki themes in the mobile app, adding more settings to ManageWiki for this, or asking SRE to change features (especially when it'd require straying from a normal MediaWiki setup), but that doesn't mean an app is a terrible idea altogether. It's been brought up on Discord and IRC before. This wouldn't have to be shoved down users' throats, it could just be an optional app you could download, like how someone might use their personal CSS and JS to make wikis look different or work better on their phone. Not all skins are mobile compatible but some of them can be made mobile compatible through slight tweaks that the app could enforce, like adding the meta viewport tag for example.
Also, despite being bloated from a technical perspective, React doesn't necessarily create bloat for the end user. It'd add a few hundred kb to the app size, or a few mb at most if it's a really large app, which it shouldn't be. The performance shouldn't be a huge decrease especially when this is going to be confined in a single app with a "browser" that is the iOS or Android webview combined with probably some native code when appropriate (the Android webview is very minimal iirc and doesn't support a lot of up-to-date browser features, so you'd probably need polyfills, but this also means it could be faster because there wouldn't be as much code it's running - could be wrong about this though because I haven't touched Android app development for 2 or 3 years). Ionic, for example, has pretty good performance and file size. React Native would be good too though I personally think Ionic is nicer because you can use some non-React code when you want to, it lets you interact with the DOM, it supports cross-platform builds with one codebase by default, etc.
Ionic also seems to have pretty good performance [1] [2] and I could work on making whatever code is needed to improve performance and file size, so bloat shouldn't be a concern. Collei (talk) (contribs) 21:05, 7 March 2024 (UTC)Reply[reply]
@Collei Here's another prototype of Wiki section of Miraheze app.
What do you think of this? Silicona (talk) 11:41, 7 March 2024 (UTC)Reply[reply]
And this
Silicona (talk) 14:00, 7 March 2024 (UTC)Reply[reply]
@Silicona: These all look good, though I don't think the trending wikis idea would be very good. Could you propose something for onboarding and first-time user experience, like asking the user if they want to login, etc.? I also think it would be nice if they could edit non-Miraheze wikis given that some wiki networks, like reception wikis, are fragmented across several wiki hosts, and it could be cool in general, but if nobody agrees with me on that idea, it could be left out. I still think we need to put more thought into the behavior of extensions and wiki appearances, though. I've given my thoughts elsewhere in this thread. Collei (talk) (contribs) 21:00, 7 March 2024 (UTC)Reply[reply]

spamblacklist and titleblacklist[edit | edit source]

2 questions:

  1. Why is it disabled the 'spamblacklistlog' right by default for any user group to view the spam blacklist logs on any Miraheze wiki unless a bureaucrat enables it through ManageWiki (search "blacklist" in the mini search engine), while in Wikimedia any user who is registered have the right and can view it? and
  2. Why is it also disabled the 'titleblacklistlog' for all wikis without the possibility of enabling it for any other user group (because apparently that option just doesn't appear on ManageWiki) to view the title blacklist logs while on Wikimedia only administrators can view it?, Is it possible to add that option to all Miraheze wikis on ManageWiki?

These 2 things disabled, but especially the second, means that we cannot have more information by not being able to see the records of users who try to ruin the miraheze wikis, I suggest this so they can fix it so that this wiki and the others Miraheze wikis are a little more "open" No se (talk | contribs) 06:00, 6 March 2024 (UTC)Reply[reply]

Unresolved steward requests counter[edit | edit source]

Hi, I made unresolved steward requests counter in User:Waki285/USRC. I implemented this rather aggressively, but is there a better way? I would like to place this on the Steward requests page in the future.    Waki285(talk|contrib|log|CA|Target) 14:03, 6 March 2024 (UTC)Reply[reply]

Thanks for this, I've brought it to the attention of other stewards as it solves a longstanding problem I have with the board structure... --NotAracham (talkcontribsglobal) 18:04, 7 March 2024 (UTC)Reply[reply]
It's a useful starting point. Building on it perhaps it should include RFRWs (another steward venue) and perhaps include reminders for email and a direct link to the rename queue. Thus the SR area or even just a specific spot in general can be the main pit stop for a steward looking to catch up. --raidarr (💬) 18:09, 7 March 2024 (UTC)Reply[reply]
I'm wondering, only stewards (or local bureaucrats) can reopen a wiki, right? If so, why is it separated from Steward requests?    Waki285(talk|contrib|log|CA|Target) 02:58, 8 March 2024 (UTC)Reply[reply]
I added RfRW and global rename queue (Navbox sandbox). but I don't know about Miraheze email systems.    Waki285(talk|contrib|log|CA|Target) 05:25, 8 March 2024 (UTC)Reply[reply]
Email is more complicated than we'd probably want to scope for a proof of concept, thanks for taking the additional time to think this through. --NotAracham (talkcontribsglobal) 06:24, 8 March 2024 (UTC)Reply[reply]
I only suggested email as a 'hey remember this while you're here!', too tricky to actually work in a counter for it I think. It should not delay the merits of the rest of the idea.
RfRW was split off because it's a high-volume venue that would have been a serious blowup to the SN as it was. However perhaps it should be rethought now because the SR pages are split anyway. The (un)deletion section is still extremely high volume but this is unusual and right now there is a huge overlap with people going to RfRW when they're going to be pointed at the SR anyway. --raidarr (💬) 10:25, 8 March 2024 (UTC)Reply[reply]
Template created.    Waki285(talk|contrib|log|CA|Target) 08:33, 11 March 2024 (UTC)Reply[reply]

Unable to log in[edit | edit source]

Hi. I can't log in to https://telepedia.miraheze.org and get a message about session hijacking (or how does it have to be called). I log in with the same credentials normally on other wikis. Can you please solve this problem? I've already had a discussion about this on https://issue-tracker.miraheze.org/T11928, but they told me to ask it here, so here I am. Пасик, Ферстикс (talk) 08:10, 8 March 2024 (UTC)Reply[reply]

The next step I would say is to try a different browser such as firefox or another chrome variant (to rule out local interference). Basically something you have never logged in with, perhaps you've visited on your phone and there is a session hiccup. If that succeeds then a more complete session purge followed by trial and error with extensions or your more restrictive settings may be needed. Worst case I'd stick with the task and see if you can be flushed out manually. I did notice my login session was reset upon visiting there. It seems to have persisted now though and I haven't spotted anything unusual (but I don't wrangle russian so take me for a grain of salt). --raidarr (💬) 10:36, 8 March 2024 (UTC)Reply[reply]
I managed to log in on a different browser. Talking about this one, I've disabled all of the extensions and it still didn't work. Is there anything else I can do to make this browser usable again? Пасик, Ферстикс (talk) 15:56, 8 March 2024 (UTC)Reply[reply]
List of things to try:
  1.   What type of browser is the one that doesn't work?
  2.   What device is the browser on?
  3.   Have you cleared cache and cookies?
  4.   Have you checked for and updated the browser?
  5.   Have you tried logging in at meta instead of at telepedia?
  6.   After successfully logging in, log out on all instances. Then wait until next day?
  7.   Are you using a shortcut? Perhaps the link is corrupted.
  8.   Have you checked the website name? Perhaps misspelled?
--- Imamy (talk) 21:36, 9 March 2024 (UTC)Reply[reply]

Can you see this RfC and give feedback on it? Silicona (talk) 09:04, 8 March 2024 (UTC)Reply[reply]

Here is my feedback.
These proposals are cranked out with little effort and discussion to offer another perspective or criticism that is anything but enabling is ignored, dismissed or trivially addressed and not resolved. I'd like to see a difference this time but then again this is not the first time (won't bother looking for older but they're there). This draft exists because you wanted a scope that covers essentially anything and the proposal is discolored by clear personal interest. It's self evident in how the summary of this page acknowledges that you were told one thing quite clearly and yet at no point explain why a) it's not too broad or why b) it should be broader. You just made arbitrary numbers, stuck them in a table and worked in a personal concern for another request that was clearly derivative of a wiki we already had which itself has struggled to attract an audience despite its production value. Is there something worth discussing about broadness yes, the Content Policy is not particularly clear on that both original and now-approved revised. The need to spell it out better is there. But this business is malformed; it should be approached by someone who can do the topic justice. The RfC process is being battered with engineered controversies and weaponized proposals. This is why I endorse sanction.
The dormancy policy section further illustrates that you frankly do not know why the processes are what they are. You do not grasp the bigger picture and the consequences are disruptive to curb time and again. An across-the-board 25% cut with effects like reducing 15 days to 11 and throwing everything off is clearly not a reasonable way to proceed.
Again I hope to be proven otherwise on this but this trend is not hopeful.
--raidarr (💬) 10:20, 8 March 2024 (UTC)Reply[reply]

Didn't receive email notification[edit | edit source]

Hello everyone,


I created an account last night, but I didn't receive an email notification to verify it. I did check my spam folder.


When I click on "create a new wiki," I get this message:


>Your email is not confirmed. To request wikis, please confirm an email first.


I'm able to log in, so my account seems okay. I don't see an option to resend the notification. Er, help? Kelly Aster (talk) 13:28, 8 March 2024 (UTC)Reply[reply]

Ok, I did find the resend option. I tried to resend the confirmation email and got this error:
Miraheze Meta could not send your confirmation mail. Please check your email address for invalid characters.
Mailer returned: Failed to connect to ssl://smtp-relay.gmail.com:465 [SMTP: HELO was not accepted (code: -1, response: )] Kelly Aster (talk) 13:33, 8 March 2024 (UTC)Reply[reply]
where is the resend thing at this happening to me aswell Soija (talk) 15:55, 8 March 2024 (UTC)Reply[reply]
Hi, sorry for the delay, I was at work. This is the resend page: Special:ConfirmEmail
I did get a confirmation email, finally, but only after I removed my email address from my account and re-added it. I hope it's smoother sailing from here, because to be honest I'm kinda disappointed by the jankiness so far. I still have to request a wiki, so here goes.
This is the page where I removed my email address, btw: Special:ChangeEmail. If you remove your email like I did, make sure you have your password saved somewhere and are able to log in. Good luck! Kelly Aster (talk) 00:59, 9 March 2024 (UTC)Reply[reply]
If there are further reports or this is a consistent behavior I'd advise a task on phorge to put it on SRE's radar, especially including that error. If not this could be a one-off, which is still a shame and you shouldn't have had to deal with it. At the end of the day email systems are not pleasant and sometimes buckle for little reason at all... --raidarr (💬) 09:52, 9 March 2024 (UTC)Reply[reply]
Hi raidarr, thank you for the input, hopefully no one else experiences this and it was indeed an isolated event.
I must apologize for my cunty remark about "jankiness" and expectations; it was unfairly passive aggressive, and tbh at the time I was hoping someone would see that and feel compelled to respond. Yeah, that wasn't cool of me. I do realize this service is curated by volunteers and that actual human beings maintain it. Thanks again for checking in on us.
I apologizforut my cunty remark about jankiness ant expectations; it was passive aggressive, and tbh I was hoping someone would see that and feel compelled to respondYeah, that wasn't cool of me. . I do realize this service is run by volunteers and that human beings maintain it. Thx again for checking in on us. Kelly Aster (talk) 16:17, 9 March 2024 (UTC)Reply[reply]
try Special:Preferences Gongxiang01 (talk) 06:17, 17 March 2024 (UTC)Reply[reply]

Request for feedback on draft RfC[edit | edit source]

I have created a draft RfC regarding simplifying current policy on reception wikis; any feedback would be appreciated. Tali64³ (talk | contributions) 22:38, 8 March 2024 (UTC)Reply[reply]

"Wikis should not be primarily used to host pornography." has some text that probably wasn't meant to be included[edit | edit source]

"WikiTide's content policy includes an outright ban on adult content, while Miraheze's does not. This proposal is an attempt to bridge the two policies while not making it more strict than it needs to be. As this is a notable change to current Miraheze policy, it is offered separately for approval."

I don't think this was meant to be included, it's just part of the justification for the RfC Collei (talk) (contribs) 00:02, 9 March 2024 (UTC)Reply[reply]

Thanks, Good catch! I've removed the extra bits. --NotAracham (talkcontribsglobal) 01:27, 9 March 2024 (UTC)Reply[reply]

CAPTCHA unworkable in china[edit | edit source]

In China, I editing a page. but the wiki need to input a captcha. Do this using reCAPTCHA? It can't working in China, please change to the hCAPTCHA. thx. Gongxiang01 (talk) 11:39, 11 March 2024 (UTC)Reply[reply]

The captcha that Miraheze is currently using is hCaptcha, but it's not loading properly in the mainland of China right now.––铁桶 (Talk) 00:27, 12 March 2024 (UTC)Reply[reply]
Maybe try using Tor? Collei (talk) (contributions) 04:03, 12 March 2024 (UTC)Reply[reply]
Is in China using Tor break the law? So can't use it. Gongxiang01 (talk) 06:14, 12 March 2024 (UTC)Reply[reply]
I'm not 100% sure, I know Tor is censored by the Chinese government, I don't remember if it's legal to use it. Collei (talk) (contributions) 06:17, 12 March 2024 (UTC)Reply[reply]
I remember using Tor is not illegal, but using it for illegal purposes is illegal.––铁桶 (Talk) 07:47, 12 March 2024 (UTC)Reply[reply]
hCaptcha currently is working now in FreeFlarum(today 06:15, 12 March 2024 (UTC)). Gongxiang01 (talk) 06:16, 12 March 2024 (UTC)Reply[reply]

Took slow in Wiki creation[edit | edit source]

Speed of note.ms wiki creation that too slow. now is 2 day now. Pending now. Gongxiang01 (talk) 06:12, 12 March 2024 (UTC)Reply[reply]

Wiki creator is run by volunteers with good intentions. The problem is that we are chronically understaffed, but anyway, lamenting the slow review process does not help.    Waki285(talk|contrib|log|CA|Target) 06:30, 12 March 2024 (UTC)Reply[reply]
A Wiki Creator requested you provide additional information on both of your requests, so they are awaiting your response as I write this. – Jph2 (talk) 13:31, 12 March 2024 (UTC)Reply[reply]

TMC “Users blocked from commenting” user right - revoke rights in ManageWiki?[edit | edit source]

I can’t find the revoke selection in user rights on ManageWiki in The Miraheze Cookbook. I created an abuse filter as an alternative.

Is there a revoke setting in ManageWiki?

See mh:cookbook:Special:ManageWiki/permissions/users_blocked_from_commenting Silicona (talk) 15:35, 13 March 2024 (UTC)Reply[reply]

This isn't supported yet via ManageWiki. SRE can probably set this up for you if you want, feel free to make a request at Phorge. OrangeStar (talk) 15:44, 13 March 2024 (UTC)Reply[reply]
I reported this to Phorge. Silicona (talk) 17:27, 13 March 2024 (UTC)Reply[reply]

Special:Ask (Semantic MediaWiki)[edit | edit source]

Good morning. For some time now, there have been problems displaying results from the special 'Ask' page of the Semantic MediaWiki extension. Using {{#ask}} the results of the searches performed appear correctly, but if it is done from the special page, it indicates that there is an internal error. The wiki in question is https://esnaruto.miraheze.org/.

Somebody could help me? Thank you Yuusha Fuyuno (talk) 09:45, 14 March 2024 (UTC)Reply[reply]

Hi, can you report this, including the full internal error, on Phorge? OrangeStar (talk) 18:27, 18 March 2024 (UTC)Reply[reply]

Incorrect time[edit | edit source]

Current time now is 22:48 but views 14:48. Gongxiang01 (talk) 14:48, 16 March 2024 (UTC)Reply[reply]

Meta default uses UTC. You can change the time displayed in Special:Preferences Reception123 (talk) (C) 16:10, 16 March 2024 (UTC)Reply[reply]

The Miraheze Cookbook renaming RfC[edit | edit source]

I have created an RfC about potential wiki rename and redesign on The Miraheze Cookbook. Please see mh:cookbook:The Miraheze Cookbook:Requests for Comment/Wiki rename and redesign. Any feedback would be appreciated! Silicona (talk) 19:13, 16 March 2024 (UTC)Reply[reply]

Just reminding that this RfC is a draft one. Silicona (talk) 19:14, 16 March 2024 (UTC)Reply[reply]
Hi, please note that as a general rule this portal is for global matters or mostly for asking for assistance with one's wiki. Advertising a local RfC pertaining to a local wiki matter isn't the most appropriate use. Reception123 (talk) (C) 20:30, 16 March 2024 (UTC)Reply[reply]
The renaming is required by @NotAracham so I created a draft RfC on that wiki. Silicona (talk) 21:22, 16 March 2024 (UTC)Reply[reply]
Understood, but community members may add their input on-wiki, it's unnecessary for the most part to advertise here on this topic. BrandonWM (talkcontributionsglobalrights) 04:59, 17 March 2024 (UTC)Reply[reply]
Please don't send it on Meta Community Portal. Gongxiang01 (talk) 06:26, 17 March 2024 (UTC)Reply[reply]

The mediawiki.org is not visible on China.[edit | edit source]

Now, we can't visit mediawiki.org on China.

There is the solution for this question:

  • Fork(copy) some useful article with mediawiki.org, but you "shouldn't to create a wiki to fork it" by Content Policy. Best is on Meta.
  • Do not use with mediawiki.org link(keep a few link to it)

Who agree? --Gongxiang01 (talk) 10:27, 17 March 2024 (UTC)Reply[reply]

Agree as creator. --Gongxiang01 (talk) 10:27, 17 March 2024 (UTC)Reply[reply]

don't tell me use VPN or Tor, it's break the law in China. And Chinese users can testing do it can visit? -- Gongxiang01 (talk) 10:27, 17 March 2024 (UTC)Reply[reply]

It's not illegal per se: https://www.tomsguide.com/features/are-vpns-legal-in-china
Also, rules are made to be broken. Collei (talk) (contributions) 18:18, 17 March 2024 (UTC)Reply[reply]

How I know Global edit count?[edit | edit source]

In permission request needed. Gongxiang01 (talk) 13:29, 17 March 2024 (UTC)Reply[reply]

I think this is where the Global Edits is found:
    It's in Special:CentralAuth.     Go to your contributions.     At the bottom, click on Accounts.
Special:CentralAuth/Gongxiang01
--- Imamy (talk) 01:27, 18 March 2024 (UTC)Reply[reply]
What? It smally for 300??? Gongxiang01 (talk) 02:47, 18 March 2024 (UTC)Reply[reply]
It looks like you joined in December 2023. That number will continue to go up.
--- Imamy (talk) 22:38, 18 March 2024 (UTC)Reply[reply]

New Welcome Template[edit | edit source]

I don't think I'm alone in being unsatisfied by our current welcome template. It focuses excessively on creating a userpage and policies not super important (or welcoming) to new users. I know of users, including myself, that use their own custom welcome template for this reason. This is also important because scripts like Twinkle use the current Welcome template by default. I'd like us to discuss potential improvements so that new users can be effectively welcomed into the community. Globe - (TalkContributionsCA) 11:33, 18 March 2024 (UTC)Reply[reply]

Agree, and not just because Globe's welcome was remade using mine. For me, the current template seems bulked up with information that most new users don't care about, and even if they do it's delivered clustered and poorly. I used w:Template:Welcome and more so w:Template:Welcome cookie(funny enough the first and only welcome message I've got on enwiki) to make it seems as welcoming as possible for new users, while including some basic information. Personally, I believe the former is more important. There's no point in giving info if they don't feel welcome or engaged. If we make them want to stay and engage, they'll find their way to the information on their own. ╚pixDeVl╝ (Talk Board Contributions CentralAuth) 14:36, 18 March 2024 (UTC)Reply[reply]
Agree too. We can go and make it the default, but first I would like the template to be in the Template: namespace. OrangeStar (talk) 18:21, 18 March 2024 (UTC)Reply[reply]