Jump to content

User talk:FR30799386

Add topic
From Meta, a Wikimedia project coordination wiki
(Redirected from User talk:Force Radical)
Latest comment: 1 year ago by Quangkhanhhuynh in topic Feedback

Welcome to Meta!

Hello, FR30799386. Welcome to the Wikimedia Meta-Wiki! This website is for coordinating and discussing all Wikimedia projects. You may find it useful to read our policy page. If you are interested in doing translations, visit Meta:Babylon. You can also leave a note on Meta:Babel or Wikimedia Forum if you need help with something (please read the instructions at the top of the page before posting there). Happy editing!

--Liuxinyu970226 (talk) 11:11, 30 November 2017 (UTC)Reply

Commond deletion bot requirements[edit]

I'm contacting you because you supported the Commons Deletion Bot proposal in the 2017 Community Wishlist. The Wishlist team has finalized the draft specifications for how the bot will work, and are seeking review in confirming or discussing the plans for the bot. If you have some time, please take a look and leave a comment. Thanks, happy editing to you. - Keegan (WMF) (talk) 19:06, 12 April 2018 (UTC)Reply

New community space for IdeaLab on Connect[edit]

Hi folks. If you're receiving this message, you've contributed to IdeaLab or an Inspire Campaign this year. Thanks for participating to develop ideas and review ones from other Wikimedians.

We are preparing some changes to IdeaLab and Inspire Campaigns. One of these changes is a new community space on Connect, where Wikimedians can find each other based on common activities or skills, and ask questions about the space. You are invited to join this community space for IdeaLab, especially if you would ever consider needing to find contributors with certain skills (like design or project management) or would like to offer your skills to others in our movement. To join, please proceed to Connect/IdeaLab and click on the "Add yourself" button on the right. Thanks, I JethroBT (WMF) 19:53, 21 June 2018 (UTC)Reply

(Opt-out instructions)

Inspire Campaign on Measuring Community Health[edit]

Do you have an idea about how to measure the health of your community? Do you want to review ideas that others have submitted? Through August 10th, we are inviting ideas on how to capture the well-being of Wikimedia communities, in terms of matters like conflict resolution, effective content creation, and being able to contribute in a collaborative environment. Ideas can be focused on either quantitative techniques, such as gathering raw data, or qualitative techniques, like surveying contributors. If you are submitting an idea, guidance is available for how to move your idea into implementation, such as through a grant or starting a Phabricator task to engage with developers.

If you're interested, consider joining the Inspire Campaign. I JethroBT (WMF) 17:13, 13 July 2018 (UTC)Reply

(Opt-out instructions)

Timeless Newsletter • Issue 1[edit]

Newsletter • July 2018

Welcome to the first issue of the Timeless newsletter! This issue is being sent or forwarded to everyone who has at some point expressed an interest in the project, give or take, as well as a couple of other potentially relevant pages, so if you would like to continue (or start) receiving this newsletter directly, please sign up for further updates on the meta page.

The news:

The Timeless grant has been selected for funding, and the project is now underway!

While I've had a somewhat slow start working on the project for health reasons, I'm pleased to announce that everything described in the proposal is now either happening, or on its way to happening.

Current progress:

  • The project now has a hub on Meta to serve as a directory for the various related pages, workboards, and local discussions and help pages. It's probably incomplete, especially with regards to specific language projects that might have local pages for Timeless, so if you know of others, please add them!
  • Outreach: I've been talking to various people and groups directly about skinning, desktop/mobile interfaces, project management, specific component support, and other things, and have begun to compile a very shoddy list of skinning problems and random issues on mw.org based on this. Some of this may inform the direction of this project, or possibly this project will result in building a more proper list that can then be used for other things. We shall see.
  • Some development - task triage, code review, bug fixing, and various rabbit holes involving ...overflows.

