Meta:Requests for help from a sysop or bureaucrat/Archives/2018-08

Add links
From Meta, a Wikimedia project coordination wiki

Report concerning EndlessLumita

EndlessLumita (talk • contribs • deleted contribs • logs • filter log • block user • block log • GUC • CA) LTA vandal sock of Liza Veniza. SA 13 Bro (talk) 09:42, 1 August 2018 (UTC)

Taken care of. — regards, Revi 09:48, 1 August 2018 (UTC)
This section was archived on a request by: — regards, Revi 09:48, 1 August 2018 (UTC)

Report concerning 46.227.72.25

46.227.72.25 (talk • contribs • deleted contribs • logs • filter log • block user • block log • GUC • CA) Persistently creating nonsense pages and vandalism. SA 13 Bro (talk) 10:10, 1 August 2018 (UTC)

Done locally by Steinsplitter and globally by me (Based on this request) --Alaa :)..! 10:46, 1 August 2018 (UTC)
This section was archived on a request by: --Alaa :)..! 10:47, 1 August 2018 (UTC)

User talk:Tegel

Hello, maybe this should be semiprotected again? --Martin Urbanec (talk) 17:57, 1 August 2018 (UTC)

Done for 1 week. Stryn (talk) 17:58, 1 August 2018 (UTC)
This section was archived on a request by: Stryn (talk) 17:58, 1 August 2018 (UTC)

Report concerning 75.131.25.207

75.131.25.207 (talk • contribs • deleted contribs • logs • filter log • block user • block log • GUC • CA) — Reasons: IP is vandalizing multiple pages Esteban16 (talk) 01:24, 2 August 2018 (UTC)

Done. Matiia (talk) 01:26, 2 August 2018 (UTC)
This section was archived on a request by: --Alaa :)..! 08:21, 2 August 2018 (UTC)

Indef-semiprotect for User talk:Маршмаллыч

Please, semi-protect page User talk:Маршмаллыч for indefinite. Now, its just redirect to my main talk page — I don't suggest ask any question in my alternative account's user talk. Also, this page was persistely vandalised. Marshmallych 09:56, 1 August 2018 (UTC)

Done Since this is effectively fighting vandalism, I'm going to take it as being within my remit even as a limited administrator. Thank you for moving the one serious question/statement/request to your main-account talk page. Don't be surprised if that page gets vandalized, though. StevenJ81 (talk) 21:35, 1 August 2018 (UTC)
This section was archived on a request by: StevenJ81 (talk) 13:39, 3 August 2018 (UTC)

Omar&lhmam

Please block user:Omar&lhmam for vandalizing Meta talk:About. 2602:306:3357:BA0:C50D:27D5:E8B8:CA8C 20:06, 1 August 2018 (UTC)

Not even get warned. Most likely they never return. So not done. Stryn (talk) 18:28, 2 August 2018 (UTC)
This section was archived on a request by:  — billinghurst sDrewth 21:53, 5 August 2018 (UTC)

Test-bad-person-to-be-blocked

There is a user named user: Test-bad-person-to-be-blocked. 2602:306:3357:BA0:C50D:27D5:E8B8:CA8C 20:11, 1 August 2018 (UTC)

So? Looks WMF test account. Stryn (talk) 20:28, 1 August 2018 (UTC)
This section was archived on a request by:  — billinghurst sDrewth 21:53, 5 August 2018 (UTC)

Global lock of account user:Asim543

@Billinghurst: Hi,it had been long since i requested for unblock of my account [1].But nothing had been progress since then.It had already been 9-10 days.I know its take time for a review but i hope not that much time is needed in any web case.However,today i had seen some progress here [2] but the account is still blocked.But i had answered the question here [3]that User talk:Ruslik0 made on my global unlock request page.Its a a humble request please help in recovering my account.(117.226.176.189 05:01, 2 August 2018 (UTC))
No value in asking meta admins about a global lock, it is nothing that we control. You should be talking to stewards at stewards' noticeboard or SRG.  — billinghurst sDrewth 08:18, 2 August 2018 (UTC)
@Billinghurst: Hi,i would have asked there but since the account is semi-protected so i would not do that.Can you please forward this message there.(117.226.129.144 14:03, 2 August 2018 (UTC))
There are multiple ways to contact stewards that they list on those and related pages, and not affected by a block, please use one of them. It needs to be an uninterrupted two-way conversation, not through third parties.  — billinghurst sDrewth 23:08, 2 August 2018 (UTC)
This section was archived on a request by:  — billinghurst sDrewth 21:53, 5 August 2018 (UTC)

