Jump to content

User talk:Dev Jadiya

Add topic
From Meta, a Wikimedia project coordination wiki
Latest comment: 2 days ago by ZI Jony in topic This Month in Education: February 2026

Welcome to my User Talk Page!

Feel free to leave any questions, comments, or suggestions here, particularly regarding my contributions or collaborations on Wikipedia. I’m open to constructive feedback and discussions that can enhance our work in this space.

Thank you, and I look forward to collaborating with you!

Translation notification: Incident Reporting System

[edit]

Hello Dev Jadiya,

You are receiving this notification because you signed up as a translator to Hindi on Meta. The page Incident Reporting System is available for translation. You can translate it here:

The priority of this page is medium.


Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

To unsubscribe or to change your notification preferences for translations, please visit Special:TranslatorSignup.

Thank you!

Meta translation coordinators‎, 03:53, 2 August 2025 (UTC)

Capacity Exchange: New Design, Features & Ways to Connect!

[edit]

Hello Dev Jadiya!

Our platform has undergone several updates and has a new design and brand-new features available. We would like to invite you to explore the tool and give your feedback to help us make it even better.

Also, call your wiki-friends to Join for the Exchange.

If you experience any difficulty navigating the tool, here is our User Guide with a step-by-step tutorial on how to use each feature.

To interact with the CapX team, share your feedback, or offer a suggestion, you can use the Bug Reports feature in the tool or email capx(_AT_)wmnobrasil.org.

For quick questions and suggestions, we've set up a Telegram channel. We also invite you to add the {{CapacityExchange}} template and the {{CapXsupporter}} userbox to your user page to express your support.

Finally, we created a newsletter channel for those interested in receiving regular updates about the tool and the Capacity Exchange project - click here to subscribe.

See you exchanging around!

You are receiving this message because you have registered on Capacity Exchange.

Sincerely,
AJurno (WMB)
MediaWiki message delivery (talk)
13:02, 19 August 2025 (UTC)Reply

Translation notification: Template:Affiliate recognition pause notice 2025

[edit]

Hello Dev Jadiya,

You are receiving this notification because you signed up as a translator to Hindi on Meta-Wiki. The page Template:Affiliate recognition pause notice 2025 is available for translation. You can translate it here:

The priority of this page is low.


Your help is greatly appreciated. Translators like you help Meta-Wiki to function as a truly multilingual community.

To unsubscribe or to change your notification preferences for translations, please visit Special:TranslatorSignup.

Thank you!

Meta-Wiki translation coordinators‎, 15:33, 30 August 2025 (UTC)

Incident Reporting System/hi translation

[edit]

Hello, thank you so much for translating Incident Reporting System/hi into Hindi! There are just a few little mistakes I'd like to point out that I hope you'll take care of in the future.

In MediaWiki and on Wikimedia, "user" is translated as "सदस्य" and not "उपयोगकर्ता"। You can refer to the Hindi MediaWiki glossary here. Also, when using first person pronouns, please include both genders of the reader. E.g. this message can be rephrased as: "मैं यह बताना चाहता/चाहती हूं कि मैं किस प्रकार की घटना से गुजर रहा/रही हूं [...]".

Lastly, when translating a list of "goals" or similar, I believe it is better to translate the list items with their "करना" forms rather than "करें" to form complete coherent sentences, i.e. "X का लक्ष्य है Y करना" is correct.

Apart from that, once again, thank you for your contributions ^^ ~ ✽ saurmanđal17:09, 30 August 2025 (UTC)Reply

Thankyou so much for helping. I will read the glossary and translate more accurately from next time. धन्यवाद 🙏 Dev Jadiya (talk) 17:39, 30 August 2025 (UTC)Reply

This Month in Education: August 2025

[edit]

Translation notification: Meta:Deletion policy

[edit]

Hello Dev Jadiya,

You are receiving this notification because you signed up as a translator to Hindi on Meta-Wiki. The page Meta:Deletion policy is available for translation. You can translate it here:

The priority of this page is low.