General plan for the future:

  • Triage the rest of the workboard.
  • Catch up with all the talkpages and other bug reports that have been left various other places that are not the project workboard
  • Do all the bug fixes/features/other things!
  • Some proposals aimed at Commons and Wikisource in particular (maybe, we'll see)

Essentially, the grant as written shall be carried out. This was the plan, and remains the plan. Timelines remain fuzzy, but while there have been some initial delays, I don't particularly expect the timeline for project as a whole to change a whole lot.

Also, for anyone at Wikimania right now: I am also at Wikimania. Come talk to me in person!

Thank you all for your interest and support thus far!

-— Isarra 12:23, 20 July 2018 (UTC)Reply

This issue has been sent regardless of signup status. To receive future issues please add yourself on the massmessage list.

Commons deletion notification bot[edit]


You are receiving this message because you supported the Commons deletion notification bot in the 2017 Community Wishlist Survey.

Commons deletion notification bot is ready to be deployed to any Wikimedia wiki that wishes to use it. If your community is interested in the bot, you can leave a request on the project page on meta-wiki. The bot messages are available for translation on translatewiki.net, as part of preparing the bot for release.

Thank you for your participation in the Wishlist. -- Keegan (WMF) (talk) 17:29, 16 August 2018 (UTC)Reply

Timeless Newsletter • Issue 2[edit]

The second issue of the Timeless newsletter is out.

The news: Themes are coming to Timeless! Your infobox and navbox templates in particular are probably going to look absolutely horrible in the new built-in night mode.

For more information, background, plans and progress updates, please see the full issue on Meta, complete with a ridiculous list of phabricator task links, gratuitous mention of other skins, and me complaining about the current state of MediaWiki skinning in general.

-— Isarra 01:48, 30 August 2018 (UTC)Reply

The Community Wishlist Survey[edit]


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)Reply

Timeless Newsletter • Issue 3[edit]

Newsletter • December 2018

Welcome to the third issue of the Timeless newsletter, complete with a somewhat dubious explanation of where I've been all this time.

Somewhat dubious explanation of where I've been all this time:

I suffered a rather bad concussion in October, which knocked me pretty much completely out of commission through November, and I'm still recovering even now. One person = bus factor of one, even though it wasn't actually a bus but a very short flight of stairs.


  • Random bugs have been fixed. More bugs have been found. For a full list of horrors, see the workboard.
  • Implementing themes (T131991: the dark/night mode and winter variants of the skin) has proven far more complicated than initially thought, lacking either the extension, or preferably, some core support for this functionality. Thus:
    • I have submitted a Request for Comment proposing to merge Extension:Theme into core - this will enable skins to specify style variants as distinct options for users to select in their preferences by letting the skin specify the styles separately for each, a much neater way of implementing this than some of the existing hacks.
    • Jack Phoenix has already submitted a patch to do this. We simply need the buy-in and consensus to merge it, and to resolve whatever issues may arise from this wider review.

Comments on the RfC (MediaWiki wiki RfC page, task) or bugs, or further reports, are always appreciated.

Until next time, hopefully with no further injuries,

-— Isarra 22:35, 20 December 2018 (UTC)Reply

Timeless Newsletter • Issue 4[edit]

Newsletter • April 2019

Welcome to the fourth issue of the Timeless newsletter, with a cat! Or maybe not.

Un chat qui miaule???

It's true! The angry cat, a fundamental part of Timeless, has resulted in confusion and bug reports all across the projects and phabricator. And now it shall be immortalised forever in the new, shiny Timeless logo.


After putting off the project for three months because I got hit in the head with a flight of stairs, and then putting off the project for another two months while working out what the status of the grant was, I have now put off the project even more in order to focus on my other project for a bit. So progress lately has been a bit whims-based as a result:


  • The French Wiktionary voted to set Timeless as their default skin, with results possibly as you might expect: I ran away and hid, and the WMF said no. A bit of discussion later and we largely agreed that all else aside, this is a bit of a branding issue, but we love the enthusiasm! Also the bug reports that inevitably come out of such a discussion. I'm still working on properly going through those.
  • Theme support is still stuck in limbo, but now we have another skinning RfC. tl;dr, we wanna replace the entire skinning system, and Skizzerz'll write a prototype later.

I will be fully resuming work on Timeless next week, or maybe the week after, depending on what madness (or illness) comes out of the Hackathon in Prague. Please come talk to me there to discuss strategy!

-— Isarra 16:51, 14 May 2019 (UTC)Reply


Hello, I frequently use your script on en-wiki. Since you are blocked on en-wiki I am contacting you here. First I've copied and pasted your script to my Undo.js on meta-wiki and test-wiki because I wanted to use this script here. Hope you don't mind. Also since the MediaWiki update about 2 months ago, some notice (edit-conflict, protected page, already reverted) don't work anymore. I've imported the script from DannyS712 script after you got blocked. The basic edit revert and thanks feature is still working. Thanks. Sincerely, Masum Reza 08:08, 26 June 2019 (UTC)Reply