Report concerning 49.163.196.154

49.163.196.154 (talk • contribs • deleted contribs • logs • filter log • block user • block log • GUC • CA) — Reasons: This IP user persistingly create fake articles and add fake informations in Korean Wiktionary. Please delete articles created by 49.163.196.154 and if possible let him stop. Thanks. --Garam (talk) 05:48, 3 August 2018 (UTC)

You're in the wrong venue. That's SRM. I'll take care of it though. — regards, Revi 06:20, 3 August 2018 (UTC)
Well, I think this is Korean Wiktionary only, not "cross-wiki" vandalism. Thanks. --Garam (talk) 06:36, 3 August 2018 (UTC)
This page is for issues on Meta-Wiki only. — regards, Revi 06:38, 3 August 2018 (UTC)
Umm... Then, informations on this article is wrong in my opinion. Thanks. --Garam (talk) 06:44, 3 August 2018 (UTC)
@Garam: Are you sure? The top part of that page says cross-wiki issues are to go to stewards, and that includes the "Miscellaneous" section. The bottom half of the page directs users with regard to meta issues.  — billinghurst sDrewth 22:38, 7 August 2018 (UTC)
@billinghurst: I understand what you and user revi said. Thanks.--Garam (talk) 23:28, 7 August 2018 (UTC)
Korean translation has "Vandalism reports". It has been abandoned, and non-meta requests for anti-vandalism matters are for SRM and meta requests are for here. I stopped using Korean in MediaWiki interface for a long time, so I don't care about the translation that much. — regards, Revi 11:48, 9 August 2018 (UTC)
This section was archived on a request by: — regards, Revi 11:54, 9 August 2018 (UTC)

Misidentified vandalism

Hi, the system has misidentified one of my posts as vandalism (when I tried to post it on the discussion for the proposal on WM) Dogs curiosity (talk) 18:57, 5 August 2018 (UTC)

Yes, it did. That filter is picking up sexual and racial abuse, and it is a little ugly to problem solve. The filter is predominantly MarcoAurelio's, so I suggest that you talk to them about the false positive.  — billinghurst sDrewth 21:49, 5 August 2018 (UTC)
I have amended the filter so confirmed users and autoconfirmed users can override the filter. I'd like to ask MusikAnimal to review the filter and see if it is okay and if it can be optimized a little so it doesn't waste 3 conditions. Regards, —MarcoAurelio (talk) 14:52, 6 August 2018 (UTC)
Hey, so a few problems: I don't think ('foo'|'bar') in user_groups works. in merely checks that the left-hand operator is in the right, treating both as strings. !('confirmed' in user_groups) should be sufficient. That will account for autoconfirmed as well, and bots will be confirmed so no need to check for that too (if a bot is hit by this early on, just manually confirm the account). I'm also checking that the regex is not in removed_lines, asserting that offending content wasn't already there. That wouldn't prevent the above false positive, but it helps.

