User Talk: Ixtal

Server-side rendered snapshot of this editor's Wikipedia talk page discussions.

{{Wikipedia:TPS/watched/banner}}
{{ds/aware|blp|ps|gg|cc|aa2}}
{{user email|letmeknow}}

{{User:ClueBot III/ArchiveThis
| age=720
| archiveprefix=User talk:Ixtal/Archives/
| format=Y/F
| archivebox=yes
| box-advert=yes
}}

Guild of Copy Editors – June 2026 Newsletter

{| style="position: relative; margin-left: 2em; margin-right: 2em; padding: 0.5em 1em; background-color: #dfeff3; border: 2px solid #bddff2; border-color: rgba( 109, 193, 240, 0.75 ); border-radius: 8px; box-shadow: 8px 8px 12px rgba( 0, 0, 0, 0.7 );"

| <span style="font-size: 110%;">'''Guild of Copy Editors ↗ June 2026 Newsletter'''</span>

<div style="float:right; width: 75px; height: 60px;"></div>
<div style="position: absolute; top: -20px; right: -12px;">100px|link= ↗</div>
<hr style="border-bottom: 1px solid rgba( 109, 193, 240, 0.75 );" />
right|thumb ↗

Hello and welcome to the June 2026 newsletter, a quarterly-ish digest of Guild activities since April.

'''Election news:''' Nominations for the '''mid-year coordinator election''' ↗ ends at 23:59 on 15 June. Voting will last from 00:00 on 16 June to 23:59 on 30 June. Results will be announced on the election page.

'''April Blitz:''' 18 of the 21 editors who signed up for the '''April 2026 Copy Editing Blitz''' ↗ copy edited 122,993 words in 56 articles. Barnstars awarded are '''here''' ↗.

'''May Drive:''' 34 of the 66 editors who signed up for the May 2026 Backlog Elimination Drive ↗ copy edited 543,972 words in 211 articles. Barnstars awarded are '''here''' ↗.

'''June Blitz:''' Our '''June 2026 Copy Editing Blitz''' ↗ will start on 14 June and finish on 30 June. Barnstars awarded will be posted '''here''' ↗.

'''Progress report:''' As of 22:40, 11 June 2025 (UTC), GOCE copyeditors have completed 132 requests since 1 January, and the backlog stands at 1,691 articles.

Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators.

{{center
| <small>To discontinue receiving GOCE newsletters, please remove your name from our mailing list ↗.</small>
}}
|}

MediaWiki message delivery (talk) 22:57, 11 June 2026 (UTC)

The DCWC is back!

frameless|right|upright=0.8|The Developing Countries WikiContest Gold Belt Buckle ↗

Hey Ixtal, the Developing Countries WikiContest ↗ is back for a third year, and '''sign-ups are now open ↗'''! The contest will run from 1{{nbsp}}July to 30{{nbsp}}September, and the objective remains the same: improve as many articles relating to developing countries as you can to help fight systemic bias on Wikipedia ↗.

Thanks to everyone who answered the call for coordinators, and please welcome the new faces on the coordinator team: the 2024 Gold Belt Buckle winner {{user|Generalissima}}; and the record-holder for most India-related submissions in 2024, {{user|Magentic Manifestations}}! Following feedback from last year, adjustments have been made to the scoring rules ↗; discussion can be found on the contest talk page ↗.

If you have any questions, please leave a message on the contest talk page or contact one of the coordinators: {{user|Arconning}}, {{user|Generalissima}}, {{user|Magentic Manifestations}}, {{user|sawyer777}}, or {{user|TechnoSquirrel69}}. <small>(To unsubscribe from these updates, remove yourself from this list ↗. Sent via MediaWiki message delivery.)</small> <span class="nowrap">—<span style="color: #0b541f;">'''TechnoSquirrel69'''</span></span> <small>(<span style="color: #0b541f;">'''talk'''</span>)</small> 16:00, 20 June 2026 (UTC)
{{clear|left}}

Arb Motion Question for SilverLocust

