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)


 * R4356th ✅ 23:23, 5 January 2021 (UTC)
 * That would be wonderful, yes. Your expertise in reviewing the Japanese wiki requests, especially, ensuring they're adequately and properly described, would be very helpful. In particular, corresponding in Japanese with wiki requestors where deficiencies in wiki requests exist. That being said, your Japanese translation work has also been very helpful, and if you would ever like to serve as a Japanese translation administrator, please let me know, as you would be quite helpful there, I think. Dmehus (talk) 23:28, 5 January 2021 (UTC)
 * Thank you very much. R4356th (talk) 09:45, 6 January 2021 (UTC)

Translation administrator granted - 2021-01-13
Hi, Waki285. An administrator on Meta has granted you the  user group permission, which gives you the ability to mark updated source pages for translation and prepare additional, untranslated pages for translation, among a few other permissions related to the administration of translated pages. You should also be aware that the granting of this user group is at the discretion of Meta administrators, so different administrators will have slightly different criteria for granting. Likewise, just as it is a discretionary appointment, revocation is also at the discretion of Meta administrators and, again, each will have their own criteria for revocation.

Nevertheless, the following are some of the main guidelines for translation administrators. If you follow these guidelines completely, it is unlikely your translation administrator user group should ever be revoked.


 * Don't mark or prepare pages too quickly. Administration of translation pages is handled by a system maintenance bot, FuzzyBot, whose tasks are handled by  and  . Accordingly, it is strongly recommended that you check FuzzyBot's recent edits and log actions to see when it has completed your request. A good rule of thumb is to wait approximately 5-10 minutes between marking pages
 * Noticeboards and talk pages should never be translated. Due to the dynamically changing nature of the content on these pages, translation of these pages is undesirable, so they should never be prepared for translation. If you note that a noticeboard is proposed for translation (i.e., pages which contain translation tags but which haven't yet been marked), it's best to remove the  and   characters from the given discussion thread(s) that note the example translation syntax, to remove the noticeboard or talk page from pages proposed for translation
 * Never remove a translated page from the translation system. This is not recommended, mainly because the translation page units (in Translations: namespace) remain. Instead, if you believe a page should no longer be translated, start a new thread at Administrators' noticeboard recommending the given translated subpage(s) for deletion by an administrator. Once all the translated subpage(s) have been deleted, then a page can be removed from the translation system
 * Make use of  and   tags. The former is especially helpful with translating the displayed text of wikilinks (including interwiki wikilinks) and external links, and the latter is particularly helpful where the linked destination page is translated into languages other than English
 * Consider the utility and usefulness before preparing new pages for translation. For example, additional untranslated pages in Tech: namespace aimed at explaining to system administrators how to perform certain procedures are unlikely to ever be read in languages other than English. A best practice here is to propose new pages for translation at Administrators' noticeboard and obtain consensus there to prepare the page
 * Ignore, generally, pages in userspace proposed for translation. Often these are userspace drafts contain translation tags. You can usually just ignore these. If in doubt, you can ask at Administrators' noticeboard
 * Bookmark this help page on MediaWiki.org. Aimed specifically at translation administrators like you, it contains very useful, well written information on the Translate extension's translation administration tools

In addition, a couple of technical limitations regarding the  user group:
 * 1) You cannot mark fully protected pages that have been updated. If you see such a page that needs to be re-marked, please leave a note on the user talk page of any administrator on Meta or at Administrators' noticeboard; and,
 * 2) You cannot delete translated subpages. Again, you can recommend long outdated and unmaintained translations, as well as poor translations, for deletion by leaving a note on the user talk page of any administrator on Meta or at Administrators' noticeboard

If you have any questions, please don't hesitate to reach out. Thank you! --Dmehus (talk) 16:54, 13 January 2021 (UTC)

Congrats!
Congratulations on becoming a translation administrator! Hope to be collaborating with you soon. R4356th (talk) 18:01, 13 January 2021 (UTC)

test 2
-- 04:00, 15 February 2021 (UTC)

A barnstar for you!
thanks!-- 08:00, 18 February 2021 (UTC)

バーンスターを贈ります!

 * Thank you! 04:11, 27 May 2021 (UTC)

バーンスターを贈ります!
ラグビートップリーグが終わっちゃって寂しいようー--シ７ク９チ２ニ (talk) 12:25, 2 June 2021 (UTC)

誤差
こんにちは、あなたのユーザーページがエラーカテゴリに表示されます. このエラーを修正していただけませんか？カテゴリはこれ、Category:Pages with non-numeric formatnum argumentsです. --Angelo Pisani (talk) 14:26, 17 July 2021 (UTC)


 * @Angelo Pisani 、ごめんなさい. 私はこのエラーを修正する方法がわかりません. (formatnum関数を使用していません) 10:49, 18 July 2021 (UTC)