Your help is greatly appreciated. Translators like you help Meta-Wiki to function as a truly multilingual community.

To unsubscribe or to change your notification preferences for translations, please visit Special:TranslatorSignup.

Thank you!

Meta-Wiki translation coordinators‎, 07:06, 15 September 2025 (UTC)

Translation notification: Wikimedia Foundation website

[edit]

Hello Dev Jadiya,

You are receiving this notification because you signed up as a translator to Hindi on Meta-Wiki. The page Wikimedia Foundation website is available for translation. You can translate it here:

The priority of this page is low.


Your help is greatly appreciated. Translators like you help Meta-Wiki to function as a truly multilingual community.

To unsubscribe or to change your notification preferences for translations, please visit Special:TranslatorSignup.

Thank you!

Meta-Wiki translation coordinators‎, 05:46, 29 September 2025 (UTC)

This Month in Education: September 2025

[edit]

Script Publisher

[edit]

Hi Dev! Has there been any community discussion about Script Publisher? We are generally very cautious about approving OAuth apps which can edit Javascript. Tgr (WMF) (talk) 19:46, 29 October 2025 (UTC)Reply

Hello Gergő,
Yes, Script Publisher has been discussed in the Community Wishlist Survey. You can find details at Community Wishlist 2022: A bot or gadget to publish public Git repo to a gadget or user script.
For your reference, a live demonstration of the project is also available: publisher Demo.
I am actively engaging with the original proposer, @Nux, as well as mentors from the Developer Skill Development Program India 2025, to ensure all aspects of the project are carefully reviewed and community feedback is incorporated.
Regarding OAuth permissions, I will proceed with local testing of all changes and only deploy to Toolforge after thorough review and feedback collection. If you have specific recommendations or requirements about permission scopes, please let me know. I am happy to adjust the configuration to meet WMF security standards and community expectations.
Thanks, Dev Jadiya (talk) 02:34, 30 October 2025 (UTC)Reply
Hi @Tgr (WMF) I suggested using toolforge and OAuth to Dev to make this a more reliable place. As I understand for JS changes the application would actually use bot accounts (which can have restricted rights and can easily be revoked) and OAuth just to get the main user name and preferences and other stuff would be saved within the app (I assume some internal database)... At least that was the idea, not sure what Dev want to implement in the end. Nux (talk) 09:13, 30 October 2025 (UTC)Reply
The current request is for an OAuth app with JS editing rights. I am not saying that's worse than other mechanisms for editing sitewide JS, but for a bot there's an established approval mechanism, and since the security risks are comparable I think we'd want a similar level of community scrutiny / support for an OAuth app (maybe via a mock bot flag request, for the lack of a better place for discussing it). Tgr (WMF) (talk) 10:37, 31 October 2025 (UTC)Reply
Re: the updated scopes, unfortunately there is very little difference security-wise between "edit your own JS" and "edit sitewide JS". A malicious application can just put some XSS code in the user's own JS and sent the user to that wiki, and then the XSS code will make an API edit to the sitwide JS.
("Malicious application" could in practice mean a whole range of things, from "you installed malware and it stole your Toolforge password" to "your application got compromised by one of its dependencies in a supply chain attack". These risks are not the end of the world - editors who can change sitewide JS can just as easily be compromised by malware etc, it's a risk we need to live with to some extent. But in all other cases, access to site JS or another user's user JS is only given out via a community review process, be that bot approval or bureaucrat review for interface admins, and I think we should match that for OAuth permissions.) Tgr (WMF) (talk) 19:50, 2 November 2025 (UTC)Reply
Hi @Tgr (WMF) and Nux: I have been supporting Dev as he is working on the projects, mostly navigating these processes. If I am understanding correctly, even if though it is OAuth permissions, since it includes JS editing access, it should involve a community review, rather than a single person deciding. If that's right, what would be a good place to have to that discussion, maybe Meta:Requests_for_adminship#Requests_for_bot_flags? Please let us know if there are better venues. Not a security expert, but I am also wondering if there any simple technical checks that we can include in the tool to prevent such malicious behaviour, like not allowing external domains, not allowing edit API calls to .js, .css, pages MediaWiki:, and Module: namespaces, from within the user script. KCVelaga (talk) 08:50, 3 January 2026 (UTC)Reply
Steward_requests/Global_permissions#Requests_for_other_global_permissions I think, since permission-wise this tool will be equivalent to Global interface editors?
Trying to detect (possibly obfuscated) malicious Javascript seems like an unwinnable battle, but that's not really the risk here anyway - OAuth tools are subject to the normal permission system so users will only be able to install gadgets with the tool if they would be allowed to do the same thing manually. If someone would use the tool to install a harmful script, presumably they would/could do the same thing by hand; the tool isn't really making things worse. (Assuming the tool does not deploy JS changes without the explicit consent of the deployer, and without making it clear to the deployer exactly what changes are being deployed. Those should be requirements for such a tool, IMO.)
Rather, the risk is that the tool itself is changed (e.g. by someone hacking into the Toolforge account) to deploy different JS code than it is supposed to. So the expectations wrt. community review are similar to interface admins, I think: account security best practices, and making sure that those with developer access to the tool know what they are doing and don't leave security holes that can be used to hijack it. Tgr (WMF) (talk) 20:55, 5 January 2026 (UTC)Reply
Hi Tgr (WMF), Nux and KCVelaga,
Following the discussion here about community review and permissions for Script Publisher, I have now opened a formal request on Steward requests for global permissions for the tool:
https://meta.wikimedia.org/wiki/Steward_requests/Global_permissions#Script_Publisher_-_OAuth_Toolforge_tool_for_publishing_public_Git_repositories_to_Wikimedia_JS/CSS_pages
This request includes the project background, Toolforge deployment, source code, OAuth client, and the security model, in line with the guidance you gave earlier.
I would appreciate your review and any feedback there so we can ensure the tool meets community and WMF security expectations before OAuth approval and wider use.
Thank you all for your guidance so far. Dev Jadiya (talk) 13:41, 10 January 2026 (UTC)Reply
Was not able to test the latest version, but I briefly went through the code. Some problems I see with that:
  1. It seems to use gitingest.com to fetch repository files [1], which seems like a bad idea. If it is only used to lint files I guess that's fine, but not sure what this does.
  2. Loading remote script might be problematic too (remote website code execute code in the context of the Script Publisher application). Like e.g. [2].
  3. Most changes in git are not described correctly (which would make the code hard to review if that continues). E.g. changes are described "updated" and should be more like e.g. "OAuth2 support"