Masumrezarock100, I'll take a look right now.  — FR 09:17, 26 June 2019 (UTC)Reply
@Masumrezarock100:, could you add mw.loader.load('//meta.wikimedia.org/w/index.php?title=User:FR30799386/undo.js&action=raw&ctype=text/javascript'); (instead of the imported script) to your minerva.js file and check if it works now?  — FR 09:31, 26 June 2019 (UTC)Reply
Thanks it's now working on both of my browsers (Firefox Nightly and Chrome Dev 76 for Android). I thought the problem was in my browsers. I will import this script right away on en-wiki. Sincerely, Masum Reza 11:20, 26 June 2019 (UTC)Reply
Working on en-wiki too. Also just a suggestion, the link in the "revert failed" message points to your en-wiki talk page when I use it on en-wiki. Since, you are blocked on en-wiki, you probably won't be able to respond to bug reports there. So I think the link should point to your meta (or whatever wiki you want) talk page. Thanks again. Have a great evening. Sincerely, Masum Reza 11:30, 26 June 2019 (UTC)Reply
Would you mind if I nominate your mobileUndo script to be a gadget at Village Pump technical? I've checked this script thoroughly and it works on meta, wikidata, test wiki and probably other wikis. Currently mobile version of mediawiki software has no undo feature whatsoever. Please say yes. It will benefit many editors who edit Wikipedia on mobile. Please reply and ping me as soon as possible. Sincerely, Masum Reza 02:33, 28 June 2019 (UTC)Reply
Also it has cross-browser compatibilities, I think. So far I've tested it using Firefox, Microsoft Edge, Chrome. Also it works with their beta versions too. Sincerely, Masum Reza 02:39, 28 June 2019 (UTC)Reply
Masumrezarock100, I certainly won't mind if you nominate the script as a gadget on VPT. (I'll create a description page over at meta in that occasion just in case.) However, is DannyS712 (the current maintainer of the script at enwiki) also on the same page ? — FR 10:08, 28 June 2019 (UTC)Reply
I have asked him. I don't think he will object. Also he asked me to take over the script but I declined the offer. Sincerely, Masum Reza 10:38, 28 June 2019 (UTC)Reply
Hello. Here's the diff of my request on en:WP:VPT. Sincerely, Masum Reza 12:05, 28 June 2019 (UTC)Reply
Yes the current maintainer is on the same page. Sincerely, Masum Reza 21:12, 28 June 2019 (UTC)Reply
Hello I've checked the script in Opera Mini. It works with the latest version the Opera Mini. Could you recheck it and update the documentation page? Sincerely, Masum Reza 22:36, 30 June 2019 (UTC)Reply
Masumrezarock100, I did check it on Opera Mini on atleast four phones, it doesn't work. AFAIK, most javascript doesn't really work on Opera Mini (or is very patchy) so I think it's best we keep the documentation the way it is.  — FR 13:52, 5 July 2019 (UTC)Reply
I see. I only tried it on my Android 7.0 and it worked. Sincerely, Masum Reza 05:04, 6 July 2019 (UTC)Reply
Hello I asked a WMF software engineer MusikAnimal. Could you please modify the script per his advice here? Thanks in advance. Sincerely, Masum Reza 15:24, 14 July 2019 (UTC)Reply
Masumrezarock100, Doing those changes will mean that I have invest a non trivial amount of time and effort into re-writing the script. Unless I have a concrete commitment that the script will be incorporated into production after the script has been rewritten to Wikimedia production standards I am hesitant to make those changes. Pinging MusikAnimal (WMF) also to this discussion. — FR 17:58, 14 July 2019 (UTC)Reply
Does that mean you are not going to make those changes? OOUI widgets are compatible with almost all mobile browsers. Sincerely, Masum Reza 08:14, 15 July 2019 (UTC)Reply
The problem is not fully regarding using OOUI (which the script uses in some parts). I can't figure out how the hell to implement localisation without breaking everything.  — FR 10:47, 15 July 2019 (UTC)Reply
I tried to rewrite the script on test wiki but failed. I am not that good at coding JavaScript.
But hang on a second, I tried to use the old version where you used OOUI, on test wiki. It works fine. Thanks and undo button both seem to be working. Sincerely, Masum Reza 08:10, 18 July 2019 (UTC)Reply
The OOUI version of the script has a few cosmetic (CSS) changes that I need to implement before it can actually be used. Also, I discovered that the script is incompatible with abuse filters. I guess I'll be able to implement (and fix) everything by the end of this week.  — FR 08:42, 18 July 2019 (UTC)Reply
Thank you very much. Could you add a similar feature like Restore this version which restores a version of a page? This feature is available in Twinkle and it automatically restores a version of a page. If not automatic restoration, you could also make it like en:User:BrandonXLF/Restorer.js which requires the user to manually save the page. You don't have to fulfil any of the above requests, if you don't want to. Sincerely, Masum Reza 09:01, 18 July 2019 (UTC)Reply
Masumrezarock100, I have updated the script to use OOUI. I'll try and implement the restore link functionality over this weekend. :)  — FR 16:37, 18 July 2019 (UTC)Reply
Glad to hear it and good night. Could you update the version written in JavaScript comments? Masum Reza 16:55, 18 July 2019 (UTC)Reply

