User talk:LoreMariano/Archive 19

== March 20: WikiWednesday Salon and Skill-Share NYC + March 23: Asian Art Archive/New York Public Library ==

(You can subscribe/unsubscribe from future notifications for NYC-area events by adding or removing your name from this list.)

Your help desk question
You didn't get a response to [https://en.wikipedia.org/wiki/Wikipedia:Help_desk/Archives/2019_March_13#Wikitext_mode? this question]. It looks like something people might answer on WP:VPT.— Vchimpanzee  •  talk  •  contributions  •  20:45, 18 March 2019 (UTC)
 * Thank you Vchimpanzee  •  talk  •  contributions  ; yes, I got the answer on WP:VPT.  The interface with the Blue Publish Changes button is the beta Wikitext mode.  Thanks for following up and directing me to the Village pump.
 * The Foundation calls it the "2017 Wikitext editor", however in fact it's part of the Foundation's continual battle to try to pressure everyone into the VisualEditor. What you're using actually a new textmode built inside VisualEditor. This has unsurprisingly resulted in a number of issues. Many people report poor performance, particularly when trying edit long pages. It doesn't provide accurate previews - they eliminated the genuine preview and used VisualEditor to generate fake previews, which can result in rendering flaws. There have also be a variety of weird bugs, because it uses very complicated code to draw the wikitext using VisualEditor's graphical engine. The beta project has largely been stalled for the last two years, when a Village pump RFC reached consensus to block deployment. The staff in charge of the project have been dismissive of community feedback on even the most simple and basic functionality. There have been endless requests for the preview to be directly accessible next to the publish button, but the staff response is basically that they don't consider it important and they don't want to fix it. They also screwed up the basic CTRL-V paste. Instead of fixing it, they added an disruptive pop-up every time you try to paste anything.
 * But if you like it, okey dokey. But it has little chance of getting out of beta unless they can reverse the strong community consensus against it. Alsee (talk) 17:56, 26 March 2019 (UTC)
 * Thank you for taking the time to explain it so thoroughly. I liked the "one stop shopping" idea of having everything in one place but now that I know it's so buggy, I'll go back to editing old school.  Lore E. Mariano (talk) 18:11, 26 March 2019 (UTC)
 * Alsee, I've always edited using source editing because I like textmode. (Let's go waaayyyy back in time and talk about Word's "reveal codes"....) Why does the Foundation want to get people to use the Visual Editor, and what are the drawbacks of using Visual Editor? Lore E. Mariano (talk) 18:22, 26 March 2019 (UTC)
 * I'm not sure I fully understand the Foundation's obsession with Visual, but they very firmly believe it's better/easier for new users. When they did user testing on approximately 8 random people who have never edited, people have zero likelihood of ever editing, people who spend just a few minutes with VisualEditor and just a few minutes with the wikitext editor, they their first impression was generally in favor of VE. They Foundation considers that superficial test data to enormously validate the Visual strategy. However that is the only data that has ever come out positive for VE. All of the real-world-use data about VisualEditor, data collected from new accounts and general usage, unfavorable of VisualEditor or at best neutral. Editing in wikitext is faster, and I believe it is helpful and important to see what's actually going on in the article. When Visual users run into any minor problem, they seem to get hopelessly lost because VisualEditor hides what's going on, you can't see what went wrong or how to fix it. VisualEditor is a big slow complicated piece of software, and most people find VisualEditor unusably slow on large pages. The wikitext editor is a fast and efficient - it's little more than a basic browser-text-box with buttons for preview&save.
 * In 2011 the foundation published a strategy to... and I quote... "Deprecate wikitext as the primary input method". The plan was to deploy a Visual editing system for article editing, to abandon wikitext and store article as HTML, and to deploy conventional forum type boards to replace talk pages. Since they were planning to kill off wikitext, they decided NOT to build a Visual editor for wikitext. Instead they hired a bunch of HTML programmers and they built a Visual system that to edit HTML. The Visual-HTML-editor has absolutely no ability to edit wikitext. Because VisualEditor was going to take time to develop, and because it had to bridge-over from our existing wikipages, they build something called Parsoid. Parsoid attempts to translate wikitext into HTML, then VisualEditor can edit that, then Parsoid tries to translate that HTML back into wikitext. And because they hate wikitext, and because they're all HTML-web-programmers, they designed Parsoid to work like HTML instead or working like wikitext. So there are a whole bunch of glitches and difficulties in Parsoid's ability to deal with wikitext. It is is an incredibly complex hack, which allows VisualEditor to indirectly load wikitext-pages and save them back as wikitext. And remember their plan was to kill wikitext and switch all of the articles over to THML format. So Parsoid was originally created as a temporary hack to let the Visual-HTML editor work here. Of course nearly all of the human editors considered wikitext a better tool for the job, and fought back against the various effort to deprecate wikitext. So now the Foundation kinda accepts that wikitext is not going away any time soon, they are still obsessed with the idea that Visual type editing is going to bring in hordes of new people, and most importantly they've invested god-knows-how-many millions of dollars on VisualEditor & Parsoid. And while Parsoid tries to translate wikitext, the design is fundamentally incompatible with wikitext. They're running into various difficulties with the software on their end, because of the incompatible design of wikitext and Parsoid. So now their plan is to kill off the existing wikitext engine and switch everything over to Parsoid. And because Parsoid resembles wikitext (most basic wikitext works the same in Parsoid), they call Parsoid wikitext. So they plan to kill off the existing wikitext engine, and to keep us from rioting they call the new engine wikitext. In preparation for this, they've started braking the current wikitext system, so that less stuff will break when they try to switch over to Parsoid instead. Look at this small bit of wikitext:



~ 
 * It's three colons, a tag, one blank line, three colons, then close the tag. It's probably obvious what that does... everything is indented by three, and everything in between the start tag and the end tag is shown as small text. If you post that in a discussion everything works fine, and it always worked fine. However the Foundation recently changed wikitext.... that used to work fine with four colons, but now if you post that with four colons it breaks the page. Every comment and even ever section on the page below that point will be displayed in small. Why? Because to make wikitext work more like Parsoid they decided to silently ignore any markup after the colons, if the current line has has at least four more colons than the line before it. So now the software ignores the tag, to make it more compatible for the switchover to Parsoid. They also want to break how templates and other stuff works, basically they want everyone to learn the most bizarre and difficult parts of HTML-programming if you want to edit in wikitext. They've decided that wikitext is too confusing for new users, so they're doing their damn-best to make wikitext more confusing.
 * Ok, I've excessively rambled on and on about this topic. Chuckle. Anyway, VisualEditor's new wikitext mode (known as the beta 2017WikitextEditor) is all part of this same strategy. They want to kill off the existing wikitext editor, they want everyone in VisualEditor as the one-and-only editor (with the new wikitext mode), and that is why the beta editor has a fake-preview-button. It uses the VisualEditor/Parsoid engine to render the preview instead of generating a real preview using the actual wikitext engine. The manager refuses to put genuine preview button in the new editor because he wants to kill the existing wikitext engine. So the new editor project has been stalled for two years, while they slowly move forwards on their plan to switch over the entire wiki to the Parsoid engine. The fact that a zillion article pages will break isn't important. The important thing is that the article views will be broken in the same way as the new editor previews are broken! And since they're broken in the same way, the new editor previews will be accurate! Problem solved! (sarcasm)
 * Oh, I have to add a P.S. The Foundation abandoned high-value work to improve the quality of wikitext diffs. Why? They're too busy chasing Visual-butterflies. They abandoned valuable upgrades to wikitext diffs to go build VISUAL DIFFs instead. Alsee (talk) 00:05, 28 March 2019 (UTC)

April 17: WikiWednesday Salon and Skill-Share NYC + April 4 and 5: LaGuardia Community College Translatathon 2019
(You can subscribe/unsubscribe from future notifications for NYC-area events by adding or removing your name from this list.)