Hi, {{u|SilverLocust}}! I saw that you closed this motion ↗. Since the latter part (from what I gather) seems to affect the remedy Arbcom enacted regarding my conduct in the WP:ARBSCE ↗ case, I thought I'd ask and get some more clarity on what exactly this changes for me. The community notes section devolved into squabbling that means it is probably a bad idea to ask in that page since it might be seen by editors I have had disagreements with over the aforementioned case as an attempt to reignite our dispute and I'd rather avoid any unnecessary drama over a long-past issue. I'm asking in my talk page and not yours since this might be useful and easier to find if my behavior is being reviewed in the future, hope that's fine. {{u|ScottishFinnishRadish}}, as a current arb who was an involved party in that arb case, if SL's busy, I'd appreciate you clarifying in {{their|SilverLocust}}'s stead. — ♠ Ixtal <sup>( T / C ↗ ) </sup> ⁂ <small> Non nobis solum ↗ </small> ♠ 20:00, 20 June 2026 (UTC)

:Before the motions, there was a requirement in the contentious topics ↗ procedure that administrators should only impose editor restrictions ↗ if the editor was considered "aware" (WP:AWARE ↗) of the contentious topic designation while engaging in some misconduct about the topic. Afterwards, "awareness" is no longer a requirement, but now instead, when responding to misconduct within a contentious topic, {{tqb|An administrator should warn an editor whose behavior is not egregiously disruptive if the administrator believes the editor does not understand what editing in a contentious topic means. Otherwise, the administrator should issue an appropriate restriction. {{pb}}If an editor does not improve their behavior after a warning, administrators should normally impose editor restrictions rather than give additional warnings.}}
:That is the general rule for all editors. To conform with that change, we amended any particular remedies in cases which referred to the old "awareness" provision. In WP:ARBSCE ↗ you were given a "reminder ↗" (a mild warning) to remain collegial, and a reminder about the BLP contentious topic designation ↗. So given the new procedures, since you've received those reminders, if in the future you were to fail to remain collegial while editing about or discussing a BLP, then applying the general rule would mean normally "the administrator should issue an appropriate restriction" (for example, a temporary ban from editing about BLPs or some particular BLP, or from interacting with some editor).
:The specific change for ARBSCE, made to conform to that general rule, was removing {{!xt|Editors named in this decision shall be considered aware ↗ of these discretionary sanctions under awareness criterion 1.}} and replacing it with {{tq|Administrators should give serious consideration to issuing contentious topic restrictions to editors named in this decision in the event of further misconduct.}} That was meant to have much the same effect as the general change applicable to all editors. ~ Jenson (SilverLocust 💬) 07:37, 21 June 2026 (UTC)
::Thanks for the clarification, {{u|SilverLocust}}. I feel like I understand the context and change much better now. Hope you have a nice rest of the weekend ^u^ — ♠ Ixtal <sup>( T / C ↗ ) </sup> ⁂ <small> Non nobis solum ↗ </small> ♠ 08:58, 21 June 2026 (UTC)

''The Signpost'': 21 June 2026

<div lang="en" dir="ltr" class="mw-content-ltr"><div style="column-count:2;"> {{Wikipedia:Wikipedia Signpost/2026-06-21}} </div> <div class="hlist" style="margin-top:10px; font-size:90%; padding-left:5px; font-family:Georgia, Palatino, Palatino Linotype, Times, Times New Roman, serif;"> * '''Read this Signpost in full ↗''' * Single-page ↗ * Unsubscribe ↗ * MediaWiki message delivery (talk) 03:20, 21 June 2026 (UTC) </div></div>

<section begin="title"/>Wikimedia Apps Newsletter – Second Quarter of 2026<section end="title"/>

<section begin="content"/>
Hello, and welcome to the second Wikimedia Apps newsletter of 2026!

In this edition, we’ll walk you through the main updates, launches, experiments, and improvements in the Wikipedia mobile apps during March, April,May, and June.

iOS ↗

=Liquid Glass migration =

A major focus this quarter was the transition to Apple’s new Liquid Glass design system.

The team completed extensive design, infrastructure, and implementation work, culminating in the release of Wikipedia iOS 8.0.0 with Liquid Glass support. This represented one of the largest visual updates to the app in recent years and required coordinated work across navigation, interface components, theming, and platform-specific behaviors.

