User talk:Aaron Liu

Welcome to Meta!

Hello, Aaron Liu. Welcome to the Wikimedia Meta-Wiki! This website is for coordinating and discussing all Wikimedia projects. You may find it useful to read our policy page. If you are interested in doing translations, visit Meta:Babylon. You can also leave a note on Meta:Babel or Wikimedia Forum if you need help with something (please read the instructions at the top of the page before posting there). Happy editing!

-- Meta-Wiki Welcome (talk) 21:56, 15 July 2015 (UTC)

Reminder to vote now to ratify the Wikimedia Movement Charter

You can find this message translated into additional languages on Meta-wiki. Please help translate to your language

Dear Wikimedian,

You are receiving this message because you previously voted in the 2021 Movement Charter Drafting Committee (MCDC) election.

This is a reminder that if you have not voted yet on the ratification of the final Wikimedia Movement Charter draft, please do so by July 9, 2024 at 23:59 UTC.

You can read the final text of the Wikimedia Movement Charter in your language. Following that, check on whether you are eligible to vote. If you are eligible, cast your vote on SecurePoll.

On behalf of the Charter Electoral Commission,

RamzyM (WMF) 15:24, 5 July 2024 (UTC)

Join us for “Many Tongues, One Movement: Voices Across Languages”!

Hello Aaron Liu,

We’re excited to invite you to an inspiring global virtual gathering: the first Capacity Exchange Translat-a-thon.

Together with Language Diversity Hub, the Capacity Exchange (CapX) team will host its first Translation Marathon dedicated to ensuring linguistic equity in access to this amazing tool aimed to connect Wikimedians.
If you enjoy contributing to Wikimedia projects through translating and adapting content into different languages, this event is for you! Join us in the celebration of the multilingual spirit of the Wikimedia Movement at an event where communities that contribute in diverse languages will be able to share local knowledge and collaborate across borders.
Many Tongues, One Movement: Voices Across Languages

• Date: December 6, 2025
• Time: 12 PM (UTC) - Check the event page for your local timezone
• Location: Online (Meta-Wiki + live session links)

Register for the Event here

If you can’t join the live event, you can still contribute to the translations! Edits will be counted for two weeks, until December 20th. And everyone who participates will receive a special badge to display on their CapX profiles.

Strengthen your collaboration through CapX

We invite you and your community to join the Capacity Exchange (CapX), a Wikimedia community-built platform for connecting, collaborating, and exchanging skills with peers across the movement.

CapX helps Wikimedians and organizations find each other, share expertise, and build stronger, more connected communities.

Whether you’re an individual contributor, a user group, a community initiative or an affiliate, CapX helps you grow through knowledge exchange.

Sign up to CapX

More information

→ Explore the CapX platform: capx.toolforge.org
→ Read: User Guide & FAQ
→ Watch: Meet the Capacity Exchange video
→ Join our Telegram community chat: CapX Telegram Group

If your community, usergroup or affiliate would like to have a CapX organization profile, please reach out at capx@wmnobrasil.org, and we’d be delighted to support you.

With warm regards,
Joris Darlington Quarshie
Outreach Facilitator,
Capacity Exchange Project – Wikimedia Brasil

MediaWiki message delivery (talk) 14:55, 13 November 2025 (UTC)

Sub-referencing feedback

Hi Aaron Liu, I just saw your signature at en:WP:WWUS [1] – I'm sorry if you felt that your feedback on sub-referencing (or that of other users) wasn't heard. Please let me know how you would have preferred our communication to be different.

We are aware that we probably can't match every user's individual preferences about sub-referencing, the feature is a result of many years iterating, getting community feedback and trying to balance the needs (and preferences in citation styles) of different communities with several technical challenges. We recently published a report about our learnings from piloting the feature on German Wikipedia (our first pilot wiki). We got a similar impression from pilot wikis that followed this year (e.g. Polish Wikipedia which already uses sub-referencing on 15k pages). Based on user feedback and feature adoption we're quite happy about the deployment process so far. But users who prefer different citation styles can of course always follow en:WP:CITEVAR.

