User talk:NE Ent/Archive/2018

Disambiguation link notification for January 5
Hi. Thank you for your recent edits. An automated process has detected that when you recently edited Forever Free (novel), you added a link pointing to the disambiguation page Forever War ([//dispenser.info.tm/~dispenser/cgi-bin/dablinks.py/Forever_Free_%28novel%29 check to confirm] | [//dispenser.info.tm/~dispenser/cgi-bin/dab_solver.py/Forever_Free_%28novel%29?client=notify fix with Dab solver]). Such links are usually incorrect, since a disambiguation page is merely a list of unrelated topics with similar titles. (Read the FAQ* Join us at the DPL WikiProject.)

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 09:05, 5 January 2018 (UTC)

Still around
I'm glad to see you're still somewhat around, Ent. Could be more, though! Bishonen &#124; talk 12:25, 9 March 2018 (UTC).
 * Thanks for the shout out. I do a little when I can. NE Ent 14:38, 17 March 2018 (UTC)

Upcoming changes to wikitext parsing
Hello,

There will be some changes to the way wikitext is parsed during the next few weeks. It will affect all namespaces. You can see a list of pages that may display incorrectly at Special:LintErrors. Since most of the easy problems have already been solved at the English Wikipedia, I am specifically contacting tech-savvy editors such as yourself with this one-time message, in the hope that you will be able to investigate the remaining high-priority pages during the next month.

There are approximately 10,000 articles (and many more non-article pages) with high-priority errors. The most important ones are the articles with misnested tags and table problems. Some of these involve templates, such as infoboxes, or the way the template is used in the article. In some cases, the "error" is a minor, unimportant difference in the visual appearance. In other cases, the results are undesirable. You can see a before-and-after comparison of any article by adding ?action=parsermigration-edit to the end of a link, like this: https://en.wikipedia.org/wiki/Arthur_Foss?action=parsermigration-edit (which shows a difference in how infobox ship is parsed).

If you are interested in helping with this project, please see Linter. There are also some basic instructions (and links to even more information) at https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2018-April/001836.html You can also leave a note at WT:Linter if you have questions.

Thank you for all the good things you do for the English Wikipedia. Whatamidoing (WMF) (talk) 21:18, 19 April 2018 (UTC)

Help us design granular blocks!
Hello :-) The Anti-Harassment Tools team at the Wikimedia Foundation will start building these granular blocking tools in a few weeks and we've asked WMF designer Alex Hollender to help us make some wireframes so the tools are intuitive to MediaWiki users.

We have a first draft of how we think this tool should work. You can read the full proposed implementation here but here are the significant parts:
 * Granular blocks (page, category, namespace, and file uploading) will be built on top of Special:Block. These blocks will function as if they were regular blocks and allow for the same options, but only take effect on specific pages.
 * We will add a new checkbox for "Block this user from the whole site" which will be checked by default. When it is unchecked the admin will be able to specify which pages, categories, and/or namespaces the user should be blocked from editing.
 * Granular blocks can be combined and/or overlap. (For example, a user could be simultaneously blocked from editing the articles Rain, Thunder, Lightning, and all pages inside the Category:Weather.)
 * Only one block is set at a time, to adjust what the user is blocked from the administrator would have to modify the existing block.
 * Block logs should display information about the granular block
 * When a blocked user attempts to edit an applicable page, they should see a block warning message which include information on their block (reason, expiration, what they are blocked from, etc.)
 * If a category is provided, the blocked user cannot edit either the category page itself and all pages within the category.
 * If the File: namespace is blocked, the user should not be allowed to upload files.

We like this direction because it builds on top of the existing block system, both a technical and usability wise. Before we get too far along with designs and development we'd like to hear from you about our prosposal:


 * 1) What do you think of the proposed implementation?
 * 2) We believe this should be an expansion of Special:Block, but it has been suggested that this be a new special page. What are your thoughts?
 * 3) Should uploading files be combined with a File namespace block, or as a separate option? (For example, if combined, when a user is blocked from the File namespace, they would neither be able to edit any existing pages in the File namespace nor upload new files.)
 * 4) Should there be a maximum number of things to be blocked from? Or should we leave it up to admin discretion?

We appreciate your feedback on this project's talk page or by email. For the Anti-Harassment Tools team, SPoore (WMF) (talk), Trust and Safety Specialist, Community health initiative (talk) 20:54, 9 May 2018 (UTC)

My poem is bad but my apology for the bad links is sincere!
Rosa Red Chateau01.jpg are red,

Good message links are blue,

My proofreading stinks,

So here's a good link for you SPoore (WMF), Trust &#38; Safety, Community health initiative (talk) 16:18, 10 May 2018 (UTC)]].

Precious six years!
--Gerda Arendt (talk) 22:23, 17 May 2018 (UTC)

File:Lions in the Desert.png listed for discussion
A file that you uploaded or altered, File:Lions in the Desert.png, has been listed at Files for discussion. Please see the to see why it has been listed (you may have to search for the title of the image to find its entry). Feel free to add your opinion on the matter below the nomination. Thank you. B (talk) 23:51, 18 September 2018 (UTC)