Jump to content

User talk:Rich Farmbrough

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
(Redirected from User talk:Helpful Pixie Bot)
Note
Email may very occasionally be delayed due to spam filtering.


Links
Talk Archive Index

Table oddities

[edit]
I II III IV V VI VII VIII
4913
7903
8991 		4913
7903
8991

4913
7903
8991

4913

7903
8991

4913

7903 8991

4913 7903 8991

4913

7903

8991

4913

7903

8991

Cheshunt Lock and other notes

[edit]

2025

[edit]

Things to unarchive

[edit]

Space discussion.

Yo Ho Ho!

[edit]

ϢereSpielChequers is wishing a foaming mug of Seasons Greetings! Whether you celebrate your hemisphere's Solstice or Christmas, Diwali, Hogmanay, Hanukkah, Lenaia, Festivus or even the Saturnalia, this is a special time of year for almost everyone!

Spread the holiday cheer by adding {{subst:User:WereSpielChequers/Dec25}} to your friends' talk pages.

Cite journal on MG WP

[edit]

Trying to get this to work with Content Translation.[18] I imagine it does not work as it is such an old version. How best does one update this? Doc James (talk · contribs · email) 09:17, 27 February 2026 (UTC)[reply]

Are you trying to translate the documentation or the template itself? All the best: Rich Farmbrough 16:36, 28 February 2026 (UTC).[reply]
Trying to use a version of Content Translation to translate into MG and want the citation templates to come through. I have added template metadata. But still not working perfectly. Doc James (talk · contribs · email) 17:01, 28 February 2026 (UTC)[reply]
OK. Not automated, but here's how I recommend migrating specific templates. This is a potentially very resilient method. (I have a lot more ideas, but they are not as easily compatible with Lua as with the pure template system.) All the best: Rich Farmbrough 19:59, 28 February 2026 (UTC).[reply]
If the mg wiki doesn't have the Extension:Cite that may be an issue. All the best: Rich Farmbrough 20:09, 28 February 2026 (UTC).[reply]
You added the Cite Journal template on MG WP in 2011.[19] The question is does it just need updating? Doc James (talk · contribs · email) 08:02, 1 March 2026 (UTC)[reply]
Looks like it is working now Doc James (talk · contribs · email) 15:25, 4 March 2026 (UTC)[reply]

"Cladotherianthrope" listed at Redirects for discussion

[edit]

The redirect Cladotherianthrope has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Anyone, including you, is welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2026 February 28 § Cladotherianthrope until a consensus is reached. Abesca (talk) 15:41, 28 February 2026 (UTC)[reply]

Time spent handling this request, 1 hour 25 minutes. All the best: Rich Farmbrough 17:41, 28 February 2026 (UTC).[reply]

CfD nomination at Wikipedia:Categories for discussion/Log/2026 February 28 § Category:Session musicians

[edit]

Categories you have created have been nominated for possible deletion, merging, or renaming. A discussion is taking place to decide whether this proposal complies with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at Wikipedia:Categories for discussion/Log/2026 February 28 § Category:Session musicians on the categories for discussion page. Thank you. SMasonGarrison 19:28, 28 February 2026 (UTC)[reply]

Wikimedians for Sustainable Development - February 2026 Newsletter

[edit]
This is our fifty second newsletter. This issue has news related to SDG 4, 5, 10, 13, 15, 16 and 17.
User group news
  • A proposal for a climate and sustainability meetup at Wikimania has been submitted. Keep your fingers crossed it gets accepted!
Other news
Events

This message was sent with Global message delivery by Ainali (talk) 12:13, 2 March 2026 (UTC) • Contribute • Manage subscription[reply]

Wikidata weekly summary #721

[edit]
Here's your quick overview of what has been happening around Wikidata in the
week leading up to 2026-03-02. Missed the previous one? See issue #720.

Discussions

  • Closed request for adminship: Jan Myšák: Closed as successful, congratulations to Wikidata's newest admin!
  • New request for comments: Notability Policy - Round 2: we are still requesting your input on the new Notablity policy. Including whether to elevate the self-promotion essay to a policy.