And to avoid misunderstandings: We are maintaining our own wishlist as WMDE Technical Wishes (we're running a survey every 2 years on German Wikipedia). We also work on Community Wishlist requests, but if you feel that your feedback on sub-referencing wasn't heard, that's something we are very sorry about, but it probably shouldn't be blamed on the WMF.

Thanks for your feedback! Johannes Richter (WMDE) (talk) 14:10, 8 June 2026 (UTC)

Thanks for reaching out! I really appreciate the candid transparency :D

It mostly boils down to the (I believe) shared frustration at the great support for the old extends syntax being handwaved over in the "Moving forward" post. Aaron Liu (talk) 21:40, 8 June 2026 (UTC)

You're right, multiple users supported the extends-syntax, as we highlighted in our statement. As with any decision we reached out to the community and gathered feedback on our talk page as well as on village pumps across different projects. A majority of users supported our proposal to move forward with the new details-syntax to allow us to overcome some of the technical challenges with {{reflist}} and VisualEditor. It's one of the compromises we had to make in order to implement the feature. We believe that the new syntax still is a good sollution, even if it might feel unusual to some users. I'm sorry if our communication felt dismissive, that might be in part because it happend on the last day before I went on a hiatus for multiple months for personal reasons.

I noticed you've updated your WWUS signature, now mentioning the long-term wish to improve VisualEditor reference names. You might be interested in reading our proposal WMDE Technical Wishes/References/VisualEditor automatic reference names (we could implement one of the proposals or a combination of them, e.g. to improve the fallback if we can't generated a meaningful name). Please share your feedback in Talk:WMDE Technical Wishes/References/VisualEditor automatic reference names#Request for comment! Johannes Richter (WMDE) (talk) 05:50, 9 June 2026 (UTC)

I don't really see that majority in the discussions. I think that given a choice between using the details syntax so we could deploy this year and indefinitely postponing the deployment while working on VE and LDRs so that the extends syntax could be realized, enwiki editors would choose the latter. I don't wish to sound mean, and there's so much great work that WMDE is doing, but I'm pretty sure this is the majority mood on enwiki. See, for example, w:Wikipedia:Village pump (technical)/Archive 227#Sub-referencing coming in 2026? (not to imply that you haven't seen that discussion before).

I did read that, actually! It's great that WMDE is making all this progress while the WMF is still dragging its feat. Unfortunately I'm afraid I don't have anything to add . Aaron Liu (talk) 13:17, 11 June 2026 (UTC)

We shared our request for comment on the new syntax on village pumps across many wikis and got responses from ~10 dewiki community members in a discussion on German Wikipedia and ~20 community members from 10 different large Wikipedia language versions in a discussion on Metawiki. There were multiple users opposing or showing concerns about the proposed syntax, I believe probably ~40% (although we of course didn't just counted opinions, but also evaluated the reasons why people showed concern / opposed the proposal). Most users were concerned because they didn't like using "XML-style" attributes for wikitext (we've addressed this in our statement as well). Community adoption on pilot wikis like German Wikipedia (currently 8k articles using sub-referencing) or Polish Wikipedia (15k) shows that most wikitext editors are ok with the syntax, even if it feels unusual to some. I'm aware how some enwiki community members feel about it, although we also saw a number of editors (most recently in the enwiki community Discord server) asking us to consider speeding-up the deployment to English Wikipedia... I'm afraid we have to accept that we can't create the perfect solution for everyone (some users object to using sub-referencing regardless of the wikitext syntax, simply because they prefer sfn) – that's why CITEVAR exists.

Regarding VE auto ref names: Adding your support on the talk page (if you're supporting a change) would certainly help (and if you're not supporting a change, stating your opinion would be even more important). We are still evaluating the RfC and grateful for every user leaving their thoughts :) Johannes Richter (WMDE) (talk) 17:28, 11 June 2026 (UTC)

Web2Cit template paths

Hi @Aaron Liu! Thank you for being a Web2Cit contributor!

Some translation templates you have worked on may need attention. Could you help us fix them?

Translation templates should be based on specific webpages and ideally should have corresponding translation tests indicating the expected output. This is important for maintainability, so other contributors can understand why a template has been set in some way, and so the Web2Cit Monitor can detect when citations break.

We found some templates for paths that do not have a corresponding test. This is usually because the path is generic (i.e., not corresponding to a specific webpage of interest; e.g., / or /**), or simply because a translation test hasn't been defined for that path.

Here's a list of domain configurations you have contributed to, and corresponding template paths for which no tests have been defined. Other editors may have contributed to these files as well and they will or have been notified too.

To help us, for as many of these paths as you can, could you please make sure:

1. that it corresponds to a specific webpage of interest, and
2. that a corresponding translation test has been defined?

Domain	Template path
www.haaretz.com	/israel-news/culture/2016-05-17/ty-article/watch-the-new-israeli-made-coldplay-video/0000017f-f37f-d5bd-a17f-f77f71840000
www.theregister.com	/2010/10/12/graun_robbins_counterblast/

For the full list of domains affected, you can check our new Web2Cit Monitor Results with missing tests category.

Note that to help prevent this issue in the future, the templates editor has been updated to only accept paths that already have a test defined.

Please let me know if you have any questions and thank you again for your support!

Diegodlh (talk) 22:56, 21 June 2026 (UTC)

Hi, @Aaron Liu! I see you've fixed this. Thank you! We have 100% test coverage for these domains now. Great!! Diegodlh (talk) 21:49, 26 June 2026 (UTC)