Jump to content

User talk:Jeremyb

Add topic
From mediawiki.org

Manual:Importing XML dumps#How to import logs?

[edit]

You wrote that logs import requires root. As you seem to be knowledgeable on the topic, could you please contribute to the section above? I only used "shell user" as a generic term, but importDump.php is supposed to work. --Nemo 16:06, 24 October 2013 (UTC)Reply

Wikitech is not on the main cluster and I guess mortals (as defined by siteadmins.pp) don't have access there at all so it would have to be a root. Maybe that's wrong, I didn't go reading manifests to verify this particular case. --Jeremyb (talk) 16:10, 24 October 2013 (UTC)Reply
Oh well, I don't think that's important/useful. :) Too bad, the page above would really use some work! --Nemo 16:14, 24 October 2013 (UTC)Reply

Error during logging in

[edit]

Dear Jeremyb, I am one of the most active contributors in Zazaki Wikipedia. I can not log in there for over a week. What am I doing wrong or what I did wrong? I dont know. It appears after every login attempt the following reason:

Request: POST http://diq.wikipedia.org/w/index.php?title=Ba%C4%9Fse:KarberC%C4%B1kewt%C4%B1%C5%9F&action=submitlogin&type=login&returnto=Pela+Seri, from 91.198.174.63 via cp1067 cp1067 ([10.64.0.104]:3128), Varnish XID 1216788132 Forwarded for: 88.74.107.192, 91.198.174.58, 91.198.174.58, 91.198.174.63 Error: 503, Service Unavailable at Sun, 07 Dec 2014 04:24:13 GMT
Can you help me in this regard? I thank you for that very much in advance. Greetings! --Mirzali (talk) 21:45, 8 December 2014 (UTC)Reply
I have no idea how you decided I was a good person to ask about this?
In a private browsing/incognito window (or a different computer with cleared cookies): Are you able to log into any wiki (even this one) with your diqwiki username? What happens if you then visit diqwiki?
The error message you quoted (a 503) sounds like a temporary, transient error. In any case this should be raised somewhere else, not on my talk page. --Jeremyb (talk) 03:54, 9 December 2014 (UTC)Reply
I thought that you can help me as a system administrator. But thanks anyway. --Mirzali (talk) 12:11, 10 December 2014 (UTC)Reply
Mirzali, Sorry for the confusiing naming. Administrator aka sysop != sysadmin. --Jeremyb (talk) 15:28, 11 December 2014 (UTC)Reply

Notice: Admin activity review

[edit]

Hello Jeremyb,

I hope that this message finds you well.

I am writing to inform you that you may lose your adminship (and other advanced permissions) on mediawiki.org because of inactivity.

A policy regarding the removal of advanced permissions (e.g.: administrator, bureaucrat, interface-admin, etc.) was adopted by community consensus in 2013. While initially that policy did not apply to this site, the mediawiki.org community decided in August 2020 to opt-in.

You are being notified because we have identified that your account meets the inactivity criteria stated in the policy: no edits and no administrative log actions for the last 2 years.

  • If you want to keep your advanced permissions, you should inform the community (at Project:Current issues) about the fact that the stewards have sent you this information about your inactivity. A community notice about this process has been also posted on said page. If the community has a discussion about it and then wants you to keep your advanced permissions, please contact the stewards at the stewards noticeboard, and link to the discussion of the local community, where they express their wish for you to continue to maintain your advanced permissions.
  • If you wish to resign your advanced permissions, you may do so by filing a request for removal on Meta-Wiki.
  • If there is no response at all on one month after this notification, the stewards will proceed to remove your advanced permissions without further notice.

In ambiguous cases, stewards will evaluate the responses and will refer a decision back to the local community for their comment and review.

If you have any questions, please let me know or feel free to message us at the stewards. If you feel we've made a mistake and your account is active, we'd also appreciate to let us know, and please accept our apologies.

Best regards,
--MarcoAurelio (talk) (via MassMessage) 22:13, 9 January 2021 (UTC)Reply

Hello, today your admin flag has been removed. Einsbor (talk) 10:22, 9 February 2021 (UTC)Reply

Wikimedia Apps newsletter – Third quarter of 2025

[edit]

In this edition, we’ll walk you through the major updates, experiments, and improvements that took place in the Wikipedia mobile apps during July, August, and September.

iOS

[edit]
  • In July, we released the first iteration of Tabbed Browsing to all users.
  • Our 30-day A/B test showed mixed but promising results: while logged-out user retention gains were modest compared to Android, survey feedback was overwhelmingly positive (93% rated the feature “Neutral to Very Satisfactory”).
  • We continued improvements throughout August and September, including a design review for “More Dynamic Tabs,” a new tab controller, and bug fixes such as inconsistent tab sizing on iPad mini and tooltip issues.
  • Work continued on Year in Review upgrades, with spikes exploring features such as sharing entire reviews, custom app icons, and showing which geographies users read about the most.
  • We also began preparing overall app data to share richer collective insights.
  • We improved code behind the History tab and recent searches to prepare for future navigational changes.

Other iOS Updates

[edit]
  • Released several app versions (7.8.1 through 7.8.3), with smoke tests completed.
  • Resolved numerous bugs including crashes (tooltips, gestures, search), iPad layout issues, and visual problems with captions, Quick Facts, and images in Dark Mode.
  • Added a new REST endpoint for remote configuration and upgraded fundraising configurations to support A/B testing.
  • Verified continued compatibility with multi-factor authentication (MFA).