The Apps team plans continued modernization of the app’s design system and navigation patterns.

= Activity Tab ↗ =

Following the successful rollout of the Activity Tab earlier this year, the team continued refining the experience based on user feedback.

One recurring theme was confusion around the relocation of reading history. Some users believed history had been removed or required an account to access.

To address this:

Additional guidance was added explaining that History is now available within Search.

Search from article view was updated to provide easier access to reading history.

Ongoing improvements were made to onboarding and user education.

= Games ↗ =

Development continued on the new "Which Came First?" daily trivia game.

The game became available on 11 June 2026.

= Other iOS improvements =

Additional work this quarter included:

hCaptcha instrumentation and rollout preparation.

Explore Feed Refresh design and infrastructure work.

Performance improvements and stability updates.

Resolution of numerous bugs affecting search, reading lists, login flows, article viewing, donations, widgets, and accessibility.

Android ↗

= Hybrid Search ↗ =

The Android team continued work on Hybrid Search, combining traditional keyword search with semantic search capabilities.

The experiment expanded to English, French, Portuguese, and Greek Wikipedias and completed its first MVP phase.

== Results ==

Increased search engagement.

Stable retention.

Strong signals supporting continued investment in semantic search experiences.

The experiment also generated valuable datasets and user insights that will guide future development.

== Learnings ==

One key learning was that users need clearer explanations of how hybrid search works. Existing onboarding and provenance indicators were not sufficient at larger scale.

= Games Hub ↗ =

Android introduced a new Games Hub, providing a centralized location for games and interactive experiences within the app.

The hub lays the groundwork for future expansion of game-based engagement features, including the upcoming trivia experience.

Cross-platform

= Explore Feed Refresh ↗ =

One of the largest initiatives this quarter was the rollout of Phase 1 of the Explore Feed Refresh on Android.

The redesign introduces a new Home experience built around two primary feeds.

== Community Feed ==

center|thumb|700px|Community Feed ↗
The Community Feed highlights curated Wikipedia and Wikimedia content, including:

Featured Article

Top Read

In the News

On This Day

Picture of the Day

== For You feed ==

center|thumb|700px|For You Feed ↗
The For You feed introduces personalized content through:

Article recommendations based on selected interests.

Because You Read recommendations.

Continue Reading suggestions.

== Additional improvements ==

Additional work included:

New onboarding flows.

Feed preference selection.

Redesigned settings.

Re-onboarding for existing users.

Improved feed controls and personalization transparency.

The redesign was released through a holdout experiment, enabling the team to measure its impact while continuing iterative improvements.

== Early learnings ==

Users respond positively to structured onboarding.

Topic selection can help personalize discovery experiences.

Recommendation quality remains a critical factor for user trust and satisfaction.

The Explore Feed Refresh was then released to 50% of app users before being fully released to all users starting on 15 June 2026.

The refreshed experience is planned to launch in the Wikipedia iOS app during July 2026.

= Wikipedia 25th Birthday Reading Challenge ↗ =

thumb|Mock-up of the Wikipedia app Reading Challenge ↗

This quarter we launched the Wikipedia 25th Birthday Reading Challenge across Android and iOS.

The challenge included:

Challenge enrollment experiences.

Daily reading goals.

Reading streak tracking.

Challenge completion flows.

Home screen widgets.

App Store and Play Store promotional events.

CentralNotice promotion.

Instrumentation and analytics support.

Translation support across target languages.

Following launch, the team implemented several improvements based on early feedback and usage patterns, while resolving onboarding and widget-related issues.

Early results showed encouraging participation, increased account creation, positive community reception, and opportunities for continued iteration.

= Year in Review learnings ↗ =

Following the conclusion of the 2025 Year in Review experience, both teams completed a comprehensive analysis of the feature.

== Key findings ==

Both apps achieved an 86% return rate.

Account creation increased significantly year over year.

Approximately half of all new accounts during the campaign period were created through Year in Review.

User satisfaction exceeded targets, with over 95% of surveyed users reporting neutral or positive experiences.

Donations increased substantially, particularly among users exposed to personalized experiences.

== Learnings ==

Personalization significantly improves engagement.