That being said I don't think there is a fool-proof way of preventing the above false positive, or at least I don't have any good ideas :( I would confirm Dogs curiosity's account myself, but it seems sysops can't do that here. Any ideas why? That would be the solution in this case, I believe. The false positive is just a necessary consequence of a generalized counter-vandalism filter like this one. On that note, since this filter isn't targeting a long-term vandal or the like, shouldn't it be public?

The other issue I saw with that filter is we were throwing a warning and disallowing. This is not necessary unless you want to show a customized message in the warning. We were using the default, which misleadingly says "If this action is constructive, you may submit it again".

The filter is still averaging at 3 conditions. Restricting to specific namespaces would help, but I'm not sure if you want to do that. There may also be an issue with the profiling itself... I've noticed on enwiki that as of late, some filters average at 0 conditions which isn't possible because the first condition is always ran (phab:T201334). That might be related, not sure. Hope this helps — MusikAnimal talk 17:24, 6 August 2018 (UTC)

MusikAnimal & billinghurst Sorry for the delay in getting back to you guys and thank you for the really quick replies. I'd keep up more but i'm getting ready for University in September so I hope you understand. I noticed you've mentioned that, at the moment, only confirmed users can bypass this anti-vandalism feature and that there have been some amendments to the filter as well. I've just tried to create the discussion again but it's still blocking its creation so I am wondering what the best thing to do would be? I mean I could provide a link to the essay at the discussion page for the Community Health Initiative proposal but then it is making it a bit more difficult to view. Dogs curiosity (talk) 21:10, 7 August 2018 (UTC)
I have manually confirmed the account (permission expires in one week, time enough to get autoconfirmed anyway). Could you please try again? Thank you. —MarcoAurelio (talk) 21:16, 7 August 2018 (UTC)

I have tried to publish a biography written by EdenTrain and edited by me, Kelvin Noel of ApogeoVideo. I keep getting the same errors as maliciuos and destructive. I don't see the errors. — The preceding unsigned comment was added by ApogeoVideo (talk)

@ApogeoVideo: This is not the site to publish an encyclopaedic article about anything, this is a coordinating wiki. You should be over at the Wikipedias, and the one of the language in which you write the article.  — billinghurst sDrewth 09:56, 8 August 2018 (UTC)
This section was archived on a request by:  — billinghurst sDrewth 13:17, 9 August 2018 (UTC)

Report concerning Mha3131

Mha3131 (talk • contribs • deleted contribs • logs • filter log • block user • block log • GUC • CA) — Reasons: This user creating Out of project scope pages via cross-wiki on Wikimedia Commons. Web SourceContent Management System 08:45, 6 August 2018 (UTC)

@Web SourceContent: Meta admins have no call on managing user accounts for xwiki abuse, that is a steward's area of action, and should be reported to SRG. In this case it has been managed.  — billinghurst sDrewth 22:30, 7 August 2018 (UTC)
This section was archived on a request by:  — billinghurst sDrewth 13:16, 9 August 2018 (UTC)

Possibly confusion?

Dear MarcoAurelio and SPoore (WMF) and Billinghurst and MusikAnimal , I am not sure if there has been some confusion however my account has been blocked and I'm not certain as to why. My account is Dogs curiosity and on my former Wikipedia project homepage, it says that I was identified as a user called A Den Jentyl Ettien Avel Dysklyver. However, I've not heard of that user before and I am not that person. The rationale for the misidentification follows per an investigation thread on the English Wikipedia:

  • submits Draft:Maisie Trollette, which was created by a BT IP (dysk's usual provider) and is a Cornwall related article.
  • Userpage with the same usual nonsense as past socks (email me for further detail.)
  • Immediately delves into AFDs of clearly notable topics just like past accounts

On the first point, BT is a very common internet service provider in the United Kingdom. I use something called BT Wifi with FON (see more information about that here). The IPs are reassigned each time you log into the BTWifi hotspot.

"And is a Cornwall related article." I'm not sure what that is supposed to mean but the reason I created Maisie Trollette is that I saw them on this BBC news report.

As for the second point regarding my homepage, this isn't very nice and it feels like a personal attack rather than anything to do with the issue at hand.

The reporting user has also taken to reversing some edits which I made on the Community health initiative discussion page despite those edits clearly not being disruptive. 109.144.209.219 10:50, 9 August 2018 (UTC)

  • I can identify myself to the Wikimedia Foundation if this will help resolve this issue? I apologise if I was too quick with the AfD, it was due to the fact I couldn't find any references on the page in question. Furthermore, the articles dates are in Irianian dates (which I had no idea about) so it looks like its an article about a living person stating they qualified in 1376 from Universities which didn't exist at the time, thus I thought the article was nonsense. 109.144.209.219
  • There'sNoTime Hello, thanks for the information. The SRG will not let me post because it says the page can only be edited by registered users which means I will have to submit an email from my email address which I'm not very comfortable with because I don't know who is going to get access to read my email address however it looks like i've got no choice really. I will email in now, I'll just copy and paste this thread if thats okay. Thanks. 109.144.209.219 11:45, 9 August 2018 (UTC)
  • There'sNoTime I have, reluctantly, emailed the Stewards email you have provided regarding this issue. It's difficult in these situations because i'm concerned about exposing my email address to people who have summarily blocked/locked my account without looking into it much but I feel pressured as I really wanted to keep up with the replies on my essay which I spent quite some time writing on the Community Health Initiative discussions page. Anyway, thank you for your time. 109.144.209.219 12:04, 9 August 2018 (UTC) (ping) (Jalexander-WMF)

Closed Closed Nothing for meta admins, this is a stewards' matter, and should be pursued at SRG

This section was archived on a request by:  — billinghurst sDrewth 13:15, 9 August 2018 (UTC)

Users getting blocked from editing

Hello, I am currently doing a series of workshops. Some of the people are not able to write on other people's talk pages because apparently their username is abusive. It affects people in this list. Are abuse filters responsible for that? Can they somehow bypass that block? Greetings, --Zenith4237 (talk) 13:30, 10 August 2018 (UTC)

Who is experiencing the errors? And which page? — regards, Revi 13:34, 10 August 2018 (UTC)
Ndyanaboandrew on his own talk page. --Zenith4237 (talk) 13:37, 10 August 2018 (UTC)
I don't want to help trolls by giving a way to override the filter publicly. I will email you with one way to bypass that filter. — regards, Revi 13:59, 10 August 2018 (UTC)
And mailed. — regards, Revi 14:02, 10 August 2018 (UTC)
Received and with thanks for the fast reply, --Zenith4237 (talk) 14:06, 10 August 2018 (UTC)
This section was archived on a request by: — regards, Revi 14:14, 10 August 2018 (UTC)

Report concerning ‎Nameisxuhuan

Nameisxuhuan (talk • contribs • deleted contribs • logs • filter log • block user • block log • GUC • CA) — Reasons: Someone adding spam & nonsense links to Talk:Privacy policy/Glossary of key terms/zh-hans. Web SourceContent Management System 19:59, 14 August 2018 (UTC)

Not sure what they are doing, though education and interaction may benefit. Sometimes a welcome message can be helpful.  — billinghurst sDrewth 04:28, 15 August 2018 (UTC)
However, Nameisxuhuan appears to be reported for cross-wiki abuse. See this request. Web SourceContent Management System 04:35, 15 August 2018 (UTC)
This is some sort of long-term cross-wiki abuser, I have come across the same type of vandalism for several times, but never summarized a list of accounts they have used. They tend to insert the name "徐环" (Xu Huan) and some other personal information into random pages, as well as other nonsense spam. One account is Wtgtam (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser) which has been locked a couple months ago. -★- PlyrStar93 →Message me. ← 04:37, 15 August 2018 (UTC)
@PlyrStar93: No problem! You have filled request on Steward requests/Global. Web SourceContent Management System 04:43, 15 August 2018 (UTC)
Globally locked by Green Giant on 16 August 2018. StevenJ81 (talk) 14:28, 17 August 2018 (UTC)
This section was archived on a request by:  — billinghurst sDrewth 02:23, 18 August 2018 (UTC)

Report concerning Roughshood

Roughshood (talk • contribs • deleted contribs • logs • filter log • block user • block log • GUC • CA) — Reasons: global banned Troll User:Avoided is stalking Wikimedians once more. Marcus Cyron (talk) 21:19, 16 August 2018 (UTC)


DEAR ADMINS! I AM NOT KIDDING! WOULD PLEASE ONE OF YOU BLOCK THIS TROLL NOW!!!!! Marcus Cyron (talk) 10:40, 17 August 2018 (UTC)

Globally locked by DerHexer. —MarcoAurelio (talk) 10:56, 17 August 2018 (UTC)
This section was archived on a request by:  — billinghurst sDrewth 02:23, 18 August 2018 (UTC)

Report concerning Itswarmevsyou

Itswarmevsyou (talk • contribs • deleted contribs • logs • filter log • block user • block log • GUC • CA) — Reasons: blanking user pages Ruthven (msg) 19:45, 19 August 2018 (UTC)

Locked. Ruslik (talk) 20:04, 19 August 2018 (UTC)
This section was archived on a request by: — xaosflux Talk 13:39, 21 August 2018 (UTC)

Removal of Autopatrollers from specific users

Hi, Please remove Autopatrollers from all of the above accounts because it's redundant either with MassMessage senders or Translation administrators. Regards, — TBhagat (contribs | talk) 07:52, 21 August 2018 (UTC)

I don't see a problem with that. Kind regards, --Vogone (talk) 07:54, 21 August 2018 (UTC)
Agree, what is the point of removing? Nothing breaks or unbreaks.  — billinghurst sDrewth 08:53, 21 August 2018 (UTC)
Yes, I also do share yours opinion but usually we do remove (we are supposed to do) because it's redundant. Regards, — TBhagat (contribs | talk) 09:22, 21 August 2018 (UTC)
For whatever it's worth, when the rights are redundant with sysop, I would remove. In these cases, it's less obvious just how long people will continue to hold these rights. And if at some point they no longer hold them, it's just as well that autopatrolled would still be in place. StevenJ81 (talk) 21:48, 22 August 2018 (UTC)
This section was archived on a request by: Action not needed, if some admin wanted to do "clean up" they may, but its not necessary. — xaosflux Talk 21:50, 22 August 2018 (UTC)

Report concerning 182.0.175.74

182.0.175.74 (talk • contribs • deleted contribs • logs • filter log • block user • block log • GUC • CA) — Reasons: fake translations Schniggendiller (talk) 19:27, 22 August 2018 (UTC)

Removed. You can mark them with delete tag, I think it's easier than reporting here. And we should really only enable tranlations for autopatrolled users. Stryn (talk) 20:11, 22 August 2018 (UTC)
This section was archived on a request by: Schniggendiller (talk) 15:44, 25 August 2018 (UTC)

Report concerning 2001:44c8:4189:6d3f:1:2:abeb:90e5

2001:44c8:4189:6d3f:1:2:abeb:90e5 (talk • contribs • deleted contribs • logs • filter log • block user • block log • GUC • CA) — Reasons: fake translations Schniggendiller (talk) 19:40, 22 August 2018 (UTC)

Removed. You can mark them with delete tag, I think it's easier than reporting here. And we should really only enable tranlations for autopatrolled users. Stryn (talk) 20:11, 22 August 2018 (UTC)
I agree with that idea. StevenJ81 (talk) 21:49, 22 August 2018 (UTC)
This section was archived on a request by: Stryn (talk) 16:27, 25 August 2018 (UTC)

Report concerning 185.89.219.162

185.89.219.162 (talk • contribs • deleted contribs • logs • filter log • block user • block log • GUC • CA) — Reasons: Vandalism/nonsense. Please block and execute Special:Nuke/185.89.219.162. Schniggendiller (talk) 15:43, 25 August 2018 (UTC)

Done. Stryn (talk) 16:27, 25 August 2018 (UTC)
This section was archived on a request by: Stryn (talk) 16:27, 25 August 2018 (UTC)

Report concerning ‎77.65.94.168

‎77.65.94.168 (talk • contribs • deleted contribs • logs • filter log • block user • block log • GUC • CA) — Reasons: Vandalism on Talk:Spam blacklist. Esteban16 (talk) 19:06, 27 August 2018 (UTC)

Sorry for the late reply, but the IP was blocked at that time by Masti. Thanks for reporting. —MarcoAurelio (talk) 17:57, 28 August 2018 (UTC)
This section was archived on a request by: —MarcoAurelio (talk) 17:57, 28 August 2018 (UTC)

Input requested regarding new access groups

Hello all, if you have not recently commented, your input would be most welcome at Meta:Babel#Tech_Admins regarding the new interface administrators access changes planned for later this month, specifically regarding establishing a process for granting access here on the meta wiki. Thank you, — xaosflux Talk 00:59, 20 August 2018 (UTC)

Block for BuddhaKuk

Status:    Done

This user has been edit warring to foil a report about it on SRG.   — Jeff G. ツ 04:54, 26 August 2018 (UTC)

Already locked by Bsadowski1. – Ajraddatz (talk) 04:59, 26 August 2018 (UTC)
This section was archived on a request by:   — Jeff G. ツ 14:43, 29 August 2018 (UTC)

Block for Windows Gril

Status:    Done

This user has been edit warring to foil a report about it on SRG.   — Jeff G. ツ 14:40, 29 August 2018 (UTC)

Already locked by Tegel. No need to fill report. Web SourceContent Management System 14:43, 29 August 2018 (UTC)
This section was archived on a request by: Web SourceContent Management System 14:45, 29 August 2018 (UTC)

Mass Message Sender for Jamie Tubers

Status:    Done
Original request on wrong page: Special:PermaLink/18316340#Mass_Message_Sender_for_Jamie_Tubers.

(Edit conflict.) @Xaosflux:: Tulsi Bhagat moved the request here from SRGP. I'm not sure he should have, but I'll leave that to you. AFAIG, Jamie Tubers is an ombudsman whose request is surely legitimate. StevenJ81 (talk) 03:07, 21 August 2018 (UTC)

(Edit conflict.) MassMessage is not actually a real global permission & it is handled by local sysops of Meta-Wiki. So that I've moved the request it to here on RFH. Sorry for bothering. Regards, — TBhagat (contribs | talk) 03:14, 21 August 2018 (UTC)
To the questions raised by the other commenters. This project has been a longterm idea, but was actively kickstarted at the just concluded Wikimania. For a start, I need to send a mass-message to people who are currently participants of WikiProject Film and WikiProject Africa (and probably individual African countries' WikiProjects), to create awareness for the new pan-African film WikiProject and invite interested participants to signup. After that, quarterly or monthly (depending on the need) message will be sent out to the list of users who have signup as participants; mostly to give updates on online and offline activities being carried out by other project members, and also areas where participation is needed. Most importantly, a Wiki writing contest is being planned for October and November, and participants would need to be informed about that too. All of these messaging needs, would be very stressful to do manually; hence the need to have the mass message sender rights. Thank you very much.--Jamie Tubers (talk) 20:40, 22 August 2018 (UTC)

Done, valid rationale. --Vogone (talk) 21:04, 22 August 2018 (UTC)

  • Thanks alot Vogone. However, I noticed that this right doesn't work on English Wikipedia (I'd need the right for both meta and WP). Does that mean that I'd need to file another request on Wikipedia?--Jamie Tubers (talk) 23:30, 22 August 2018 (UTC)
No, this user right indeed works on all WMF wikis. Please follow the instructions on MassMessage#Global message delivery and make use of the Template:Target which also allows targets on other wikis like enwiki. Kind regards, --Vogone (talk) 23:35, 22 August 2018 (UTC)
I'll clarify a bit. The massmessage rights on meta grant access to Special:MassMessage only on metawiki. But unlike on other wikis, it is possible to add global message delivery targets in your metawiki delivery list. This means you will be using Special:MassMessage on metawiki no matter to whom you send the messages. I hope this has become clearer to you, now. Regards, --Vogone (talk) 23:45, 22 August 2018 (UTC)
Now it does. ;-) Next time, create your list with the help of Special:CreateMassMessageList if you want your list to render that way. --Vogone (talk) 00:52, 23 August 2018 (UTC)
  • Thank you very much! I did check out Special:CreateMassMessageList, but it says I have unauthorized access, so I thought I probably didn't need it. Now that you have done that bit, doesn't seem like I need it so much afterall. Everything seem fine for now. Thank you once again, you were very helpful! I do appreciate your efforts :).--Jamie Tubers (talk) 01:05, 23 August 2018 (UTC)
