Page MenuHomePhabricator

Alsee
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Friday

  • Clear sailing ahead.

User Details

User Since
Feb 26 2015, 7:19 PM (245 w, 5 d)
Availability
Available
LDAP User
Unknown
MediaWiki User
Alsee [ Global Accounts ]

Recent Activity

Fri, Nov 8

Alsee added a comment to T235592: Replies v1.0: Create mockups.

Depending on the design, the interface might make this information directly visible....

We've been thinking of making this visible by "indenting" the reply textbox on the page

I still like showing the indent string and sig string for several reasons:
(1) Indenting the box would consume X characters of whitespace at the beginning of every line, whereas showing the indent-characters only consumes X characters on the first line of the reply box. This is particularly significant for mobile. (2) Experienced users will be instantly comfortable seeing exactly how the new interface works. (2) The new interface becomes an actively helpful on-ramp. New users will passively absorb how the underlying page works, especially if the shown characters have a tip appear on mouseover. If the new user sticks around they will sometimes need to use the edit button to directly edit the page for various reasons. (3) Making indent characters visible and click-to-edit allows people to replace the indents with an {{od}} outdent or otherwise alter the indentation for various reasons, without having having to leave the new interface. The community likes the power, flexibility, and control they have on talk pages. We should't hardcode-lock the indentation string if we don't have to.

Having the signature characters moving with your cursor as your type sounds annoying.

Agreed. Instead I picture it attached to the bottom-right corner of the text entry box.
While I expect it would be rare to want to delete or change the sig portion, if the indent-characters are click-to-edit then this part should work the same.

