User talk:He7d3r
Add topicContact information: @pt.wikibooks
Your temporary permissions have expired
[edit]Hello,
This is to inform you that the temporary local or global permissions you requested have expired. If you want them back, please feel free to make a local announcement and open a new request on stewards' permission request page on Meta-Wiki later. Please ask me or any other steward if you have any questions.
Thank you!
--MarcoAurelio 15:30, 18 August 2016 (UTC)
Hello Christian Payan (talk) 21:48, 12 November 2016 (UTC)
SVG Translate Community wishlist survey project
[edit]Hello! Thank you for voting for the SVG Translate project that was proposed in the 2017 Wishlist survey. The Community Tech team in the Wikimedia Foundation is beginning to start their work on the project. We're currently looking for feedback on some open questions which will allow us to come up with preliminary designs for the tool. If you are interested in being involved, you can watch the project page and join in the discussions on the talk page. Looking forward to hearing your thoughts and learning from your experiences. Thank you. -- NKohli (WMF), Product Manager, Community Tech (talk) 21:53, 16 August 2018 (UTC)
The Community Wishlist Survey
[edit]Hi,
You get this message because you’ve previously participated in the Community Wishlist Survey. I just wanted to let you know that this year’s survey is now open for proposals. You can suggest technical changes until 11 November: Community Wishlist Survey 2019.
You can vote from November 16 to November 30. To keep the number of messages at a reasonable level, I won’t send out a separate reminder to you about that. /Johan (WMF) 11:24, 30 October 2018 (UTC)
"Who Wrote That" project update
[edit]Hello. I'm reaching out to you as you participated in the 2017 Community Wishlist proposal for "Who Wrote That" project (previously known as "Blame Tool"). The Community Tech team is kicking things off on the project and we have an early-stage mockup available for you to look at. I invite you to follow that project page, where I will be posting periodic status updates for the project. You are also welcome to provide your thoughts on the talk page. Thank you. -- NKohli (WMF) (talk) 22:57, 21 February 2019 (UTC)
User script to access other watchlists
[edit]Hi He7d3r,
If you remember, you participated in the 2019 Community Wishlist Survey, including the discussion for reviving "Crosswatch" to allow for cross-wiki watchlists (Community Wishlist Survey 2019/Watchlists/Revive Crosswatch tool).
I sent you this MassMessage because I wanted to let you know that I have made a user script to make accessing your watchlists on different wikis easier, since for now that wishlist item has not been actioned.
The way it works is that, on any wiki, when you look at your watchlist, there is a button labeled "CA" that takes you to the CentralAuth page for you. There, when looking at your own information, each link to a wiki ("meta.wikimedia.org", "www.wikidata.org", "de.wikipedia.org", etc.) is changed so that it links to your watchlist on that wiki.
If you are interested in using it, just add mw.loader.load('//meta.wikimedia.org/w/index.php?title=User:DannyS712/Watchlist.js&action=raw&ctype=text/javascript'); to your global javascript page. This imports the code at m:User:DannyS712/Watchlist.js.
If you want to learn more, there is documentation for the script available at w:en:User:DannyS712/Watchlist. If you would like to discuss the script, talk to me at m:User talk:DannyS712.
Thanks, --05:50, 6 June 2019 (UTC)
Hi He7d3r,
I have been using //meta.wikimedia.org/w/index.php?title=User:He7d3r/Tools/ScoredRevisions.js&action=raw&ctype=text/javascript for over 3½ years on en.wiki, but it recently stopped working for me.
I have heavily depended upon the color scoring to sort through my watchlist of 4,000+ pages. I greatly miss it!
Peaceray
- The revision scoring color shading is back as of a few minutes ago! I don't know if anybody did anything special to restore it, but I am thankful to see it again. Peaceray (talk) 16:14, 20 August 2019 (UTC)
- Hi!
- I didn't notice this problem, but I'm glad it was solved by itself :-) Helder 20:58, 20 August 2019 (UTC)
ScoredRevisions.js
[edit]Hey! I'd like to request a feature for this script: running it on large result sets (e.g. RecentChanges with limit 5000) is *very* slow. Would it be possible to add a check for that, with a config option? I'm thinking about a global, like scoredRevisionsMaxResults, that people could set to a reasonable amount (e.g. 200). Then, the script would check if the result size is greater than that variable, and immediately exit if it is. Thanks, --Daimona Eaytoy (talk) 19:55, 23 September 2019 (UTC)
Watchlist Expiry project page
[edit]Hello,
During the Community Whishlist survey 2019, you have voted for the Watchlist item Expiration wish.
Community Tech has created the Watchlist Expiry project page to work on this feature, and is looking for your feedback about the open questions they have.
Regards, IFried_(WMF), 15:51, 25 September 2019 (UTC)
Over-qualified CSS selectors
[edit]My apologies that this message is just available in English.
Over-qualified CSS selectors of portals in Wikimedia skins have been changed. div#p-personal, div#p-navigation, div#p-interaction, div#p-tb, div#p-lang, div#p-namespaces or div#p-variants are now all removed of the div qualifier, as in for example it is #p-personal, #p-navigation …. This is so the skins can use HTML5 elements. Your gadgets or user styles seem to use them and you will have to update them. You can read more in phab:T252467. Johan (WMF) through MediaWiki message delivery (talk) 12:27, 8 June 2020 (UTC)

