Moving this to our Q3 column so we can assess with our other maintenance tasks for the quarter and decide whether we have time in balance with our feature work to prioritize this task.

We believe this is likely the responsibility of the core platform team. Let us know if you need any support from us.

We believe this is likely the responsibility of the core platform team. Let us know if you need any support from us.

@phuedx could you clarify what your concerns about this approach are?

In T189569#5584691, @kaldari wrote:

There are two easy solutions:

• Make Getting Started temporarily suppress the VE dialog by adding "vehidebetadialog" to the query string. The user will still see it the next time they use the editor, so they won't be missing out on any info.
• Disable Getting Started entirely (until it can be updated to address this issue).

Can we just choose one of those?

I am David's manager, and I approve the business need for this access. Thank you!

In T224921#5292216, @Aklapper wrote:

@marcella: Could you please elaborate if the WMF Editing Team is responsible for the SpamBlacklist extension? Thanks.

I am David's manager and I confirm his business need for this access. Thank you!

Hi @Ryuch, could you provide us with more information on your working environment, particularly your input method and browser/browser version so that we can try to nail down what's happening. Thank you!

@DLynch can you add some information on why a user would assign an alias that is the same as the name field, and what the repercussions of that might be?

@Ryasmeen this looks like a separate issue--could you make a separate task for it? Thank you!