I never used Django though, so cannot really review the code. Nux (talk) 15:19, 10 January 2026 (UTC)Reply

This Month in Education: October 2025

[edit]

Translation notification: Template:Cat main

[edit]

Hello Dev Jadiya,

You are receiving this notification because you signed up as a translator to Hindi on Meta-Wiki. The page Template:Cat main is available for translation. You can translate it here:

The priority of this page is low.


Your help is greatly appreciated. Translators like you help Meta-Wiki to function as a truly multilingual community.

To unsubscribe or to change your notification preferences for translations, please visit Special:TranslatorSignup.

Thank you!

Meta-Wiki translation coordinators‎, 06:12, 6 November 2025 (UTC)

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

[edit]

Hello Dev Jadiya,

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 ProjectWikimedia Brasil

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

This Month in Education: November 2025

[edit]

Translation notification: Help:Two-factor authentication

[edit]

Hello Dev Jadiya,

You are receiving this notification because you signed up as a translator to Hindi on Meta-Wiki. The page Help:Two-factor authentication is available for translation. You can translate it here:

The priority of this page is medium.


Your help is greatly appreciated. Translators like you help Meta-Wiki to function as a truly multilingual community.

To unsubscribe or to change your notification preferences for translations, please visit Special:TranslatorSignup.

Thank you!

Meta-Wiki translation coordinators‎, 03:09, 6 December 2025 (UTC)

This Month in Education: December 2025

[edit]

Translation notification: Universal Code of Conduct/Annual review/Messages/Review open

