Hi @Praffq, Are you still planning to submit a new pull request instead of reopening the closed one?

Hi @Aklapper, thanks for the thoughtful feedback.
The goal of #Arabic-Sites is to make it easier to track tasks that directly impact Arabic Wikimedia projects, as they are currently scattered and hard to follow (e.g., UI issues, RTL bugs, localization gaps, editing experience issues).
This tag will help contributors discover relevant issues, follow ongoing work, and coordinate efforts more effectively.
For now, I will take responsibility for adding the tag to relevant tasks. In the near future, we also plan to attract more Arabic-speaking volunteers to watch and maintain these tasks.

@Praffq, You can use via Toolforge: wikitech:Help:Toolforge/Redis
It’s a better fit because it provides a shared, persistent queue, supports list operations, and works well if we scale to multiple servers. It also handles reconnections more reliably using Last-Event-ID.
Additionally, this task is mainly about reducing load on the JVM container, and moving the event buffer to Redis helps offload memory and connection pressure from the application itself.

@Praffq, What will you do about that?

Architectural Note: Since the server currently maintains a single global EventSource connection to Wikimedia and broadcasts to all SseEmitter clients, handling individual client catch-ups requires either caching recent events in memory/Redis or allowing clients to fetch missed events via a separate REST endpoint before joining the live stream again.

@Praffq, Thanks :)

@Nemoralis, You can proceed with it, and thank you. If any assistance is needed, please feel free to ping me in the channel #wikimedia-operations on IRC (my nick is _Gerges).

Yes, I noticed this; see pull 44.

Hi! 👋
Thanks for your contribution — I've reviewed your pull request and approved it. Great work!

Thank you for tagging this task with good first task for Wikimedia newcomers!

Hi @Praffq, I cannot grant you rollback permissions, but I added a variable REQUIRE_ROLLBACK_RIGHT, set its value to false, to bypass the validation check.

I have submitted a pull request:
https://github.com/wiki-connect/wikimonitor/pull/42

This is an example:

In T420850#11758561, @Praffq wrote:

Hey @Gerges , When I try to log in to WikiMonitor locally, the OAuth flow with Wikimedia completes successfully, but the app then rejects my login with a "no_rollback_rights" error. This happens because AuthController.java (line 52) calls mediaWikiService.checkAnyRollbackRights(username) which queries the Wikimedia API to verify the user is a rollbacker or sysop on at least one wiki, and my account (Praffq) doesn't have those rights. As a temporary workaround I've commented out the rollback rights check, but I wanted to ask, is there a recommended way to test locally without rollback rights, or a sandbox wiki where these rights can be obtained for development?

After thinking about it, I believe storing a user’s access token is extremely risky. It is better to store the refresh token on the user side for 30 days.

Hi @Praffq, Currently, there is no way to do this without rollback permission (See also: test2.wikipedia.org and test.wikidata.org). You can open a ticket explaining the problem in general terms so we can work on it in the future.

Hi @Praffq! 👋
Great to hear that you're interested in working on this issue — welcome! 🎉
Yes, feel free to go ahead and open a PR directly on the GitHub repository. If anything is unclear or you need guidance at any step, don’t hesitate to ask.
Looking forward to your contribution! 🚀

Thanks @Vishaldevops :)

@Vishaldevops, Good to hear that. please submit a pull request so we can test it on the beta server.

Thank you for tagging this task with good first task for Wikimedia newcomers!

The pull request has been merged. Thank you for your contribution!

Thanks @TANMy789.

Hello @SheetalPro and @Vishaldevops ,
It’s great to see this level of enthusiasm for collaboration—teamwork is at the heart of open-source projects.
You’re both welcome to work together on resolving this issue; however, only one person should submit the pull request.
You can also include Co-authored-by: Name <email> in the commit message to give proper credit.

Hi @TANMy789, please follow https://www.mediawiki.org/wiki/New_Developers#Communication_tips.

Thank you for tagging this task with good first task for Wikimedia newcomers!

Thank you for tagging this task with good first task for Wikimedia newcomers!

done :)

I’ve submitted pull: https://github.com/wiki-connect/wikimonitor/pull/24

@SheetalPro, Did you create a .env file?

Hi @SheetalPro and @Vishaldevops,

Thank you for tagging this task with good first task for Wikimedia newcomers!

Done

search works for me now, I searched for WQ, it took a long time and I didn't get any results, before it crashed.