Bug report[edit]

Something is probably wrong with codes in the script. When I click Undo, a dialogue box appears asking for a reason, and if I click or tap OK (doesn't matter if I write a reason or not), the text, Undo changes to Loading as usual. But if I tap or click on Loading text the same dialogue box appears again asking for a reason. The box stays like that, until the page reloads or if I don't click cancel. Users with high speed internet, might not find this as an issue. But I think the page should reload immediately. Also if the revert fails for some reason (doesn't matter what the reason is), a Failed text appears in the button same as usual. If I click it same thing happens. Also if the script loads, the Thanks button becomes smaller and the icon in it disappears. All main functions are fine such as undo and thanks. Sincerely, Masum Reza 17:48, 18 July 2019 (UTC)Reply

Masumrezarock100, I temporarily fixed the undo button problem.  — FR 04:10, 19 July 2019 (UTC)Reply
Looks good. But I have another big report, if I try to revert (doesn't matter if I intentionally choose or not) a revision that is not latest, the undo button text changes to Loading and stays like that. No alert box comes up with a reason. I thought it was just a browser problem, then I replaced my Chrome Dev 77.0 with my Firefox Nightly 68.1a1. Still the bug remained the same. Could kindly check it and fix it? Basic undo feature (reverting the latest revision) works without any issue. At least I couldn't find anything. Sincerely, Masum Reza 04:44, 19 July 2019 (UTC)Reply
Masumrezarock100, Could you paste your console output for that page here? (removing any personal information that you don't want) — FR 05:02, 19 July 2019 (UTC)Reply
I don't think such a feature exists in browsers for Android. Or perhaps you are talking about the Tracing feature? Masum Reza 05:07, 19 July 2019 (UTC)Reply
This could be a network problem. But I don't know for sure. Does this happen to you too? Sincerely, Masum Reza 05:22, 19 July 2019 (UTC)Reply
Masumrezarock100, It should be fixed now.  — FR 05:55, 19 July 2019 (UTC)Reply
Excellent! I's working. I don't think any other bug is present right now. Though I am not quite certain of it. Also like I said before, thanks button becomes smaller and the icon in it disappears. Anyway, shalI inform MusikAnimal now that it's ready for production? Sincerely, Masum Reza 06:21, 19 July 2019 (UTC)Reply
Masumrezarock100, I had an email exchange with MusikAnimal where he told me that it would be better if a member of the reading web team could take a look at the script.  — FR 14:37, 19 July 2019 (UTC)Reply
I see. I am going to send talk page messages to the en-wiki users who currently import your script to let them know that the en-wiki version has some bugs and request them to import the current beta version of your script on meta or the stable version on en-wiki. Also I plan to make an edit request on your en-wiki script's talk page to replace the outdated code with mw.loader.load('//meta.wikimedia.org/w/index.php?title=User:FR30799386/undo.js&action=raw&ctype=text/javascript');. Do you have any objections? Masum Reza 15:29, 19 July 2019 (UTC)Reply
Masumrezarock100, I personally have no problems. However, you should ideally have a talk with the admin/checkuser who blocked me before you do them.  — FR 15:53, 19 July 2019 (UTC)Reply
I don't think anyone will object. I already notified all of the editors listed en:Special:WhatLinksHere/User:FR30799386/undo.js that aren't indefinitely blocked. I will ping the checkuser when I will post the edit request. Sincerely, Masum Reza 16:43, 19 July 2019 (UTC)Reply

A barnstar for you![edit]

The Technical Barnstar
I am grateful that you created this anti-vandalism (mobileUndo.js) tool for reverting vandalism when editing on mobile. Also thanks for fixing the bugs. Therefore I hereby award you this barnstar to show my appreciation. Masum Reza📞 12:23, 26 June 2019 (UTC)Reply

Undo.js script[edit]

I started a new thread because it becomes harder to add colons. Regarding the edit request, I am sorry to say that it was declined. I updated the version to 2.0.2 because the script has been rewritten and it haa entirely a different UI. Hope you don't mind. Also I updated the documentation page on en-wiki and made it a soft redirect. Masum Reza 19:14, 19 July 2019 (UTC)Reply

I'm aware of this.  — FR 12:32, 21 July 2019 (UTC)Reply
I know I am being impatient. But given the situation that you were treated like a LTA, I thought that you might not want to add restore feature. Or is it just impossible? Masum Reza 14:20, 24 July 2019 (UTC)Reply
I will probably create a seperate script and load it into undo.js. I'll get around to making it within this week.  — FR (mobileUndo) 14:39, 24 July 2019 (UTC)Reply
Ok. Let me know when you do and I will do a beta test to find out bugs if there will be any. Masum Reza 15:46, 24 July 2019 (UTC)Reply
I was wondering if there is an global message similar to Revert successful... Reloading in a sec. You see this particular message is the only message that doesn't translate if I change wiki. Is there any replacement? Masum Reza 08:54, 26 July 2019 (UTC)Reply
Not much I can do about that, there are quite a few messages that are not translated. I've checked, and there isn't anything similar.  — FR (mobileUndo) 14:55, 26 July 2019 (UTC)Reply
This is awesome. It's pretty much like rollback. Now I don't have to undo edits over and over again. Saves time. Masum Reza 16:16, 28 July 2019 (UTC)Reply
Hmm. It uses a browser's built-in dialog box. Not bad. Also I found a bug. If I click restore and then click cancel, the text restore changes to Loading.... It should stay unchanged. Basic feature is working though. Masum Reza 16:29, 28 July 2019 (UTC)Reply
Another bug, if I click a restore and click ok(doesn't matter if I give a reason or not), the link changes to Loading and if I click the loading text very quickly, the dialog again pops up asking for a reason. Pretty much like the previous Undo button bug. Also if the restore fails because I can't or don't have the permission to edit the page, the text changes to Loading... and dialog window pops up showing a reason. If I click OK, and then click the Loading link the dialog window again pops up asking for a reason. Masum Reza 16:54, 28 July 2019 (UTC)Reply
I made changes that should stop this behaviour. :)  — FR (mobileUndo) 17:08, 28 July 2019 (UTC)Reply
I've striked out those bug reports that have been fixed. One bug is still not fixed. I will explain it again. It happens when I try to restore a protected page revision (for example your JavaScript file's revision). If I click restore, it changes to Loading... and a reason pops up why I can't edit the page. And after clicking OK, I see that the text is still Loading.... It should change to Failed. Masum Reza 17:29, 28 July 2019 (UTC)Reply
Thanks for fixing the bug. I can't think of anymore bugs at present. Masum Reza 17:40, 28 July 2019 (UTC)Reply
It doesn't seem like that this restorer script has anymore bugs. During it's beta-testing period, I tested it on various wikis such as Wikidata, Wiktionary etc. This script works flawlessly. It is also compatible with AMC mode (I tested it on Japanese Wikipedia). Masum Reza 02:25, 6 August 2019 (UTC)Reply
Edit summary's language is not changing on wikis with different language. For example, this. Masum Reza 03:09, 6 August 2019 (UTC)Reply

Certain comments made over at enwiki[edit]

It really hurts when people decide to ignore around two whole years of volunteer dedication to a project and instead focus on just ones block log. The fact that I created two GA's from scratch, was active in anti-vandalism and coded scripts for the benifit of the community is all flushed down the toilet and I am potrayed as being some sort of attention hungry LTA who will abuse peoples accounts the moment I get remote access to them via a script.  — FR 12:32, 21 July 2019 (UTC)Reply

I can't help but feel sorry. Can you appeal at ArbCom? I mean it's better than just accept your block. There's no harm in it. You are already blocked on en-wiki. You have nothing more to lose. Masum Reza 14:23, 21 July 2019 (UTC)Reply
According to a email I received from a member of the Arbitration Committee, I cannot appeal my block before October 4, 2019.  — FR 14:48, 21 July 2019 (UTC)Reply
That's a good news. Kind of. I shall await your return. Another thing, they are telling me to maintain the script. Even Danny refused to copy-paste your new version. He says that he is maintaining your script but he doesn't work on them one bit. Not his fault though, he has too many script in his possession. Every time someone retires on en-wiki, he takes over their script. I refused until now but I can't bear the fact that no one can recognize your work. Shall I copy your script to enwiki? I am not that experienced in JavaScript coding. But I did make one script or two. If so, I will probably have to rely on your for assistance on technical. I am happy to give up my maintainer status and delete those scripts once you return. If you agree, should Danny give up your scripts? Sincerely, Masum Reza 16:52, 21 July 2019 (UTC)Reply
I don't think you should be copying over the script. Given the current mood, it will surely get deleted/reverted almost immediately by someone citing the proxy editing policy. I guess it's best to wait a few more months. In the meantime, keep using the script for reverting vandalism.  — FR 05:44, 22 July 2019 (UTC)Reply
Ok. But I won't be using this script for just reverting vandalism, it's useful for editing as well. Sincerely, Masum Reza 10:09, 22 July 2019 (UTC)Reply

Socking and outing are hard for editors to recover from. And this fact is known to almost all editors so it shouldn't be a surprise. Your best chance is to wait it out, don't sock, try the standard offer and write an eloquent unblock request where you honestly state what happened and how it won't happen again. I've seen it work when editors have been open about their mistakes but it will be quickly denied if you don't accept responsibility for your mistakes or are less than forthcoming about your socking. The checkusers have a lot of data that they don't reveal which can catch when editors are trying to conceal their activity. Good luck and see you in October. Liz (talk) 01:32, 3 August 2019 (UTC)Reply

Liz, I'll certainlly take your advice when filing an unblock request.  — FR (mobileUndo) 17:14, 3 August 2019 (UTC)Reply

MobileUndo Localization[edit]

Do you have plan for Localization? I would like to help for Bengali Localization. --আফতাবুজ্জামান (talk) 17:58, 10 August 2019 (UTC)Reply

আফতাবুজ্জামান, by localisation, you mean creating a custom version of mobileUndo for Bengali wikis by translating the interfaces messages and so? — FR (mobileUndo) 10:09, 11 August 2019 (UTC)Reply
From what I know, only the Revert successful... Reloading in a sec. needs to be translated. I don't think undo button label is that important for translating though. Masum Reza 15:21, 12 August 2019 (UTC)Reply
@আফতাবুজ্জামান and Masumrezarock100:, I need the translation of all the messages listed at User:FR30799386/undo.json to create a Bengali Wiki version of the script in Bengali script. I have intentions to make the script wiki agnostic in the future... However, right now most of the messages are hard coded and need to be replaced manually. — FR (mobileUndo) 16:02, 12 August 2019 (UTC)Reply
Hmm. Would it be possible for you make it available for translation on Translatewiki? Masum Reza 16:08, 12 August 2019 (UTC)Reply
I've gone through the docs and everything. It appears that translatewiki.net was built for bigger applications with far more complex system messaging systems. So the best way forward would be to implement something similar to the system currently used by Jayprakash12345 in the script User:Indic-TechCom/Script/MoveAndReplace.js. I will try an implement such a system for my script in the following days. In any case, manual translations for those messages will be needed for localisation. — FR (mobileUndo) 17:27, 12 August 2019 (UTC)Reply
Here is the Bengali translation. --আফতাবুজ্জামান (talk) 20:07, 12 August 2019 (UTC)Reply

@আফতাবুজ্জামান and Masumrezarock100: Done. I have also translated "HTTP error :" to "HTTP ত্রুটি: " and added a few punctuations based on other Bengali translations I was looking over at translatewiki. Please report any bugs or problems with the script. Regards. — FR (mobileUndo) 14:48, 13 August 2019 (UTC)Reply

@আফতাবুজ্জামান and Masumrezarock100: reping since I messed up the last time.  — FR (mobileUndo) 14:51, 13 August 2019 (UTC)Reply
@FR, maybe you can add a similar translate function like User:DannyS712/Global_watchlist/Translate. It would be easier to translate this way. Masum Reza 12:00, 8 September 2019 (UTC)Reply
I'll take a look  — FR (mobileUndo) 14:12, 8 September 2019 (UTC)Reply
Please do. Like I said, it would be more easier to translate this way. The current user interface for translating is good. You could create an user subpage like Danny did, and ask a translation admin to mark it for translation. Masum Reza 20:33, 14 September 2019 (UTC)Reply

Timeless Newsletter • Issue 5[edit]

Newsletter • August 2019

Welcome to the fifth and final issue of the Timeless newsletter!

Progress was made. True story.

I am happy to announce that after about a year, this delightful project in which absolutely nothing has gone according to plan is coming to a close. Or at least, the grant-funded portion is. Which means we will now be resuming our regular schedule of random whims-based development, you probably won't notice any difference whatsoever unless you use MonoBook, and there's a report.

What's new from the past two months:

A lot less than we'd hoped, frankly. We:

We also wound up with:

  • Patches resulting in RelatedArticles working in MonoBook, and FlaggedRevisions showing up in Minerva, unless someone actually managed to turn that off as well. (Blame T181242.) It's possible we went a little overboard with the whole 'let's close all the tasks!' sprint.
  • An unfortunate repeated discovery that themes (the Night/Winter variants I keep insisting will happen at some point) are still pretty far off on the horizon. Um.
  • Possibly a quite a few more bugs coming your way. This month, and especially the past week, have been a bit of a mess, development-wise. While hopefully none of the worse issues make it to production, please keep the reports coming for whatever you do find and we'll get it fixed as soon as we can. Y'all've been amazing about this, and it's really appreciated.

And I guess that's that. I'm really bad at reporting, and this is a report. For the purposes of the grant, this was a requirement, but do you want me to keep trying to send these out?

-— Isarra 18:08, 31 August 2019 (UTC)Reply

Not helpful[edit]

I know about IRC in general and #wikimedia-stewards specifically more than one FR (mobileUndo) may expect. If you see nothing to criticize in the scheme without referring to “my” (Incnis_Mrsi’s) needs, then please keep your advices out of discussions interesting for me. Incnis Mrsi (talk) 18:15, 5 September 2019 (UTC)Reply

@Incnis Mrsi: That's a "discussion", and editors have the right to express their opinions (unless it goes off-topic, of course). Masum Reza 18:53, 5 September 2019 (UTC)Reply
Sure, it’s also my right to be irritated reading various “all are volunteers” clichés in reply to a decent intellectual effort on my part. Incnis Mrsi (talk) 19:29, 5 September 2019 (UTC)Reply
@Incnis Mrsi:, I reserve the right to make any comment based on my judgement on any freaking discussion on Meta Wiki regardless of whether you are involved in it or not. Also, I stand by the position I took on that discussion and fail to see anything derogatory or otherwise offensive enough in my comment to warrant this response on my talk page.  — FR (mobileUndo) 14:57, 6 September 2019 (UTC)Reply

You aware[edit]

of Kosta's feedback over here? Winged Blades of Godric (talk) 04:22, 14 September 2019 (UTC)Reply

Per [1], I'm not very sure I am allowed to contribute gerrit anymore. Maybe Ammarpad or Krinkle could clarify. That being said, if I am allowed I will certainly rebase the patch and work on the feedback given.  — FR (mobileUndo) 09:58, 14 September 2019 (UTC)Reply
Sigh; I hope that you be allowed to contribute:) In the meanwhile, any comments on this? Winged Blades of Godric (talk) 12:33, 14 September 2019 (UTC)Reply
Yup, you are right, Taggednonote-NPF isn't used by the PageTriage system at all. That being said, implementing that particular proposed change would be pretty easy for the developers to do.  — FR (mobileUndo) 16:54, 14 September 2019 (UTC)Reply
You know, it sucks that some people disregard other people's positive contributions citing just one block log. We can't change anything about it though. Anyway, would it be possible for you to request an unblock? Masum Reza 19:53, 14 September 2019 (UTC)Reply
  • Hi FR30799386, as long as you can still log in Gerrit, you can certainly make contribution. Your lack of addition to the Zuul CI whitelist is not barrier to submitting patches, it'll only delay some CI tests on your patches. However, on hindsight I think I should not have opposed your addition since you were not locked globally or banned on many wikis then and now. (I actually forgot that I did withdraw my opposition at the time). It's also worth noting that my comment in and itself was not the only reason for abandoning the patch and cannot prevent adding you if the people with merge right to the repo so wish. So if you still want to be added you can contact Krinkle or Kosta to consider reopening the patch. You can also submit patches completely without that. Thanks. – Ammarpad (talk) 12:03, 15 September 2019 (UTC)Reply

Abuse filter support[edit]

Hi FR, I tried to undo an edit on en-wiki, and it got blocked by abuse filter. Actually I removed an OTRS permission template, and then tried to undo myself. So a dialog should have come up saying that my actions has been blocked, but instead the diff page got redirected to Special:MobileDiff/undefined subpage. I even saw the "Revert successful. Reloading in a sec" message. So maybe you can fix this bug? PS. The abuse filter setting was set to "disallowed". The abuse log is w:en:Special:AbuseLog/24795925. The matter has been resolved, thanks to Vermont. But bug is still present, so reporting. Masum Reza 19:44, 14 September 2019 (UTC)Reply

Fixed :)  — FR (mobileUndo) 09:51, 15 September 2019 (UTC)Reply
Many thanks. Masum Reza 15:11, 15 September 2019 (UTC)Reply
+ I just realized that the restore script needs to be fixed too. Abuse filter blocking is not currently supported in the mobile restorer script. Another thing, I noticed that restored script doesn't use OOUI dialog, no OOUI widgets at all! Actually the layout doesn't look good without it IMO. Masum Reza 17:27, 15 September 2019 (UTC)Reply
I'll get to doing it. I'm currently working on the patches to PageTriage mentioned above. I'll do this the moment I finish with those.  — FR (mobileUndo) 18:27, 15 September 2019 (UTC)Reply

Thanks button problem[edit]

Hi FR, sorry if I am bothering you. After the recent mediawiki update, "thanks button" looks a bit different. The text "Thank" is being shown partially. So can you fix it when you have time. Check out the screenshot https://screenshot.net/l65d2f5 . Tell me if the screenshot link is not working. Masum Reza 08:27, 19 September 2019 (UTC)Reply

Fixed :)  — FR (mobileUndo) 13:12, 19 September 2019 (UTC)Reply
Yeah, it has been fixed but it created another bug. So after I thank someone, the thank button remains blue and if I click on it again a dialoge box appears asking for my permission to send thanks. Masum Reza 20:20, 19 September 2019 (UTC)Reply
To cut the long story short, somebody has broken almost every way of "disabling" the thank button by converting it into a link. I've used some hacky css to prevent the button from creating a dialog, but I've no idea how to bring back the grey visual feedback for disabling a button.  — FR (mobileUndo) 20:57, 19 September 2019 (UTC)Reply
I see. Masum Reza 08:37, 20 September 2019 (UTC)Reply