Logged-out users benefit from receiving limited personalized experiences.

Account-gated personalization remains a strong driver of account creation.

Users continue to request richer insights, improved sharing capabilities, and cross-platform statistics.

The findings will help shape future iterations of Year in Review and other personalized experiences within the apps.

Looking ahead

This quarter focused on launching major experiences while laying the groundwork for future growth.

The rollout of the Explore Feed Refresh, launch of the Reading Challenge, continued investment in Hybrid Search, and preparation for new games all reflect the team's broader focus on helping users discover, engage with, and contribute to knowledge in new ways.

We're excited to continue iterating on these experiences and look forward to sharing more updates in the next edition of the newsletter.

Thank you for reading!

<section end="content"/>

~~ARamadan-WMF11:59, 29 June 2026 (UTC)

WikiCup 2026 July newsletter

The third round of the 2026 WikiCup ended on 28 June at 23:59 (UTC). As a reminder, good article nomination reviews ↗ now receive 10 points, while peer reviews ↗, which continue to be worth 5 points, are now listed in the same section as featured article candidate reviews ↗, rather than with good article reviews. Everyone who competed in round 3 will advance to round 4 unless they have withdrawn or been banned. No other changes to the round-point system have been made for this year.

Round 3 was competitive. Three contestants scored more than 1,000 round points; eight scored over 500; and thirteen scored over 300. The top three contestants had at least one featured article ↗ (two of them with two apiece). The following competitors scored more than 800 round points:

{{Wikipedia:WikiCup/Participant17|MCE89}} with 1567 points, mainly from good and featured articles about Australian people and geography, as well as some article reviews

{{Wikipedia:WikiCup/Participant17|Bgsu98}} with 1547 points, mainly from good articles, featured articles, featured lists, and a good topic about figure skating, along with 20 article reviews

{{Wikipedia:WikiCup/Participant17|Reconrabbit}} with 1004 points, mainly from a high-multiplier featured article on European rabbit ↗ and several good articles, DYKs, and reviews

{{Wikipedia:WikiCup/Participant17|A.Cython}} with 1004 points, mainly from good articles about warfare, along with 22 article reviews

{{Wikipedia:WikiCup/Participant17|Generalissima}} with 859 points, mainly from good and featured articles about rivers and East Asian topics

The full scores for round 3 can be seen here ↗. During this round, contestants have claimed 12 featured articles, 12 featured lists, 7 featured-topic articles, 117 good articles, 74 good-topic articles and more than 30 Did You Know articles. In addition, competitors have worked on 13 In the News ↗ articles, and they have conducted nearly 180 reviews. The tournament points table ↗ has been updated.

Remember that any content promoted after 28 June but before the start of Round 4 can be claimed in Round 4. Invitations for collaborative writing efforts or any other discussion of potentially interesting work is always welcome on the WikiCup talk page. Remember, if two or more WikiCup competitors have done significant work on an article, all can claim points. If you are concerned that your nomination—whether it is at good article candidates, a featured process, or anywhere else—will not receive the necessary reviews, please list it on Wikipedia:WikiCup/Reviews Needed ↗. If you want to help out with the WikiCup, feel free to review one of the nominations listed on Wikipedia:WikiCup/Reviews Needed. Questions are welcome on Wikipedia talk:WikiCup ↗, and the judges are reachable on their talk pages. Good luck! <small>If you wish to start or stop receiving this newsletter, please feel free to add or remove your name from Wikipedia:WikiCup/Newsletter/Send ↗.</small> MediaWiki message delivery (talk) 13:49, 29 June 2026 (UTC)

The DCWC is open!