Additional note: OAuth 2.0 using Owner-only consumers works correctly and allows editing without issues.
The problem appears when using standard OAuth 2.0 consumers (non owner-only), where the API returns HTTP 401 with Jwt issuer is not configured.
This suggests the issue may be limited to JWT validation or issuer configuration for non owner-only flows.

Community consensus is needed to make this change.

I introduced a change that a BotPassword::login(). As a result, the assertion in BotPasswordTest::testLogin() expecting a nosuchuser error for UTDummy@BotPassword is no longer valid.
Should I delete the test on line 318, or reverse it and make it assertStatusGood?

Done

Hi @sanjaisid, Thanks for your contribution, Sorry for the delay, I've been busy with several projects outside of Wikimedia. I'll try my best to review your patch.

I searched on Google using the query "WikiPedia [MN]" site:mn.wikipedia.org, and based on my check, the affected pages seem to be very limited. I found only one page showing this unusual title in the search results: Файл:Mongolian_Aimags,_Mongolia.png
It appears that this issue is isolated to this specific page, and I did not observe the same behavior for other pages on Mongolian Wikipedia.

@Pppery, can't upload on File:Wikibooks-wordmark-v2-ar.svg for per https://w.wiki/FgE2 "the wordmark width should not exceed 124px".

@Pppery, Yes. Sorry, I forgot the task.

I would like to request being added to acl*Project-Admins, as I am currently leading the Tech Hub team at the Egypt Wikimedians User Group. Our team will soon begin creating new projects, along with several sub-projects, and I will need the appropriate permissions to manage them effectively.

In T399334#11114809, @Daimona wrote:

In T399334#11113340, @hubaishan wrote:

arwiki use FlaggedRevs so no need to this line. review right is assigned to editor which work as patrol.

Ah, nice! So does that mean this task can be closed?

I'm not good at Chinese and the browser translation is bad, no one mentioned disable the use of magic words __INDEX__/__NOINDEX__ in User namespace.

Hi @Dringsim, You mean wmgExemptFromUserRobotsControlExtra?

When I try via curl to simulate an android browser session and delete User-Agent it works without problems, there is a problem from User-Agent.

Hi @Aklapper, I use kiwi browser (Powered by Chromium kernel), this my request

GET /r/c/operations/mediawiki-config/+/1063920 HTTP/1.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
Accept-Encoding: gzip, deflate, br
Accept-Language: en-GB,en;q=0.9,ar-EG;q=0.8,ar;q=0.7,en-US;q=0.6
Cache-Control: max-age=0
Connection: keep-alive
Cookie: _shopify_y=C68A09C********; _tracking_consent=%7B%22con%22%3A%7B%22CMP%22%3A%7B%22a%22%3A%22%22%2C%22m%22%3A%22%22%2C%22p%22%3A%22%22%2C%22s%22%3A%22%22%7D%7D%2C%22v%22%3A%222.1%22%2C%22region%22%3A%22EGGZ%22%2C%22reg%22%3A%22%22%2C%22purposes%22%3A%7B%22a%22%3Atrue%2C%22p%22%3Atrue%2C%22m%22%3Atrue%2C%22t%22%3Atrue%7D%2C%22display_banner%22%3Afalse%2C%22sale_of_data_region%22%3Afalse%2C%22consent_id%22%3A%226550575E-924c-4EE4-8620-306ea5dfbbc7%22%7D; __mmapiwsid=0195a12******
Host: gerrit.wikimedia.org
Sec-Fetch-Dest: document
Sec-Fetch-Mode: navigate
Sec-Fetch-Site: none
Sec-Fetch-User: ?1
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Mobile Safari/537.36
sec-ch-ua: "Not-A.Brand";v="99", "Chromium";v="124"
sec-ch-ua-mobile: ?1
sec-ch-ua-platform: "Android"

Done.

I will delete the test isAvailable() uses window.chrome to filter certain chrome-like browsers because the condition windowObj.chrome === undefined has been removed. Are there any concerns or objections to this change?

I've written the patch and tested the code on Firefox. The "Download PDF" button appears successfully, but some Firefox-specific tests are failing. Does anyone have any comments so I can write new tests?

Thank you for tagging this task with good first task for Wikimedia newcomers!

Hi @Bugreporter, Would you also like to noindex all pages in User Talk namespace?

@CDobbins, Yes, I still need access to Logstash. I do need an NDA, but please note that I’m working independently as a volunteer, without support from team wmf.