[edit]

Hello Dev Jadiya,

You are receiving this notification because you signed up as a translator to Hindi on Meta-Wiki. The page Universal Code of Conduct/Annual review/Messages/Review open is available for translation. You can translate it here:

The priority of this page is medium. The deadline for translating this page is 2026-01-19.

This message will be sent to all the wikis to inform communities about their chance to participate in proposing changes to the Universal Code of Conduct.

Your help is greatly appreciated. Translators like you help Meta-Wiki to function as a truly multilingual community.

To unsubscribe or to change your notification preferences for translations, please visit Special:TranslatorSignup.

Thank you!

Meta-Wiki translation coordinators‎, 22:30, 14 January 2026 (UTC)

This Month in Education: January 2026

[edit]

Translation notification: Wiki Loves Ramadan 2026/List of Articles/Culture/1

[edit]

Hello Dev Jadiya,

You are receiving this notification because you signed up as a translator to Hindi on Meta-Wiki. The page Wiki Loves Ramadan 2026/List of Articles/Culture/1 is available for translation. You can translate it here:

The priority of this page is low. The deadline for translating this page is 2026-02-28.

Hello! We have a new page for translation: Wiki Loves Ramadan 2026/List of Articles/Culture/1. Thank you!

Your help is greatly appreciated. Translators like you help Meta-Wiki to function as a truly multilingual community.

To unsubscribe or to change your notification preferences for translations, please visit Special:TranslatorSignup.

Thank you!

Meta-Wiki translation coordinators‎, 11:02, 15 February 2026 (UTC)

Translation notification: Global username policy

[edit]

Hello Dev Jadiya,

You are receiving this notification because you signed up as a translator to Hindi on Meta-Wiki. The page Global username policy is available for translation. You can translate it here:

The priority of this page is medium. The deadline for translating this page is 2026-12-31.

Hello! We have a new page for translation: Global username policy. Thank you very much!

Your help is greatly appreciated. Translators like you help Meta-Wiki to function as a truly multilingual community.

To unsubscribe or to change your notification preferences for translations, please visit Special:TranslatorSignup.

Thank you!

Meta-Wiki translation coordinators‎, 14:25, 15 February 2026 (UTC)

Translation notification: Event:Queer Women in Arts

[edit]

Hello Dev Jadiya,

You are receiving this notification because you signed up as a translator to Hindi on Meta-Wiki. The page Event:Queer Women in Arts is available for translation. You can translate it here:

The priority of this page is high. The deadline for translating this page is 2026-02-28.

Hello! We have a new page for translation: Event:Queer Women in Arts. Thanks!

Your help is greatly appreciated. Translators like you help Meta-Wiki to function as a truly multilingual community.

To unsubscribe or to change your notification preferences for translations, please visit Special:TranslatorSignup.

Thank you!

Meta-Wiki translation coordinators‎, 19:10, 18 February 2026 (UTC)

Expression of Interest to volunteer for WikiConference India 2026

[edit]

Thank you Dev Jadiya for signing up to volunteer for WikiConference India 2026.

We kindly request you to complete this Google Form with your contact information before February 28th, 2026 to help us coordinate with you. The information you provide will assist the organizing team in planning effectively and ensuring a meaningful volunteering experience for everyone.

Thank you for your support

Warmly,
Athul R T
on behalf of the Organizing Team of WCI 2026
This message was sent with MediaWiki message delivery (talk) on 10:03, 19 February 2026 (UTC)Reply

Translation notification: Mission

[edit]

Hello Dev Jadiya,

You are receiving this notification because you signed up as a translator to Sanskrit on Meta-Wiki. The page Mission is available for translation. You can translate it here:

The priority of this page is medium.


Your help is greatly appreciated. Translators like you help Meta-Wiki to function as a truly multilingual community.

To unsubscribe or to change your notification preferences for translations, please visit Special:TranslatorSignup.

Thank you!

Meta-Wiki translation coordinators‎, 02:15, 28 February 2026 (UTC)

This Month in Education: February 2026

[edit]