thumb|upright=1.2|See a {{nowrap|{{legend inline|ffb219}} "developing"}} or {{nowrap|{{legend inline|ff562f}} "least}} developed" country? Write about it to earn points! ↗

Hey Ixtal, the third annual Developing Countries WikiContest ↗ is now '''open for submissions'''. The coordinators have addressed some of the queries at the last contest and we are hopeful that it'll turn out great! If you haven't done so already, please review the following:

New to Wikipedia? Many experienced editors are part of this contest and willing to help; feel free to ask questions on the talk page ↗.

Got open nominations? List them at the review requests sidebar ↗.

Looking for a topic to work on? Check out suggested articles ↗ and eligible reviews ↗.

Not sure if your article qualifies? See the scoring rules ↗ for more information or contact a coordinator ↗.

Know someone else who might be interested? Sign-ups remain open ↗ throughout the contest, so don't hesitate to invite other editors!

On behalf of the coordinators, we hope you enjoy participating and wish you the best of luck! If you have any questions, please leave a message on the contest talk page ↗ or ask one of the coordinators: {{noping2|Arconning}}, {{noping2|Generalissima}}, {{noping2|Magentic Manifestations}}, {{noping2|sawyer777}}, or {{noping2|TechnoSquirrel69}}. <small>(To unsubscribe from these updates, remove yourself from this list ↗. Sent via MediaWiki message delivery.)</small> <span class="nowrap">—<span style="color: #0b541f;">'''TechnoSquirrel69'''</span></span> <small>(<span style="color: #0b541f;">'''talk'''</span>)</small> 00:00, 1 July 2026 (UTC)
{{clear|right}}

Administrators' newsletter – July 2026

News and updates for administrators ↗ from the past month (June 2026).

right|150px ↗

20px|alt= ↗ '''Administrator changes'''
:20px|alt=added|Added ↗ {{hlist|class=inline|Chipmunkdavis ↗|TechnoSquirrel69 ↗}}
:20px|alt=removed|Removed ↗ {{hlist|class=inline
|Mlaffs ↗
|SpuriousQ ↗
|Lectonar ↗
|Dennis Brown ↗
|Hog Farm ↗
}}

20px|alt= ↗ '''CheckUser changes'''
:20px|alt=readded|Readded ↗ {{hlist|class=inline
|Giraffer ↗
|TonyBallioni ↗
}}
:20px|alt=removed|Removed ↗ {{hlist|class=inline
|Dbeef ↗
|EdJohnston ↗
}}

20px|alt= ↗ '''Oversight changes'''
:20px|alt=readded|Readded ↗ {{hlist|class=inline
|Giraffer ↗
|TonyBallioni ↗
}}
:20px|alt=removed|Removed ↗ L235 ↗

20px|alt= ↗ '''Guideline and policy news'''

A request for comment ↗ asks whether the criteria for autoconfirmed and extended confirmed should be modified.

A request for comment ↗ proposes an addendum for the Real name section of the Username policy ↗.

20px|alt= ↗ '''Technical news'''

The special page Special:RangeCalculator ↗ has been created for any users to use to find an IP range. (phab:T268429 ↗)

The "indefinitely" button in Special:Block ↗ for temporary accounts can be replaced with a preferred block duration stated on MediaWiki:ipb-indefinite-expiry-temporary-account ↗. (phab:T427125 ↗)

20px|alt= ↗ '''Arbitration'''

Following a series of motions ↗, changes to the contentious topics procedure ↗ to restructure awareness ↗ have been implemented.

The arbitration case ''Michael Jackson ↗'' has been closed.

20px|alt= ↗ '''Miscellaneous'''

The 2026 Developing Countries WikiContest ↗ will run from 1{{nbsp}}July to 30{{nbsp}}September. '''Sign up now ↗'''!

10 candidates have been appointed ↗ to the U4C.

----
{{center|{{flatlist|

Discuss this newsletter ↗

Subscribe ↗

Archive ↗

}}}}
{{center|1=<small>Sent by MediaWiki message delivery (talk) 14:07, 2 July 2026 (UTC)</small>}}

You're invited to the Mentorship noticeboard

Hi, Ixtal. You are cordially invited to the brand new Wikipedia:Mentorship noticeboard ↗. I get the impression sometimes that we mentors are each toiling in our own cubbyhole or hamster wheel, quietly answering mentee questions with little to no interaction with other mentors. I think we have a lot to share and learn from each other, and I know it will make me feel better just having the opportunity to interact with you and other mentors there, and I hope it will for you, too. Looking forward to hearing your feedback. Please take the {{slink|WP:MNB|Survey|nopage=yes}} when you get there! Mathglot (talk) 00:52, 5 July 2026 (UTC)