User talk:PokestarFan/Archive 7
 | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
| Archive 1 | ← | Archive 5 | Archive 6 | Archive 7 |
In addition to the problems of the day, please be aware of our policies in Wikibooks:Bots: Bots may be used provided they work as expected, do not interfere with or reduce people's ability to contribute meaningful content to Wikibooks, and do not perform any controversial actions or violate policies. Bots which break these basic principles may be blocked without warning.
This would be a reason to block your user account (and this too). Imagine that it had been your book where you had spent one week of your expertise, it's totally unacceptable because your bot has been refused because it had too many bugs and you have persisted to launch it with your user account. So this is my last friendly warning before blocking any account used by your buggy bot (unless it's in your user space). JackPotte (discuss • contribs) 21:28, 20 August 2017 (UTC)
Besides, this is not serious to welcome new users by saying possibly contact me personally without any signature. JackPotte (discuss • contribs) 08:00, 24 August 2017 (UTC)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
- You can now test the new Timeless skin on the test wiki and mediawiki.org. You can turn it on in your preferences. You can report bugs in Phabricator. It will come to more wikis soon. [1][2]
- Your watchlist can now have the option to unwatch pages. You have to turn this on in your preferences. [3]
- If a table has several columns you can often choose which column you want to use to sort the table. This has not worked for some columns for readers who have used Firefox or Safari. This has now been fixed. [4]
- The RelatedArticles extension has shown related pages on Wikivoyages. You will now see the related pages at the end of the article together with an image. Previously the links were in the sidebar. Wikis that want this extension can request it on Phabricator.
Changes later this week
- Videos will now be played in the WebM format in all browsers. Previously some browsers used Ogg Theora (.ogv). If you use Safari, Internet Explorer or Edge you may see slower playback speed at high resolutions. Instead we will get better quality and smaller file size. You can still upload video as Ogg files. They are automatically converted to WebM. This doesn't affect Ogg audio files. [5]
- The default font in the edit window will change for some users this week. Instead of using the browser default, it will be monospace. Users can change this in their preferences. This should only change this for some users on Macs and iOS devices. [6]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 22 August. It will be on non-Wikipedia wikis and some Wikipedias from 23 August. It will be on all wikis from 24 August (calendar).
Meetings
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 23 August at 15:00 (UTC). See how to join.- You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 22 August at 19:00 (UTC). See how to join.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
18:00, 21 August 2017 (UTC)
Speedy deletion nomination of "User:PokestarFanBot/patrol_whitelist"
User:PokestarFanBot/patrol_whitelist, a page you created, has been tagged for deletion, as it meets one or more of the criteria for speedy deletion; specifically, you removed all content from the page or otherwise requested its deletion.
You are welcome to contribute content that complies with our content policies and any applicable inclusion guidelines. However, please do not simply re-create the page with the same content, or remove the speedy deletion tag from the page. You can contest the deletion by clicking the "Contest this speedy deletion" button inside the speedy deletion tag. You may also wish to read our introduction to editing and guide to writing your first article.
Thank you. PokestarFan • Talk • Contributions 19:40, 23 August 2017 (UTC),
Speedy deletion nomination of "User:PokestarFanBot/possible_vandalisim_archivelist"
User:PokestarFanBot/possible_vandalisim_archivelist, a page you created, has been tagged for deletion, as it meets one or more of the criteria for speedy deletion; specifically, you removed all content from the page or otherwise requested its deletion.
You are welcome to contribute content that complies with our content policies and any applicable inclusion guidelines. However, please do not simply re-create the page with the same content, or remove the speedy deletion tag from the page. You can contest the deletion by clicking the "Contest this speedy deletion" button inside the speedy deletion tag. You may also wish to read our introduction to editing and guide to writing your first article.
Thank you. PokestarFan • Talk • Contributions 19:40, 23 August 2017 (UTC),
Speedy deletion nomination of "User:PokestarFanBot/possible_vandalisim/archivelist"
User:PokestarFanBot/possible_vandalisim/archivelist, a page you created, has been tagged for deletion, as it meets one or more of the criteria for speedy deletion; specifically, you removed all content from the page or otherwise requested its deletion.
You are welcome to contribute content that complies with our content policies and any applicable inclusion guidelines. However, please do not simply re-create the page with the same content, or remove the speedy deletion tag from the page. You can contest the deletion by clicking the "Contest this speedy deletion" button inside the speedy deletion tag. You may also wish to read our introduction to editing and guide to writing your first article.
Thank you. PokestarFan • Talk • Contributions 19:48, 23 August 2017 (UTC),
Speedy deletion nomination of "Template:Bot code"
Template:Bot code, a page you created, has been tagged for deletion, as it meets one or more of the criteria for speedy deletion; specifically, you removed all content from the page or otherwise requested its deletion.
You are welcome to contribute content that complies with our content policies and any applicable inclusion guidelines. However, please do not simply re-create the page with the same content, or remove the speedy deletion tag from the page. You can contest the deletion by clicking the "Contest this speedy deletion" button inside the speedy deletion tag. You may also wish to read our introduction to editing and guide to writing your first article.
Thank you. PokestarFan • Talk • Contributions 19:49, 23 August 2017 (UTC),
Hi,
Sophie Cheng is owned by a colleague of mine. Eliarani (discuss • contribs) 15:58, 24 August 2017 (UTC)
Learning Quarterly: August 2017
L&E Newsletter / Volume 4 / Issue 13 / August 2017
Learning Quarterly
Frontpage:
#NewVoices
#MovementStrategy
Stay tuned
blogs, events
& more!
Leave your mark on Meta!
Inspiring ideas and learning patterns you can contribute to.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
- Syntax highlighting is now a beta feature on Wikimedia wikis with text written from left to right. It will come to right-to-left wikis later. This beta feature is based on CodeMirror. [7][8]
- You will now get a notification when someone tries to log in to your account and fails. If they try from a device or IP address that have logged in to your account before you will be notified after five failed attempts. You can turn this off or choose to get an email notification in your preferences. You can also turn on to get an email when someone logs in to your account from a new device or IP address. [9]
Problems
- Some pages show the error
Lua error in mw.wikibase.entity.lua at line 34: The entity data must be a table obtained via mw.wikibase.getEntityObject. This problem happens on pages with a Lua module that use Wikidata. This has now been fixed and no new pages will get this problem. You still need to fix pages that were broken before and still show the error message. You can see how on this page. [10]
Changes later this week
- You can block users from sending you notifications. [11]
- The new version of MediaWiki will be on test wikis and MediaWiki.org from 29 August. It will be on non-Wikipedia wikis and some Wikipedias from 30 August. It will be on all wikis from 31 August (calendar).
Meetings
- You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 29 August at 19:00 (UTC). See how to join.
- You can join the next meeting with the Technical Committee. The topic this week is Migrate to HTML5 section ids. The meeting will be on 30 August at 21:00 (UTC). See how to join.
Future changes
- In the future you will have global preferences. This means you could set something in your preferences to work in the same way on all wikis. You will not be forced to use global preferences. The developers are now asking if editors need exceptions. This is where you want to use global settings on almost all wikis, but have some wikis where you want it to work in a different way. If you want this you need to tell the developers now. You can do so on the talk page. [12]
- New filters for edit review is a beta feature to improve recent changes pages. It will work on watchlists from 5 September. [13]
- The jQuery library will be upgraded to version 3 in September 2017. Wikis can ask on Phabricator to get it early, so they can help find and solve problems now.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
22:09, 28 August 2017 (UTC)
Nieuwsbrief 64 Wikikimedia Nederland
|
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Tech News
- We are asking Tech News readers five questions to make the newsletter better. You can answer the questions here. We are grateful for every reply we get.
Recent changes
- The RevisionSlider user interface has changed. You can now select revisions by clicking on the bars. You can move the blue knob past the yellow one and the yellow one will move along, and the other way around. [14][15]
Problems
- Some users have problems loading very large watchlists. It is working better than earlier but the problem has not been solved. The developers are working on fixing it. Until it has been fixed you can turn on "Expand watchlist to show all changes, not just the most recent" in your preferences and see if it helps. [16]
Changes later this week
- New filters for edit review is a beta feature to improve recent changes pages. It will work on watchlists from 5 September. [17]
- The new version of MediaWiki will be on test wikis and MediaWiki.org from 5 September. It will be on non-Wikipedia wikis and some Wikipedias from 6 September. It will be on all wikis from 7 September (calendar).
Meetings
- You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 5 September at 19:00 (UTC). See how to join.
- You can see a presentation about and discuss the new Technical Committee on 5 September at 17:30 (UTC). There will be a presentation on YouTube and a discussion in
#wikimedia-officeon Freenode. You can use the web chat. [18]
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
22:14, 4 September 2017 (UTC)
The Signpost: 6 September 2017
- From the editors: What happened at Wikimania?
- News and notes: Basselpedia; WMF Board of Trustees appointments
- Featured content: Warfighters and their tools or trees and butterflies
- Traffic report: A fortnight of conflicts
- Special report: Biomedical content, and some thoughts on its future
- Recent research: Discussion summarization; Twitter bots tracking government edits; extracting trivia from Wikipedia
- WikiProject report: WikiProject YouTube
- Technology report: Latest tech news
- Wikicup: 2017 WikiCup round 4 wrap-up
- Humour: Bots
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
- You can get a notification when a page you created is connected to a Wikidata item. You can choose to get these notifications in your preferences. Some wikis already had this option. It is now available on all wikis. [19]
- The Newsletter extension is now on mediawiki.org. The newsletter extension is for newsletters where you can subscribe by getting a notification when a new issue has been published. It will come to more wikis later. [20]
- The Linter extension helps you find technical errors in articles. There is now a new high-priority category:
tidy-whitespace-bug. This usually affects templates with horizontal lists. You can read more about using Linter and the Tidy whitespace bug. [21]
Problems
- Tech News 2017/36 reported about new filters for edit review coming to watchlists. This was planned to happen last week. It will happen next week instead. [22]
Changes later this week
- The new version of MediaWiki will be on test wikis and MediaWiki.org from 12 September. It will be on non-Wikipedia wikis and some Wikipedias from 13 September. It will be on all wikis from 14 September (calendar).
- OOjs UI will be updated. This could affect some icons. You can read more about the changes.
Meetings
- You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 13 September at 15:00 (UTC). See how to join.
- You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 12 September at 19:00 (UTC). See how to join.
Future changes
- You can't use OCG to create PDFs after 1 October. This is because of technical problems. You can use Electron instead. Most PDFs are already created with Electron. Electron will get missing features before 1 October. You can create books but they will not have all planned features until November or December. You can read more on mediawiki.org.
- New filters for edit review are available now on recent changes as a beta feature. Some of those filters and other features will be deployed as default features in the coming weeks. Users will be able to opt out in their preferences. [23]
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
19:15, 11 September 2017 (UTC)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
- You can now see contributions from an IP range at Special:Contributions. Before you could only see contributions from single IP addresses. Some older contributions from IP ranges could be missing at first because it will take some time to add them. [24][25]
- Flow has been re-scoped to become Structured Discussions and the development has restarted. Phabricator projects and repositories have been renamed. [26]
Changes later this week
- The new version of MediaWiki will be on test wikis and MediaWiki.org from 19 September. It will be on non-Wikipedia wikis and some Wikipedias from 20 September. It will be on all wikis from 21 September (calendar).
Meetings
- You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 19 September at 18:30 (UTC). See how to join.
- You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 20 September at 15:00 (UTC). See how to join.
Future changes
- We are replacing Tidy on Wikimedia wikis. Editors need to fix pages that could break. You can read the simplified instructions for editors. Some wikis have already switched. If your wiki would like to switch to the new format now, you can file a task.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
15:31, 18 September 2017 (UTC)
English-Hanzi
I suddenly realized I didn't recall what had happened with the RFD on this, so I went back to investigate, and it looks as if you marked it closed, with an assertion that some pages were deleted but most were kept, and then you archived the whole thing. However, you aren't an admit and do not have the power to delete anything, furthermore I'm not convinced this was really a solid interpretation of consensus. I also see that you didn't take care of the other administrative tasks associated with closure — the book still has the RFD notice on it, and there is nothing on the book's talk page about an outcome.
So it looks to me as if you didn't have the ability to entirely implement the closure, didn't do all the things you were able to do, and made a dodgy call in "closing" it. Non-admins shouldn't be closing RFDs when the outcome is controversial, nor should they do so when the outcome involves deleting anything since they don't have the power to do that themselves (and the community hasn't designated them as someone who can make the call to do so), and RFDs shouldn't be closed without doing the associated cleanup.
That's what it looks like. I'd really like to hear your side of this.
I'm thinking it's probably not appropriate for you to close any RFD; one of your particular weaknesses is in making consistently solid judgement calls, and closing an RFD demands making very sound judgement calls. --Pi zero (discuss • contribs) 05:53, 22 September 2017 (UTC)
- @Pi zero: I usually wait one or two weeks, and then decide based on the votes. PokestarFan • Talk • Contributions 18:51, 22 September 2017 (UTC)
- I'm going to need to agree with Pi zero here and I should have caught this earlier myself. Please do not close any additonal RFD or RFP's. --Az1568 (discuss • contribs) 18:57, 22 September 2017 (UTC)
- Ok then. It just seems like they are never closed. PokestarFan • Talk • Contributions 18:58, 22 September 2017 (UTC)
- I'm going to need to agree with Pi zero here and I should have caught this earlier myself. Please do not close any additonal RFD or RFP's. --Az1568 (discuss • contribs) 18:57, 22 September 2017 (UTC)
The Signpost: 25 September 2017
- News and notes: Chapter updates; ACTRIAL
- Humour: Chickenz
- Recent research: Wikipedia articles vs. concepts; Wikipedia usage in Europe
- Technology report: Flow restarted; Wikidata connection notifications
- Gallery: Chicken mania
- Traffic report: Fights and frights
- Featured content: Flying high
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
- Wikitext syntax highlighting is a beta feature on Wikimedia wikis with text written from left to right. This beta feature is based on CodeMirror. You can now search through the entire article with
CTRL+Forcmd+Fwhen you edit. Before it just searched through a part of the article. The developers are also fixing a couple of other bugs. [27][28] - Administrators on wikis that use Structured Discussions as a beta feature or by default can now create and move Structured Discussions boards. Structured Discussions was previously called Flow. [29]
Changes later this week
- You now get a notification when someone tries to log in to your account and fails. If they try from a device or IP address that have logged in to your account before you will be notified after five failed attempts. For security reasons you will soon get an email by default when someone tries to log in to your account and when someone logs in to your account from a new device or IP address. This can be turned off in your preferences. [30]
- Users with extremely old browsers (for example Netscape 2–4, released from 1995–1997) which do not support Unicode will no longer be able to edit. They should try to install a new browser. [31]
- The new version of MediaWiki will be on test wikis and MediaWiki.org from 26 September. It will be on non-Wikipedia wikis and some Wikipedias from 27 September. It will be on all wikis from 28 September. (calendar).
Meetings
- You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 27 September at 15:00 (UTC). See how to join.
Future changes
- The Wikimedia Foundation Readers department has proposed changing the mobile website. You can read more on mediawiki.org. This would be a big change.
- You can't use OCG to create PDFs after 1 October. This is because of technical problems. You can still create PDFs. Tech News 2017/37 said the function to create PDFs from books would still work. It is now clear it will not work for the next few months. The developers are working on fixing this. You can read more on mediawiki.org.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
15:59, 25 September 2017 (UTC)
Book categories
Moving book categories from the old naming scheme to the new one is a tricky operation, requiring human attention to all manner of complications that may arise. Doing those by bot is likely to create a mess that may be harder to clean up than the whole operation would have been to do without the bot. --Pi zero (discuss • contribs) 03:31, 25 September 2017 (UTC) 
- @Pi zero: What about semi automatically moving them, such as having the texts pop up on page? PokestarFan • Talk • Contributions 19:18, 25 September 2017 (UTC)
- I'm not sure what you're proposing. --Pi zero (discuss • contribs) 02:31, 26 September 2017 (UTC)
- You can see what I did to process the ones the bot had moved (well, you can see what I did beyond the many null-edits, which don't show up as edits). --Pi zero (discuss • contribs) 14:58, 28 September 2017 (UTC)
Nieuwsbrief 65 Wikimedia Nederland
|
This Month in Education: September 2017
Volume 6 | Issue 8 | September 2017
This monthly newsletter showcases the Wikipedia Education Program. It focuses on sharing: your ideas, stories, success and challenges. You can see past editions here. You can also volunteer to help publish the newsletter. Join the team! Finally, don't forget to subscribe!
In This Issue
| Featured Topic | "Wikipedia – Here and Now": 40 students in the Summer School "I Can – Here and Now" in Bulgaria heard more about Wikipedia | |
|
| ||
| From the Community | ||
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
- You can now use preload features in the visual editor. This means you can create links to create new pages and some text will already be in the edit window when someone clicks on it. [32]
Changes later this week
- If you have turned on "Automatically enable most beta features" you will now get the 2017 wikitext editor. Before this you had to turn it on manually even though it is a beta feature. [33]
- Special:Block and Special:Unblock will get the OOUI look. [34]
- The jQuery library will be upgraded to version 3 on all Wiktionary wikis from 2 October. It will be on all non-Wikipedia wikis from 4 October. It will be on all wikis from 5 October. [35]
- The new version of MediaWiki will be on test wikis and MediaWiki.org from 3 October. It will be on non-Wikipedia wikis and some Wikipedias from 4 October. It will be on all wikis from 5 October (calendar).
Meetings
- You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 3 October at 19:00 (UTC). See how to join.
- You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 4 October at 15:00 (UTC). See how to join.
Future changes
- A new feature called Reading Lists are coming to the Wikipedia mobile apps. First it will be in the Android version. Reading Lists are a private user preference where you can see lists of articles on multiple devices. You can give feedback on this feature. [36]
- The search function has used fallback languages for language analysis. This means a language could be analysed with the grammar of a completely unrelated language to find related words. This will be removed from most wikis the week starting with 9 October. You can read more and give feedback.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
23:25, 2 October 2017 (UTC)
Book categories
I see you've moved a large number of book categories from old naming convention to new. Did you do the other things that need to be done as each one is moved? If not, moving the categories alone could cause the task of moving to the new conventions to take much longer, and more more work, than it would otherwise have done, and would also mean that all of those categories would lack the contents they should have for all the book you've moved until somebody fixes them — thus rendering all of those categories largely useless to Wikibooks users until somebody fixes them. Those being the reasons we have been moving them only a few at a time. I had already anticipated that the migration to the new naming scheme would take another six to nine months. --Pi zero (discuss • contribs) 11:58, 7 October 2017 (UTC)
- @Pi zero: So what you're saying is that I should check each page in a cat is not using BookCat and/or making null edits? Like if a book page contains
[[Category:BOOKNAME]]we should remove them? I can make a script to do that, if you give me some time. PokestarFan • Talk • Contributions 12:04, 7 October 2017 (UTC)- I'm not altogether in favor of scripts, truthfully. For the advanced stuff (like this) it's not possible to contain in an algorithm what needs to be done, exactly because what needs to be done is to look at each individual situation, with understanding of the big picture of Wikibooks infrastructure, and see what wants doing. Often there are templates that want renaming, often in irregular ways requiring thought, and various customized structural changes to the templates' categorization and sometimes their functionality as well. Subcategories also need moving. Sometimes category structure needs to be completely rethought (not automatable at all). Each category moved needs to be checked for incoming links, and they have to be dealt with in various ways often requiring deep thought. And, well, other stuff comes up in particular cases that cannot be predicted ahead of time (and thus cannot be automated). And of course eventually an admin should make sure that there is no category redirect left behind after everything has been done — either by the admin moving each category individually without leaving a redirect (so the admin can manually check everything immediately, before moving on to the next one) or by the admin checking everything carefully before deleting the redirect left behind by a non-admin move (but if some well-meaning admin should come along and delete one of those redirects without doing the checks, we could easily end up leaving a bunch of messed up infrastructure that nobody knows is there, thus creating a vast mess that would linger about the project degrading its quality more-or-less permanently).
All of which is why we've spend the past four months doing them manually, one at a time, and expected to spend about twice that much additional time doing the remaining ones. Not everything can be automated without large-scale damage to the project. --Pi zero (discuss • contribs) 12:28, 7 October 2017 (UTC)
- I'm not altogether in favor of scripts, truthfully. For the advanced stuff (like this) it's not possible to contain in an algorithm what needs to be done, exactly because what needs to be done is to look at each individual situation, with understanding of the big picture of Wikibooks infrastructure, and see what wants doing. Often there are templates that want renaming, often in irregular ways requiring thought, and various customized structural changes to the templates' categorization and sometimes their functionality as well. Subcategories also need moving. Sometimes category structure needs to be completely rethought (not automatable at all). Each category moved needs to be checked for incoming links, and they have to be dealt with in various ways often requiring deep thought. And, well, other stuff comes up in particular cases that cannot be predicted ahead of time (and thus cannot be automated). And of course eventually an admin should make sure that there is no category redirect left behind after everything has been done — either by the admin moving each category individually without leaving a redirect (so the admin can manually check everything immediately, before moving on to the next one) or by the admin checking everything carefully before deleting the redirect left behind by a non-admin move (but if some well-meaning admin should come along and delete one of those redirects without doing the checks, we could easily end up leaving a bunch of messed up infrastructure that nobody knows is there, thus creating a vast mess that would linger about the project degrading its quality more-or-less permanently).
- Unfortunately, the problems reported below by Efex3 are a small part of what I mean: similar problems will have occurred with all of the hundreds of categories that were moved. Even if we can keep track of them all in the mean time, it'd be next spring or summer before we could fix all the problems caused by prematurely moving all those categories. Only, it'd probably take even longer than that, because the project is no longer a simple operation; it's considerably messier, and rather than feeling like a "move these categories one-at-a-time" task it feels like a "check each one of these to clean up the mess" task, which is psychologically less attractive. That large-scale move should not have been done. I admit to some frustration because I did warn you not to do this, when you moved a bunch of them a while ago. I'm guessing you did use automation for this, despite being warned about that too. The problem with your bot isn't just the bot, it's that you, the operator, don't exercise nearly as much caution as you should before applying it. --Pi zero (discuss • contribs) 12:47, 7 October 2017 (UTC)
- By the way, this damaging mass move cannot be undone by a non-admin moving the pages page to their old names, because the redirect left behind will trash the behavior of the automation that was put in place to allow the naming-scheme transition to be performed smoothly. The only way to reverse the damage is for an admin to go through renaming the categories back to the old names without leaving a redirect — and checking each one manually to make sure some pages didn't get left behind under the new name. --Pi zero (discuss • contribs) 12:51, 7 October 2017 (UTC)
Problems happened after pages moved
Could you help to fix the problems of the following pages: [37] [38] [39] [40]--Efex3 (discuss • contribs) 12:31, 7 October 2017 (UTC)
Problems with the requests for deletion closures
I've just noticed that Category:Requests for deletion was still containing some pages whose requests had been closed by you, eg: Wikibooks:Requests for deletion/K-Means++. So please stop closing the votes without applying them, because we can't treat them as usual in this case. JackPotte (discuss • contribs) 22:41, 7 October 2017 (UTC)
- @JackPotte: I've stopped. PokestarFan • Talk • Contributions 20:14, 8 October 2017 (UTC)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
- The number of active users listed by
{{NUMBEROFACTIVEUSERS}}and on Special:Statistics will now only include Wikidata edits as activity on Wikidata and not on other wikis too. [41] - Previously you could create wiki links starting with two colons. Now you need to use one colon. [[::File:X.jpg]] now has to be [[:File:X.jpg]]. There is now a new Linter category. You can see a list on Special:Linterrors/multi-colon-escape. The Linter extension helps you find technical errors in articles. You can read more about using Linter. [42]
Problems
- You will not be able to edit or upload files to Commons for around 30 minutes on 11 October. This will start at 06:00 UTC. This is because of work to let Commons show 3D models. [43]
Changes later this week
- The font in the edit window is monospace by default. Today you can change preferences to another font family or use "the browser default" instead of monospace. Switching to the browser default has only changed the font on Macs. The option to use browser default will be removed this week. [44]
- If you want to print a page or make a PDF of a page you can do so in the side menu. The way the pages look when you do this will change. You can read more on mediawiki.org.
- The new version of MediaWiki will be on test wikis and MediaWiki.org from 10 October. It will be on non-Wikipedia wikis and some Wikipedias from 11 October. It will be on all wikis from 12 October (calendar).
Meetings
- You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 10 October at 19:00 (UTC). See how to join.
- You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 11 October at 15:00 (UTC). See how to join.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
14:20, 9 October 2017 (UTC)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
- When you edit a template with the visual editor it follows the template's
formatconfiguration on how to save it. You can now change the format in more powerful ways if your wiki wants it. [45][46] - The TwoColConflict extension is a new way to solve edit conflicts. It makes it easier to copy and paste the relevant text to the text field. It has been a beta feature for the last five months. You can now try out the new interface on a page where you will actually get simulated edit conflicts. You can give feedback to the developers.
Problems
- There is a problem with recent changes pages and your watchlist that show a large number of pages. Until it is fixed, Wikidata edits will not be shown on recent changes or in your watchlist on Commons or Russian Wikipedia. If necessary, Wikidata edits will be removed from all wikis. [47]
- Notifications are not working for some actions. For example some users don't get a notification when they are mentioned. The developers are working on fixing this. [48]
- Users on some wikis could not change their preferences. This has now been fixed. [49]
Changes later this week
- Editors and readers who still use Internet Explorer 8 on Windows XP will not be able to use Wikipedia from 17 October. Internet Explorer 8 on Windows XP can't connect securely to the wikis. When we allow them to do so it means that we get less security for everyone else. If you use Internet Explorer 8 on Windows XP you can install Firefox 52 ESR instead. Around 0.1% of the traffic to the Wikimedia wikis comes from Internet Explorer 8 on Windows XP. [50]
- The new version of MediaWiki will be on test wikis and MediaWiki.org from 17 October. It will be on non-Wikipedia wikis and some Wikipedias from 18 October. It will be on all wikis from 19 October (calendar).
Meetings
- You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 17 October at 19:00 (UTC). See how to join.
- You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 18 October at 15:00 (UTC). See how to join.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
15:31, 16 October 2017 (UTC)
The Signpost: 23 October 2017
- News and notes: Money! WMF fundraising, Wikimedia strategy, WMF new office!
- Featured content: Don, Marcel, Emily, Jessica and other notables
- Humour: Guys named Ralph
- In the media: Facebook and poetry
- Special report: Working with GLAMs in the UK
- Traffic report: Death, disaster, and entertainment
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
- You can use
ccnorm_contains_anywhen you create an abuse filter. This can be used to look for multiple words or phrases within a string. It will find words where some characters have been replaced. You can read more in the documentation. [51]
Changes later this week
- When you search in some languages the search function could use specific other languages if the first language didn't work. This is called a fallback language. This didn't work properly and created bad searches. The search index is being fixed to work better. [52]
- The new version of MediaWiki will be on test wikis and MediaWiki.org from 24 October. It will be on non-Wikipedia wikis and some Wikipedias from 25 October. It will be on all wikis from 26 October (calendar).
Meetings
- You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 24 October at 18:30 (UTC). See how to join.
- You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 25 October at 15:00 (UTC). See how to join.
Future changes
- There is a Structured Commons community focus group for Commons and Wikidata contributors who want to give input on structured data on Wikimedia Commons. You can sign up to join it. [53]
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
18:18, 23 October 2017 (UTC)
Structured Commons newsletter, October 25, 2017
Welcome to the newsletter for Structured Data on Wikimedia Commons! You can update your subscription to the newsletter. Do inform others who you think will want to be involved in the project!
- Community updates
- Rama published an article about Structured Commons in Arbido, a Swiss online magazine for archivists, librarians and documentalists: original in French, illustrated and the article translated in English.
- We now have a dedicated IRC channel: wikimedia-commons-sd webchat
- Join the community focus group!
- Translation. Do you want to help out translating messages about Structured Data on Commons from English to your own language? Sign up on the translators page.
- The documentation and info pages about Structured Data on Commons have received a thorough update, in order to get them ready for all the upcoming work. Obsolete pages were archived. There are undoubtedly still a lot of omissions and bits that are unclear. You can help by editing boldly, and by leaving feedback and tips on the talk pages.
- We have started to list tools, gadgets and bots that might be affected by Structured Commons in order to prepare for a smooth transition to the new situation. You can help by adding alerts about/to specific tools and developers on the dedicated tools page. You can also create Phabricator tasks to help keep track of this. Volunteers and developers interested in helping out with this process are extremely welcome - please sign up!
- Help write the next Structured Commons newsletter.
- Structured Data on Commons was presented at Wikimania 2017 in Montréal for a packed room. First design sketches for search functionality were discussed during a breakout session. Read the Etherpad reports of the presentation and the breakout session.
- Katherine Maher, Executive Director of the Wikimedia Foundation, answered questions on Quora. One of her answers, mentioning Structured Data on Commons, was republished on Huffington Post.
- Sandra Fauconnier, Amanda Bittaker and Ramsey Isler from the Structured Commons team will be at WikidataCon. Sandra presents Structured Commons there (with a focus on fruitful collaboration between the Wikidata and Commons communities). If you attend the conference, don't hesitate to say hi and have a chat with us! (phabricator task T176858)
- Team updates
Two new people have been hired for the Structured Data on Commons team. We are now complete! :-)
- Ramsey Isler is the new Product Manager of the Multimedia team.
- Pamela Drouin was hired as User Interface Designer. She works at the Multimedia team as well, and her work will focus on the Structured Commons project.
- Partners and allies
- We are still welcoming (more) staff from GLAMs (Galleries, Libraries, Archives and Museums) to become part of our long-term focus group (phabricator task T174134). You will be kept in the loop of the project, and receive regular small surveys and requests for feedback. Get in touch with Sandra if you're interested - your input in helping to shape this project is highly valued!
- Research
Design research is ongoing.
- Jonathan Morgan and Niharika Ved have held interviews with various GLAM staff about their batch upload workflows and will finish and report on these in this quarter. (phabricator task T159495)
- At this moment, there is also an online survey for GLAM staff, Wikimedians in Residence, and GLAM volunteers who upload media collections to Wikimedia Commons. The results will be used to understand how we can improve this experience. (phabricator task T175188)
- Upcoming: interviews with Wikimedia volunteers who curate media on Commons (including tool developers), talking about activities and workflows. (phabricator task T175185)
In Autumn 2017, the Structured Commons development team works on the following major tasks (see also the quarterly goals for the team):
- Getting Multi-Content Revisions sufficiently ready, so that the Multimedia and Search Platform teams can start using it to test and prototype things.
- Determine metrics and metrics baseline for Commons (phabricator task T174519).
- The multimedia team at WMF is gaining expertise in Wikibase, and unblocking further development for Structured Commons, by completing the MediaInfo extension for Wikibase.
- Stay up to date!
- Follow the Structured Data on Commons project on Phabricator: https://phabricator.wikimedia.org/project/profile/34/
- Subscribe to this newsletter to receive it on a talk page of your own choice.
- Join the next IRC office hour and ask questions to the team! It takes place on Tuesday 21 November, 18.00 UTC.
Warmly, your community liaison, SandraF (WMF) (discuss)
Message sent by MediaWiki message delivery - 14:26, 25 October 2017 (UTC)
Your half-changes of category system
Hi!
Some weeks ago, you moved Category:Swedish to Category:Book:Swedish (here), with the motivation New naming system. However, neither you, nor any other user (or bot) moved the content. Thus, the redir category now has 27 members, but the book category just has one. Moreover, you did not change the wikidata object, whence the redir category has two linked iw sisters, but the book category just has one.
(Compare this with what User:Green Giant did on May 14, namely, first moving e.g. the Category:Afrikaans to the Category:Book:Afrikaans, and then spending a few hours in moving all the content from the first category to the second, as you can see here.)
Did you also "change" other categories in this incomplete manner, or was this a one-time mistake?
Will you correct the mistake by also moving the content, or do you expect others to do that?
Where can I read more about the change of naming-system? JoergenB (discuss • contribs) 14:22, 20 October 2017 (UTC)
- @JoergenB: See Wikibooks:Reading room/Proposals#Category infrastructure (continued). --Pi zero (discuss • contribs) 15:11, 20 October 2017 (UTC)
- Completed that particular move. --Pi zero (discuss • contribs) 15:44, 20 October 2017 (UTC)
- Thanks! JoergenB (discuss • contribs) 16:35, 20 October 2017 (UTC)
- @Pi zero: However, you choose not to update the wikidata object. If you in general ignore that bit in these name changes, you might loose quite a bit of the iw linkage. In this case, when you removed the category, you also automatically deleted the English member from the wd object, here. Unhappily, as you also see from the history, when PokestarFan moved the category, there was no accompanying automatic change of that English member. I do not know why; possibly, it has something to do with leaving or not leaving a redirect.
- When you moved Category:Languages of Europe to Category:Subject:Languages of Europe, you indeed also automatically changed the enbook item of the wikidata object for Category:Languages in Europe (here), and thus maintained the iw linkage. However, in that case, you moved without leaving a redir, while PokestarFan did leave a redir (which retained the same associated wikidata item).
- You may have a problem here. I think that you should recommend not leaving redirs in these moves (if there still are some left to do). Alternatively, the relinking should be fixed by hand, when the temporary redir category is deleted. IMHO, the iwlinkage is potentially of great use, although it is still underdeveloped for the various wikibooks projects, and by mistake loosing what small beginnings you have thus could be decidedly negative. JoergenB (discuss • contribs) 17:20, 20 October 2017 (UTC)
- @JoergenB: Thanks for pointing this out. Alas. I always suppress redirect when renaming these, and so was unaware of the problem; but I'm usually the only admin who does these, so the only one who does them with the option to suppress redirect. I'll have to check this with each one from now own, but there are hundreds of them that would have lost their wikidata links this way. Even though we at en.wb do not remove interwikis even after they've been added to wikidata, we don't wish to mess up wikidata. At some point I'll have to compile a list of all the category redirects deleted over the past half year or so, to be checked one-at-a-time thereafter. --Pi zero (discuss • contribs) 17:30, 20 October 2017 (UTC)
- ...if indeed leaving a redir causes the trouble, as I suspect; perhaps checking with some wizard before you compile that list would be wise. JoergenB (discuss • contribs) 19:13, 20 October 2017 (UTC)
- Apparently those changes to Wikiata show up under my username; so I can find them all by looking through my Special:Contributions there. --Pi zero (discuss • contribs) 22:40, 20 October 2017 (UTC)
- Turns out there were only a handful of them, for all time; mostly, a few subject categories deleted last December. --Pi zero (discuss • contribs) 23:41, 20 October 2017 (UTC)
- ...if indeed leaving a redir causes the trouble, as I suspect; perhaps checking with some wizard before you compile that list would be wise. JoergenB (discuss • contribs) 19:13, 20 October 2017 (UTC)
- @JoergenB: Thanks for pointing this out. Alas. I always suppress redirect when renaming these, and so was unaware of the problem; but I'm usually the only admin who does these, so the only one who does them with the option to suppress redirect. I'll have to check this with each one from now own, but there are hundreds of them that would have lost their wikidata links this way. Even though we at en.wb do not remove interwikis even after they've been added to wikidata, we don't wish to mess up wikidata. At some point I'll have to compile a list of all the category redirects deleted over the past half year or so, to be checked one-at-a-time thereafter. --Pi zero (discuss • contribs) 17:30, 20 October 2017 (UTC)
- Thanks! JoergenB (discuss • contribs) 16:35, 20 October 2017 (UTC)
@Pi zero: I did not change the Wikidata because I'm blocked there. PokestarFan • Talk • Contributions 23:04, 22 October 2017 (UTC)
- Yes, I came to that conclusion myself. The change on wikidata happens automatically, though, and is supposed to ensure consistency between projects. So by blocking you there they caused their own automation to compromise their database. The root of the problem, in my engineering judgement, is the bad design decision to have fully-automated centralization at all. At any rate, I think I'll find that every category you moved that has a wikidata link is now out-of-sync on wikidata; and once I've found a few more so I'm sure of that, I'll leave a note for them over at wikidata, just so they're aware of the software flaw. (A polite note; after all, afaict this is in the wiki software, so it's really not under the control of the Wikidatans, nor are they responsible for the design error inherent in the the way their project was set up.) --Pi zero (discuss • contribs) 23:31, 22 October 2017 (UTC)
- Btw, I have done something similar to your earlier suggestion, to null-edit {{BookCat}}. As I mentioned, I don't think that in itself would do the trick, because the software would recognize that nothing had actually changed. However, {{BookCat}} and other related templates use {{BOOKCATEGORY}} to deduce, from the name of the book, the name of its book-category. During the transition, I had wired {{BOOKCATEGORY}} to look for existing category pages in order to deduce this: if the new-name category existed, that would be the book category, otherwise if the old-name category existed, that would be the book category, otherwise use the new name. I'd always planned that after all the categories had been moved, I would change {{BOOKCATEGORY}} to just always use the new name, avoiding all that expensive logic. And since all the categories have, actually, been moved, there are no more under the old naming scheme, I have make that one-time, heavy-server-load change to {{BOOKCATEGORY}}. I think it's a heavy-server-load thing, anyway. {{BOOKCATEGORY}} is used on over 70,000 pages. Hopefully, now that I've done the update to {{BOOKCATEGORY}}, the software will (given a bit of time) update the categorization of every page that uses {{BookCat}}, and while that won't do all of what needs doing, it ought to do more than half of it. --Pi zero (discuss • contribs) 14:23, 26 October 2017 (UTC)
- Things are going fairly smoothly, so far. The total time to complete may even be somewhat lower this way; there are a different set of advantages and disadvantages to this approach than to the one I'd envisioned, but we'll still get there. :-) --Pi zero (discuss • contribs) 16:07, 27 October 2017 (UTC)
- Btw, I have done something similar to your earlier suggestion, to null-edit {{BookCat}}. As I mentioned, I don't think that in itself would do the trick, because the software would recognize that nothing had actually changed. However, {{BookCat}} and other related templates use {{BOOKCATEGORY}} to deduce, from the name of the book, the name of its book-category. During the transition, I had wired {{BOOKCATEGORY}} to look for existing category pages in order to deduce this: if the new-name category existed, that would be the book category, otherwise if the old-name category existed, that would be the book category, otherwise use the new name. I'd always planned that after all the categories had been moved, I would change {{BOOKCATEGORY}} to just always use the new name, avoiding all that expensive logic. And since all the categories have, actually, been moved, there are no more under the old naming scheme, I have make that one-time, heavy-server-load change to {{BOOKCATEGORY}}. I think it's a heavy-server-load thing, anyway. {{BOOKCATEGORY}} is used on over 70,000 pages. Hopefully, now that I've done the update to {{BOOKCATEGORY}}, the software will (given a bit of time) update the categorization of every page that uses {{BookCat}}, and while that won't do all of what needs doing, it ought to do more than half of it. --Pi zero (discuss • contribs) 14:23, 26 October 2017 (UTC)
Talkheader
I record my objection to your adding Talkheader to talk pages. --Dan Polansky (discuss • contribs) 16:05, 27 October 2017 (UTC)
Scribus speedy nomination
In Special:Diff/3298135, you nominated Scribus for speedy deletion. That is inappropriate since Scribus survived Wikibooks:Requests_for_deletion. --Dan Polansky (discuss • contribs) 19:48, 27 October 2017 (UTC)
- I've added {{rfd-survived}} to the book's talk page. --Pi zero (discuss • contribs) 19:55, 27 October 2017 (UTC)
Windows Command Prompt Commands
You have started Windows Command Prompt Commands. That seems redundant to Windows Batch Scripting. --Dan Polansky (discuss • contribs) 18:42, 28 October 2017 (UTC)
Windows Command Prompt Commands/mkdir seems to be a copyvio in that it contains the output of "help mkdir" unmodified. Windows Command Prompt Commands/xcopy seems to be the same story, copyvio. --Dan Polansky (discuss • contribs) 18:44, 28 October 2017 (UTC)