The 2021 Community Wishlist Survey is now open! This survey is the process where communities decide what the Community Tech team should work on over the next year. We encourage everyone to submit proposals until the deadline on 30 November, or comment on other proposals to help make them better. The communities will vote on the proposals between 8 December and 21 December.
The Community Tech team is focused on tools for experienced Wikimedia editors. You can write proposals in any language, and we will translate them for you. Thank you, and we look forward to seeing your proposals!
18:26, 20 November 2020 (UTC)

We invite all registered users to vote on the 2021 Community Wishlist Survey. You can vote from now until 21 December for as many different wishes as you want.
In the Survey, wishes for new and improved tools for experienced editors are collected. After the voting, we will do our best to grant your wishes. We will start with the most popular ones.
We, the Community Tech, are one of the Wikimedia Foundation teams. We create and improve editing and wiki moderation tools. What we work on is decided based on results of the Community Wishlist Survey. Once a year, you can submit wishes. After two weeks, you can vote on the ones that you're most interested in. Next, we choose wishes from the survey to work on. Some of the wishes may be granted by volunteer developers or other teams.
We are waiting for your votes. Thank you!
16:08, 11 December 2020 (UTC)
He7d3r
[edit]Olá Helder. Notei que você fez uma edição no título de um artigo em 22 de setembro de 2020, argumentando que de acordo com a ortografia da língua portuguesa o correto seria Coomologia, e não Cohomologia. Essa mesma nomenclatura argumentada por você encontrei no corpo do artigo. Sou novato no Wikipedia, e de forma despretensiosa editei para Cohomologia os termos no corpo do artigo. Talvez eu devesse ter consultado você antes de o fazer. De qualquer forma não seria mais 'correto' usar a terminologia Cohomologia ao invés de Cohomologia, apesar de não estar de acordo com a convenção da língua portuguesa? Claro que isso não altera o entendimento do artigo, mas ao meu ver estaria matematicamente mais correto. É uma sugestão. Obrigado pela atenção.
Lucas Lucas Henrique Cardinal (talk) 21:40, 10 March 2021 (UTC)
Score revision tools
[edit]Hi He7d3r, for my patrolling work on itwiki I'm using your tool for revision score. Perhaps in the last weeks is no more working because the api is no more supported. At this link you can find a working version with the new ores v3 api. Lucarosty (talk) 20:00, 8 October 2023 (UTC)
Test and co-create a new feature for reusing references with different details
[edit]Hi,
this is Lina and Eline from the Technical Wishes product team at Wikimedia Deutschland. We hope this message finds you well!
We are currently working on a solution to help Wikimedians easily reuse references with different details – a problem related to several Community Wishlist Survey wishes (partially) supported by you (e.g. 1, 2, 3, 4).
We want to invite you to a user testing session. During the session, you can test a prototype for Visual Editor and provide your feedback. Sessions will take 30–45 minutes, compensation is available. If you are interested, please sign up here (privacy policy).
Please note that most likely, we won’t be able to have sessions with everyone who is interested. We will try to test with a diverse group of wiki contributors. If you’re a fit, we will reach out to you to schedule an appointment.
Hope to hear from you soon, and please let us know if you have any questions!
Best, Lina Farid (WMDE) (talk) 18:17, 10 July 2024 (UTC)
Updates from Capacity Exchange (CapX)!
[edit]
Hello He7d3r,
My name is Joris Darlington Quarshie, and I am an Outreach Facilitator for the Capacity Exchange (CapX) — a platform for finding and connecting with peers to exchange knowledge and skills on a global level.
CapX is a community-built tool, designed by and for the Wikimedia Movement, to make it easier for Wikimedians across the world to find and connect, collaborate, and exchange skills and knowledge with peers.
If you don't know it yet, I invite you to access capx.toolforge.org and create your user profile with your Wikimedia account. But, if you already have a profile, I invite you to check out the new features and possibilities we just launched. I am sure you will be delighted.
CapX's new version incorporates valuable community feedback gathered over the past months, including the Organization Profile - a feature for Wikimedia affiliates, initiatives, or community groups to create their own CapX presence (see here how to create yours).
Click to log in using your Wikimedia unified account through authentication:
Explore CapX's new features
[edit]→ Access: capx.toolforge.org
→ Watch the launch video:Meet the Capacity Exchange
→ Navigate CapX's User Guide and Frequently Asked Questions
→ Share your profile on Meta by adding the predefinition {{CapacityExchange}} to your userpage.
→ Visit our Meta Page for all documentation on the project
→ Join our telegram channel: Capx Telegram Group
Please, let me know if you think your community would enjoy a presentation, workshop demonstration, or feedback session. I would be happy to support you on that. Just reach out, and we can schedule the best date and time together.
Best regards,
Joris Darlington Quarshie
Outreach Facilitator,
Capacity Exchange Project – Wikimedia Brasil
MediaWiki message delivery (talk) 16:02, 29 October 2025 (UTC)
Join us for “Many Tongues, One Movement: Voices Across Languages”!
[edit]
Hello He7d3r,
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)
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
[edit]
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.
More information
[edit]→ 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)
Script Publisher - Community Wishlist 2022 implementation update
[edit]Hello He7d3r,
I hope you are doing well. I am reaching out regarding the Community Wishlist Survey 2022 proposal you supported: “A bot or gadget to publish public Git repo to a gadget or user script”
Over the past few months, I have been working on implementing this as a Toolforge-based OAuth application called Script Publisher. The goal is to provide a web-based interface that allows users to publish JS/CSS files from a public Git repository (e.g., GitHub) directly to user scripts or gadget pages, with explicit preview and confirmation before publishing.
Current project links:
- Toolforge deployment (work-in-progress MVP): https://script-publisher.toolforge.org/
- Source code (public repository): https://gitlab.wikimedia.org/toolforge-repos/script-publisher/
- Initial demo prototype: https://wikipublisher.vercel.app/
The tool currently supports:
- Public repository fetching
- File selection (JS/CSS)
- Mapping files to target wiki pages
- Preview before publish
- Manual publish flow (no background automation)
The main blocker now is OAuth approval for JS-editing permissions. WMF security has raised valid concerns around applications that can edit JavaScript pages, especially site-wide JS. The discussion is ongoing here:
- User_talk:Dev_Jadiya#Script_Publisher
- https://meta.wikimedia.org/wiki/Steward_requests/Miscellaneous#OAuth_permissions
Since you originally supported this wishlist proposal, your technical input and perspective would be extremely valuable. In particular:
- Does the current MVP align with what you expected from this wishlist?
- Are there safeguards you believe are necessary for responsible deployment?
- Would you be willing to share your view in the ongoing Meta discussion?
My intention is not to bypass any security expectations, but to implement this in a way that is aligned with community review standards (similar to bots or interface editors), while keeping the tool transparent, auditable, and limited to user-authorized edits.
Thank you again for supporting the original idea. I would truly appreciate your feedback. Regards, Dev Jadiya (talk) 14:34, 7 February 2026 (UTC)