Page MenuHomePhabricator

Disable accountcreation on ptwikimedia
Open, Stalled, LowPublic

Description

I'm not a member of ptwikimedia, however, it would make sense to ask them, if we should do that.

There are using this filter: https://pt.wikimedia.org/wiki/Especial:Filtro_de_abusos/1?uselang=en to prevent account creation. However, this is a waste of ressources and leads to errors at scripts and other stuff, confuses users. Instead removing the right to create an account from * would be more clear.

Details

Related Gerrit Patches:
operations/mediawiki-config : masterMake ptwikimedia a fishbowl wiki

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 24 2017, 6:00 PM

Just adding the wiki to the fishbowl.dblist would make that. That filter is
horrible indeed, and potentially violates privacy as I've reported already
in another task.

Furthermore, the filter is currently disabled at writing time (> 5% actions triggered the filter).

@Beria Any thoughts on this task?

AbuseFilter autodisable does not seem to be working @Dereckson. I think I reported that issue already but cannot find the bug.

WRT to privacy concerns, see T152394.

Oh yes I did, but was marked as dupe of T54525

Change 367892 had a related patch set (by MarcoAurelio) published:
[operations/mediawiki-config@master] Make ptwikimedia a fishbowl wiki

https://gerrit.wikimedia.org/r/367892

So the logic is: they are already using an AbuseFilter to make the wiki de facto a fishbowl one. As such I don't think it'll cause any problem to make it really a fishbowl wiki. Does it sound right?

It can't be fishbowl - fishbowl restrict editing too. Please set createaccount to false instead.

But the filter also blocks editting. I think they only want the accounts listed in the filter to be able to edit, which is why I feel fishbowl is what they wanted instead.

Oh, then go for fishbowl (with notification, please!).

@Urbanecm Sure. That's why we've pinged @Alchimista and @Beria so they can confirm this. I won't schedule anything for deployment without their approval. Thanks.

Maybe just send them an email through Email a user feature? ;)

Well, indeed they don't want anyone to edit but the listed users. I've tried to leave a message at the Talk:Main Page and https://pt.wikimedia.org/w/index.php?title=Especial:Registro_de_abusos&wpSearchUser=MarcoAurelio was the result ;-)

Note that the Abuse filter was just a stop-gap measure while we finished the setup (which has been taking longer than we'd like), it wasn't meant to be permanent. I personally would prefer not making well-meaning editors with established accounts on other Wikimedia wikis (like MarcoAurelio :)) jump through hoops to make edits. But that's something we can look at later down the road. For now the fishbowl approach is probably the quickest solution.

That filter was intended to mimic the fishbawl configuration, especially in this early stage of the wiki recreation, where we're importing the content from the old one, adapting it and checking if everything is ok. I've disabled the filter, and if possible, please ad it to fishbowl.dblist.

MarcoAurelio triaged this task as Low priority.
MarcoAurelio moved this task from Backlog to To deploy on the Wikimedia-Site-requests board.

Given the approval from the management board of WMPT, I'll schedule the patch above to be merged to make the wiki a fishbowl one.

Change 367892 merged by jenkins-bot:
[operations/mediawiki-config@master] Make ptwikimedia a fishbowl wiki

https://gerrit.wikimedia.org/r/367892

Mentioned in SAL (#wikimedia-operations) [2017-07-31T23:17:48Z] <thcipriani@tin> Synchronized dblists: SWAT: [[gerrit:367892|Make ptwikimedia a fishbowl wiki]] T171501 (duration: 00m 43s)

MarcoAurelio added a subscriber: demon.EditedJul 31 2017, 11:30 PM

This is being reverted. When we made the wiki a fishbowl one, all accounts there broke because it stopped to depend on CentralAuth as before, so their passwords and email addresses wouldn't work. I think we need to reserve a larger window to migrate existing users and then fishbowling again -or- just remove from '*' the 'createaccount' permission, which I'd not advocate so we don't have pseudo-fishbowl wikis spread all over the config. Fishbowl wikis should all stay in one dblist. @Dereckson and @demon might want to give us ideas on how to do this. Sorry for any issues. Things should be back to normal in few minutes.

In the meantime maybe adding .* <newaccountonly> to their MediaWiki:Titleblacklist could do the trick.

Mentioned in SAL (#wikimedia-operations) [2017-07-31T23:34:44Z] <thcipriani@tin> Synchronized dblists: SWAT: [[gerrit:368951|Revert "Make ptwikimedia a fishbowl wiki"]] T171501 (duration: 00m 42s)

What would be the best way to move forward with this?

RuyP added a subscriber: RuyP.Aug 15 2017, 5:22 PM
MarcoAurelio removed MarcoAurelio as the assignee of this task.Aug 17 2017, 2:46 PM

I find myself unable to process this request now. Giving way.

Disabling account creation is easy and can be done immediately and I think would be a decent stopgap for the current issue. Titleblacklist should be able to handle the editing issue, I think. Could probably add some new group if desired to simplify things?

This is being reverted. When we made the wiki a fishbowl one, all accounts there broke because it stopped to depend on CentralAuth as before, so their passwords and email addresses wouldn't work. I think we need to reserve a larger window to migrate existing users and then fishbowling again -or- just remove from '*' the 'createaccount' permission, which I'd not advocate so we don't have pseudo-fishbowl wikis spread all over the config. Fishbowl wikis should all stay in one dblist. @Dereckson and @demon might want to give us ideas on how to do this. Sorry for any issues. Things should be back to normal in few minutes.

I tend to agree. It's ugly, but that's where we're at right now though. My initial thought when the sync/rollback occured was: "why the heck don't we take the time to SUL-ify the fishbowl wikis?"

Is this still wanted?

I don't think this is needed anymore, the filter is disabled and we don't have a massive problem with vandalism.