Events

  • Upcoming events:
    • Next Linked Data for Libraries LD4 Wikidata Affinity Group session 3 March, 2026: We have our next LD4 Wikidata Affinity Group Session on Tuesday, March 3 9am PT / 12pm ET / 17:00 UTC / 6pm CET (Time zone converter). Wikiproject P244 maintenance uses SPARQL queries to identify and resolve two types of constraint violations in Wikidata: instances of Wikidata items with more than one LCNAF identifier and instances of the same LCNAF identifier existing on more than one Wikidata item. The February 17th session walked participants through how to resolve the former issue, while the March 3rd session will focus on the latter. This session will be more discussion-focused, since instances where two LCNAF identifier have the same Wikidata item can be difficult to resolve because of Wikidata’s innate quirks. Maybe your ideas will become the official best practice! Event page: https://www.wikidata.org/wiki/Wikidata:WikiProject_LD4_Wikidata_Affinity_Group/Project_Series/LCNAF_Duplicate_Detection_P244_Maintenance
    • Bring-Your-Own-Data-Lab, on 24.04.2026, the HERMES Data Competence centre hosts an online BYODL. Dr. Katrin Moeller and Dr. Olaf Simons will share how to enrich your own personal data with standard data and the Wikibase FactGrid. Click the link for registration and more information.
    • Wikidata Workshop w/ Wikipedia Riba Aruba + University of Aruba Research Center (UARC), March 2, 12 - 2pm GMT-4. Click here to register.

Press, articles, blog posts, videos

Tool of the week

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

  • Mobile statement editing:
  • GraphQL: We are getting ready to launch the first version later this week, including preparing the documentation for how to use it.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Weekly Tasks

Tech News: 2026-10

