User talk:Waki285

Let's get in touch!

Wiki creator helpful tips
Hi Waki285,

First off, I will just start by welcoming you to the wiki creator team. Thank you for volunteering, and for self-nominating yourself. As you are no doubt aware, Content Policy is our key global policy that guides us in creating wikis for customers. Essentially, every wiki needs to have both a clear purpose, some sort of scope (broad or narrow), and a topical focus. This is the main criterion that helps us to determine whether a wiki will have any potential Content Policy problems.

Second, I wanted to share with you a few tips that I found helpful when I first joined as a wiki creator:


 * 1) "Request comments" tab. Intuitively, one would think to use this tab when requesting more information, but as Amanda Catherine (and others) pointed out to me shortly after I joined as a wiki creator, there was currently a known issue with this in that the requestor wasn't notified via e-mail unless their wiki is either (a) approved or (b) declined. While requestors are now notified of updated requests, changes in status, or new comments now, it's still somewhat preferred to continue with this approach, mainly because it gives the request more attention, keeps the Special:RequestWikiQueue minimal, and prevents other wiki creators from inadvertently approving a request needing more information. Thus, when requesting more information on a wiki request, you really either (a) use the "decline" tab, referencing your follow-up comments in that text box and telling them to back into Special:RequestWikiQueue/  in order to add to, but not replace, their existing description with the needed information or (b) use either the "request comments" or "decline" tab in combination with a message on the requestor's user talk page on Meta. The approach you use is entirely up to you. I personally prefer option A, but either one is fine;
 * 2) Private wikis. Private wikis can generally have a shorter description and a less specific purpose, scope, or topic, but they do still need one. If you have some reservations about approving it as, say, a public wiki, due to that vagueness, you can tell them, in your comments prior to approving it, that you're approving it only as a private wiki and remind them to ensure their wiki complies with all aspects of Content Policy;
 * 3) Eurovision song contest and fictional worldbuilding wikis. These are two types of wikis that have few, if any, problems with them. So, as long as there's a clear sitename, URL, and at least a few words in the description that indicates this as the purpose, it's fine to approve them;
 * 4) Reception wikis (positive and negative). Many of the Reception wikis tend to give us the most the grief, especially in terms of content that is very negative about users. If it's a Reception wiki that focuses on terrible fast-food restaurants, that's usually less problematic than, say, one that focuses on gamer or YouTube celebrities, mainly because you're not dealing with content about real, living people. Please don't hesitate to ask follow up questions, sometimes multiple times, of these wiki requests, trying to narrow down whether the wikis will write about real people in some way and, if so, how they will do it. And, at the end of the day, if you are still not comfortable approving, you can write "on hold" for review by another wiki creator in "request comments";
 * 5) Chinese language mini-world wiki requests. These ones are tricky, but cause us arguably the most grief, particularly when they publish personal information of real people without their consent. Stewards have recently closed a swath of them following a detailed report on stewards' noticeboard, but some of the tricks I've observed them using are odd descriptions like "anti-dog wiki" or to "expose the truth and scandal". Somewhat less common, they will use a completely different, but vague, description, then change their tune when you follow up with them and use some of those key phrases I mentioned in the previous sentence;
 * 6) Google Translate. Don't hesitate to use Google Translate to review non-English public and private wikis. Notwithstanding the above point, most of these wikis' descriptions translate surprisingly well. As you've probably already noticed, I like to copy and paste the translated to English description into "request comments," so other wiki creators can see it easily. This is optional, but it's a good practice, I think; and,
 * 7) Don't hesitate to reach out on Discord and ask for a second opinion. If you are still unsure about approving a wiki, or just want a second opinion, don't hesitate to reach out to any wiki creator on Discord. This might be the most important guideline.

Cheers,

Dmehus (talk) 16:56, 8 December 2020 (UTC)


 * ✅:I'm currently working. 05:49, 13 December 2020 (UTC)

test
test

-- 04:24, 11 December 2020 (UTC)

chakuwikiアカウントの件のご確認
Chakuwikiへのご登録ありがとうございます. 念のためご確認ですが、あちらのわっきーさんはご本人でしょうか？--Bakaba (talk) 04:42, 13 December 2020 (UTC) そうです. -- 04:50, 13 December 2020 (UTC)
 * ご回答ありがとうございます. こちらでもよろしくお願いいたします. --Bakaba (talk) 05:09, 13 December 2020 (UTC)

署名について
はじめまして(?)、ウソペディアやらアンサイクロペディアやらに居座るシュヴァルツと申します.

User:Waki285/sigの投稿記録のリンクがただのSpecial:Contributionsになっているようなのでご報告しておきます. -- Schwarz ・ Talk /  ウソペディア  04:46, 13 December 2020 (UTC)

教えてくださってありがとうございます. -- 04:52, 13 December 2020 (UTC)

Request for Resuming Reviewing Wiki Requests
Hello, I have noticed that you have not been reviewing wiki requests lately. Instead, you have been translating pages. While I do understand that life can be very busy and you may not have enough time, could you please try to review at least the Japanese wiki requests instead of translating pages? That would be a great help. Thank you very much. R4356th (talk) 10:55, 2 January 2021 (UTC)