Android

[edit]
  • In August, we launched the Customizable Donation Reminder experiment in Italy. The reminder will allow users to decide if they want to be reminded to donate, and how often.
  • By September, we finalized core modules, onboarding, instrumentation, and validation tasks needed for the A/B test of the new Activity Tab against the Edit Tab.
  • This marks a major step toward testing whether an Activity space can improve multi-day engagement and retention.

Bug Fixes & Improvements

[edit]
  • Fixed crashes with image gallery long-press, saved article syncing for Chinese, edit previews, and special links.
  • Addressed rendering and Dark Mode issues affecting math tags, GIFs, and citation numbers.

Other Android Updates

[edit]
  • We released a new beta and conducted multiple regression tests to ensure stability.
  • We added a general-purpose remote configuration REST endpoint, aligned with iOS.
  • Continued technical debt cleanup, including removing allowMainThreadQueries and adding suspend to DAO functions.
  • Upgraded fundraising configuration to support A/B testing.

Cross-Platform

[edit]
  • Both apps upgraded fundraising A/B test support and created a shared remote configuration REST endpoint.
  • We began tracking Account Vanish events on iOS and Android for privacy features.

Looking Ahead

[edit]

This quarter marked a big step forward on Tabbed Browsing, Activity Tab, and Year in Review — three projects aimed at making Wikipedia more personal, navigable, and engaging. We also advanced donation experiments and backend improvements to support future flexibility.

Make sure you’re subscribed to this newsletter to stay in the loop — and thank you for being part of the journey!


ARamadan-WMF 02:12, 14 October 2025 (UTC)Reply

Wikimedia Apps Newsletter – Fourth Quarter of 2025

[edit]


Hello, and welcome to the final newsletter of 2025!

In this edition, we’ll walk you through the major updates, experiments, and improvements in the Wikipedia mobile apps during October, November, and early December.

iOS

[edit]

Throughout October and November, the team made final updates to the Year in Review feature, preparing it for its early December release.

Key improvements included:

  • Updating the Total Edits slide to represent global edits across all Wikimedia projects.
  • Running usability tests, which showed strong user interest in personalized slides—especially reading patterns, top articles, categories, and geo insights.
  • Preparing the A/B test that will allow some logged-out users to view personalized content.

We also added fundraising banner suppression for users who donated in the past 250 days, so that users who may have donated from the Year in Review do not see a banner.

We continued work on the New Tab Experience and ran the A/B/C test for recommendations within the tabs overview.

The experiment concluded on November 18 and showed:

  • Recommendations increased pageviews and new tab openings. However, they did not improve multi-day usage or overall retention.
  • “Because you read” recommendations performed better than “Did you know.”
  • Group C had slightly higher satisfaction and lower dissatisfaction.

Next steps:

  • Scale the new tab experience, including “close all tabs,” to all users.
  • Do not scale recommendations yet until after further investigation.

Work continued on Activity Tab V2, preparing to test it against the existing History tab. Updates included:

  • Integrating learnings from Android’s successful Activity Tab experiment.
  • Building new onboarding, instrumentation, and module behavior.
  • A first version was released in early December.

Other iOS Updates

[edit]
  • We ran a survey on the Explore tab launched to gather user feedback.
  • OAuth adoption was explored by engineering and design.
  • Bug fixes for login with 2FA, search in Saved, and other regressions.
  • Compatibility testing completed for m. subdomain removal.

Android

[edit]

By October, the Activity Tab experiment delivered strong results:

  • Return rate for logged-in users increased by 11.6% compared to the previous Edit tab.
  • Experiment had no negative impact on overall retention.
  • Only 0.7% of users turned the feature off.

In November, we made several improvements, and then scaled the Activity Tab to all logged-in users.

Year in Review 2025

[edit]

The team finalized core implementation, prepared for the December release, and:

  • Updated the Total Edits slide to reflect global edits across projects.
  • Prepared the A/B test for the Year in Review Reading List, which will offer a personalized reading list to some users.
  • Conducted final usability reviews.

We began development of the second donation reminder experiment, planned for December–March.

This experiment:

  • Targets users who click “Maybe later” on fundraising banners.
  • Tests a fully customizable reminder flow versus the current “Maybe later” behavior.
  • Allows users to adjust reminder frequency, article-count triggers, and manage their reminder settings.

Other Android Updates

[edit]
  • We ran a survey on the Explore tab launched to gather user feedback.
  • OAuth adoption was explored by engineering and design.
  • Fixed issues with “Forgot your password” in Chinese, dark-mode rendering problems, punctuation-based errors, and navigation bugs.
  • Added ISO currency codes to donation forms.
  • Updated several settings and entry points to prepare for the fundraising season.

Cross-Platform

[edit]

Release of Wikipedia Year in Review 2025

[edit]
  • Both Android and iOS teams released their Year in Review features on December 2, 2025!
  • They were met with positive interactions on social media, and from the press.
  • There were 2 articles written about the feature by The Verge and by Vice.

Looking Ahead

[edit]

This quarter brought major progress across Tabs, Activity, Year in Review, and Donation Reminder work.

As we close 2025, both apps now support a richer set of personalization features, clearer navigation paths, and more user-controlled donation experiences.

Thank you for following along, and stay tuned for our next newsletter in early 2026!


~~ARamadan-WMF16:17, 17 December 2025 (UTC)Reply