User talk:Leaderboard/Archive 1

Welcome
Welcome to Wikibooks, Leaderboard!

 First steps tutorial Wikibooks is for collaborative development of free textbooks.

You do not need technical skills to contribute. You can easily change most books. Please introduce yourself, and let us know what interests you.

If you already contribute at other Wikimedia projects, our Wikimedia Orientation should quickly get you started. (Would you like to provide feedback on this message?)

  Getting help   Made a mistake?   Goodies, tips and tricks
 * Read the Using Wikibooks book for a friendly introduction to the project, or our help pages for more information.
 * You can get friendly help from the community in the user assistance room or our IRC channel.
 * Upload freely licensed files to Wikimedia Commons. You may request permission to upload fair use files locally. Please include author and source information and a non-free use rationale for non-free files.
 * You can restore a previously saved version.
 * Pages should follow the  naming convention.
 * Need to rename a page? Use the move tab (is available once your account is 4 days old - until then, ask for help).
 * To request a page be deleted, add to the top of the page.
 * Was a page you made deleted? Please read the deletion policy, and check the deletion log to find out why. Also check the RFD archives if applicable. You can request undeletion at WB:RFU, or ask the administrator who deleted the page.
 * Please fill in the edit summary and preview your edits before saving.
 * Sign your name on discussion pages by typing &#126;&#126;&#126;&#126;
 * User scripts can make many tasks easier. Look at the Gadgets tab of my preferences; check off the boxes for the scripts you want, and hit save!