[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

  • Wikipedia 25 Birthday mode is now live on Betawi, Breton, Chinese, Czech, Dutch, English, French, Gorontalo, Indonesian, Italian, Luxembourgish, Madurese, Sicilian, Spanish, Thai, and Vietnamese Wikipedias! This limited-time campaign feature celebrates 25 years of Wikipedia with a birthday mascot, Baby Globe. When turned on, Baby Globe is shown on ~2,500 articles, waiting to be discovered by readers. Communities can choose to turn Birthday mode on by getting consensus from their community and asking an admin to enable the feature and customize it via community configuration on the local wiki.

Updates for editors

  • Sub-referencing, a new feature to re-use references with different details has been released to Swedish Wikipedia, Polish Wikipedia and a couple of other wikis. You can try the feature on these projects or on testwiki and betawiki. Learnings from the first pilot wiki German Wikipedia have been published in a report. Reach out to the Wikimedia Deutschland team if you are interested in becoming a pilot wiki.
  • Paste Check will become available at all Wikipedias this week. The feature prompts newcomers who are pasting text they are not likely to have written into VisualEditor to consider whether doing so risks a copyright violation. Paste Check tags all edits where it is shown for potential review. Local administrators can configure various aspects of the feature via Special:EditChecks. Research across 22 wikis found that Paste Check resulted in an 18% decrease in relative reverted-edits compared to the control group. Translators can help to localize this and related features.
  • The Reader Experience team will be standardizing the user menu in the top right for all mobile users so that it is closer to the desktop experience. Currently this user menu is only visible to users with Advanced Mobile Controls (AMC) turned on. The only change is that a couple buttons previously in the left-side menu will move to the top right for users who do not have AMC turned on. This change is expected to go out March 9 and seeks to improve the user interface. [20]
  • Starting in the week of March 2, the emails sent out when an email address was added, removed, or changed for an account will switch to a substantially nicer and clearer HTML email from the prior plaintext one. [21]
  • Notifications are currently limited to 2,000 historic entries per user, and extend back to 2013 when the feature was released. This is going to be changed to only store Notifications from the last 5 years, but up to 10,000 of them. This will help with long-term infrastructure health and help to prevent more recent notifications from disappearing too soon. [22]
  • The Global Watchlist which lets you view your watchlists from multiple wikis on a single page continues to see improvements. The latest update improves label usage experience. The extension now allows activating the language fallback system for Wikidata items without labels in the viewed language, and showing those labels in the user’s preferred Wikidata language if no uselang= URL parameter is provided. [23][24]
  • The Wikipedia Android team has started a beta test of hybrid search on Greek Wikipedia. Hybrid search capabilities can handle both semantic and keyword queries enabling readers to find what they’re looking for directly on Wikipedia more easily.
  • For security reasons, members of certain user groups are required to have two-factor authentication (2FA) enabled. Currently, 2FA is required to use the group, but not to be a member of it. Given that this model still has some vulnerabilities, the situation will gradually change in March. Members of these groups will be unable to disable last 2FA method on their account, and it will be impossible to add users without 2FA to these groups. Users will still be able to add new authentication methods or remove them, as long as at least one method is continuously enabled. In the second half of March, users without 2FA will be removed from these groups. This applies to: CentralNotice administrators, checkusers, interface administrators, suppressors, Wikidata staff, Wikifunctions staff, WMF Office IT and WMF Trust & Safety. Nothing will change for other users. See the linked task for deployment schedule. [25]
  • Recurrent item View all 27 community-submitted tasks that were resolved last week. For example, the issue preventing users from creating an instance in Wikibase.cloud has now been fixed. [26]

Updates for technical contributors

  • To help ensure fair use of infrastructure, over the next month the Wikimedia Foundation will implement global API rate limits across our APIs. In early March, stricter limits will be applied to unidentified requests from outside Toolforge/WMCS and API requests that are made from web browsers. In April, higher limits will be applied to identified traffic. These limits are intentionally set as high as possible to minimise impact on the community. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see Wikimedia APIs/Rate limits.
  • The Wikidata Query Service Linked Data Fragment (LDF) endpoint will be decommissioned in February. This endpoint served limited traffic, which was successfully migrated to other data access methods that were better suited to support existing use cases. The hardware used to support the LDF endpoint will be reallocated to support the ongoing backend migration efforts. [27]
  • The new Parsoid parser continues to be deployed to additional wikis, improving platform sustainability and making it easier to introduce new reading and editing features. Parsoid is now the default parser on 488 WMF wikis (268 Wikipedias), now covering more than 10% of all Wikipedia page views.
  • The process and criteria for requesting exceptional access to the high volume feed of the Wikimedia Enterprise APIs (at no cost for mission-aligned usecases), have now been published. This is to provide more thorough and clearer documentation for users.
  • Tech Blog, the blog dedicated to the Wikimedia technical community will be migrating to Diff, the community news and event blog. The migration should be complete in April 2026, after which new posts will be accepted for publishing. Readers will be able to access posts – old and new – on the landing page at https://diff.wikimedia.org/techblog.
  • Recurrent item Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 17:50, 2 March 2026 (UTC)[reply]

Your edit to Talk:Killing of Renée Good

[edit]

On February 2nd, you added a hidden comment - 15 <-- please do not reduce this without discussion --> - and also changed the number of posts retained to before auto-archiving. Now the talk page has posts & threads from all through January etc. with no new comments. Since the posting furor has gone down a bit, I would like to change the auto-archiving from 7 days to 14 & the number of 'threads kept' to 5 (instead of 15), but wanted to have your thoughts on the matter first. Thanks, Shearonink (talk) 01:43, 6 March 2026 (UTC)[reply]

HI, thanks for messaging me. I'm completely happy for you to make the timescale 14 days, but I'd rather not let the number of threads fall as low as 5, maybe 10 would be more appropriate. Established articles tend to have shorter threads, and letting these sit on the talk page for a long time allows editors to see consensus on the most relevant topics, without resulting in excessively long talk pages: effectively the talk page is a FAQ. While it's sometimes advisable to read, or at least look at, archives, in general it's not something we can expect most editors to do most of the time. All the best: Rich Farmbrough 00:42, 8 March 2026 (UTC).[reply]
Your explanation makes sense. Will adjust the archiving. Thanks - Shearonink (talk) 01:22, 8 March 2026 (UTC)[reply]

Most murders

[edit]

Hi, I am trying to understand your reasons for creating the article about most murders back on 29 June 2025. None of your edit summaries meaningfully explain your edits, so I have no idea of your reasons for creating this article. Also, many of your edits are marked it as "minor", but it may not have been. On Wikipedia, "minor edit" refers only to superficial edits that could never be disputed, such as fixing typos or reverting obvious vandalism. Any edit that changes the meaning of an article is not minor, even if it only concerns a single word. One of your edits removed a proposal for speedy deletion, without explaining why you are opposed to the article being deleted. While another reverted a blank and redirect to murder, again without explanation. Based on its current content, most of the existing article content is probably off-topic, and I have added clean-up tags to suggesting better locations for most of this content, but I would welcome you sharing your opinion at Talk:Most murders. - Cameron Dewe (talk) 21:38, 7 March 2026 (UTC)[reply]

See talk page for discussions about the content page. All the best: Rich Farmbrough 19:57, 9 March 2026 (UTC).[reply]

Wikidata weekly summary 722

[edit]
Here's your quick overview of what has been happening around Wikidata in the
week leading up to 2026-03-09. Missed the previous one? See issue #721.

Discussions

  • New requests for permissions/Bot: DifoolBot 8 - Task: Remove Wikipedia import references from statements where the referenced article has since been deleted.

Events

Press, articles, blog posts, videos

Tool of the week

  • Data2Go : An iOS app for browsing and editing Wikidata with a mobile-first UI. It combines fast search, rich item detail views, statement editing, map previews, media galleries, and account-based write access to Wikidata.

Other Noteworthy Stuff

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

  • GraphQL: We have released the first version of this new API. You can read more about it and try it out.
  • Wikidata integration in the other Wikimedia projects: We have worked with editors to improve some highly-used modules that access Wikidata in a suboptimal way. They have been adjusted to lead to less unneeded change notification in people's watchlists and recent changes on Wikipedia and co.
  • Mobile statement editing: We fixed an issue where certain Properties were not accessible in the new mobile UI. We are also working on fixing a bug with saving musical notation statements. We are continuing the work on supporting editing of geocoordinates.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Weekly Tasks

Tech News: 2026-11

[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

  • All wikis will be read-only for a few minutes on Wednesday, 25 March 2026 at 15:00 UTC. This is for the datacenter server switchover backup tests, which happen twice a year. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies.
  • Last week, all wikis had 2 hours of read-only time, and extended unavailability for user-scripts and gadgets. This was due to a security incident which has since been resolved. Work is ongoing to prevent re-occurrences. For current information please see the post on the Stewards' noticeboard (translations).

Updates for editors

  • Users facing multiple blocks on mobile will now see the reasons for each block separately, instead of a generic message. This helps them understand why they are blocked and what steps they can take to resolve the issue. For example, users affected for using common VPNs (such as iCloud Private Relay) will receive clearer guidance on what they need to do to start editing again. [28]
  • Later this week, Suggestion Mode will become available as a beta feature within the visual editor at all Wikipedias. This feature proactively suggests various types of actions that people can consider taking to improve Wikipedia articles, and learn about related guidelines. The feature is locally configurable, and can also be locally expanded with custom Suggestions. Current settings can be seen at Special:EditChecks and there are instructions for how administrators can customize the links to point to local guidelines. The feature is connected to Edit check which suggests improvements while someone is writing new content. In the future, the Editing team plans to evaluate the feature's impact with newcomers through a controlled experiment. [29]
  • Recurrent item View all 23 community-submitted tasks that were resolved last week. For example, the issue where the cursor became misaligned during the use of CodeMirror’s syntax highlighting, which makes wikitext and code easier to read, has now been fixed. This problem specifically affected users who defined a font rule in a custom stylesheet while creating a new topic with DiscussionTools. [30]

Updates for technical contributors

  • API rate limiting update: To help ensure fair use of infrastructure, global API rate limits will be applied this week to requests without a compliant User-Agent that originate from outside Toolforge/WMCS and to unauthenticated requests made from web browsers. Higher limits will be applied to identified traffic in April. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see Wikimedia APIs/Rate limits.
  • The new GraphQL API has been released. The API was developed as a flexible alternative to select features of the Wikidata Query Service (WDQS), to improve developer experience and foster adaptability, and efficient data access. Try it out and give feedback. You can also sign up for usability tests.
  • The PTAC Unsupported Tools Working Group continued improvements to Video2Commons in February, with fixes addressing authentication errors, large-file handling, task queue visibility, and clearer upload behavior. Work is still ongoing in some areas, including changes related to deprecated server-side uploads. Read this update to learn more.
  • Recurrent item Detailed code updates later this week: MediaWiki

In depth

  • The Article Guidance team invites experienced Wikipedia editors from selected pilot wikis and interested contributors from other Wikipedias to fill out this questionnaire which is available in English, Arabic, Bengali, Japanese, Portuguese, Persian, and Turkish. Your answers will help the team customize guidance for less experienced editors and help them learn community policies and practices while creating an article. Learn more on the project page.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 18:51, 9 March 2026 (UTC)[reply]

The Signpost: 10 March 2026

[edit]
  • Special report: What actually happened during the Wikimedia security incident?
    A horrifying exploit took place, which could have had catastrophic and far-reaching consequences if used maliciously; instead, it seems to have happened by accident and was used for childish vandalism. How did this happen, and what did the script actually do?
* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 04:12, 10 March 2026 (UTC)[reply]
Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:Rich_Farmbrough&oldid=1342671034"