And same here: https://www.mediawiki.org/wiki/Special:ApiSandbox#action=query&format=json&list=allusers&aufrom=MarcoAurelio
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 22 2018
Feb 21 2018
Apparently once you enter a username, the extension starts querying the API. In my case https://www.mediawiki.org/w/api.php?action=query&format=json&list=allusers&auprefix=MarcoAu will start giving errors.
I've been doing some console testing with &debug=true as well. I get this:
Thanks!
MarcoAurelio (test) and MarcoAurelio (test 2) are both recognized.
I've created https://www.mediawiki.org/wiki/Newsletter:Test-Newsletter-T187834. The system put me as publisher as creator. Still if I remove my username and try to re-add it, it does not recognize it. Want me to debug this with X-Wikimedia-Debug or something else? IRC chat? Regards.
In T187786#3990175, @Bawolff wrote:Btw, if anyone wants to verify, easiest way to check is to send mail to a gmail account, and see if google complains about the email being insecure (it will have a little unlocked lock icon if tls was not used)
Yes, that's what happening. See the attached pictures for evidence.
If I opened this ticket is because emails I've received from translatewiki.net are not encrypted as my mail client tells me. What can I do to show you?
Removing User-notice : it's just a subtle change and the MediaWiki messages (Grouppage-flood, etc.) remain unchanged, so local customizations, if they exist, will be kept so no to very little impact here.
TBH I'm not sure if this qualifies for User-notice. It's just a naming change.
@Johan No, sorry. Bot flags and 'bot users' are different. It should be more simpler, like "the previously called 'bot users' group (a.k.a. flood flags on some wikis) has been renamed to 'pseudobots' for clarity - wikis can still customize their naming locally" or something along those lines.
User-notice people (@Johan) can work with the announcements now. Closing this task.
Please note that abuselog entries older than 90 days will not have any private data attached as per our privacy policy. The access log is not kept in the checkuser log but in a sublog at Special:Log.
Ping translatewiki.net staff here to see if they know why/hows/etc.
@Rfarrand @Aklapper I've created Wikimedia-Hackathon-2018. Please let me know if you think it's okay or needs or lacks something. You should be able to edit most (if not all) the things. If the project is okay, let me know and I'll close the task. Thanks and happy hacking (for good!).
Feb 20 2018
- Ombudsmen and Staff: abusefilter-private and abusefilter-private-log added
- Stewards: abusefilter-private-log added
- Checkusers: patch incoming.
- Stewards: patch incoming
So what might be the cause for this? I guess people is allowed to self-add themselves? If not that might be the issue.
So I've fixed two Talk:Draft illegal wordings through the API. Maybe running cleanupTitles could fix the remaining ones.
Troll extension... heh.
@demon ran the fixing script so nearly everything should be good now. However we now have Talk:Draft:WikiJournal of Medicine/Endometrial cancer which is innacesible. Somebody should check the database and see if they can fix those.
Quim, I've tried all forms. No success... I'll try again in few minutes and see if you trying to add me refreshed the list of usernames for some reason.
I'll go with another option. Let's see if that works.
@Strainu A fishbowl wiki is a wiki that is publicly viewable but editting is restricted to user accounts. Accounts have to be created manually by request by some of the other members.
/me head-desk - okay :-(
I run maintenance scripts on deployment-tin absent a better place...
@Tgr Please consider deploying on https://deployment.wikimedia.beta.wmflabs.org/wiki/Main_Page too -- that wiki is non-stop spambots.
@Reedy What about a deployment.wikimedia beta cluster test? That wiki is only getting spambot registration. We could test there if the new fancy captcha is of any help?
Ping. Status please?
Ping. Except for my objections above, is there anything else remaining to do here?
If there's no community consensus, the task is declined. Plus the bug is going to make in April one year, as well as the plwiki discussion. We require fresh discussions to implement things. Maintenance closure of old tasks.