No problem. I reported your permission error at phabricator.

Tracked in Phabricator:
Task T202597 --Vogone (talk) 01:37, 23 August 2018 (UTC)

@Vogone: I replied at phab, this "error" is by design - of course the design could be altered. — xaosflux Talk 02:52, 23 August 2018 (UTC)
Considering the special page is not as old as the user group and the fact that the MassMessage documentation on mediawikiwiki clearly mentions the use of that special page as part of the workflow, I can only very hardly believe this is "by design". It's much more likely an unintended side effect. --Vogone (talk) 03:21, 23 August 2018 (UTC)
@Jamie Tubers: I created you an empty list at User:Jamie Tubers/MMS1, you can use the 'move' action to rename it and put it where it needs to go. — xaosflux Talk 02:52, 23 August 2018 (UTC)
Created a "list of empty lists for non-admins to use" for cases like this @ Global message delivery/Targets, tho I am not sure how popular it will be :P — regards, Revi 09:14, 29 August 2018 (UTC)
This section was archived on a request by: StevenJ81 (talk) 13:30, 7 September 2018 (UTC)

Request for a MassMessage sending

Given that I fully intend to do this every month for the next... few, should I be asking for the right to just do this myself?

Whatever the case: could someone please send out the following for me?

Thanks! -— Isarra ༆ 03:32, 30 August 2018 (UTC)

Done you should be able to send this now, if you still need someone else to send, please let us know. — xaosflux Talk 03:47, 30 August 2018 (UTC)
Yup, that simplifies things on my end, too. Thanks! -— Isarra ༆ 04:07, 30 August 2018 (UTC)
This section was archived on a request by: StevenJ81 (talk) 13:30, 7 September 2018 (UTC)
Retrieved from "https://meta.wikimedia.org/w/index.php?title=Meta:Requests_for_help_from_a_sysop_or_bureaucrat/Archives/2018-08&oldid=18364037"