Administrators' newsletter – April 2019
News and updates for administrators from the past month (March 2019).

Administrator changes
 * Gnome-colors-view-refresh.svg Reaper Eternal • ThaddeusB
 * Gnome-colors-list-remove.svg Bogdangiusca • Christopher Parham • Necrothesp • Schneelocke • Siroxo • Sarah
 * Pictogram voting rename.png →

Interface administrator changes
 * Gnome-colors-list-remove.svg Mr. Stradivarius

Bureaucrat changes
 * Gnome-colors-list-add.svg DeltaQuad
 * Gnome-colors-list-remove.svg Kingturtle

Technical news
 * In Special:Preferences under "Appearance" → "Advanced options", there is now an option to show a confirmation prompt when clicking on a rollback link.
 * The Wikimedia Foundation's Community health initiative plans to design and build a new user reporting system to make it easier for people experiencing harassment and other forms of abuse to provide accurate information to the appropriate channel for action to be taken. Please see meta:Community health initiative/User reporting system consultation 2019 to provide your input on this idea.

Arbitration
 * The Arbitration Committee clarified that the General 1RR prohibition for Palestine-Israel articles may only be enforced on pages with the ARBPIA 1RR editnotice edit notice.

Miscellaneous
 * Two more administrator accounts were compromised. Evidence has shown that these attacks, like previous incidents, were due to reusing a password that was used on another website that suffered a data breach. If you have ever used your current password on any other website, you should change it immediately. All admins are strongly encouraged to enable two-factor authentication, please consider doing so. Please always practice appropriate account security by ensuring your password is secure and unique to Wikimedia.
 * As a reminder, according to WP:NOQUORUM, administrators looking to close or relist an AfD should evaluate a nomination that has received few or no comments as if it were a proposed deletion (PROD) prior to determining whether it should be relisted.

Discuss this newsletter

Subscribe

Archive Sent by MediaWiki message delivery (talk) 21:57, 7 April 2019 (UTC)

Problems with upload of File:Confidential.gif
Thanks for uploading File:Confidential.gif. You don't seem to have said where the image came from, who created it, or what the copyright status is. We require this information to verify that the image is legally usable on Wikipedia, and because most image licenses require giving credit to the image's creator.

To add this information, click on this link, then click the "Edit" tab at the top of the page and add the information to the image's description. If you need help, post your question on Media copyright questions.

For more information on using images, see the following pages:
 * Image use policy
 * Image copyright tags

Thank you for your cooperation. --ImageTaggingBot (talk) 21:31, 25 April 2019 (UTC)

Proposed deletion of File:Confidential.gif


The file File:Confidential.gif has been proposed for deletion&#32;because of the following concern: "File not being used in any constructive way. File would have no obvious value being hosted on Commons"

While all constructive contributions to Wikipedia are appreciated, pages may be deleted for any of several reasons.

You may prevent the proposed deletion by removing the notice, but please explain why in your edit summary or on the file's talk page.

Please consider addressing the issues raised. Removing will stop the proposed deletion process, but other deletion processes exist. In particular, the speedy deletion process can result in deletion without discussion, and files for discussion allows discussion to reach consensus for deletion.

This bot DID NOT nominate any file(s) for deletion; please refer to the page history of each individual file for details. Thanks, FastilyBot (talk) 01:00, 28 April 2019 (UTC)


 * Very sorry! It was a test and I didn't mean to upload it! Lore E. Mariano (talk) 14:18, 2 May 2019 (UTC)

Administrators' newsletter – May 2019
News and updates for administrators from the past month (April 2019).

Administrator changes
 * Gnome-colors-list-add.svg HickoryOughtShirt?4 • RexxS
 * Gnome-colors-view-refresh.svg Necrothesp
 * Gnome-colors-list-remove.svg Bratsche • Kyle Barbour • Kzollman • Madman

Interface administrator changes
 * Gnome-colors-list-remove.svg Pharos