'''Jai Jinendra Vishal Bakhai - Works 17:01, 14 September 2014 (UTC)

Thanks
Thank you for reviewing and checking the page I had changed. Also, I have changed the home page of the book "Qbasic". It will be very helpful if you could just review and check the page. Thank you again. Debanshu.Das (discuss • contribs) 15:30, 4 June 2019 (UTC)

Note about welcoming users
I have seen that you have welcomed a user, named Horizon051, yet this account had no contributions. It's best to welcome users when they have edit/contributed. Because I could welcome an account that popped up out of no where, with no contributions, and welcomed him/her with the welcome template. Then 2 hours later, I find out the person I welcomed was a vandalism only account posting gross/disgusting/unacceptable comments. So the user I welcomed for there "Great contributions" was a vandalism only account.

Bottom line is, (I'm not forcing you, but it is recommended and most prefered) to welcome users when they have contributed, so you don't accidentally welcome a spammer/vandalism only account. Thanks. --atcovi (talk) 13:59, 8 February 2015 (UTC)
 * atcovi, I generally welcome most users , even new accounts , because a new user would feel better being welcomed immediately.

Also, even if that account turns out to be a vandalism only account , that is not a problem to me. Because not all accounts would vandalize, so it is better to welcome users immediately(in my opinion) than delay it. People who only want to vandalize would do so whether there is a welcome message or not, but other users would feel better and be more encouraged to contribute if we welcome them.--Leaderboard 14:06, 8 February 2015 (UTC)
 * I have no problem with whatever decision you make. Regards, --atcovi (talk) 14:08, 8 February 2015 (UTC)

Have you been on Wikibooks' IRC?
http://webchat.freenode.net/?channels=#wikibooks

Me, Aza158 (admin), and pizero (admin) are there. This is where I am in contact with the Wikbooks administrators, since you seem helpful enough, you could possibly join me and some other Wikibooks editors here?

Thanks. --atcovi (talk) 14:12, 8 February 2015 (UTC)
 * Hi ,

I do not know much about IRC. What is it used for?

Thanks , --Leaderboard 14:17, 8 February 2015 (UTC)


 * Chatting, Contact. I can contact the admins there and ask them to do stuff, it'll possibly be helpful for you. --atcovi (talk) 14:22, 8 February 2015 (UTC)
 * It's a helpful place, I've been using it for a year. It's really handy, like talking with users about specific stuff. --atcovi (talk) 15:56, 8 February 2015 (UTC)
 * Atcovi, As for the user details , should I choose the Authorisation checkbox and enter my current Wikibooks credinals?

Or should I enter as a 'guest'?--Leaderboard (discuss • contribs) 17:54, 9 February 2015 (UTC)
 * Enter as a guest, it's best. --72.84.233.224 (discuss) 21:00, 9 February 2015 (UTC)

I would also like to see these things happen &#39;Palianco&#39; (discuss • contribs) 19:41, 27 March 2019 (UTC)
 * Sorry, I'm not sure what you mean, and this is a thread that's 4 years old... Leaderboard (discuss • contribs) 19:57, 27 March 2019 (UTC)

Just to make it easier for you
https://en.wikibooks.org/w/index.php?title=Wikijunior:Ancient_Civilizations/Minoans&curid=78456&diff=2763564&oldid=2763395 - Use "rollback" for spam/gross vandalism/vandalism in general/disruptive edits. "Rejected changes" are usually meant to be undoing good faith edits. Seeing here, this is obviously a not good faith edit, thus it's vandalism. Thanks. --atcovi (talk) 12:35, 10 February 2015 (UTC)
 * Hi atcovi. I generally use Rejected Changes for all unwanted edits for pages which are not reviewed. For pages which are reviewed or special(like talk), I use rollback or undo. Can you tell me why I should use rollback for general vandalism?

Thanks, --Leaderboard (discuss • contribs) 12:55, 10 February 2015 (UTC)


 * Rollback usually is for reverting vandalism, more here: WP:Rollback --atcovi (talk) 12:56, 10 February 2015 (UTC)

Invitation


Hello, Leaderboard,

I am contacting you because you have left feedback about VisualEditor at pages like VisualEditor/Feedback in the past. The Editing team is now asking for your help with VisualEditor. Please tell them what they need to change to make VisualEditor work well for you. The team has a list of top-priority problems, but they also want to hear about small problems. These problems may make editing less fun, take too much of your time, or be as annoying as a paper cut. The Editing team wants to hear about and try to fix these small things, too.

You can share your thoughts by clicking this link. You may respond to this quick, simple, anonymous survey in your own language. If you take the survey, then you agree your responses may be used in accordance with these terms. This survey is powered by Qualtrics and their use of your information is governed by their privacy policy.

More information (including a translatable list of the questions) is posted on wiki at mw:VisualEditor/Survey 2015. If you have questions, or prefer to respond on-wiki, then please leave a message on the survey's talk page.

Unsubscribe from this list •  Sign up for VisualEditor's multilingual newsletter  •   Translate the user guide

Thank you, Whatamidoing (WMF) (talk) 17:39, 3 April 2015 (UTC)


 * Done it. I've responded with the main issues that I face. --Leaderboard (discuss • contribs) 17:04, 4 April 2015 (UTC)

Is it really that necessary to do that in action sypos? &#39;Palianco&#39; (discuss • contribs) 19:41, 27 March 2019 (UTC)
 * Sorry, I can't understand what you're trying to say. Leaderboard (discuss • contribs) 19:57, 27 March 2019 (UTC)

VisualEditor News #2—2015


Did you know? With Citoid in VisualEditor, you click the 'book with bookmark' icon and paste in the URL for a reliable source:



Citoid looks up the source for you and returns the citation results. Click the green "Insert" button to accept its results and add them to the article:



After inserting the citation, you can change it. Select the reference, and click the "Edit" button in the context menu to make changes.

The user guide has more information about how to use VisualEditor. Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's performance, the Citoid reference service, and support for languages with complex input requirements. Status reports are posted on Mediawiki.org. The worklist for April through June is available in Phabricator.

The weekly task triage meetings continue to be open to volunteers, each Wednesday at 11:00 (noon) PDT (18:00 UTC). You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker. Instead, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug. Learn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal.

Recent improvements
VisualEditor is now substantially faster. In many cases, opening the page in VisualEditor is now faster than opening it in the wikitext editor. The new system has improved the code speed by 37% and network speed by almost 40%.

The Editing team is slowly adding auto-fill features for citations. This is currently available only at the French, Italian, and English Wikipedias. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to improve precision and reduce the need for manual corrections by contributing to the Citoid service's definitions for each website.

Citoid requires good TemplateData for your citation templates. If you would like to request this feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.

The special character inserter has been improved, based upon feedback from active users. After this, VisualEditor was made available to all users of Wikipedias on the Phase 5 list on 30 March. This affected 53 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh.

Work continues to support languages with complex requirements, such as Korean and Japanese. These languages use input method editors ("IMEs”). Recent improvements to cursoring, backspace, and delete behavior will simplify typing in VisualEditor for these users.

The design for the image selection process is now using a "masonry fit" model. Images in the search results are displayed at the same height but at variable widths, similar to bricks of different sizes in a masonry wall, or the "packed" mode in image galleries. This style helps you find the right image by making it easier to see more details in images.

You can now drag and drop categories to re-arrange their order of appearance ​on the page.

The pop-up window that appears when you click on a reference, image, link, or other element, is called the "context menu". It now displays additional useful information, such as the destination of the link or the image's filename. The team has also added an explicit "Edit" button in the context menu, which helps new editors open the tool to change the item.

Invisible templates are marked by a puzzle piece icon so they can be interacted with. Users also will be able to see and edit HTML anchors now in section headings.

Users of the TemplateData GUI editor can now set a string as an optional text for the 'deprecated' property in addition to boolean value, which lets you tell users of the template what they should do instead. (T90734)

Looking ahead
The special character inserter in VisualEditor will soon use the same special character list as the wikitext editor. Admins at each wiki will also have the option of creating a custom section for frequently used characters at the top of the list. Instructions for customizing the list will be posted at mediawiki.org.

The team is discussing a test of VisualEditor with new users at the English Wikipedia, to see whether they have met their goals of making VisualEditor suitable for those editors. The timing is unknown, but might be relatively soon. (T90666)

Let's work together

 * Share your ideas and ask questions at mw:VisualEditor/Feedback.
 * Can you translate from English into any other language? Please check this list to see whether more interface translations are needed for your language.  Contact us to get an account if you want to help!
 * The design research team wants to see how real editors work. Please sign up for their research program.
 * File requests for language-appropriate "" and "" icons for the character formatting menu in Phabricator.

Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

— Elitre (WMF)

19:45, 10 April 2015 (UTC)

VisualEditor News #3—2015


Did you know? When you click on a link to an article, you now see more information: The link tool has been re-designed: There are separate tabs for linking to internal and external pages. The user guide has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team has created new interfaces for the link and citation tools and fixed many bugs and changed some elements of the design. Some of these bugs affected users of VisualEditor on mobile devices. Status reports are posted on mediawiki.org. The worklist for April through June is available in Phabricator.

A test of VisualEditor's effect on new editors at the English Wikipedia has just completed the first phase. During this test, half of newly registered editors had VisualEditor automatically enabled, and half did not. The main goal of the study is to learn which group was more likely to save an edit and to make productive, unreverted edits. Initial results will be posted at Meta later this month.

Recent improvements
Auto-fill features for citations are available at a few Wikipedias through the citoid service. Citoid takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. If Citoid is enabled on your wiki, then the design of the citation workflow changed during May. All citations are now created inside a single tool. Inside that tool, choose the tab you want (,, or ). The cite button is now labeled with the word "" rather than a book icon, and the autofill citation dialog now has a more meaningful label, "", for the submit button.

The link tool has been redesigned based on feedback from Wikipedia editors and user testing. It now has two separate sections: one for links to articles and one for external links. When you select a link, its pop-up context menu shows the name of the linked page, a thumbnail image from the linked page, Wikidata's description, and appropriate icons for disambiguation pages, redirect pages and empty pages (where applicable). Search results have been reduced to the first five pages. Several bugs were fixed, including a dark highlight that appeared over the first match in the link inspector. (T98085)

The special character inserter in VisualEditor now uses the same special character list as the wikitext editor. Admins at each wiki can also create a custom section for frequently used characters at the top of the list. Please read the instructions for customizing the list at mediawiki.org. Also, there is now a tooltip to describing each character in the special character inserter. (T70425)

Several improvements have been made to templates. When you search for a template to insert, the list of results now contains descriptions of the templates. The parameter list inside the template dialog now remains open after inserting a parameter from the list, so that users don’t need to click on "" each time they want to add another parameter. (T95696) The team added a new property for TemplateData, "", for template parameters. This optional, translatable property will show up when there is text describing how to use that parameter. (T53049)

The design of the main toolbar and several other elements have changed slightly, to be consistent with the MediaWiki theme. In the Vector skin, individual items in the menu are separated visually by pale gray bars. Buttons and menus on the toolbar can now contain both an icon and a text label, rather than just one or the other. This new design feature is being used for the cite button on wikis where the Citoid service is enabled.

The team has released a long-desired improvement to the handling of non-existent images. If a non-existent image is linked in an article, then it is now visible in VisualEditor and can be selected, edited, replaced, or removed.

Let's work together

 * Share your ideas and ask questions at mw:VisualEditor/Feedback.
 * The weekly task triage meetings continue to be open to volunteers, usually on Wednesday at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings.  You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker, though.  Instead, go to Phabricator and "associate" the VisualEditor Q4 blocker project with the bug.
 * If your Wikivoyage, Wikibooks, Wikiversity, or other community wants to have VisualEditor made available by default to contributors, then please contact James Forrester.
 * If you would like to request the Citoid automatic reference feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
 * The team is planning the second VisualEditor-related "translathon" for July. Please follow this task on Phabricator for details and updates! Announcements will follow in due course.

Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

— Elitre (WMF)

10:45, 13 June 2015 (UTC)

VisualEditor News #4—2015
Read this in another language •  Subscription list for this multilingual newsletter

 Did you know? You can add quotations marks before and after a title or phrase with a single click.

Select the relevant text. Find the correct quotations marks in the special character inserter tool (marked as Ω in the toolbar). Click the button. VisualEditor will add the quotation marks on either side of the text you selected. You can read and help translate the user guide, which has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team have been working on mobile phone support. They have fixed many bugs and improved language support. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving language support and functionality on mobile devices.

Wikimania
The team attended Wikimania 2015 in Mexico City. There they participated in the Hackathon and met with individuals and groups of users. They also made several presentations about and the future of editing.

Following Wikimania, we announced winners for the VisualEditor 2015 Translathon. Our thanks and congratulations to users Halan-tul, Renessaince,  जनक राज भट्ट (Janak Bhatta), Vahe Gharakhanyan, Warrakkk, and Eduardogobi.

For interface messages (translated at translatewiki.net), we saw the initiative affecting 42 languages. The average progress in translations across all languages was 56.5% before the translathon, and 78.2% after (+21.7%). In particular, Sakha improved from 12.2% to 94.2%; Brazilian Portuguese went from 50.6% to 100%; Taraškievica went from 44.9% to 85.3%; Doteli went from 1.3% to 41.2%. Also, while 1.7% of the messages were outdated across all languages before the translathon, the percentage dropped to 0.8% afterwards (-0.9%).

For documentation messages (on mediawiki.org), we saw the initiative affecting 24 languages. The average progress in translations across all languages was 26.6% before translathon, and 46.9% after (+20.3%). There were particularly notable achievements for three languages. Armenian improved from 1% to 99%; Swedish, from 21% to 99%, and Brazilian Portuguese, from 34% to 83%. Outdated translations across all languages were reduced from 8.4% before translathon to 4.8% afterwards (-3.6%).

We published some graphs showing the effect of the event on the Translathon page. We thank the translators for participating and the translatewiki.net staff for facilitating this initiative.

Recent improvements
Auto-fill features for citations can be enabled on each Wikipedia. The tool uses the citoid service to convert a URL or DOI into a pre-filled, pre-formatted bibliographic citation. You can see an animated GIF of the quick, simple process at mediawiki.org. So far, about a dozen Wikipedias have enabled the auto-citation tool. To enable it for your wiki, follow the instructions at mediawiki.org.

Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top. In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.

Future changes
The team will be changing the appearance of selected links inside VisualEditor. The purpose is to make it easy to see whether your cursor is inside or outside the link. When you select a link, the link label (the words shown on the page) will be enclosed in a faint box. If you place your cursor inside the box, then your changes to the link label will be part of the link. If you place your cursor outside the box, then it will not. This will make it easy to know when new characters will be added to the link and when they will not.

On the English Wikipedia, 10% of newly created accounts are now offered both the visual and the wikitext editors. A recent controlled trial showed no significant difference in survival or productivity for new users in the short term. New users with access to VisualEditor were very slightly less likely to produce results that needed reverting. You can learn more about this by watching a video of the July 2015 Wikimedia Research Showcase. The proportion of new accounts with access to both editing environments will be gradually increased over time. Eventually all new users have the choice between the two editing environments.

Let's work together

 * Share your ideas and ask questions at mw:VisualEditor/Feedback. This feedback page is now using Flow instead of LiquidThreads.
 * Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mediawiki.org if you can help.
 * If your wiki would like VisualEditor enabled on another namespace, you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
 * Please file requests for language-appropriate "" and "" icons for the styling menu in Phabricator.
 * The design research team wants to see how real editors work. Please sign up for their research program.
 * The weekly task triage meetings continue to be open to volunteers, usually on Tuesdays at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings.  You do not need to attend the meeting to nominate a bug for consideration as a Q1 blocker, though.  Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.

If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you! —Elitre (WMF), 22:27, 14 August 2015 (UTC)

VisualEditor News #5—2015
Read this in another language •  Subscription list for this multilingual newsletter

 Did you know?

You can use the visual editor on smartphones and tablets. Click the pencil icon to open the editor for a page. Inside that, use the gear menu in the upper right corner to "".

The editing button will remember which editing environment you used last time, and give you the same one next time. The desktop site will be switching to a system similar to this one in the coming months. You can read and help translate the user guide, which has more information about how to use the visual editor. Since the last newsletter, the VisualEditor Team has fixed many bugs, added new features, and made some small design changes. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving support for languages like Japanese and Arabic, making it easier to edit on mobile devices, and providing rich-media tools for formulæ, charts, galleries and uploading.

Recent improvements
Educational features: The first time ever you use the visual editor, it now draws your attention to the and  tools. When you click on the tools, it explains why you should use them. (T108620) Alongside this, the welcome message for new users has been simplified to make editing more welcoming. (T112354) More in-software educational features are planned.

Links: It is now easier to understand when you are adding text to a link and when you are typing plain text next to it. (T74108, T91285) The editor now fully supports ISBN, PMID or RFC numbers. (T109498, T110347, T63558) These  "magic links" use a custom link editing tool.

Uploads: Registered editors can now upload images and other media to Commons while editing. Click the new tab in the " " tool. You will be guided through the process without having to leave your edit. At the end, the image will be inserted. This tool is limited to one file at a time, owned by the user, and licensed under Commons's standard license. For more complex situations, the tool links to more advanced upload tools. You can also drag the image into the editor. This will be available in the wikitext editor later.

Mobile: Previously, the visual editor was available on the mobile Wikipedia site only on tablets. Now, editors can use it on all devices regardless of size if they wish. (T85630) Edit conflicts were previously broken on the mobile website. Edit conflicts can now be resolved in both wikitext and visual editors. (T111894) Sometimes templates and similar items could not be deleted on the mobile website. Selecting them caused the on-screen keyboard to hide with some browsers. Now there is a new "" button, so that these things can be removed if the keyboard hides. (T62110) You can also edit table cells in mobile now.

Rich editing tools: You can now add and edit sheet music in the visual editor. (T112925) There are separate tabs for advanced options, such as MIDI and Ogg audio files. (T114227, T113354) When editing formulæ and other blocks, errors are shown as you edit. It is also possible to edit some types of graphs; adding new ones, and support for new types, will be coming.

On the English Wikipedia, the visual editor is now automatically available to anyone who creates an account. The preference switch was moved to the normal location, under Special:Preferences.

Future changes
You will soon be able to switch from the wikitext to the visual editor after you start editing. (T49779) Previously, you could only switch from the visual editor to the wikitext editor. Bi-directional switching will make possible a single edit tab. (T102398) This project will combine the "" and "" tabs into a single "" tab, similar to the system already used on the mobile website. The "" tab will open whichever editing environment you used last time.

Let's work together

 * Share your ideas and ask questions at VisualEditor/Feedback. This feedback page uses Flow for discussions.
 * Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).
 * Local admins can set up the Citoid automatic reference feature for your wiki. If you need help, then please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
 * The weekly task triage meetings are open to volunteers. Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings.  You do not need to attend the meeting to nominate a bug for consideration, though.  Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.

If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you! —Elitre (WMF), 18:19, 30 October 2015 (UTC)

VisualEditor News #6—2015
 Did you know?

A new, simpler system for editing will offer a single Edit button. Once the page has opened, you can switch back and forth between visual and wikitext editing.



If you prefer having separate edit buttons, then you can set that option in your preferences, either in a pop-up dialog the next time you open the visual editor, or by going to Special:Preferences and choosing the setting that you want:

The current plan is for the default setting to have the Edit button open the editing environment you used most recently. You can read and help translate the user guide, which has more information about how to use the visual editor. Read this in another language •  Subscription list for this multilingual newsletter

Since the last newsletter, the visual editor team has fixed many bugs and expanded the mathematics formula tool. Their workboard is available in Phabricator. Their current priorities are improving support for languages such as Japanese and Arabic, and providing rich-media tools for formulæ, charts, galleries and uploading.

Recent improvements
You can switch from the wikitext editor to the visual editor after you start editing. The LaTeX mathematics formula editor has been significantly expanded. (T118616) You can see the formula as you change the LaTeX code. You can click buttons to insert the correct LaTeX code for many symbols.

Future changes
The single edit tab project will combine the "" and "" tabs into a single "" tab, like the system already used on the mobile website. (T102398, T58337) Initially, the "" tab will open whichever editing environment you used last time. Your last editing choice will be stored as a cookie for logged-out users and as an account preference for logged-in editors. Logged-in editors will be able to set a default editor in the tab of Special:Preferences in the drop-down menu about "".

The visual editor will be offered to all editors at the following Wikipedias in early 2016: Amharic, Buginese, Min Dong, Cree, Manx, Hakka, Armenian, Georgian, Pontic, Serbo-Croatian, Tigrinya, Mingrelian, Zhuang, and Min Nan. (T116523) Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. The developers would like to know how well it works. Please tell them what kind of computer, web browser, and keyboard you are using.

In 2016, the feedback pages for the visual editor on many Wikipedias will be redirected to mediawiki.org. (T92661)

Testing opportunities
If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Elitre (WMF), 00:03, 25 December 2015 (UTC)
 * Please try the new system for the single edit tab on test2.wikipedia.org. You can edit while logged out to see how it works for logged-out editors, or you can create a separate account to be able to set your account's preferences.  Please share your thoughts about the single edit tab system at the feedback topic on mediawiki.org or sign up for formal user research (type "single edit tab" in the question about other areas you're interested in).  The new system has not been finalized, and your feedback can affect the outcome.  The team particularly wants your thoughts about the options in Special:Preferences. The current choices in Special:Preferences are:
 * , and
 * . (This is the current state for people already using the visual editor.  None of these options will be visible if you have disabled the visual editor in your preferences at that wiki.)
 * Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).
 * . (This is the current state for people already using the visual editor.  None of these options will be visible if you have disabled the visual editor in your preferences at that wiki.)
 * Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).

VisualEditor News #1—2016
Read this in another language • Subscription list for this multilingual newsletter



Did you know?

Among experienced editors, the visual editor's table editing is one of the most popular features. If you select the top of a column or the end of a row, you can quickly insert and remove columns and rows.

Now, you can also rearrange columns and rows. Click "Move before" or "Move after" to swap the column or row with its neighbor. You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has fixed many bugs. Their workboard is available in Phabricator. Their current priorities are improving support for Japanese, Korean, Arabic, Indic, and Han scripts, and improving the single edit tab interface.

Recent changes
You can switch from the wikitext editor to the visual editor after you start editing. This function is available to nearly all editors at most wikis except the Wiktionaries and Wikisources.

Many local feedback pages for the visual editor have been redirected to mw:VisualEditor/Feedback.

You can now re-arrange columns and rows in tables, as well as copying a row, column or any other selection of cells and pasting it in a new location.

The formula editor has two options: you can choose "Quick edit" to see and change only the LaTeX code, or "Edit" to use the full tool. The full tool offers immediate preview and an extensive list of symbols.

Future changes
The single edit tab project will combine the "" and "" tabs into a single "" tab. This is similar to the system already used on the mobile website. (T102398) Initially, the "" tab will open whichever editing environment you used last time. Your last editing choice will be stored as an account preference for logged-in editors, and as a cookie for logged-out users. Logged-in editors will have these options in the tab of Special:Preferences: The visual editor uses the same search engine as Special:Search to find links and files. This search will get better at detecting typos and spelling mistakes soon. These improvements to search will appear in the visual editor as well.
 * , and
 * . (This is the state for people using the visual editor now.)
 * , and
 * . (This is the state for people using the visual editor now.)

The visual editor will be offered to all editors at most "Phase 6" Wikipedias during the next few months. This will affect the following languages, amongst others: Japanese, Korean, Urdu, Persian, Arabic, Tamil, Marathi, Malayalam, Hindi, Bengali, Assamese, Thai, Aramaic.

Let's work together
If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Elitre (WMF), 19:22, 26 February 2016 (UTC)
 * Please try out the newest version of the single edit tab on test2.wikipedia.org. You may need to restore the default preferences (at the bottom of test2wiki:Special:Preferences) to see the initial prompt for options. Were you able to find a preference setting that will work for your own editing? Did you see the large preferences dialog box when you started editing an article there?
 * Can you read and type in Korean, Arabic, Japanese, Indic, or Han scripts? Does typing in these languages feels natural in the visual editor? Language engineer David Chan needs to know. Please see the instructions at mw:VisualEditor/IME Testing if you can help. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org.
 * Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Join the Tech Talk about "Automated citations in Wikipedia: Citoid and the technology behind it" with Sebastian Karcher on 29 February 2016.

Editing News #2—2016
Read this in another language • Subscription list for this multilingual newsletter

 Did you know?

It's quick and easy to insert a references list.

Place the cursor where you want to display the references list (usually at the bottom of the page). Open the "" menu and click the "" icon (three books).

If you are using several groups of references, which is relatively rare, you will have the opportunity to specify the group. If you do that, then only the references that belong to the specified group will be displayed in this list of references. Finally, click "" in the dialog to insert the. This list will change as you add more footnotes to the page.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has fixed many bugs. Their workboard is available in Phabricator. Their current priorities are improving support for Arabic and Indic scripts, and adapting the visual editor to the needs of the Wikivoyages and Wikisources.

Recent changes
The visual editor is now available to all users at most Wikivoyages. It was also enabled for all contributors at the French Wikinews.

The single edit tab feature combines the "" and "" tabs into a single "" tab. It has been deployed to several Wikipedias, including Hungarian, Polish, English and Japanese Wikipedias, as well as to all Wikivoyages. At these wikis, you can change your settings for this feature in the "" tab of Special:Preferences. The team is now reviewing the feedback and considering ways to improve the design before rolling it out to more people.

Future changes
The "" button will say "". This will affect both the visual and wikitext editing systems. More information is available on Meta.

The visual editor will be offered to all editors at the remaining "Phase 6" Wikipedias during the next few months. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including: Arabic, Hindi, Thai, Tamil, Marathi, Malayalam, Urdu, Persian, Bengali, Assamese, Aramaic and others.

The team is working with the volunteer developers who power Wikisource to provide the visual editor there, for opt-in testing right now and eventually for all users. (T138966)

The team is working on a modern wikitext editor. It will look like the visual editor, and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices around September 2016. You can read about this project in a general status update on the Wikimedia mailing list.

Let's work together
If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready.
 * Do you teach new editors how to use the visual editor? Did you help set up the Citoid automatic reference feature for your wiki? Have you written or imported TemplateData for your most important citation templates? Would you be willing to help new editors and small communities with the visual editor?  Please sign up for the new VisualEditor Community Taskforce.
 * Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Watch the Tech Talk by Sebastian Karcher for more information.

17:18, 3 July 2016 (UTC)

Editing News #3—2016
Read this in another language • Subscription list for this multilingual newsletter

 Did you know?

Did you know that you can easily re-arrange columns and rows in the visual editor?

Select a cell in the column or row that you want to move. Click the arrow at the start of that row or column to open the dropdown menu (shown). Choose either "Move before" or "Move after" to move the column, or "Move above" or "Move below" to move the row.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has mainly worked on a new wikitext editor. They have also released some small features and the new map editing tool. Their workboard is available in Phabricator. You can find links to the list of work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, releasing the 2017 wikitext editor as a beta feature, and improving language support.

Recent changes

 * You can now set text as small or big.
 * Invisible templates have been shown as a puzzle icon. Now, the name of the invisible template is displayed next to the puzzle icon.  A similar feature will display the first part of hidden HTML comments.
 * Categories are displayed at the bottom of each page. If you click on the categories, the dialog for editing categories will open.
 * At many wikis, you can now add maps to pages. Go to the Insert menu and choose the "Maps" item. The Discovery department is adding more features to this area, like geoshapes. You can read more at mediawiki.org.
 * The "Save" button now says "Save page" when you create a page, and "Save changes" when you change an existing page. In the future, the "" button will say "".  This will affect both the visual and wikitext editing systems.  More information is available on Meta.
 * Image galleries now use a visual mode for editing. You can see thumbnails of the images, add new files, remove unwanted images, rearrange the images by dragging and dropping, and add captions for each image.  Use the "Options" tab to set the gallery's display mode, image sizes, and add a title for the gallery.

Future changes
The visual editor will be offered to all editors at the remaining 10 "Phase 6" Wikipedias during the next month. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including Thai, Burmese and Aramaic.

The team is working on a modern wikitext editor. The 2017 wikitext editor will look like the visual editor and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices in October 2016. You can read about this project in a general status update on the Wikimedia mailing list.

Let's work together

 * Do you teach new editors how to use the visual editor? Did you help set up the Citoid automatic reference feature for your wiki? Have you written or imported TemplateData for your most important citation templates? Would you be willing to help new editors and small communities with the visual editor?  Please sign up for the new VisualEditor Community Taskforce.
 * If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready.

—Elitre (WMF) 17:48, 15 October 2016 (UTC)

Editing News #1—2017
Read this in another language • Subscription list for this multilingual newsletter

 Did you know?

Did you know that you can review your changes visually?

When you are finished editing the page, type your edit summary and then choose "". In visual mode, you will see additions, removals, new links, and formatting highlighted. Other changes, such as changing the size of an image, are described in notes on the side.



Click the toggle button to switch between visual and wikitext diffs.



The wikitext diff is the same diff tool that is used in the wikitext editors and in the page history. You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has spent most of their time supporting the 2017 wikitext editor mode which is available inside the visual editor as a Beta Feature, and adding the new visual diff tool. Their workboard is available in Phabricator. You can find links to the work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, supporting the 2017 wikitext editor as a beta feature, and improving the visual diff tool.

Recent changes

 * A new wikitext editing mode is available as a Beta Feature on desktop devices. The 2017 wikitext editor has the same toolbar as the visual editor and can use the citoid service and other modern tools.  Go to Special:Preferences to enable the.
 * A new visual diff tool is available in VisualEditor's visual mode. You can toggle between wikitext and visual diffs.  More features will be added to this later.  In the future, this tool may be integrated into other MediaWiki components.
 * The team have added multi-column support for lists of footnotes. The  block can automatically display long lists of references in columns on wide screens.  This makes footnotes easier to read.  You can request multi-column support for your wiki.
 * You can now use your web browser's function to switch typing direction in the new wikitext mode. This is particularly helpful for RTL language users like Urdu or Hebrew who have to write JavaScript or CSS. You can use Command+Shift+X or Control+Shift+X to trigger this.
 * The way to switch between the visual editing mode and the wikitext editing mode is now consistent. There is a drop-down menu that shows the two options. This is now the same in desktop and mobile web editing, and inside things that embed editing, such as Flow.
 * The item has been moved to the top of the  menu (from clicking on the "hamburger" icon) for quicker access.  There is also now a "Templates used on this page" feature there.
 * You can now create   tags (sometimes used as  ) for chemical formulas inside the visual editor.
 * Tables can be set as collapsed or un-collapsed.
 * The menu now includes characters for Canadian Aboriginal Syllabics and angle quotation marks (‹› and ⟨⟩) .  The team thanks the volunteer developer, Tpt.
 * A bug caused some section edit conflicts to blank the rest of the page. This has been fixed.  The team are sorry for the disruption.
 * There is a new keyboard shortcut for citations:  + +  on a PC, or  + +  on a Mac.  It is based on the keyboard shortcut for making links, which is  +  or  +  respectively.

Future changes

 * The team is working on a syntax highlighting tool. It will highlight matching pairs of   tags and other types of wikitext syntax.  You will be able to turn it on and off.  It will first become available in VisualEditor's built-in wikitext mode, maybe late in 2017.
 * The kind of button used to, , and finish an edit will change in all WMF-supported wikitext editors. The new buttons will use OOjs UI.  The buttons will be larger, brighter, and easier to read.  The labels will remain the same.  You can test the new button by editing a page and adding   to the end of the URL, like this:  https://www.mediawiki.org/wiki/Project:Sandbox?action=edit&ooui=1  The old appearance will no longer be possible, even with local CSS changes.
 * The outdated 2006 wikitext editor will be removed later this year. It is used by approximately 0.03% of active editors.  See a list of editing tools on mediawiki.org if you are uncertain which one you use.
 * If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready.

—Elitre (WMF) 17:59, 12 May 2017 (UTC)

Editing News #1—2018
Read this in another language • Subscription list for this multilingual newsletter Did you know? Did you know that you can now use the visual diff tool on any page?



Sometimes, it is hard to see important changes in a wikitext diff. This screenshot of a wikitext diff (click to enlarge) shows that the paragraphs have been rearranged, but it does not highlight the removal of a word or the addition of a new sentence.

If you enable the Beta Feature for "", you will have a new option. It will give you a new box at the top of every diff page. This box will let you choose either diff system on any edit.

Click the toggle button to switch between visual and wikitext diffs.

In the visual diff, additions, removals, new links, and formatting changes will be highlighted. Other changes, such as changing the size of an image, are described in notes on the side.



This screenshot shows the same edit as the wikitext diff. The visual diff highlights the removal of one word and the addition of a new sentence.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the Editing Team has spent most of their time supporting the 2017 wikitext editor mode, which is available inside the visual editor as a Beta Feature, and improving the visual diff tool. Their work board is available in Phabricator. You can find links to the work finished each week at VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, supporting the 2017 wikitext editor, and improving the visual diff tool.

Recent changes

 * The 2017 wikitext editor is available as a Beta Feature on desktop devices. It has the same toolbar as the visual editor and can use the citoid service and other modern tools.  The team have been comparing the performance of different editing environments.  They have studied how long it takes to open the page and start typing.  The study uses data for more than one million edits during December and January.  Some changes have been made to improve the speed of the 2017 wikitext editor and the visual editor.  Recently, the 2017 wikitext editor opened fastest for most edits, and the 2010 WikiEditor was fastest for some edits.  More information will be posted at Contributors/Projects/Editing performance.
 * The visual diff tool was developed for the visual editor. It is now available to all users of the visual editor and the 2017 wikitext editor.  When you review your changes, you can toggle between wikitext and visual diffs.  You can also enable the new Beta Feature for "Visual diffs".  The Beta Feature lets you use the visual diff tool to view other people's edits on page histories and Special:RecentChanges.
 * Wikitext syntax highlighting is available as a Beta Feature for both the 2017 wikitext editor and the 2010 wikitext editor.
 * The citoid service automatically translates URLs, DOIs, ISBNs, and PubMed id numbers into wikitext citation templates. It is very popular and useful to editors, although it can be a bit tricky to set up.  Your wiki can have this service.  Please read the instructions. You can ask the team to help you enable citoid at your wiki.

Let's work together

 * The team will talk about editing tools at an upcoming Wikimedia Foundation metrics and activities meeting.
 * Wikibooks, Wikiversity, and other communities may have the visual editor made available by default to contributors. If your community wants this, then please contact Dan Garry.
 * The  block can automatically display long lists of references in columns on wide screens.  This makes footnotes easier to read.  You can request multi-column support for your wiki.
 * If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation.

—Elitre (WMF) 20:54, 2 March 2018 (UTC)

Suicide warning
Is that [your warning] true? I really do wonder. I have never really understood this book; there is something to it that I do no understand... I think... some benefit that makes it potentially valuable to people who are depressed and want to be talked to rationally, I think, that can somehow help them... or something. Or at least some of those who (very rarely) contribute to it seem to think so. I've (very, very nearly) never tampered with the book for this reason (and the one time I did, I had doubts afterward whether my contribution had been positive or negative). I do know it's not generally understood by (some of) its contributors as a "how-to manual", at least not in its psychological impact. So I have no real insight into whether or not that warning you've put on it is for the very best; it's an example of one of the many sort of tampering with the book I've never undertaken because I don't understand the dynamics of what I'd be tampering with. I'm not even suggesting a course of action, more like sharing my doubts. --Pi zero (discuss • contribs) 12:49, 6 June 2018 (UTC)

Hello. The topic of Suicide is a risky grey area; hence I erred on the side of caution as such topics have the potential to cause issues. By the way, I did not add anything new; only that I placed some of the text in the beginning as a warning. Leaderboard (discuss • contribs) 13:02, 6 June 2018 (UTC)

Self-promotion
Hi, the article Quantum theory of observation is exclusively the work of Thierry Dugnolle (same in French: fr:Théorie quantique de l'observation) - the same user who added the link to it. And added it in multiple Wikipedia articles, reverted by various different editors there. If this is not self-promotion, what is it? --Mfb (discuss • contribs) 09:04, 4 July 2018 (UTC)
 * Hello, thanks for notifying me. I did not notice that he had placed his name in the top of the article; also, I mistakely thought of 'self-promotion' as that of your work (I've removed that link). That being said, I am not sure whether your claim "by far not important enough to be mentioned here" is accurate enough; can you explain that? Thanks. Leaderboard (discuss • contribs) 09:13, 4 July 2018 (UTC)
 * Just try to find the book outside Wikibooks. Zero reception. --Mfb (discuss • contribs) 09:26, 4 July 2018 (UTC)
 * Okay, it's probably not popular, but how is that a reason for not linking it here (even if it's one person's work)? As long as the content is accurate and relevant, I cannot see any issue at this time(And if indeed it is inaccurate/irrelevant/duplicated, then it should be fixed or a request for deletion initiated). Leaderboard (discuss • contribs) 09:32, 4 July 2018 (UTC)
 * I don't know if it is accurate or relevant, but there is nothing that would demonstrate either. It looks like a pet "theory" of this user. And I don't think Wikibooks is the right place to spread pet theories, especially not into articles about actual science. --Mfb (discuss • contribs) 11:26, 4 July 2018 (UTC)
 * If it's original research, that's against Wikibooks policy. --Pi zero (discuss • contribs) 12:40, 4 July 2018 (UTC)
 * Huh? What's this all about?  To state the obvious, there's no such thing as a Wikibook that belongs to a particular user; that would be directly contradictory to the very concept of Wiki-ness.  WB:HOST.  --Pi zero (discuss • contribs) 10:59, 4 July 2018 (UTC)
 * And hence I'll stand by my decision of removing the author's name at Quantum theory of observation., you should note the comment made by , as indeed putting your name there sounds like a Wikibook that belongs to you. The talk page is a better page to mention that(or maybe a section at the bottom of the page like Contributors). Leaderboard (discuss • contribs) 11:24, 4 July 2018 (UTC)
 * Why would I put a list of contributors whereas I am the single one ?
 * This book is an educational textbook. This is standard quantum physics explained in the framework of Everett's theory. Everything is proved from the first principles, and the computations are usually very simple and can be found in any textbook on the same subject. There are a few paragraphs where I explain my original work because it was made for educational purposes.
 * My name in the front page is not a property right, only an information given to the readers, that I am the author. Authorscan identify themselves on Wikibooks. I am not the first to do it.--TD (discuss • contribs) 12:56, 4 July 2018 (UTC)
 * I get it that you want to attribute yourself as the major contributor, but again, the way that you are doing it is where I have the issue. You may be the single one, but the potential implication is that that wikibook is yours, which is not allowed. Whether you are the only editor or otherwise, you could probably attribute it like how wikibooks like How_To_Assemble_A_Desktop_PC or Basic_Computing_Using_Windows do it. (Yes, those aren't 'one-man' projects, but even then)

Or at least put it in a 'Contributors' section at the bottom of the main page. and other admins, your views on this? Leaderboard (discuss • contribs) 13:16, 4 July 2018 (UTC)
 * I am the single contributor, except for very few minor corrections (typographical...). The book is finished. It is not supposed to be completed because it is consistent as it stands. This is why new contributors are not explicitly invited. If a new contributor wants to change the book against my will, this never happened, but it could, I will want to restore the book as I want it to be, because it is finished. If I think the new contribution is good, it will be welcome, of course, and its author will decide if he or she wants to be identified as a contributor. --TD (discuss • contribs) 13:31, 4 July 2018 (UTC)
 * Contributions are always welcome. That is the nature of Wikibooks.  WB:OWN.  --Pi zero (discuss • contribs) 13:40, 4 July 2018 (UTC)

Note: This discussion was copied (not by me) to Talk:Quantum theory of observation, where there has been some additional discussion. --Pi zero (discuss • contribs) 14:21, 4 July 2018 (UTC)

IRC
Haven't seen you online recently. I assume you are back in the country. I was discussing about pens and that reminded me of the UK and that convinced me to ask you about the plan. Any chance you would be available on August 19? <span style="font-family:Helvetica Neue, Helvetica, san serif; color:#000000;">acagastya 💭 13:55, 5 August 2018 (UTC)

Nope, I'm in India at this time. I'll be back on August 10. P.S: I tried to connect to IRC on my browser, but all I get is "#wikibooks Cannot join channel (+b) - you are banned". This happens no matter which username I use. Leaderboard (discuss • contribs) 14:03, 5 August 2018 (UTC)


 * Is your nick registered? I mean, do you need a password to use it?  Freenode has been under botnet attack for a few days, so I gather, and I think they've taken some sort of measures against that. --Pi zero (discuss • contribs) 14:20, 5 August 2018 (UTC)


 * No, I don't need a password to use it; I just entered my username (nickname) in the 'Nickname' box, but did not check the 'Auth to services' options in here. Leaderboard (discuss • contribs) 14:31, 5 August 2018 (UTC)


 * I suspect you now need an authenticated account to use any wikimedia freenode channel. --Pi zero (discuss • contribs) 14:35, 5 August 2018 (UTC)
 * When I said "back in the country" (well you answered that) -- you should be careful about disclosing real-life identity and other details online. BTW, congratulations! (for some reason the ping did not work) <span style="font-family:Helvetica Neue, Helvetica, san serif; color:#000000;">acagastya 💭 18:57, 6 August 2018 (UTC)

You need to get a cloak, and that would be a good idea, now that you are an admin. <span style="font-family:Helvetica Neue, Helvetica, san serif; color:#000000;">acagastya 💭 11:39, 7 August 2018 (UTC)
 * ? Leaderboard (discuss • contribs) 11:55, 7 August 2018 (UTC)
 * IRC/Cloaks. --Pi zero (discuss • contribs) 13:22, 7 August 2018 (UTC)
 * "User must not be actively blocked from a project" I'm banned on Wikipedia... Leaderboard (discuss • contribs) 13:39, 7 August 2018 (UTC)

Adminship
Welcome to the janitorial squad. --Pi zero (discuss • contribs) 11:19, 6 August 2018 (UTC)
 * Hi, thanks. By the way, have a small doubt; how do I cascade the stability level setting of a book? For instance, if the main page of a book has the stability level set to stable by default, I want to make this applicable to the pages linked in that page (ie, inside the book) as well. Leaderboard (discuss • contribs) 11:41, 6 August 2018 (UTC)
 * Congrats! As far as I know it's not possible to cascade protect subpages, only the included ones. And for MW:Help:Extension:FlaggedRevs there isn't any cascade in the doc. JackPotte (discuss • contribs) 11:46, 6 August 2018 (UTC)
 * Lots of book-oriented things can't be done well by the software. One we've wanted more-or-less forever is the ability to "watch" a book.  Some years ago I figured out an easy way it could be done:  in addition to the existing watchlist, keep a list of pages for, let's call it 'in-depth tracking'.  At the moment a page is added to the 'in-depth' list, add it and all its subpages to the user's watchlist.  At any time in the future, whenever a subpage of anything on the 'in-depth' list is created, at that moment add the new page to the user's watchlist.  And that's it.  Nothing else has to be done.  If the user wants to unwatch any of those subpages, they can.  The feature could be useful on other projects for various purposes, e.g. on Wikipedia one could automatically watch all discussions of a certain kind (say, RFPs, or whatever).  (Alas, I stopped believing years ago that the Foundation can be motivated to do simple things that would benefit the volunteers.) --Pi zero (discuss • contribs) 12:27, 6 August 2018 (UTC)
 * Should've left this message a while ago but I'm really busy with schoolwork and travelling: Congratulations and welcome to the sysop team. --Atcovi (Talk - Contribs) 20:36, 20 August 2018 (UTC)

autoreview
I don't understand why you want to do anything about autoreview, one way or another. I see nothing problematic about the status quo ante. --Pi zero (discuss • contribs) 22:43, 14 August 2018 (UTC)

A few doubts
Hi. I'm not a mathematician, but I will try to help. Have a nice day. --Adam majewski (discuss • contribs) 17:47, 18 August 2018 (UTC)

Pseudo-bot
Looks to me as if pseudo-bot is no longer an effective way to keep edits off RC, probably due to the (candidly, pointless and counterproductive) tampering of the devs with the user interface. My own attitude toward the Foundation's screwing around with the platform is that it's just a force of nature one has to live with; pseudo-bot is something we used to have, and apparently don't anymore because the Foundation that maintains the platform doesn't care about preserving it. --Pi zero (discuss • contribs) 12:08, 19 August 2018 (UTC)
 * In that case, how can I continue with my high-volume edits without flooding RC? I can't grant the bot flag to myself, and even if I do request the bot flag, can't remove it from myself when I'm done (and the duration of the edits do not warrant use of a bot account).
 * Leaderboard (discuss • contribs) 12:17, 19 August 2018 (UTC)
 * I don't see your recent AWB stuff on RC, so perhaps it's working right after all. (Such edits still show up on a watchlist.) --Pi zero (discuss • contribs) 15:11, 19 August 2018 (UTC)
 * , it's indeed working. The trick is to use AWB after setting the pseudo-bot flag; you want  on AWB. Thanks for your help.Leaderboard (discuss • contribs) 16:36, 19 August 2018 (UTC)
 * Again confused. Toggled the pseudo-bot flag, modified permissions of some users, created some pages and edited one page. Only the permissions were marked as a bot; the others flooded RC. What's going on - or am I missing something? Tagging as well in case I've made some mistake. Leaderboard (discuss • contribs) 19:17, 19 August 2018 (UTC)
 * I'd have to look at it and do some testing. I have the advantage that I can set and unset the bot flag as well as the flood flag so can test if there are differences. Per Pi zero, as Wikipedia no longer uses +flood it has likely fallen into disrepair. QuiteUnusual (discuss • contribs) 09:10, 20 August 2018 (UTC)
 * If I filter Recent Changes properly, I don't see your bot edits. It may be that the default, or your chosen, RC filters are incorrect. QuiteUnusual (discuss • contribs) 12:34, 20 August 2018 (UTC)
 * If the default failed to exclude pseudo-flood, wouldn't that effectively nix the whole concept of pseudo-flood, since it would apply to all uses except the few registered users who are able to figure out the perverse filter interface? --Pi zero (discuss • contribs) 12:44, 20 August 2018 (UTC)
 * That's only partially true (I did verify this with RC, taking care to distingush betwen  (bot) edits and otherwise).
 * * The AWB edits were correctly marked as bot edits.
 * * The modification of users' permissions were also correctly marked as bot edits.
 * * The pages created under the Wikibooks namespace were not marked as bot edits, neither were modifications to pages on that namespace.
 * * The permission entry where I removed the pseudo-bot flag was marked as a bot edit.
 * I thought that pseudo-bot = bot; the default shouldn't be showing edits made with either flag. Leaderboard (discuss • contribs) 12:51, 20 August 2018 (UTC)
 * Pseudo-bot / flood is the same as bot. Did you make the Wikibooks namespace edits via AWB or as direct edits? I ask because anything that uses the API needs to set "bot" with each call in order to set the flag even if the account is +bot or +flood. It is therefore possible that AWB doesn't set bot when operating in certain namespaces. If you made the edits directly, then that's clearly not the issue. If I edit the sandbox, which is in the WB namespace, with pseudo-bot set, then it is flagged as a bot edit and doesn't appear in RC. QuiteUnusual (discuss • contribs) 14:18, 20 August 2018 (UTC)
 * The edits to the Wikibooks namespace were made as direct edits. Leaderboard (discuss • contribs) 14:24, 20 August 2018 (UTC)
 * Further note: A page was deleted during that time. That edit was marked as a bot. Leaderboard (discuss • contribs) 14:30, 20 August 2018 (UTC)

Code formatting
Julia code formatting standard suggests 4 spaces indentation (https://github.com/JuliaLang/julia/blob/master/CONTRIBUTING.md#code-formatting-guidelines), but some of your recent edits have changed 4 to 2... Not sure I like the inconsistency... :) Cormullion (discuss • contribs) 15:33, 19 August 2018 (UTC)


 * Hi, the AWB filter is very simple and while the changes work as desired for over 98% of cases, I understand the issue that you have which was an unintentional consequence of the filter. Please feel free to revert the offending edits. On my part, I'll modify the filter to ignore pages on Julia. Thanks again. Leaderboard (discuss • contribs) 16:36, 19 August 2018 (UTC)


 * No problem, only a few places need redoing... :) Cormullion (discuss • contribs) 16:39, 19 August 2018 (UTC)

fr.wb
I don't quite remember what one does to import from another language; Special:Import seems to be for importing from English projects only. Seems like the sort of thing QU would know. --Pi zero (discuss • contribs) 18:33, 22 August 2018 (UTC)
 * , can you help on this? There is an article which needs to be history-merged as the user is simply translating it from fr.wikibooks. Leaderboard (discuss • contribs) 18:44, 22 August 2018 (UTC)
 * It needs someone with the importupload right, usually a Steward. I'll take a look in the morning. QuiteUnusual (discuss • contribs) 22:38, 23 August 2018 (UTC)
 * Which book are we discussing, and do we know the source page on fr.wb? QuiteUnusual (discuss • contribs) 10:30, 24 August 2018 (UTC)
 * the book is Kids-Economy, and the source book on fr.wb is at here, though I note that the principal author is the same. Leaderboard (discuss • contribs) 11:03, 24 August 2018 (UTC)
 * The wiki markup for that would be, fr:Economie-Enfants. --Pi zero (discuss • contribs) 11:40, 24 August 2018 (UTC)
 * All done, although it probably wasn't necessary given the original source was external to fr.wb anyway... However, it is nice for it to be tidy this way. QuiteUnusual (discuss • contribs) 12:54, 24 August 2018 (UTC)

Thank you
I recieved your message. I think I've fixed the problem. I'm going to go back on my previous posts and see if they need fixing as well. Thank you again ! <b style="color:#000">Necromonger</b><b style="color:#000"> Wekeepwhatwekill</b>

I saw your message
Leaderboard, I saw your message. What I'm doing is standard wiki-gnoming. I realize I'm not an active user here, but I was an active en.wikipedian for 10+ years. When a tag is placed on a page and no discussion is started -- for years, yes, it's perfectly acceptable to remove the tag with a descriptive note like this one explaining that a discussion needs to be started because no one else will know what the actual issue is. The same is true here In that example, Mike's Bot placed a npov tag on the page back in 2007, as he had done on multiple pages of relationships, but with no explanation nor any following discussion since the tag was placed. Again, this is simple gnoming and doesn't meet the definition of vandalism. I get it that you disagree with me, and that's fine, people disagree all the time so for now, I'm going to stop all gnoming activity and we'll talk it out and come to an agreement. I've given you my reasons for removing the tag, what are your reasons for wanting them to stay ? <b style="color:#000">Necromonger</b><b style="color:#000"> Wekeepwhatwekill</b> 14:07, 28 August 2018 (UTC)
 * &lt;dropping by&gt; It sounds as if you're applying, on a massive scale, a principle from Wikipedia that isn't contextually appropriate on Wikibooks. --Pi zero (discuss • contribs) 14:16, 28 August 2018 (UTC)
 * Okay, why are you saying this doesn't apply. There's no discussion for these tags, or the discussion has been dead for years. The tags are, then, serving no purpose and they need to be removed.    Also, I didn't see any policy prohibiting the removal of tags for the reason I gave. Again, it's standard on en.wikipedia. <b style="color:#000">Necromonger</b><b style="color:#000"> Wekeepwhatwekill</b> 14:22, 28 August 2018 (UTC)
 * Wikibooks is not Wikipedia. --Pi zero (discuss • contribs) 14:28, 28 August 2018 (UTC)
 * I don't disagree with you there. There's no way a book could be published on Wikipedia!   Now, what are your concerns with my removing the tags ? <b style="color:#000">Necromonger</b><b style="color:#000"> Wekeepwhatwekill</b> 14:41, 28 August 2018 (UTC)
 * Obviously I don't speak for Leaderboard, who is far more familiar with this case than I. My immediate thought on the principle is that book communities have fundamentally different dynamics than Wikipedia articles, essentially stretching out over time in a way that makes it quite inappropriate to put a clock on such tags.  (I took this to be the point Leaderboard was making on your talk page; such tags do not "expire" on Wikibooks, and I read nothing into the fact that the passage Leaderboard cited for this lack-of-expiration happened to be on the vandalism page.) --Pi zero (discuss • contribs) 15:14, 28 August 2018 (UTC)
 * Got it. Yeah I just looked over at NPOV_dispute and didn't see that there was an expiration on tags, I considered to be more or less IAR, after all, what good is a tag on a page if there's been no discussion for years.  I realize for IAR to work there has to be agreement on it.  I tell you what, I'll stop touching any tags at this point and start a discussion on the actual policy pages to see if there is a consensus for removal under certain conditions (like what I've been removing for ).  Thanks for sharing your point of view.. <b style="color:#000">Necromonger</b><b style="color:#000"> Wekeepwhatwekill</b> 15:33, 28 August 2018 (UTC)

I've now reverted all of your edits which removed the tags. Please seek consensus before removing the tags again. Thanks. Leaderboard (discuss • contribs) 15:46, 28 August 2018 (UTC)

Just reverted you
I just reverted your edit on Homeopathy/Introduction. I left a pretty detailed rationale for removing the part about cancer and AIDS. I typically don't revert agian, however, the links don't support homeopathy treating / curing cancer or aids, and, per the talk page, Cancer isn't one disease, it's many. I know you're a sysop so I'll just suggest that you not re-add that section again without some kind of a reliable souirce to back up the allegation that homeopathy can treat or cure cancer or aids. Thanks <b style="color:#000">Necromonger</b><b style="color:#000"> Wekeepwhatwekill</b> 19:04, 4 September 2018 (UTC)

Catching up...
Since that issue of IRC, were you able to join #wikibooks on IRC? Also, got to discuss something related to both on and off wiki. <span style="font-family:Helvetica Neue, Helvetica, san serif; color:#000000;">acagastya 💭 09:46, 16 September 2018 (UTC)
 * Yes, I am now able to join #wikibooks on IRC. Leaderboard (discuss • contribs) 09:49, 16 September 2018 (UTC)
 * Let me know if you have time to spare after this Wednesday -- got exams this week so I will be "studying". <span style="font-family:Helvetica Neue, Helvetica, san serif; color:#000000;">acagastya 💭 09:50, 16 September 2018 (UTC)
 * Looks like I can; just inform me when you're free. Leaderboard (discuss • contribs) 09:52, 16 September 2018 (UTC)

Recent edit to RFP page
I notice that you deleted Educator57's RFP. That's ... unusual. Sure it's too early, and I quite agree with denying the privilege (and not only because he has trouble with spelling simple words), but usual procedure is to use the Closed macro and leave the request up as closed for at least a little while before archiving. Any particular reason why you chose to simply remove it? Chazz (talk) 17:09, 23 September 2018 (UTC)


 * I did a double-take too, on the diff for that edit; but it wasn't deleted, just moved down to the bottom while being closed. --Pi zero (discuss • contribs) 18:40, 23 September 2018 (UTC)


 * Clearly I should learn to open my eyes a bit more. Nevermind. Chazz (talk) 19:39, 23 September 2018 (UTC)

Translating "The_implementation_of_E-Government" pages
Yes, I've translate my The_implementation_of_E-Government pages from ru.wikibooks and uk.wikibooks.

Danilka5469


 * Please see (for history-merge). Leaderboard (discuss • contribs) 05:23, 25 September 2018 (UTC)


 * Tell me please when I may start working on my "The implementation of E-Government" pages (also Administrative e-services of Ukraine). Danilka5469 (discuss)


 * You can continue working on your pages; QU will simply perform a history-merge on them - the page itself isn't modified. Leaderboard (discuss • contribs) 09:18, 25 September 2018 (UTC)

Reverting my edits err.. changing them on Wikijunior:Future?
I was changing the years to stay up with the years, on Wikijunior:Future. Why did you change it? It’s inaccurate by one year, we should update it ASAP. Educator57 (discuss • contribs) 09:50, 2 October 2018 (UTC)
 * Which one? I checked the wikibook and can't see any edit of yours which I reverted. Leaderboard (discuss • contribs) 09:45, 2 October 2018 (UTC)

The “Wikijunior:Future/10 years into the future” page I meant. Why did you change the dates back to 2017 and 2027? It’s already 2018, get out of 2017 cuz it’s already 2018. And also the 2027 date, update it! Educator57 (discuss • contribs) 09:50, 2 October 2018 (UTC)
 * I didn't do anything. I accidentally reverted Pi zero's edit and immediately corrected it. I didn't do any modification. You might want to check with User:Pi zero instead. Leaderboard (discuss • contribs) 09:54, 2 October 2018 (UTC)
 * Hi. I think I left a note on the book page's talk page.  The trouble is that the page is making predictions about what will happen in the future, but the prediction is based on projecting forward from the state of the world in (presumably) 2017 to the expected state of the world in 2027.  Those are not predictions of the state of things in 2028.  For example, I think the prediction about the size of computer storage media is based on expected exponential growth in the size of computer storage media; but then the prediction for 2018 would be larger than the prediction for 2017, and might also be modified a little if the growth from 2017 to 2018 turned out to be slightly different than expected.  This is an inherent problem with a book about the future that doesn't have a fixed date of publication, and while I think a book like that about the future is a cool thing to have, I feel we need to invent a strategy for how to handle the relationship between the date of predictions, the date on which they were predicted, and the inexorable march of time. --Pi zero (discuss • contribs) 13:40, 2 October 2018 (UTC)

Thanks
Thanks for appreciating my anti-vandalism edits! I have been intensively fighting vandalism lately and expand into projects where I was not so active before, and by using Huggle it's easy to identify where increased anti-vandalism is needed. Cheers and thanks, Dan Koehl (discuss • contribs) 14:25, 5 October 2018 (UTC)

Reversion of change made to "BASIC Programming/Beginning BASIC/PRINT, CLS, and END"
Hi Leaderboard. I made some changes "BASIC Programming/Beginning BASIC/PRINT, CLS, and END". I added some extra stuff that I thought would be good (GOSUB, LET, RETURN), but then saw that it was one page in a collection of pages making up a course. So I made another revision to remove the additions about that.

However, I also made some changes to that I thought brought clarity. I am a programmer/developer, and looking at your code confused me. It only makes sense after reading the following explanation paragraphs. My final change left those in. So my question is, why did you revert that part?


 * Taking another look at the changes, I found that the first of the three changes was a test edit (which you corrected). Your two edits did not seem to make sense at first glance (as I thought the page was as good as it should be), so I reverted all of the changes. I've however restored the page back to original - you did contribute positively to that page. Thank you for notifying me and I apologise for the unintentional error. Leaderboard (discuss • contribs) 15:43, 10 October 2018 (UTC)


 * Thanks!

Wondering about this
You'd sighted. Truthfully it looks like vandalism to me. Am I missing something? --Pi zero (discuss • contribs) 14:29, 31 October 2018 (UTC)
 * Sorry, I'm not sure what you mean. I don't recall reviewing that edit (and neither does the history). Leaderboard (discuss • contribs) 14:31, 31 October 2018 (UTC)
 * By now I'm kind of making a mountain out of a mole hill, but, in for a penny. Explanation:  I noticed this edit, which had been sighted, didn't look right.  I therefore "deprecated" it (un-sighted the revision), and rejected the edit.  It seemed only polite, and appropriately cautious, to check with the user who had sighted it about what I'd done.  The most likely explanation was always that the reviewer who sighted it just didn't notice the problem with the edit, a trivial little mistake of a sort that happens.  That you don't even remember it supports that theory.  As for the history, it's there but flaggedrevs make it remarkably difficult to find a review that's been deprecated like that; I found it by selecting the history tab for the page, clicking the unobtrusive link up at the top of the history display that says "View logs for this page", changing the dropdown menu at the top of that from "All public logs" to "Review log", and clicking the "Show" button.  Which finally produces . --Pi zero (discuss • contribs) 15:20, 31 October 2018 (UTC)
 * The history for that page does not mention my username anywhere (shouldn't it read "checked by ")? Leaderboard (discuss • contribs) 15:25, 31 October 2018 (UTC)
 * It would if I hadn't deprecated your review. Deprecating your review causes it to no longer appear on the history; then the only way to find a record of your review is to dig up the review log for the page, which I got to by that circuitous route described above. --Pi zero (discuss • contribs) 15:28, 31 October 2018 (UTC)
 * Fine; I admit defeat, though I still cannot recall reviewing that edit (let alone accept it). I apologise for that misreview. Leaderboard (discuss • contribs) 15:35, 31 October 2018 (UTC)

It is 'strange'
Not sure if you watch MCU movies, well, (you would get it only if you watched it) Just because you don't get it does not mean it is strange. (I really hope you respond by saying, "Well, who am I to judge?") Though I am not a doctor. <span style="font-family:Helvetica Neue, Helvetica, san serif; color:#000000;">acagastya 💭 20:29, 1 November 2018 (UTC)
 * While ideally I've responded at Darkfrog24's userpage, the fact is that (from what I have understood at least) your reasons for editing under an IP address isn't acceptable, especially considering that you are a significant contributor to Wikinews and that it gets needlessly confusing when you do not use your registered account. Leaderboard (discuss • contribs) 20:45, 1 November 2018 (UTC)
 * Okay, before it gets messy, tell me, do you really know why I do not log in sometimes? And give your justification for calling it "unacceptable". Defend it like how you would have defended your thesis. <span style="font-family:Helvetica Neue, Helvetica, san serif; color:#000000;">acagastya 💭 07:08, 2 November 2018 (UTC)
 * this one (2.3'- >not a smartphone -> no Wikinews; 20+ character password is your problem) and many more (I'm just can't remember where exactly I see it, but it's there). Obviously not going to defend my thesis, but the point stands. The problem is simple: you are a reviewer and hence you are virtually obliged to login as when you post opinions, users get confused as to whether there are two or one opinions. You have sock accounts; why not use one of your socks for "insecure" cases (if the reason for a long password is sheer security)? Leaderboard (discuss • contribs) 22:55, 2 November 2018 (UTC)
 * I don't think you quite understand enwn, policies, and the simple fact that, "reviewer or not, what is being said is more important than who is saying that. Weird that you chose to pick "opinions" when there were clear cases of complex issues being discussed. That is the problem that a lot many think, "Oh, it was said by someone with a rank, so must be valid. Guess what? It is not." Otherwise, one of the most important things like "separation of church and state", or equal rights for any group would not have been there. You might wonder why I went on to the real world while discussing this? On or off-wiki, do not listen to someone for their rank, but for what they present to you.
 * It came from a veteran wikinewsie, Brian McNeil: if there is something obviously wrong with an article, it does not need a reviewer to flag it. And that was said before I was a reviewer. So, per enwn's stance, any opinion or comments about any issue of any article or policy (anything which does not involves voting/endorsements) can come from anyone including anon. The question is: will the obvious issues of any article raised on the talk page would be less valid if a non-reviewer said that? If the same wordings for the raised issue were used by a reviewer, and if your stance changes, [your as in the editor's], that means you do not quite understand the dynamics. <span style="font-family:Helvetica Neue, Helvetica, san serif; color:#000000;">acagastya 💭 06:55, 3 November 2018 (UTC)
 * Pardon my dropping in. It is preferable that you log in, even if it's an alternative account.  Brian McNeil maintained an alternative account with lower privileges for exactly this purpose.  Although a user who isn't a reviewer can flag something wrong with an article, it is highly desirable to know, for certain, which user is doing that flagging.  It always matters who is doing things, because the whole project is geared toward gathering and publicizing each user's accumulated reputation (see n:Wikinews:Never assume).  Right now, we have a mess on Wikinews because someone who lacks understanding of the basic principles is going around making wrong statements about how Wikinews articles should be written and claiming (through sincere belief) to know what they're talking about. --Pi zero (discuss • contribs) 12:10, 3 November 2018 (UTC)

Pi, let me remind you, Brian McNeil said that when I was using college IP and not the account. Though "desirable", critical things are still welcomed to be raised by anyone. It is the content that matters. I do not need to login for raising NPOV issues. To follow or not, it is up to others. I am not going to change my worldview that what is being said is more important than the name of the deliverer. If I say, "Hey, do not put your finger in the socket, you would get an electrical shock", why would you respond: "Is that you, John?" No, regardless of the fact I am John Doe or not, see the stupidity you are doing. <span style="font-family:Helvetica Neue, Helvetica, san serif; color:#000000;">acagastya 💭 05:43, 4 November 2018 (UTC)
 * Preferably is worth keeping an eye on, though. If the discussion is being read by someone who doesn't understand the principles being addressed (such as a newcomer, but also someone who's having trouble understanding the principles), they can't necessarily tell whether the advice is from an experienced Wikinewsie or some random netizen.  Other considerations: continuity of identity helps in tracking a conversation (which has also been phrased as: not logging in can be confusing); and, a particularly important point, if you make comments when not logged in, someone looking back in the future to see your activity at that time will miss those comments.  That means you're undermining the accumulated-reputation principle on which Wikinews rests.  I have sympathy for the difficulties that may lead you to sometimes not log in to comment, but you in turn should be actively looking for a solution for those difficulties. --Pi zero (discuss • contribs) 13:09, 4 November 2018 (UTC)

Everything that you said, we have discussed this off-wiki previously. The problem is, Leaderboard jumped in between, and had a conclusion which they could not defend (or opted not to) even before they knew the entire thing. Just like how Pence was talking about evolution. 103.254.128.86 (discuss) 17:05, 4 November 2018 (UTC)
 * Pi zero's argument support (at least to some extent) my view on your IP editing. Leaderboard (discuss • contribs) 17:53, 4 November 2018 (UTC)
 * You have no stance, Leaderboard. You opted to be silent and could not defend a thing about your conclusions about things you don't know about. Pizero and I discussed most of this separately, in private, and what you see here is just few points from the long discussions we have for over a year. Don't pretend that some points matched, and I highly doubt you can list them, as most of them are debatable. Certain advantages that pi had over you is: they know the project in and out, has been there since my day zero, and I had discussed this with some users including pizero. Really, don't jump to conclusions about things that are completely alien to you. 103.254.128.86 (discuss) 16:38, 5 November 2018 (UTC)
 * My stance is clear - your IP editing isn't correct. If there is something which I don't know which could impact my opinion, then that's not my fault and I can only speak from what I know - and unless you give some evidence to the contrary - I will have to assume like that. I, however, do have sufficient evidence on wiki to prove my thoughts, and it's on you to show something to the contrary to me (and the other users whom you argue with on wiki regarding this). Leaderboard (discuss • contribs) 16:43, 5 November 2018 (UTC)

Editing News #2—2018
Read this in another language • Subscription list for this multilingual newsletter

Did you know?

Did you know that you can use the visual editor on a mobile device?

Tap on the pencil icon to start editing. The page will probably open in the wikitext editor.

You will see another pencil icon in the toolbar. Tap on that pencil icon to the switch between visual editing and wikitext editing.



Remember to publish your changes when you're done.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the Editing Team has wrapped up most of their work on the 2017 wikitext editor and the visual diff tool. The team has begun investigating the needs of editors who use mobile devices. Their work board is available in Phabricator. Their current priorities are fixing bugs and improving mobile editing.

Recent changes

 * The Editing team has published an initial report about mobile editing.
 * The Editing team has begun a design study of visual editing on the mobile website. New editors have trouble doing basic tasks on a smartphone, such as adding links to Wikipedia articles.  You can read the report.
 * The Reading team is working on a separate mobile-based contributions project.
 * The 2006 wikitext editor is no longer supported. If you used that toolbar, then you will no longer see any toolbar.  You may choose another editing tool in your editing preferences, local gadgets, or beta features.
 * The Editing team described the history and status of VisualEditor in this recorded public presentation (starting at 29 minutes, 30 seconds).
 * The Language team released a new version of Content Translation (CX2) last month, on International Translation Day. It integrates the visual editor to support templates, tables, and images. It also produces better wikitext when the translated article is published.

Let's work together

 * The Editing team wants to improve visual editing on the mobile website. Please read their ideas and tell the team what you think would help editors who use the mobile site.
 * The Community Wishlist Survey begins next week.
 * If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation.

—Whatamidoing (WMF) (talk) 14:15, 2 November 2018 (UTC)

Advice needed
Hi, my first page here, Wikijunior:World Heritage Sites/Botanic Gardens. Is it okay? Any suggestions or things I did wrong? Advice much appreciated!--Cohaf (discuss • contribs) 10:24, 27 December 2018 (UTC)
 * Hi, it's a pretty good start. My initial thoughts on this is that each sentence is independent on its own and do not 'connect' together; however, the articles on this topic largely follow that style. A map could also be included as outlined at the main page. Leaderboard (discuss • contribs) 10:55, 27 December 2018 (UTC)
 * Thanks for your prompt review and stylistic changes. Much appreciated as a newbie here. As of the sentences that are independent, yes I followed the general trend of articles in the series. Regarding a map, I'll try to get one and add in. Thanks for reviewing!--Cohaf (discuss • contribs) 12:17, 27 December 2018 (UTC)

Re-correction after copyvio?
Hello, You have detected a copyvio in . For my part, my intervention was only aesthetic: use of lowercase for common names, layout, grammar, etc. Following , could you tell me if I can do the same job again on the last healthy version, or if you saw something that bothered you?

Looking forward to reading you. Cordially. p.s: I never wrote that autoreview was reviewer. --Eihel (discuss • contribs) 21:25, 17 January 2019 (UTC)
 * Seems similar to the last discussion on your talkpage, could you comment. Thanks.--Cohaf (discuss • contribs) 01:25, 18 January 2019 (UTC)
 * Very long history. I believe this IP address is the same IP that has been causing disruption on the Vietnamese Wikibooks. This IP has had loads of problems, including incorrect Vietnamese language and other malice works on there. I know of this IP because I used to serve the Vietnamese Wikibooks project as an administrator for a couple of months. This person has migrated to Wikibooks and has continued his/her useless spam which provides no useful content to WB. Though I may be wrong and I might be confusing this IP with another IP. I only gave my opinion since I was asked to by Cohaf above, but check for Leaderboard's response, as I perceive it to be most accurate.--Atcovi (Talk - Contribs) 01:37, 18 January 2019 (UTC)
 * If this is the case and should the collateral being not large, a global block of some length may be considered, leaving to your experience to decide. Thanks for your input.--Cohaf (discuss • contribs) 01:55, 18 January 2019 (UTC)
 * This is multiple IPs were are discussing here - so a global block on the range MIGHT suffice, though I'm not completely positive. Atcovi (Talk - Contribs) 02:01, 18 January 2019 (UTC)
 * I am unaware of cross-wiki issues with that family of IP addresses (though if I recall correctly, there was a Vietnamese link between them). Rather, from what I am aware of, that family is a copyright-violating LTA that has repeatedly refused to engage into discussion (also see this discussion), and several IP addresses have been blocked for long periods with one being indef. Yes Eihel, you can modify the page on the last healthy version. Leaderboard (discuss • contribs) 06:18, 18 January 2019 (UTC)
 * I see, are the same range doing the same thing at Vietnamese Wikibooks. If yes we can apply for a global range block. Regards,--Cohaf (discuss • contribs) 06:26, 18 January 2019 (UTC)

+1 Ok for enWB and viWB. But there is also viWP in March 2017 for the same reasons. 3 wikis also seems to me a reason to abound in the sense of Cohaf. If every time he comes on Wikimedia, it's to be outside the rules, is not it better to let him know globally the rules? Cordially. --Eihel (discuss • contribs) 07:17, 18 January 2019 (UTC)
 * . To be honest, this is really a very good case for a global block already, however, can you or someone calculate the range, I admit although I'm a sysop elsewhere, I don't know how to calculate ranges. Global block needs 3 project disruption, so it fits the bill. That said, I don't know the collateral and if the range is busy, stewards may decline the request, but yes, this nonsense have to be stopped. --Cohaf (discuss • contribs) 07:35, 18 January 2019 (UTC)
 * 184.149.0.0/16 (rules: maximum /16). But what do others say? --Eihel (discuss • contribs) 07:53, 18 January 2019 (UTC)
 * I don't know, but that copyright sock has been operating from multiple ranges (select only IP blocks). By the way, /16 is pretty harsh in any case. Leaderboard (discuss • contribs) 08:00, 18 January 2019 (UTC)
 * Whois: Bell Canada, another CIDR: 184.149.29.0/24. It is you who speak of range, we can ask the blocking of the IP only. Global blocking may include ranges. You show blockages on WB only. Needless to say, I have never seen blocked address ranges on a specific chapter or project. Even if the user uses a dynamic IP, we can see that it doesn't change a lot for 2 and a half years. And you, what do you think? If you are not busy --Eihel (discuss • contribs) 08:08, 18 January 2019 (UTC)
 * If the IP does not change that often and it isn't a significant nuisance to the project, then I don't think we need to go to far measures like this to take care of the problem. Simply reverting the IP's edits and blocking the copyright vandal should be enough. From the looks of it, if your statement seems to be factual ("we can see that it doesn't change a lot for 2 and a half years"), then there is really no need to dwell in much about this case (unless, of course, I'm misunderstanding something) . --Atcovi (Talk - Contribs) 11:25, 18 January 2019 (UTC)

Math problem on Facebook
There was a math equation of

3+3x3+3.

The answers were multiple choice.

21, 36, or 15.

The question is: even with no parenthesis you should always do the multiplication first. Which would make the answer 15.

Thanks. Njjohns (discuss • contribs) 00:30, 14 March 2019 (UTC)
 * I think you've answered your own question... Leaderboard (discuss • contribs) 00:41, 14 March 2019 (UTC)

Thanks, and existing "pending changes"
Hi, Thanks for adding me to "autoreviewed users". That is very handy. However, some of the pages I am working on in the book are still marked with "Pending Changes" as I made changes prior to being an "autoreviewed user" e.g. the first page of the book as well as other pages. How do I get all the past changes on all pages of the book to be accepted?... its quite annoying to have them as pending changes. Thanks again, Theo --Theo Hughes (discuss • contribs) 05:51, 19 March 2019 (UTC)
 * I've applied my discretion as an administrator and raised your permission to reviewer. This will allow you to review all pages yourself. Please read WB:REVIEW before reviewing. Good luck. Leaderboard (discuss • contribs) 06:41, 19 March 2019 (UTC)
 * Thanks! At the moment I just want to be able to sort out the book I have started. However, into the future I hope I might be of more use across wikibooks.
 * Ooopps forgot to sign --Theo Hughes (discuss • contribs) 04:33, 23 March 2019 (UTC)

WikiSource Copy Clarification
Hello: I noticed you deleted my sandbox page and my US Constitution transcript. Yes, the Wikisource page is the same (as far as actual content goes), but no, I did not copy and paste. This should clarify. I wrote the document in a notebook when I visited the Constitution Center and today I felt I should type it and share it on Wikibooks. I double-checked it to a government website then published it to an article. Thanks, TypicallyTrue

TypicallyTrue (discuss • contribs) 17:49, 29 March 2019 (UTC)
 * Are you trying to say that you typed a whole country's constitution? Thanks. Leaderboard (discuss • contribs) 17:51, 29 March 2019 (UTC)
 * I could have as the US constitution isn't that long. More accurately, I scanned it and used handwriting recognition software, control-c, control-v, double checked to the archives.gov version.  But yes, I did write it down -- TypicallyTrue (discuss • contribs) 17:56, 29 March 2019 (UTC)
 * ✅. Sorry for the miss-assessment on my part. By the way, you can move your sandbox to your main article. Leaderboard (discuss • contribs) 18:00, 29 March 2019 (UTC)
 * No problem, thanks -- TypicallyTrue (discuss • contribs) 18:01, 29 March 2019 (UTC)

Thank You For Your Hep!
Hi Leaderboard I just wanted to say thanks for giving me the basics of what Wikibooks is and supplying me with necessary advice on the project. Much appreciated!

Thank you
Thanks for blocking User:Bunadea1. Note that User:Vandaopal is in fact the same user - it's a long-term serial troll who has started branching out from en.wiki. His original username is Nsmutte, and the back-and-forth reverting using different socks is one of his trademark behaviours. --Bonadea (discuss • contribs) 10:12, 28 April 2019 (UTC)

Action on User:Bonadea, thanq for block User:Bunadea1
If want to remove content from wiki...have to discuss the matter with admin or on talk page.

These two editors disturbs the board a lot

(Vandaopal (discuss • contribs) 10:21, 28 April 2019 (UTC)).


 * Please dont under estimate new user.If you are a check user...you never block..

Please verify my ip from japan,

Bunadea1 edited from ip 183.83.119.214 (please verify edit of talk page admin)

Please come to conclusion .Bunadea1 forgot to login and edited once admins talk page

Please verify my edits...I posted edits.I didnt rever any one. Because of confusion and mis understand you blocked me.

Please encourage new editors

Main points:

Thanq
 * Appeal on your talk page. Leaderboard (discuss • contribs) 11:09, 28 April 2019 (UTC)


 * I was appealed to my talk page.But some one reverted. I am from Japan.Please verify my ip.

User:Bonadea and User:Bunadea are same.These two users from India.

Please unblock me 60.151.2.17 (discuss) 17:01, 28 April 2019 (UTC)

Main points:

Main points:

I edit from my mobile. The Bonadea persons edit from computer

I didnt revert.

I am new to your wiki. But well experienced editor in other wiki.

I edit from Japan. Please check my ip location

Bunadea1 from India

I dont want to create new account,if i do like that...i wl be a sock...I dont like.You never recognize my new user name.

Please encourage a new editor

css
What is Meta:User:Leaderboard/global.css? --Pi zero (discuss • contribs) 18:37, 5 May 2019 (UTC)
 * It is a simple CSS script which creates the feel of threading (usually in discussion pages), and works mainly using indents . You can try it by importing it to your userpage CSS. Leaderboard (discuss • contribs) 19:20, 5 May 2019 (UTC)

Transportation Deployment Casebook
It looks to me as if  intended to create a new chapter for the book, but instead overwrote the book main page. You had done some copyedits and sighted it all, and I was quite perplexed, looking at the resulting situation, till the theory it was meant as a new chapter occurred to me. I'm going to contact  about it. If you think I've misjudged the situation, give a holler. --Pi zero (discuss • contribs) 23:40, 13 May 2019 (UTC)
 * (Oh, to clarify: I split the edit history in two, moving  's material to Transportation Deployment Casebook/Aircraft, which is just a guess at what to call it.) --Pi zero (discuss • contribs) 23:43, 13 May 2019 (UTC)
 * It's possible either way. I might have not realised that page was a chapter and mistakenly thought that the aircraft page was the index page of the book; not sure really. Leaderboard (discuss • contribs) 08:51, 14 May 2019 (UTC)

MediaWiki:Pagecategories
I'm thinking about undeleting this, since we did have customizations in some othe namespaces. Have you any thoughts/objections? --Pi zero (discuss • contribs) 17:58, 7 June 2019 (UTC)
 * No, I only did that as your edit simply replaced the text with "Categories", which is pretty much the default text. Leaderboard (discuss • contribs) 18:07, 7 June 2019 (UTC)
 * Ah, okay. I'm still thinking...  Likely the customizations for other namespaces would never have occurred to anyone to do if they hadn't already been tinkering with that page because of the "Subject"/"Subjects" thing; but since they had done that other tinkering... --Pi zero (discuss • contribs) 18:21, 7 June 2019 (UTC)

Dear Leaderboard, How do I start my wikibook ? Do I use my sandbox ?
Hello Leaderboard,

I am interested in starting a wikibook, but I don't know where to start, can you explain to me where do I write my chapters ? What is acceptable when writing a wikibook ? I will be including citations from textbooks, can the work be half fictional and half non-fiction ? Most of my work is of non-fiction ? Will it be deleted ? How can I get my work to be reviewed ? How can my work become a Wikipedia wikibook without being deleted ?

Thank-you for your assistance, --Sutton Publishing (discuss • contribs) 13:31, 8 June 2019 (UTC)
 * Hi, please see the welcome guide that User:Pi zero has put in your talk page. (P.S: you might want to change your username as it implies a commercial entity and will be blocked on sites like Wikipedia) Leaderboard (discuss • contribs) 08:34, 9 June 2019 (UTC)

Editing News #1—July 2019
Read this in another language • Subscription list for this multilingual newsletter

Did you know?

Did you know that you can use the visual editor on a mobile device?

Every article has a pencil icon at the top. Tap on the pencil icon to start editing.

 Edit Cards 



This is what the new Edit Cards for editing links in the mobile visual editor look like. You can try the prototype here: 📲 Try Edit Cards.

Welcome back to the Editing newsletter.

Since the last newsletter, the team has released two new features for the mobile visual editor and has started developing three more. All of this work is part of the team's goal to make editing on mobile web simpler.

Before talking about the team's recent releases, we have a question for you:

Are you willing to try a new way to add and change links?

If you are interested, we would value your input! You can try this new link tool in the mobile visual editor on a separate wiki.

Follow these instructions and share your experience:

📲 Try Edit Cards.

Recent releases
The mobile visual editor is a simpler editing tool, for smartphones and tablets using the mobile site. The Editing team recently launched two new features to improve the mobile visual editor:


 * 1) Section editing
 * 2) * The purpose is to help contributors focus on their edits.
 * 3) * The team studied this with an A/B test. This test showed that contributors who could use section editing were 1% more likely to publish the edits they started than people with only full-page editing.
 * 4) Loading overlay
 * 5) * The purpose is to smooth the transition between reading and editing.

Section editing and the new loading overlay are now available to everyone using the mobile visual editor.

New and active projects
This is a list of our most active projects. Watch these pages to learn about project updates and to share your input on new designs, prototypes and research findings.


 * Edit cards: This is a clearer way to add and edit links, citations, images, templates, etc. in articles. You can try this feature now.  Go here to see how: 📲 Try Edit Cards.
 * Mobile toolbar refresh: This project will learn if contributors are more successful when the editing tools are easier to recognize.
 * Mobile visual editor availability: This A/B test asks: Are newer contributors more successful if they use the mobile visual editor?  We are collaborating with 20 Wikipedias to answer this question.
 * Usability improvements: This project will make the mobile visual editor easier to use. The goal is to let contributors stay focused on editing and to feel more confident in the editing tools.

Looking ahead

 * Wikimania: Several members of the Editing Team will be attending Wikimania in August 2019.  They will lead a session about mobile editing in the Community Growth space.  Talk to the team about how editing can be improved.
 * Talk Pages: In the coming months, the Editing Team will begin improving talk pages and communication on the wikis.

Learning more
The VisualEditor on mobile is a good place to learn more about the projects we are working on. The team wants to talk with you about anything related to editing. If you have something to say or ask, please leave a message at Talk:VisualEditor on mobile.

PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk) 18:33, 23 July 2019 (UTC)