(Unassigning as i assigned myself by mistake)

In T225126#5244925, @Aklapper wrote:

The crash is very likely due to which software crashes and should not crash, and it's not MediaWiki that is crashing here.

@Aklapper but in this situation i think the crash is due to MediaWiki.

Not enough details given, and the event is now over.

(Woops accidentally unstalled) I could work on this task though the event is soon to be over, but i will need the ips! @Drarialshogren

Not occurred since the last instance.

Looks like that fixed it :) thanks

I will schedule for deployment as soon as I have a free time during a SWAT window!

@Aklapper enwiki infact does not index user namespace amongst others, see https://en.wikipedia.org/wiki/Wikipedia:Controlling_search_engine_indexing#Namespace_control

I wonder if this task should be higher priority as this is imho a core feature of the bot..

Is there a fix foreseen in the future?

Shouldnt really require discussion on if he should be granted the rights imho

In T220201#5102061, @Bstorm wrote:

@Zppix The project should be good to go in horizon now

Okay then i wont require an floating ip if thats the case.

In T220201#5089542, @bd808 wrote:

The combo of "long term abuse" and wanting a public IP makes me think you are thinking about user tracking in some form. Please do remember to read and consider the https://wikitech.wikimedia.org/wiki/Wikitech:Cloud_Services_Terms_of_use. Especially:

• Clearly communicate to End Users a) that Private Information is being collected, b) how you will use it, and c) when you will delete it;
• Get express authorization from the End Users for the collection;

Updated title to reflect that it affects iOS devices as a whole as i can confirm as mentioned before it happens on iPhone aswell

Can confirm this happens in safe mode, I am running the latest iOS 12.2 on an iPhone X, i have also noticed this when I used to have an iPhone 6 (I do not remember what iOS version). So it appears this may affect iOS devices as a whole.

per IRC.

It has been deployed im resolving this if needed feel free to reopen if needed!

In T216149#4959831, @Aklapper wrote:

Which specific and non-theoretical problem is created by the "excess of lines"?

If consensus is needed we should wait for that otherwise I'd be willing to take this on

I forgot to have it deployed on the 7th I will schedule it for deployment before the event (I will update when I figure out what time i can do it)

In T215511#4935670, @Legoktm wrote:

This is on purpose, and a good thing IMO. It can be a bit confusing if they're all at the same time, but often they're not.

In T212868#4931635, @Nikerabbit wrote:

Sorry, I forgot to deploy and test this on last export. I'll do it on Thursday.

Closing for the moment since this no longer being sought after.

@Nikerabbit Hey just going through trying to clean up my to-do list, is this task resolved or is it still an on-going issue?

Will schedule for deployment feb 7th (during morning swat hopefully)

Just so your aware this is to lift a cap for account creation only, once you get the public ips for the event I will be willing to take this on.

While I trust @Rxy in this case, as @Huji brings up in the future something else like populating fake CU data would be ideal. Perhaps for this one time, we can allow it, but then we should make an effort in finding another way for the future.

I've noticed that the reupload right wasnt brought over to the patroller usergroup was that intentional?

@Nikerabbit Has the changed work, or do I have to have it deployed, I'm not to familiar with translatewiki

In T214374#4902360, @Aklapper wrote:

I am pointing out that T198601 proposes to archive that extension, as written in its task summary. Is something unclear with that?

@Aklapper Are you suggesting that T198601 invalidates this task? I'm confused on what your meaning is by bringing up that task.

If a consensus can be reached on what it should be changed to, then I'd be willing to implement the change.