Bureaucrat changes
 * Gnome-colors-list-add.svg Primefac

CheckUser changes
 * Gnome-colors-view-refresh.svg Reaper Eternal

Guideline and policy news
 * A request for comment concluded that creating pages in the portal namespace should be restricted to autoconfirmed users.
 * Following a request for comment, the subject-specific notability guideline for pornographic actors and models (WP:PORNBIO) was removed; in its place, editors should consult WP:ENT and WP:GNG.

Technical news
 * XTools Admin Stats, a tool to list admins by administrative actions, has been revamped to support more types of log entries such as AbuseFilter changes. Two additional tools have been integrated into it as well: Steward Stats and Patroller Stats.

Arbitration
 * In response to the continuing compromise of administrator accounts, the Arbitration Committee passed a motion amending the procedures for return of permissions (diff). In such cases, the committee will review all available information to determine whether the administrator followed "appropriate personal security practices" before restoring permissions; administrators found failing to have adequately done so will not be resysopped automatically.  All current administrators have been notified of this change.
 * Following a formal ratification process, the arbitration policy has been amended (diff). Specifically, the two-thirds majority required to remove or suspend an arbitrator now excludes (1) the arbitrator facing suspension or removal, and (2) any inactive arbitrator who does not respond within 30 days to attempts to solicit their feedback on the resolution through all known methods of communication.

Miscellaneous
 * A request for comment is currently open to amend the community sanctions procedure to exclude non XfD or CSD deletions.
 * A proposal to remove pre-2009 indefinite IP blocks is currently open for discussion.

Discuss this newsletter

Subscribe

Archive Sent by MediaWiki message delivery (talk) 00:37, 5 May 2019 (UTC)

May 22: WikiWednesday Salon and Skill-Share NYC
(You can subscribe/unsubscribe from future notifications for NYC-area events by adding or removing your name from this list.)

Administrators' newsletter – June 2019
News and updates for administrators from the past month (May 2019). Administrator changes
 * Gnome-colors-list-remove.svg Andonic • Consumed Crustacean • Enigmaman • Euryalus • EWS23 • HereToHelp • Nv8200pa • Peripitus • StringTheory11 • Vejvančický

CheckUser changes
 * Gnome-colors-list-remove.svg Ivanvector

Guideline and policy news
 * An RfC seeks to clarify whether WP:OUTING should include information on just the English Wikipedia or any Wikimedia project.
 * An RfC on WT:RfA concluded that Requests for adminship and bureaucratship are discussions seeking to build consensus.
 * An RfC proposal to make the templates for discussion (TfD) process more like the requested moves (RM) process, i.e. "as a clearinghouse of template discussions", was closed as successful.

Technical news
 * The CSD feature of Twinkle now allows admins to notify page creators of deletion if the page had not been tagged. The default behavior matches that of tagging notifications, and replaces the ability to open the user talk page upon deletion.  You can customize which criteria receive notifications in your Twinkle preferences: look for Notify page creator when deleting under these criteria.
 * Twinkle's d-batch (batch delete) feature now supports deleting subpages (and related redirects and talk pages) of each page. The pages will be listed first but use with caution!  The und-batch (batch undelete) option can now also restore talk pages.

Miscellaneous
 * The previously discussed unblocking of IP addresses indefinitely-blocked before 2009 was approved and has taken place.
 * The 2019 talk pages consultation produced a report for Phase 1 and has entered Phase 2.

Discuss this newsletter

Subscribe

Archive Sent by MediaWiki message delivery (talk) 09:48, 8 June 2019 (UTC)

June 19: WikiWednesday Salon and Skill-Share NYC (stay tuned for Pride on weekend!)
(You can subscribe/unsubscribe from future notifications for NYC-area events by adding or removing your name from this list.)

Sunday June 23: Wiki Loves Pride @ Metropolitan Museum of Art
(You can subscribe/unsubscribe from future notifications for NYC-area events by adding or removing your name from this list.)