IRL Problems[edit]

Due to a un-expected increase in workload IRL coupled with a chronically malfunctioning laptop (think malfunctioning mouse, OS problems and a sick battery), I'll be taking a break of around 3 weeks to a month so get my life in order. I may edit very sporadically via mobile, however, don't expect any long term commitments to be fulfilled during that period. — FR (mobileUndo) 15:12, 23 September 2019 (UTC)Reply

I know you are in a wikibreak and all. But I have just one question. When you're gonna appeal your block? Masum Reza 22:43, 7 October 2019 (UTC)Reply
I don't think I'll be appealing for sometime (think first week of November or something...). At this moment I just don't think I can devote enough time and handle the anxiety related to the un-block appeal.  — FR (mobileUndo)
Could you create a rollback like script (like Twinkle) when you have time? The script will work without rollback and will let an user to add custom edit summary. Masum Reza 11:35, 3 November 2019 (UTC)Reply

Undo script[edit]

Hello. Your undo script has disappeared for me. It was very useful. Please fix it. Thanks. 4nn1l2 (talk) 06:07, 22 February 2020 (UTC)Reply

Script for special user groups[edit]

Hi, to avoid abuses actions of this tool, can you update the code only for the extended user group? Thank you! 11:21, 3 October 2020 (UTC)Reply

SGrabarczuk (WMF)

18:26, 20 November 2020 (UTC)

SGrabarczuk (WMF)

16:08, 11 December 2020 (UTC)

Invitation for Functionary consultation 2021[edit]

Greetings SWMT member,

I'm letting you know in advance about a meeting I'd like to invite you to regarding the Universal Code of Conduct and the community's ownership of its future enforcement. I'm still in the process of putting together the details, but I wanted to share the date with you: 10 July, 2021. I do not have a time on this date yet, but I will let you soon. We have created a meta page with basic information. Please take a look at the meta page and sign up your name under the appropriate section.

Thank you for your time.--BAnand (WMF) 03:21, 3 June 2021 (UTC)Reply


I installed script but script isn't working anybody please help Uricdivine (talk) 21:25, 18 July 2022 (UTC)Reply


Hello! I like you MobileUndo script. But when using source editing to undo, last verson is alternating overlap at new verson. I switch over at visual editor. In some cases, that's useful. But at big editing, memory is often faulty. So, I think you should overcome this error. (Sorry if my English is mistake, I'm Vietnamese) Quangkhanhhuynh (talk) 10:06, 5 December 2022 (UTC)Reply