[posting in places that aren't a reply]

Ideally we'd add some cue that you can reply to those places, and ideally it would also describe the expected way to indent (imagine a template like {{replywith|#}} that generates some invisible marker), and then the user won't have to know what to do beforehand. I don't think we've thought this through yet (I certainly haven't).

I'm picturing a reply link after each signature, plus a link at the bottom of every section. I think the section-link should say something like "Add comment" or "Add new comment" instead of "Reply". It would add a zero-indent post. The user can supply the * or # if appropriate. Note: For the zero indent case the software will need to prepend a blank line unless one of the following is true: (1) There's already a blank line or section heading directly above (2) the user starts their reply with one of :*# (3) any other known-safe case I missed.

Fri, Nov 8, 10:51 AM · Editing Design, Editing-team, OWC2020

Tue, Nov 5

Alsee added a comment to T232780: Write a client-side parser for signatures (username & timestamp).

The community already has guidelines for custom signatures. (Or at least Enwiki does, and I expect any non-minimal wiki will too.) I believe our current rules already require at least one link to user/user_talk/user-contributions, and if we don't already have a rule about not screwing up the timestamp then that rule would certainly be added as soon as anything breaks.

Tue, Nov 5, 10:29 PM · OWC2020, VisualEditor (Current work)
Alsee added a comment to T235592: Replies v1.0: Create mockups.

Another common case is that we use a single-bullet-indent comment for many of our workflows. (RFCs, AFDs, RFAs.) ...I think this pretty much confirms the answer to the last question - the user needs to be able to add or modify the indent-markup.

Are you able to share a link to a conversation where we can observe this convention?

Tue, Nov 5, 10:05 PM · Editing Design, Editing-team, OWC2020

Fri, Nov 1

Alsee added a comment to T228862: One feed to pull all the announcements published by the Foundation.

Could we designate a page on EnWiki to receive these announcements? I suspect we'd want to fully protect the page, so it's reserved solely for this announcement stream.

Fri, Nov 1, 6:31 AM · Space (Oct-Dec-2019)

Sun, Oct 27

Alsee added a comment to T234403: Create a VE-based text input for replying.

VE is not viable as for a primary/default. Multiple communities have created hacks to the sitewide javascript to kill VE-defaults, the Talk Page Consultation finally killed Flow fundamentally due to it being entirely built around VE and attempted to force VE as the sole interface for Talk, and EnWiki (nearly half our global community) put a block on the 2017wikitext editor again fundamentally because it was built entirely around VE and it attempted to force VE as the sole interface for non-talk. Using VE for plaintext and/or wikitext is grossly dysfunctional design.

Sun, Oct 27, 12:26 AM · VisualEditor (Current work), Editing-team, OWC2020

Sat, Oct 26

Alsee added a comment to T235592: Replies v1.0: Create mockups.

@iamjessklein

I have two versions of the editor itself. One of these versions is VE first but will handle wikitext if written

Building Flow around VE was the core cause of failure. The community is adamant that wikitext is primary. It will not be possible to deploy the product unless the initial/default input box properly handles and previews wikitext. (Note: Running it through the VE's parser is not proper wikitext support.)

Sat, Oct 26, 11:52 PM · Editing Design, Editing-team, OWC2020

Oct 10 2019

Alsee added a comment to T223793: On non-SET wikis (two edit tabs), links to new pages (red links) should open the user's preferred editor (last used).

@Theklan I don't want a long debate of VE-vs-Wikitext here, but in short the data and the general community both strongly disagree. File:2018-10_Wikimedia_editing_interface_retention.png data shows desktop& mobile interface-retention rates for VE are about half of the interface-retention rates for the wikitext editor. Foundation Research:VisualEditor's_effect_on_newly_registered_editors shows that VE utterly fails to provide the intended benefits for new users, and results in massively slower editing and lower rates of new users successfully making an edit. Global edit counts show the wikitext editor is overwhelmingly the primary editor, chosen as the best tool for the job by almost everyone. On wikis where VE is the default, new users rapidly abandon it and quickly shift to wikitext for a majority of edits. The Foundation attempted to roll out a VE-default for new users with SET deployment - two wikis (one being EnWiki) wrote hacks for the sitewide javascript to change the default and a third wiki unanimously demanded it be reversed. This effectively halted any further deployment of SET. It was clear that the community was not going to tolerate a Visual default, and management behind SET apparently lost interest in further SET deployment if it wasn't going to include a VE-default.

Oct 10 2019, 8:31 PM · MW-1.34-notes (1.34.0-wmf.8; 2019-06-04), User-notice, VisualEditor-MediaWiki, VisualEditor (Current work)

Oct 3 2019

Alsee added a comment to T230653: Use a parser function to encapsulate signatures.

For raw disruption, I believe someone could put image(s) in their signature. Aside from the obvious image-content issues, the image(s) may be up to 100 megabytes each and/or animated gifs.

Oct 3 2019, 6:52 PM · Patch-For-Review, OWC2020, MediaWiki-Parser

Sep 29 2019

Alsee added a comment to T230653: Use a parser function to encapsulate signatures.

oft-requested user feature: automatically updating signatures on old talk pages.

While there may have been requests for this, I think it unlikely that the community would actually want this. Changing signatures with no entry in the page history would be strange, confusing, and open to abuse.

  1. Make an apparently innocent edit.
  2. At any time, change signature preference. Purge the page to apply the change. These actions are unlogged and invisible to the community.
  3. The page may now be in a deceptive or malicious state.
  4. At any time, change signature preference. Purge the page to apply the change. These actions are unlogged and invisible to the community.
  5. The page is back in an apparently innocent state. There does not exist any log or other evidence that the user committed the abuse.

The most obvious issue would be to impersonate someone else, however it's more serious than may first be apparent. This exploit enables a clever user to inject arbitrary wikitext&content at several points in the page, with surprisingly powerful possibilities.

Sep 29 2019, 5:16 AM · Patch-For-Review, OWC2020, MediaWiki-Parser
Alsee updated the task description for T232780: Write a client-side parser for signatures (username & timestamp).
Sep 29 2019, 1:42 AM · OWC2020, VisualEditor (Current work)
Alsee added a comment to T232780: Write a client-side parser for signatures (username & timestamp).

According to Manual:Echo:

The signature must contain a plain wiki link ([[ ]]) to the user's page, user talk page, or contributions page, on the local wiki

I will update the task description here to match, adding 'contributions page' to the list.

Sep 29 2019, 1:41 AM · OWC2020, VisualEditor (Current work)

Aug 31 2019

Alsee added a comment to T76997: Edit conflict automatic resolution can silently produce unexpected results.

Another example was posted in T223433 and it's worth noting here. I'll detail the three edits involved:

Aug 31 2019, 9:31 PM · Patch-For-Review, MediaWiki-Page-editing

Aug 22 2019

Alsee added a comment to T230659: Automatically-assigned id attributes for list items.

If I understand this correctly, it appears to be a non-starter. One of the clear outcomes of the Talk Page Consultation was not to disrupt normal editing of talk pages, and that any new tools be optional. It appears either impossible or unreasonable for experienced editors to type these IDs, and surely you don't expect a new users to look at the wikipage and figure out how to comment like this.

Aug 22 2019, 2:48 PM · OWC2020, MediaWiki-Parser

Aug 8 2019

Alsee added a comment to T230010: Wiki text: <s> in front of : makes rest of the text on the page strike-through.

@Aklapper, this example involved the small tag instead of strikethough, so it was perhaps less obvious on a "quick look".

Aug 8 2019, 2:08 PM · MediaWiki-Parser
Alsee added a comment to T230010: Wiki text: <s> in front of : makes rest of the text on the page strike-through.

@Aklapper you can see in another revision from Admin noticeboard the bottom of the page is mangled even when the opening tag is placed after the colons.

Aug 8 2019, 11:40 AM · MediaWiki-Parser
Alsee added a comment to T230010: Wiki text: <s> in front of : makes rest of the text on the page strike-through.

@Aklapper I apologize if my bug-description was not sufficiently clear.

Aug 8 2019, 10:29 AM · MediaWiki-Parser

Aug 7 2019

Alsee updated the task description for T230010: Wiki text: <s> in front of : makes rest of the text on the page strike-through.
Aug 7 2019, 11:08 AM · MediaWiki-Parser
Alsee created T230010: Wiki text: <s> in front of : makes rest of the text on the page strike-through.
Aug 7 2019, 11:02 AM · MediaWiki-Parser

Aug 5 2019

Alsee added a comment to T227733: Draft: Masking IP addresses for increased privacy.

First a nitpick, problem behavior is a far larger category than "vandalism". For example if someone is a partisan political warrior and they persistently put inappropriate negative content into the biographies of politicians of a particular political party, they are not a vandal. However they do need to be blocked.

Aug 5 2019, 2:03 PM · Privacy, MediaWiki-User-management, Anti-Harassment

Jul 30 2019

Alsee added a comment to T159678: [Bug] Special:Nearby isn't showing thumbnails on Wikidata.

The default behavior of PageImages is Free-only for good reason. The Board of Trustee's Resolution:Licensing_policy says that unauthorized use of copyrighted content (non-free content) must be "minimal" and subject to EDP (Exception Doctrine Policy), and that this may not be circumvented, eroded, or ignored by Wikimedia Foundation officers or staff nor local policies of any Wikimedia project.

Jul 30 2019, 11:30 PM · User-aude, Wikimedia-Site-requests, MediaWiki-extensions-WikibaseRepository, PageImages, Wikidata

Jul 6 2019

Alsee added a comment to T141901: MultimediaViewer processes all thumbnails on the page even when it's supposedly disabled.

I do not like that MV preprocesses all images on load (I think it's unnecessary, whether it's enabled or not) but that seems like a significant effort to change and I'm not sure it's worth it unless it is causing serious problems.

Jul 6 2019, 8:25 PM · MediaWiki-User-preferences, Multimedia, MediaViewer

Jul 1 2019

Alsee added a comment to T224797: Activate Structured Discussions/Flow as a Beta feature on ckbwiki.

I can't find the task number at the moment, but I believe a different request to activate Flow was recently declined due to the early stage outcome of the Talk_Page_Consultation, and the decision to shift direction to enhancements for existing talk pages instead of Flow. Assuming new deployments have indeed been suspended, I think an appropriate update should be made at MediaWiki:Request_Structured_Discussions_on_a_page.

Jul 1 2019, 10:35 PM · Wikimedia-Site-requests, Growth-Team, StructuredDiscussions

May 19 2019

Alsee added a comment to T10681: Group changes across days in enhanced rc.

(Edit: I'm not sure whether this task covers the watchlist. I'm referring mainly to watchlist below)

May 19 2019, 3:51 AM · Growth-Team, MediaWiki-Watchlist, MediaWiki-Recent-changes

May 7 2019

Alsee updated subscribers of T218820: Ensure CTRL-V paste works as expected in text editing mode.

@JTannerWMF or anyone, if you are interested in Discussion/Analysis input from the community then I'd be happy to help. I'm confident what the result will be, but I can easily organize feedback from EnWiki and, if needed, other English wikis.

May 7 2019, 3:36 PM · VisualEditor-CopyPaste, VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor

Apr 27 2019

Alsee added a comment to T210281: Find a better way to highligth letters then bold.

Oh yeah, I forgot reflow. Most cases would be negligible, but hitting an uncommon big reflow might be unpleasant. I think it would probably be better to just apply the darkened background to the relevant backlink, without changing the size of anything. Is there anything holding back a styling change?

Apr 27 2019, 7:35 PM · WMDE-Design, Cite, Design, TCB-Team

Apr 18 2019

Alsee added a comment to T210281: Find a better way to highligth letters then bold.

Don't add any extra padding on the letters, except perhaps on the single letter being highlighted.

Apr 18 2019, 12:40 AM · WMDE-Design, Cite, Design, TCB-Team

Apr 9 2019

Alsee added a comment to T119365: Enable Flow for testing on Hungarian Wikipedia.

@Aklapper Thanks for confirming what I said. If the HuWiki discussion is revived it may be helpful. Extra thanks for reminding me about the link to configuration changes. That link should definitely be included if there are ever any more discussions activate Flow anywhere. Some people might find it hard to believe the Foundation would be so unwilling or unable to roll back deployment of the software if a trial-deployment ends badly.

Apr 9 2019, 7:38 AM · Growth-Team, User-Tgr, MW-1.27-release (WMF-deploy-2016-03-08_(1.27.0-wmf.16)), Patch-For-Review, Wikimedia-Site-requests, StructuredDiscussions, Collaboration-Team-Triage

Apr 8 2019

Alsee added a comment to T119365: Enable Flow for testing on Hungarian Wikipedia.

@Tgr your goal is good, however during the Uninstall-Flow-from-Commons incident (T186463), the Foundation determined that creating even a single Flow topic on a wiki leaves the wiki in a state where Flow can no longer be easily or safely uninstalled. The Flow extension is dangerously defective or incomplete, lacking procedures to safely clean up the logs or other content left behind if even one post is created (T188806). Due to this issue the software has been uninstalled from all wikis do not have any existing Flow content (T188812).

Apr 8 2019, 1:59 AM · Growth-Team, User-Tgr, MW-1.27-release (WMF-deploy-2016-03-08_(1.27.0-wmf.16)), Patch-For-Review, Wikimedia-Site-requests, StructuredDiscussions, Collaboration-Team-Triage

Mar 20 2019

Alsee created T218821: Ensure CTRL-V paste works as expected in text editing mode.
Mar 20 2019, 8:31 PM

Feb 27 2019

Alsee added a comment to T216837: Edit conflict preview not working on big pages.

I believe I just ran into this problem as well. I'd just like to note surprise at 2000 bytes being described as a big. At EnWiki that would be considered an extremely short page.

Feb 27 2019, 7:09 PM · MW-1.34-notes (1.34.0-wmf.3; 2019-04-30), Patch-For-Review, WMDE-QWERTY-Sprint-2019-04-17, TCB-Team, Two-Column-Edit-Conflict-Merge

Nov 21 2018

Alsee added a comment to T194945: Infobox overlaps with text, prevents editing the latter..

(just imagine that instead of <nowiki />, the template had foo there: it would become a part of the first paragraph of the page).

Excellent example, I was going to raise that case myself. It's a pretty simple and obvious thing we might do at any time. We expect (and need) to be able to edit the plaintext after the template. Any editor that can't edit plaintext is clearly broken, regardless of explanations for why it is broken.

Nov 21 2018, 10:08 AM · Parsoid, VisualEditor

Oct 25 2018

Alsee added a comment to T193665: Don't show the loading bar on the 2017 Wikitext editor for the first 750ms.

Previous tests I ran on VE timings with online website test sites, over a year ago, were under reporting by upwards of 20 or 30 seconds. Improvements may have improved the times, but it's not merely an issue of not counting some fixed initial page load time. The time being reported was close to half of actual time.

Oct 25 2018, 1:48 PM · VisualEditor, Patch-For-Review, VisualEditor-MediaWiki-2017WikitextEditor
Alsee added a comment to T91683: Allow editors control of the page image.

Randomization wouldn't be much of an improvement. At minimum it still hurts us when some people think we aligned with one candidate and other people think we aligned with another candidate. I'll also note that the infobox may contain five or more candidates, some of whom are extremely fringe candidate with no chance of winning. We could literally select a Nazi.

Oct 25 2018, 12:43 PM · Readers-Web-Backlog (Needs Product Owner Decisions), Readers-Community-Engagement, PageImages
Alsee added a comment to T91683: Allow editors control of the page image.

Serious problem case: Articles on upcoming elections may contain an image of each candidate. Page image grabs one political-candidate photo and uses it as the image for the election itself. Yikes!

Oct 25 2018, 12:41 AM · Readers-Web-Backlog (Needs Product Owner Decisions), Readers-Community-Engagement, PageImages
Alsee added a comment to T193665: Don't show the loading bar on the 2017 Wikitext editor for the first 750ms.

@Deskana I promise that I did not deliberately omit information. I recall being concerned that my post was already too long, and my main focus was whether the graph was accurate.

Oct 25 2018, 12:05 AM · VisualEditor, Patch-For-Review, VisualEditor-MediaWiki-2017WikitextEditor

Oct 18 2018

Alsee added a comment to T169441: Spike: Page Curation should create a new AfD discussion page if one already exists [8 hours].

Note: For assorted reasons, there occasionally gaps in the (Nth nomination) sequence. If you look at Gay Nigger Association of America (22nd nomination), no pages exist at 3rd 4th 10th 11th 19th 20th or 21st. I'm not sure if Twinkle would create a new nomination at the first open slot (3rd), or if it's smart enough to create the new page at 23rd. Creating the new page at 23rd would definitely be preferable. It's probably worth checking the Twinkle code to see if it contains a solution for this, as well as checking whether it reveals any other corner cases or implementation details we've overlooked.

Oct 18 2018, 2:46 AM · Community-Tech (Kanban (Q1 2019-20)), Growth-Team, Collaboration-Team-Triage, PageCuration

Oct 17 2018

Alsee added a comment to T193665: Don't show the loading bar on the 2017 Wikitext editor for the first 750ms.

@Niharika I think I can help clear up the discrepancy between the slide you saw and why "Most people on wiki however have this 'impression' of how 2017 wikitext editor and VE are slow in general".

Oct 17 2018, 10:36 AM · VisualEditor, Patch-For-Review, VisualEditor-MediaWiki-2017WikitextEditor

Oct 11 2018

Alsee updated the task description for T206735: New Page Feed filter-popup can go partially inaccessible off screen.
Oct 11 2018, 5:20 AM · Growth-Team, PageCuration, English-Wikipedia-New-Pages-Patrol
Alsee updated the task description for T206735: New Page Feed filter-popup can go partially inaccessible off screen.
Oct 11 2018, 5:18 AM · Growth-Team, PageCuration, English-Wikipedia-New-Pages-Patrol
Alsee created T206735: New Page Feed filter-popup can go partially inaccessible off screen.
Oct 11 2018, 5:18 AM · Growth-Team, PageCuration, English-Wikipedia-New-Pages-Patrol

Oct 3 2018

Alsee added a comment to T62493: StructuredDiscussions posts are not indexed in builtin search.

The way Flow splits a page into a multitude of independent objects is a notable issue. It's common to try to find something based on fragments that come from different comments or different parts of the page. Hopefully this will help answer some of the questions asked in this task. Fragments of a search may include any or all of the following:

  • "noticeboard" matches in page title
  • "dispute resolution" matches in board description
  • "foo" matches in topic title
  • "bar" matches in a comment
  • "johndoe" matches author of a different comment
  • "january" matches in the timestamp of a different comment
  • "baz" matches in topic summary
  • "insource:spammer.com" match hidden within a comment, in the board description, in the topic summary, in the topic title, in a username. An insource search could credibly match in the timestamp, although I find it hard to picture a use case requiring insource while wanting flow_timestamp hits.
  • Plus anything I missed.
Oct 3 2018, 4:48 PM · Growth-Team, Collaboration-Community-Engagement, Collaboration-Team-Triage, StructuredDiscussions

Sep 27 2018

Alsee added a comment to T169441: Spike: Page Curation should create a new AfD discussion page if one already exists [8 hours].

The RFC currently has 10 responses at 80% Oppose. There's little chance it will turn the other way.

Sep 27 2018, 11:07 AM · Community-Tech (Kanban (Q1 2019-20)), Growth-Team, Collaboration-Team-Triage, PageCuration

Sep 17 2018

Alsee added a comment to T204457: Incoherent styling of number on a list in bold when part of one item in the list is not bold.

the input is invalid.

Sep 17 2018, 3:07 AM · MediaWiki-Parser

Sep 16 2018

Alsee updated the task description for T204457: Incoherent styling of number on a list in bold when part of one item in the list is not bold.
Sep 16 2018, 7:15 PM · MediaWiki-Parser
Alsee created T204457: Incoherent styling of number on a list in bold when part of one item in the list is not bold.
Sep 16 2018, 6:58 PM · MediaWiki-Parser

Sep 9 2018

Alsee added a comment to T193728: Address concerns about perceived legal uncertainty of Wikidata .

There is a very serious error pervading this discussion. Everyone is working on the presumption that Wikidata is importing pure facts. This is false. Wikidata often imports creative works of authorship.

Sep 9 2018, 12:44 AM · WMF-Legal, Wikidata

Aug 25 2018

Alsee added a comment to T154843: New Wikitext Editor: Major improvement to load time and preview time.

Visual Editor is a resource hog, particularly on large pages, regardless of whether it's in wikitext mode or not. It maxes out the CPU and I suspect overloads memory. (I have 6 gig RAM BTW.)

Aug 25 2018, 1:02 AM · Performance Issue, VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor, VisualEditor-MediaWiki, Epic

Aug 23 2018

Alsee added a comment to T197525: Let users sort results by time (older or newer results).

Prefer Recent is interesting, but it's no help for key use cases. If I know a discussion happened in approximately May 2016 and there are thousands of search hits, I can't find it.

Aug 23 2018, 7:27 PM · MW-1.34-notes (1.34.0-wmf.14; 2019-07-16), User-notice, Wikimedia-Hackathon-2019, Advanced-Search, TCB-Team
Restricted Application added a project to T160446: Kill the edit threshold notifications (other than 1st): Growth-Team.
Aug 23 2018, 7:09 PM · Growth-Team, good first bug, Collaboration-Team-Triage, Notifications
Alsee added a comment to T169924: Option to disable notifications about 1st, 10th, etc. edit ("You made your <milestone> edit!").

We are going to wait a little bit as we continue to learn about how these notifications impact new users.

Aug 23 2018, 6:54 PM · MW-1.34-notes (1.34.0-wmf.3; 2019-04-30), User-notice, Patch-For-Review, Growth-Team (Current Sprint), Notifications
Alsee added a comment to T85847: Grant editcontentmodel right to all logged in users.

I suggest this task be closed. If necessary any current use cases can be addressed in a more narrow fashion. Per Harej, a non-default model might be created via workflow rather than modifying an existing page, or we could narrowly allow swapping Talk pages between wikitext and Flow, or admins can grant a permission by-need-and-approval (like TemplateEditor).

Aug 23 2018, 3:42 PM · Community-consensus-needed, MW-1.28-release (WMF-deploy-2016-09-13_(1.28.0-wmf.19)), MW-1.28-release-notes, MW-1.27-release-notes, MW-1.27-release (WMF-deploy-2016-03-01_(1.27.0-wmf.15)), Patch-For-Review, MediaWiki-ContentHandler

Aug 22 2018

Alsee added a comment to T199057: Changing indentation of a comment which already included broken HTML causes grossly inconsistent page results.

@Legoktm the WMF has concluded that it would be harmful to apply HTLM semantics to a tag wrapping a list. So instead of wandering off topic into generalisms, I'm happy to focus on the bug at hand.

Aug 22 2018, 6:31 PM · RemexHtml, MediaWiki-Parser
Alsee added a comment to T199057: Changing indentation of a comment which already included broken HTML causes grossly inconsistent page results.

! In T199057#4521165, @ssastry wrote:
this is standard HTML5 behavior

Aug 22 2018, 3:56 PM · RemexHtml, MediaWiki-Parser

Aug 21 2018

Alsee added a comment to T199057: Changing indentation of a comment which already included broken HTML causes grossly inconsistent page results.

@ssastry, I've re-titled the bug to try and focus on the actual bug. Please don't get distracted by the tag details. That is merely the known example-case which exposes this new and bad parser behavior.

Aug 21 2018, 10:19 PM · RemexHtml, MediaWiki-Parser
Alsee renamed T199057: Changing indentation of a comment which already included broken HTML causes grossly inconsistent page results from Four or more colons at beginning of line breaks markup, spilling it across the entire page to Changing comment indentation level causes grossly inconsistent page results.
Aug 21 2018, 9:28 PM · RemexHtml, MediaWiki-Parser

Aug 20 2018

Alsee added a comment to T199057: Changing indentation of a comment which already included broken HTML causes grossly inconsistent page results.

The problem also appears in Chrome 67.0.3396.99.

Aug 20 2018, 8:15 AM · RemexHtml, MediaWiki-Parser

Aug 19 2018

Alsee added a comment to T199057: Changing indentation of a comment which already included broken HTML causes grossly inconsistent page results.

@Izno switching to Remex was deliberate, however I don't think it could be deliberate to have radically different, confusing, and broken differences in behavior between three colons and four colons. Independent of any lint issues, is there any reason that this bizarre behavior should not be fixed?

Aug 19 2018, 6:40 PM · RemexHtml, MediaWiki-Parser

Jul 15 2018

Restricted Application added a project to T173011: Explore in-context discussions on articles: Growth-Team.

The mock-up illustration creates a very over-optimistic impression of how well this would work in reality. The sample comments do not resemble real world content.

Jul 15 2018, 11:19 AM · Growth-Team, StructuredDiscussions, Collaboration-Team-Triage, Wikimania-Hackathon-2017

Jul 8 2018

Alsee added a comment to T197525: Let users sort results by time (older or newer results).

@Lea_WMDE I'll make up a typical example search I'd use. Here's a search for "short description" in namespace Wikipedia or Wikipedia talk.

Jul 8 2018, 4:22 PM · MW-1.34-notes (1.34.0-wmf.14; 2019-07-16), User-notice, Wikimedia-Hackathon-2019, Advanced-Search, TCB-Team
Alsee renamed T199057: Changing indentation of a comment which already included broken HTML causes grossly inconsistent page results from Four colons at beginning of line breaks markup, spilling it across the entire page to Four or more colons at beginning of line breaks markup, spilling it across the entire page.
Jul 8 2018, 2:12 PM · RemexHtml, MediaWiki-Parser
Alsee created T199057: Changing indentation of a comment which already included broken HTML causes grossly inconsistent page results.
Jul 8 2018, 2:02 PM · RemexHtml, MediaWiki-Parser

Jun 18 2018

Alsee added a comment to T197525: Let users sort results by time (older or newer results).

I've been considering requesting something like this myself, but I realize it may be difficult. I expect the primary use case is searching talk pages. I assume using the date of an edit itself is infeasible, but maybe catching standard signature timestamps could be viable?

Jun 18 2018, 5:36 AM · MW-1.34-notes (1.34.0-wmf.14; 2019-07-16), User-notice, Wikimedia-Hackathon-2019, Advanced-Search, TCB-Team

May 20 2018

Alsee added a comment to T193857: Support 'noreplace' keyword in {{SHORTDESC}}.

@Pbsouthwood, I also originally thought the simple and obvious answer was to use the first description. I definitely see some ugly and backwards aspects of using noreplace. However on deep thought, noreplace is probably the right answer. Consider an infobox that tries to add an automatic description, and an editor adds a short description template somewhere below that infobox. Yes yes, that's unthinkably gross and bizarre. The reason I did think of it is because I've already seen it. The description was either below the infobox, or it was below the infobox & below the lead. Gross... but it's a wiki.... we gotta expect stuff like that. If we use "first description" then we'd get the infobox-auto-description. If we use noreplace then the human description can be given priority. I think noreplace is probably what we want, even if it is a bit ugly.

May 20 2018, 12:00 AM · MW-1.32-notes (WMF-deploy-2018-06-12 (1.32.0-wmf.8)), Patch-For-Review, Product-Infrastructure-Team-Backlog (Kanban), MediaWiki-extensions-WikibaseClient, Wikidata

May 11 2018

Alsee added a comment to T162474: Revisit the app restriction on non-free images in non-article contexts.

Hi @JMinor. I'm the one who originally suggested enabling non-free images for PagePreviews, and I organized the community endorsement for it. However it doesn't look like non-free images will work in the two cases you described.

May 11 2018, 9:19 PM · Wikipedia-iOS-App-Backlog

Apr 27 2018

Alsee renamed T187070: Investigate the performance of visual diffs when user pastes a huge, complex article into another one from Investigate the performance of visual diffs when user pastes a huge, complex article into another one to Investigate the performance of visual diffs for large diffs.
Apr 27 2018, 5:20 AM · MW-1.31-release-notes (WMF-deploy-2018-02-27 (1.31.0-wmf.23)), VisualEditor (Current work), Performance Issue, VisualEditor-VisualDiffs
Alsee added a comment to T187070: Investigate the performance of visual diffs when user pastes a huge, complex article into another one.

Visual Diff is still completely failing on large diffs. Tested in three browsers on two computers.

Apr 27 2018, 5:17 AM · MW-1.31-release-notes (WMF-deploy-2018-02-27 (1.31.0-wmf.23)), VisualEditor (Current work), Performance Issue, VisualEditor-VisualDiffs

Mar 17 2018

Alsee added a comment to T186463: Uninstall Flow from Commons.
Mar 17 2018, 2:00 PM · Growth-Team, Commons, Patch-For-Review, Wikimedia-Site-requests, Collaboration-Team-Triage, StructuredDiscussions

Mar 15 2018

Alsee added a comment to T153306: Have Show preview and Review your changes more directly accessible in the New Wikitext Editor.

@Dvorapa, the proposed change doesn't fix the problem. You're still going to have an unending stream of people filing the same bug report.

Mar 15 2018, 1:29 PM · VisualEditor, Patch-For-Review, Design, VisualEditor-MediaWiki-2017WikitextEditor

Mar 14 2018

Alsee added a comment to T153306: Have Show preview and Review your changes more directly accessible in the New Wikitext Editor.

If this is deployed as in the above screenshot there will be an unending stream of complaints that the preview button needs to be more directly accessible.

Mar 14 2018, 4:04 PM · VisualEditor, Patch-For-Review, Design, VisualEditor-MediaWiki-2017WikitextEditor
Alsee added a comment to T57370: [Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing.

@Deskana ah good. I posted the info here when I couldn't find any mention or task of the 'switching editors' issue. Should the new task be added to the Related Objects task graph?

Mar 14 2018, 3:23 PM · User-notice, MW-1.31-release-notes (WMF-deploy-2018-03-06 (1.31.0-wmf.24)), VisualEditor (Current work), Community-Wishlist-Survey-2017, Community-Tech, Front-end-Standards-Group, Epic, VisualEditor-MediaWiki
Alsee added a comment to T57370: [Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing.

@Aklapper are you kidding? This is clearly a serious bug in the new code, and it directly relates to the discussion in the previous dozen comments.

Mar 14 2018, 2:45 PM · User-notice, MW-1.31-release-notes (WMF-deploy-2018-03-06 (1.31.0-wmf.24)), VisualEditor (Current work), Community-Wishlist-Survey-2017, Community-Tech, Front-end-Standards-Group, Epic, VisualEditor-MediaWiki

Mar 13 2018

Alsee added a comment to T57370: [Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing.

Report from VisualEditor/Feedback:
Whenever I switch from VE to the source editor, and then switch back to VE, it literally deletes the changes I made with the source editor, and then it gives me a ridiculous message saying the following:
"Changes recovered Your unsaved changes have been automatically recovered."
Well, thanks, but how do I get rid of this? Now I can't use VE properly anymore.

Mar 13 2018, 10:08 PM · User-notice, MW-1.31-release-notes (WMF-deploy-2018-03-06 (1.31.0-wmf.24)), VisualEditor (Current work), Community-Wishlist-Survey-2017, Community-Tech, Front-end-Standards-Group, Epic, VisualEditor-MediaWiki

Mar 7 2018

Alsee added a comment to T95543: Obviate the need for wikis' wrapper and functionality-replacement templates.

If you want no-one wants (or needs) these templates let's examine what that means. There is discussion of putting the new #shortdesc keyword in a template. Here's a list of functionality currently planned, or under consideration:

Mar 7 2018, 6:42 PM · VisualEditor, Contributors-Team

Mar 6 2018

Alsee updated subscribers of T188577: Add a config setting making all Flow boards read-only.
Mar 6 2018, 5:58 PM · Growth-Team, MW-1.31-release-notes (WMF-deploy-2018-03-13 (1.31.0-wmf.25)), Patch-For-Review, StructuredDiscussions, Collaboration-Team-Triage
Alsee added a comment to T188806: create a Flow uninstall script.

@TheDJ thank you.

rewriting stuff introduces significant risks when the system is complex

Mar 6 2018, 5:45 PM · Growth-Team, Commons, StructuredDiscussions, Collaboration-Team-Triage

Mar 4 2018

Alsee added a comment to T186463: Uninstall Flow from Commons.

+1 to @Krenair's history/logs/etc. be converted where possible to be in a core-native format (wikitext).

Mar 4 2018, 11:13 PM · Growth-Team, Commons, Patch-For-Review, Wikimedia-Site-requests, Collaboration-Team-Triage, StructuredDiscussions
Alsee added a comment to T154844: New Wikitext Editor: Previews should use the article-view rendering engine.

I'm copying related concerns submitted at 2017 wikitext editor/Feedback:

  • Accidental misspelling of a category's name is not seen in the preview.
  • List of used templates won't get updated.
  • The effect of {{lowercase title}} or other title-changing code cannot be previewed.
  • Category changes resulting from addition of new templates do not appear in the preview. For example, try inserting a {{Use British English}} template in English Wikipedia.
Mar 4 2018, 7:42 PM · VisualEditor, VisualEditor-MediaWiki-2017WikitextEditor

Mar 3 2018

Alsee awarded T188812: Uninstall Flow on all wikis where it has zero topics a Love token.
Mar 3 2018, 11:50 PM · Growth-Team, User-notice-collaboration, Patch-For-Review, Collaboration-Team-Triage, Technical-Debt, Wikimedia-Site-requests, StructuredDiscussions
Jeff_G awarded T186463: Uninstall Flow from Commons a Mountain of Wealth token.
Mar 3 2018, 7:11 PM · Growth-Team, Commons, Patch-For-Review, Wikimedia-Site-requests, Collaboration-Team-Triage, StructuredDiscussions
Alsee added a comment to T188806: create a Flow uninstall script.

Just to toss out another idea, is it possible to delete or sanitize the objectionable log entries?

Mar 3 2018, 9:04 AM · Growth-Team, Commons, StructuredDiscussions, Collaboration-Team-Triage
Alsee added a comment to T186463: Uninstall Flow from Commons.
Mar 3 2018, 6:32 AM · Growth-Team, Commons, Patch-For-Review, Wikimedia-Site-requests, Collaboration-Team-Triage, StructuredDiscussions
Alsee added a comment to T188577: Add a config setting making all Flow boards read-only.

Building a superprotect for Flow is a really really REALLY bad idea.

Mar 3 2018, 6:10 AM · Growth-Team, MW-1.31-release-notes (WMF-deploy-2018-03-13 (1.31.0-wmf.25)), Patch-For-Review, StructuredDiscussions, Collaboration-Team-Triage
Alsee added a comment to T188577: Add a config setting making all Flow boards read-only.
Mar 3 2018, 4:12 AM · Growth-Team, MW-1.31-release-notes (WMF-deploy-2018-03-13 (1.31.0-wmf.25)), Patch-For-Review, StructuredDiscussions, Collaboration-Team-Triage
Alsee closed T188577: Add a config setting making all Flow boards read-only as Invalid.
Mar 3 2018, 4:11 AM · Growth-Team, MW-1.31-release-notes (WMF-deploy-2018-03-13 (1.31.0-wmf.25)), Patch-For-Review, StructuredDiscussions, Collaboration-Team-Triage

Mar 2 2018

Alsee added a comment to T153306: Have Show preview and Review your changes more directly accessible in the New Wikitext Editor.

Adding another complaint reported at Mediawiki 2017 wikitext editor/Feedback.

Mar 2 2018, 4:18 AM · VisualEditor, Patch-For-Review, Design, VisualEditor-MediaWiki-2017WikitextEditor

Mar 1 2018

Alsee added a comment to T153315: Pasting annotated wikitext results in double encoding and therefore <nowiki>s.

Firstly, please provide diffs for the offending edits that have nowiki tags in them, as I can't know what's going wrong without them.

Mar 1 2018, 9:48 PM · Regression, User-Ryasmeen, MW-1.30-release-notes (WMF-deploy-2017-07-11_(1.30.0-wmf.9)), VisualEditor-CopyPaste, VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor
Alsee added a comment to T186463: Uninstall Flow from Commons.

@Aklapper I took note of your request that I not ping you. I explicitly avoided doing so. However you just pinged me. And pinged me with unreasonable criticism to boot.

Mar 1 2018, 1:06 AM · Growth-Team, Commons, Patch-For-Review, Wikimedia-Site-requests, Collaboration-Team-Triage, StructuredDiscussions

Feb 28 2018

Alsee added a comment to T187690: Copy-pasting section headings emits JS error and doesn't let you save.

I tried testing the bug mentioned just above, at this revision of the EnWiki article Sonic_X-treme.

Feb 28 2018, 6:18 PM · MW-1.31-release-notes (WMF-deploy-2018-03-13 (1.31.0-wmf.25)), VisualEditor (Current work), VisualEditor-CopyPaste

Feb 27 2018

Alsee added a comment to T186463: Uninstall Flow from Commons.

@DannyH thanks for replying. I can hang on for a response "by the end of this week". However I do have to pointedly note that you were also non-responsive on why the task was halted and what is being discussed.

Feb 27 2018, 10:21 PM · Growth-Team, Commons, Patch-For-Review, Wikimedia-Site-requests, Collaboration-Team-Triage, StructuredDiscussions

Feb 23 2018

Alsee added a comment to T186463: Uninstall Flow from Commons.

@Mattflaschen-WMF @Aklapper or anyone else:
The RFC was closed on January 26. I'm planning to post a 'one month update' to the Village Pump RFC at Commons, on or around Feb 26.

Feb 23 2018, 11:12 AM · Growth-Team, Commons, Patch-For-Review, Wikimedia-Site-requests, Collaboration-Team-Triage, StructuredDiscussions

Feb 21 2018

Alsee added a comment to T184000: Magic word on English WP to override display of Wikidata short description.

According to the API info, it looks like a pageterms API call is doing the correct thing, returning a Wikidata value. That probably shouldn't be broken. It appears the issue is the bits of code making the API calls. They are explicitly requesting Wikidata values.

Feb 21 2018, 4:44 PM · MW-1.32-notes (WMF-deploy-2018-06-12 (1.32.0-wmf.8)), Wikipedia-iOS-App-Backlog, MW-1.31-release-notes (WMF-deploy-2018-03-13 (1.31.0-wmf.25)), Product-Infrastructure-Team-Backlog (Kanban), MediaWiki-extensions-WikibaseClient, Wikidata, Community-Tech
Alsee added a comment to T184000: Magic word on English WP to override display of Wikidata short description.

@Tgr thanks for catching my sloppy hatmaking example. Hatmaking is an illustration for a completely different serious bug - interwiki links are badly broken. 75% of the interwiki links are missing from the English article , and 75% of languages with an article are missing interwiki links to English version.

Feb 21 2018, 9:09 AM · MW-1.32-notes (WMF-deploy-2018-06-12 (1.32.0-wmf.8)), Wikipedia-iOS-App-Backlog, MW-1.31-release-notes (WMF-deploy-2018-03-13 (1.31.0-wmf.25)), Product-Infrastructure-Team-Backlog (Kanban), MediaWiki-extensions-WikibaseClient, Wikidata, Community-Tech

Feb 20 2018

Alsee added a comment to T184000: Magic word on English WP to override display of Wikidata short description.

I'm not familiar with all of the API issues, but if this helps:
The magicword Shortdesc: is actually a description of the article. The Wikidata label is a description of the Wikidata item. Someone thought Wikidata labels could conveniently be re-used as if they were article descriptions. But they aren't article descriptions.

Feb 20 2018, 8:16 PM · MW-1.32-notes (WMF-deploy-2018-06-12 (1.32.0-wmf.8)), Wikipedia-iOS-App-Backlog, MW-1.31-release-notes (WMF-deploy-2018-03-13 (1.31.0-wmf.25)), Product-Infrastructure-Team-Backlog (Kanban), MediaWiki-extensions-WikibaseClient, Wikidata, Community-Tech

Feb 16 2018

Alsee added a comment to T186463: Uninstall Flow from Commons.

@Zoranzoki21, thanks. Is the block potentially related to this task???!?

Feb 16 2018, 1:23 PM · Growth-Team, Commons, Patch-For-Review, Wikimedia-Site-requests, Collaboration-Team-Triage, StructuredDiscussions
Alsee added a comment to T186463: Uninstall Flow from Commons.

@Zoranzoki21 thanks for so quickly addressing this task. A four minute response time and a 15 minute gerrit submission was impressive. Could you provide an update on why your efforts were halted? As well as if or when the task expected to be completed?

Feb 16 2018, 8:35 AM · Growth-Team, Commons, Patch-For-Review, Wikimedia-Site-requests, Collaboration-Team-Triage, StructuredDiscussions

Feb 14 2018

Alsee added a comment to T184000: Magic word on English WP to override display of Wikidata short description.

@DannyH, if you dispute the close result then this is not the way to handle the situation.

Feb 14 2018, 11:07 AM · MW-1.32-notes (WMF-deploy-2018-06-12 (1.32.0-wmf.8)), Wikipedia-iOS-App-Backlog, MW-1.31-release-notes (WMF-deploy-2018-03-13 (1.31.0-wmf.25)), Product-Infrastructure-Team-Backlog (Kanban), MediaWiki-extensions-WikibaseClient, Wikidata, Community-Tech
Alsee updated the task description for T184000: Magic word on English WP to override display of Wikidata short description.
Feb 14 2018, 11:06 AM · MW-1.32-notes (WMF-deploy-2018-06-12 (1.32.0-wmf.8)), Wikipedia-iOS-App-Backlog, MW-1.31-release-notes (WMF-deploy-2018-03-13 (1.31.0-wmf.25)), Product-Infrastructure-Team-Backlog (Kanban), MediaWiki-extensions-WikibaseClient, Wikidata, Community-Tech
Alsee updated subscribers of T187285: Magic word on English WP to replace Wikidata short descriptions.

@MZMcBride, I'd like to first note that this task is not about "what I want". Half of the text here is copied from T184000 written by @DannyH. The other half reflects an RFC community consensus. In fact I supported DannyH's version during the RFC. I am submitting the consensus result on behalf of the community.

Feb 14 2018, 7:20 AM · MediaWiki-extensions-WikibaseClient, Wikidata
Alsee added a comment to T187285: Magic word on English WP to replace Wikidata short descriptions.

Not in scope of this task:

  1. It's hard for EnWiki editors to see vandalism or changes to Wikidata content:
    1. Showing Wikidata changes on EnWiki watchlists is not in scope. Locally defined descriptions resolves this issue natively.
  2. Editing Wikidata content requires going to another site:
    1. Providing a remote-editing UI to modify Wikidata content from the Wikipedia site is not in scope. Locally defined descriptions resolves this issue natively.
  3. Edits to Wikidata bypass EnWiki page protection:
    1. Removing Wikidata-Admin userrights to add/remove edit-protection on Wikidata English-descriptions and effectively assigning these rights to EnWiki Admins is not in scope. Locally defined descriptions resolves this issue natively.
  4. Wikidata content is subject to Wikidata policies and Administrative enforcement:
    1. Removing Wikidata-Admin userrights to block EnWiki users&Admins from editing Wikidata English-descriptions and assigning these rights to EnWiki Admins is not in scope. Locally defined descriptions resolves this issue natively.

(Any alternate proposal for the above item(s) should be sure to include all four.)

Feb 14 2018, 5:25 AM · MediaWiki-extensions-WikibaseClient, Wikidata
Alsee added a comment to T184000: Magic word on English WP to override display of Wikidata short description.

Closed as invalid. There is no request for this task.

Feb 14 2018, 5:24 AM · MW-1.32-notes (WMF-deploy-2018-06-12 (1.32.0-wmf.8)), Wikipedia-iOS-App-Backlog, MW-1.31-release-notes (WMF-deploy-2018-03-13 (1.31.0-wmf.25)), Product-Infrastructure-Team-Backlog (Kanban), MediaWiki-extensions-WikibaseClient, Wikidata, Community-Tech