User talk:Billinghurst/2019

From Meta, a Wikimedia project coordination wiki


Wikidata weekly summary #345

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Not much happened this week because we took some time off over the holidays. Getting back to full speed again in the next days.

On v:zh:MediaWiki:Colloquium/en

An interesting fact: Chinese Wikiversity community had chosen "互助客栈" as a translation for Colloquium. However, in Chinese Wikipedia, "互助客栈" is a flexible translation for Village Pump... --Mend My Way 15:45, 4 January 2019 (UTC)

It was an example only for Cohaf. Do what ever you need.  — billinghurst sDrewth 15:54, 4 January 2019 (UTC)

Wikidata weekly summary #346

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Working on getting final pieces in place to regularly run constraint check jobs so all constraint violations get fed into the query service (phabricator:T204031)
    • Fixed alignment issues with Glosses on Lexeme pages (phabricator:T207401)
    • Working on getting the layout right for the termbox in the mobile view so that in the future you can also see labels, descriptions and aliases in different languages on mobile (phabricator:T207150)
    • Getting ready to start working on basic Shape Expression support

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


A Barnstar for you!

The Special Barnstar
Thanks for your help over the holiday with the spambot problem. CKoerner (WMF) (talk) 17:17, 8 January 2019 (UTC)
@CKoerner (WMF): Thanks, good bit of team effort and thanks to those developers who came to my aid, most especially BAW who starred! Note the above comment about Special:AbuseFilter/195 which is related, and while being reasonably effective against other standard spambots, does have a low positive false hit rate. If we are going to keep 195, we need to look at ramifications, applying mitigation where possible, and maybe a level of communication through a newsletter.  — billinghurst sDrewth 01:58, 9 January 2019 (UTC)
Further noting that I am not a steward, so while I am given unfettered access to extended bits, it should not be without review or consideration, as my granted permissions are not a full-blown election.  — billinghurst sDrewth 02:00, 9 January 2019 (UTC)

Cross-wiki spam by Areokye

Hi, I saw you moved the report to SRG. FYI there is already an open request, see Steward requests/Global#Global lock for Areokye. -★- PlyrStar93 →Message me. ← 01:11, 14 January 2019 (UTC)

Then feel happy to merge it. Thanks.  — billinghurst sDrewth 01:28, 14 January 2019 (UTC)

Wikidata weekly summary #347

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • Structured data for Commons: multilingual captions are deployed on Commons on January 10th (documentation)
    • The Wikidata Query Service has been encountering some data corruption issues that impact the results you can see when running a query. Some may still be running. You can check the current ticket for more updates.
    • New dashboard for percentage of pages on a Wikimedia project make use of data from Wikidata (doesn't include sitelinks, doesn't include Commons file and category pages for now)
    • Science Stories, a project highlighting women in sciences, uses Wikidata
  • Development
    • Solving an issue that blocked deployments over the past weeks (phab:T212427)
    • Improved the visual appearance of glosses (phab:T207401)
    • Fixing problems with reverting Sense addition (phab:T211438)
    • Improving our Javascript to be more standard (phab:T210744)
    • Working on performing more constraint type checks in PHP before falling back to SPARQL (phab:T209504)
    • Making the query service logo and favicon configurable in one's own Wikibase (phab:T212210)
    • More work on displaying the termbox on mobile (phab:T207150)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


new alychidesign-ish spam

I think we've successfully stopped the alychidesign spam (filter is disallowing it every time!) however I've seen a new variant of a similar type of spam: [1][2][3][4] which are all variants of this. Praxidicae (talk) 15:16, 16 January 2019 (UTC)

Done put in a couple of common phrases. You are right in that it does look like the same crew.  — billinghurst sDrewth 21:01, 16 January 2019 (UTC)

Meta email from user "Namesbiography"

Status:    Not done
Hi Namesbiography. Blacklisting is not punitive, it is preventative, and the source of the link spam is not particularly relevant when it needs to be excluded. That said please let me first undertake some enquiries at English Wikipedia prior to responding more fully. @Ravensfire and Praxidicae: noting SPI there.  — billinghurst sDrewth 12:29, 17 January 2019 (UTC)
Thanks for the ping. I've had a short conversation with them on my English WP talk page (here). I'm going to add similar comments to the SPI later today (work IP is hard blocked on EN, so may be later this afternoon), but overall, there are a couple of things that are suspicious. First, rarely does the domain notice that they have been blacklisted so quickly unless there is an active campaign to add links to their site to Wikipedia. Second, this is a new website - the whois record shows the domain was created on November 27, 2018. It is very clearly not a reliable source for EN Wikipedia - blog, way too new, no editorial oversight, no sources mentioned. I don't feel that it matters if the spam campaign comes from folks behind the site or if it's a joe-job, this site doesn't offer a benefit to Wikipedia. Harsh opinion (and didn't really intend it to be that harsh, but short on time so needs to be quick), but my honest view on this. Ravensfire (talk) 15:53, 17 January 2019 (UTC)
Your communications were noted and the reason for the ping, and guided me in my choice of approach taken. My own thoughts will follow at a more suitable time.  — billinghurst sDrewth 22:18, 17 January 2019 (UTC)

@Namesbiography: I asked a checkuser at English Wikipedia to investigate the edits, including this account, and it would appear that your story has more elements of fiction, than elements of truth. I will not be progressing your request for removal via this direct representation, and if you progress to a process elsewhere, I will argue against any removal.  — billinghurst sDrewth 23:27, 17 January 2019 (UTC)

Shocking result that was. Utterly shocking. I couldn't have been more surprised. (And if your sarcastometer didn't peg on that one, please have it re-calibrated ...) Thank you for your help and patience on this. Ravensfire (talk) 14:41, 18 January 2019 (UTC)
@Ravensfire: One has to AGF and (try to) hold personal feelings aside.  — billinghurst sDrewth 03:50, 19 January 2019 (UTC)

Wikidata weekly summary #348

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Fixed a small bug that we introduced with editing badges on wd.org (phab:T213998)
    • Finished collecting data about the user of the termbox (phab:T211015)
    • Fixed an i18n message (phab:T206416)
    • Created some maintenance scripts for creating and approving oauth consumers (phab:T211568)
    • Checked for possible data coruptions due to an issue with change tags (phab:T213281)
    • Fixed an issue with restoring merge revisions in Lexeme (phab:T204041)
    • Configured WikibaseQualityConstraints on test.wikidata (phab:T209922)
    • Turned on the new entity id formatting for properties (phab:T201838)
    • Continued work on glosses, displaying the language name also in edit mode (phab:T209931)
    • Starting investigating on Shape Expressions
    • Mobile termbox: showing language, description and aliases (phab:T207150)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Global abuse filter 163

Hi to all. For the sake of a misplaced parenthesis the spam filter which tested fine locally, was, however, spitting hits xwiki. Fixed now, apologies for that.  — billinghurst sDrewth 14:00, 28 January 2019 (UTC)

Wikidata weekly summary #349

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Started development on Shape Expressions
    • Termbox: show an expanded-by-default section for the user's preferred languages (phab:T211865)
    • Provide visualization LUA usage on a dashboard (phab:T211768)
    • Fixed issues with sense ID wrapping (phab:T210502)
    • Background work to support the deployment of the next pieces for Structured Data on Commons

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Questions regarding Special:Diff/18816769

Hello Billinghurst, I have noticed a change you have made on Samuel (WMF)/CA Reminder/MassMessage List, and would like to thank you for flagging user Cpettiti.

However, I have few concerns and need some clarification. You have added users like DerHexer or Salvio giuliano to the list but those have already signed the Confidentiality Agreement and do not need to be reminded. Also, Bbb23 and NickK were removed from the list purposely, yet their usernames were again. Finally, you changed the targets, replacing talk pages on local wikis with meta-wiki talk pages. Is there any particular explanation?

Finally, you still haven't signed the Agreement yourself. Since you are part of the Obudsmen, signing this agreement is a requirement too :)

Sincerely -- Samuel (WMF) (talk) 16:14, 28 January 2019 (UTC)

Did I add people, ouch, that wasn't my intention, sorry about that. I must have edited that delivery version, not the latest, that is a trickster that log page link. Re myself, I signed for a year on OC, and that is about to complete. Other than my completing OC, I have no rights that require me to sign the NDA.  — billinghurst sDrewth 22:06, 28 January 2019 (UTC)

Re: Globally blacklisted \bcaoliu2019\.blogspot\b

Thanks a lot for adding those url into Global blacklist. Stang 10:01, 1 February 2019 (UTC)

wikisource

(copied from ban discussion)

For the record, I would indeed like to be unblocked from WikiSource. The reason I cannot request there, is that the nice EncycloPetey person also muzzled me from making any appeal on my talkpage at Wikisource, and nothing to do with which languages I may be fluent in. As several here have noted the unjust nature of this block being used as a technical pretext to ban me, I would be grateful if anyone could reverse that frivolous block, from which EncycloPetey unilaterally stripped me of any right of appeal. Til Eulenspiegel (talk) 12:11, 3 February 2019 (UTC)
I would think that waiting out the ban discussion, at least a little longer, would be worthwhile. My activity at English Wikisource is presently significantly reduced.  — billinghurst sDrewth 22:02, 3 February 2019 (UTC)
It won't be very worthwhile if I am banned first, but I may as well wait I guess. Til Eulenspiegel (talk) 23:14, 3 February 2019 (UTC)

Wikidata weekly summary #350

Here's your quick overview of what has been happening around Wikidata over the last week.

Please

see these two threads; concerned with the Ombudsman Commission. Your opinion is solicited:-) Winged Blades of Godric (talk) 12:27, 7 February 2019 (UTC)

I stopped being an active member of the OC in the middle of last year. I am not the person to ask.  — billinghurst sDrewth 12:46, 7 February 2019 (UTC)
Noted. Thanks for your service, Winged Blades of Godric (talk) 13:43, 7 February 2019 (UTC)

Wikidata weekly summary #351

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Working on the "in more languages" and "all entered languages" parts of the termbox on mobile
    • Working on making undo, revert, edit summaries and more work for Shape Expressions
    • Fixed an error when detecting the same label and description in another Item (phabricator:T194770, thanks Matěj)
    • Making Lemma input on Lexeme pages save your input when you press enter (phabricator:T206140)
    • Making QuickStatements work more easily for other Docker-powered Wikibase instances (phabricator:T205606)
    • Worked more on making Federation work for making Statements on Wikimedia Commons (phabricator:T214557)
    • Working on stripping whitespaces at the beginning and end of Glosses when saving them (phabricator:T212019)
    • Looking into adding more signals to ORES' vandalism detection model so we can detect bad edits more accurately (phabricator:T194737)
    • Preventing a redirect of an Entity onto itself (phabricator:T214775)
    • Fixed an issue with adding sitelinks from Wikimedia Commons (phabricator:T213975)
    • Unified the separators between language and lexical category in different places (phabricator:T201808)

Fix

Hi. I tweaked the template instead so it uses both categories. Regards, —MarcoAurelio (talk) 13:31, 14 February 2019 (UTC)

Wikidata weekly summary #352

Here's your quick overview of what has been happening around Wikidata over the last week.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Revert

Any reason for your revert? On 4omni's user page one of the stewards asked us to place the request at exactly the page you've just reverted. If its the wrong place I would kindly ask the stewards to fix their messages, or if you are not a steward any longer, please ask for their reconfirmation. Dropping a reason for the revert would be useful as well. The meta wiki as a jungle of articles for the most users and its not easy to find the right way here. Thanks -- DerFussi 10:41, 25 February 2019 (UTC)

@DerFussi: Urk, phatphingerbuttonitus. Was only viewing from watchlist, so must have got caught in a screen refresh. <shrug> Sorry about that.  — billinghurst sDrewth 10:51, 25 February 2019 (UTC)
hahaha.. ok it happens. Very often on tablets, if you just scroll through recent changes. Happened many times to me. :) -- DerFussi
Yep, usually I notice when I do it. Clearly I am distracted tonight, or trying to achieve too many things at once.  — billinghurst sDrewth 11:22, 25 February 2019 (UTC)

COI bot?

Deceased currently?? Cheers --Herby talk thyme 13:47, 25 February 2019 (UTC)

@Herbythyme: The tools cloud servers are in the part of the spectrum somewhere b/w WTF <-> FFF. See discussion at user talk of Beetstra of where he is at with the recovery.  — billinghurst sDrewth 21:23, 25 February 2019 (UTC)
I am seeing reports generated, and I know that there was a backlog of files, though cannot say how much retrospective it will do for the down time.  — billinghurst sDrewth 01:23, 26 February 2019 (UTC)

Wikidata weekly summary #353

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Updated some icons with the new WikimediaUI icon set (phab:T209259)
    • Fixed an issue that was causing occasional failures when creating new Items (phab:T194299)
    • Investigated Wikidata Tours not loading correctly (phab:T215919)
    • Adjusted spacing between Sense ID, bar and Gloss (phab:T215502)
    • Fixing a long time issue with introducing new data types in production (phab:T216728)
    • Fixing docs for backup of wikibase container images (phab:T214941)
    • Making undo, rollback and restore work on schema content pages (phab:T214399)
    • Improving edit summaries for schema content pages (phab:T213724)
    • Tightening up the process for editing "identifying information" for Schemas (phab:T214466)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Filter

Can you add this nonsense to the alychi spam filter? Seeing it pop up in a lot of places on a lot of ranges. Praxidicae (talk) 15:10, 15 February 2019 (UTC)

Done AF 96 updated with a few components, it is still set as challenge only. 03:02, 16 February 2019 (UTC)
Looks like they're getting through again: [5][6][7]. Praxidicae (talk) 18:05, 28 February 2019 (UTC)
@Praxidicae: Abuse filters 88 and 96 are challenge, not disallow, so maybe we should be looking at a change, though if we are looking to do that then we may need to toughen one of the two filters (AF88 88 log and AF96 log.)

Of the three examples: 1) was tagged, 2) is shWP which is outside global filters, and 3) is zhWP which is outside global filters.  — billinghurst sDrewth 00:10, 1 March 2019 (UTC)

Stray blocks

Hi, in a couple of days you have managed to ban both 1997kB and Tegel. Be careful :) --Base (talk) 00:44, 1 March 2019 (UTC)

Did I? Sheesh. Thanks. Apologies to Tegel.  — billinghurst sDrewth 01:14, 1 March 2019 (UTC)

Filter 208

FYI: Meta:Requests_for_help_from_a_sysop_or_bureaucrat#Emoji_blocker is open for discussion. — xaosflux Talk 13:08, 1 March 2019 (UTC)

Wikidata weekly summary #354

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Added monolingual language code tlb (Tobelo), thanks User:Mbch331! (T216798, will be deployed next week)
    • Integrating the termbox with Wikibase (phab:T214679)
    • Viewing historic revisions and fetching the termbox data from Special:EntityData (phab:T210615)
    • Fixing emoji breaking the termbox (phab:T217244)
    • Renamed special pages under Wikibase to avoid confusion with Schemas special pages (phab:T216719)
    • Removed unsupported php 7 constant in production, causing a notice and potential undefined behavior ([[phab:T217241
    • Investigated wb_term normalization solution (phab:T215902)
    • Fix for outdated cached WB datatypes on client-side (phab:T216728 (blocks enabling new datatypes, e.g. phab:T216730))
    • Allowing access to wikibase entities from multiple (wikibase) databases (phab:T214557)
    • Allowing to return a proper API error on 'wbformatvalue' action (phab:T207479)
    • Providing open-graph title and discretion meta-tags for lexemes (phab:T206414)
    • Allowing quickstatements to work out-of-the-box in wikibase-quickstatments docker image (phab:T205606)
    • Implementing “undo” for Schemass (phab:T214914, making it work via the API (phab:T217250)
    • Implementing “restore” for Schemas (phab:T214915)
    • Adding created and edited Schemas to the watchlist according to the user’s preferences (phab:T213725)
    • Splitting edit parts on Schemas (phab:T215395, phab:T215393, phab:T215392, phab:T215394)
    • Improving support for multilingual edit comments in MediaWiki (phab:T215637)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #355

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: Dimon2711
    • Closed request for adminship: Esteban16, welcome onboard!
  • Other Noteworthy Stuff
    • Client wikis calling geocoordinate statements from Wikidata using mw.wikibase.entity:formatStatements or the #statements parser function will now have it displayed using a Kartographer <maplink> if available. In case of bug or question, feel free to ask in phab:T210926. Thanks to Tpt for the change!
    • A Google Summer of Code/Outreachy project seeks to add structure to the Commons app. Photographers will be able to pick Wikidata items that are depicted by the picture they upload.
    • Suggestions based on constraints can be enabled for all users

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.



Spambots creeping through filter

1 2 and 3 if you're interested. Thanks Jon Kolbert (talk) 00:43, 12 March 2019 (UTC)

@Jon Kolbert: Thanks for the examples. I have updated and upgraded special:Abusefilter/68 to catch that term as it has been around a little while. [Noting an alternate approach per special:Abusefilter/208 where there are using a surfeit of links.) Earlier I did put a request in for a block of an IP address that was doing similar, though first that I have seen account-based attack undertaking that methodology for a while, usually it is IPs. It is not my favoured way to manage as it does AF overlap and cause a lot of duplicate noise in the Abuselog, though, in this case it looks necessary.  — billinghurst sDrewth 02:54, 12 March 2019 (UTC)
A few more 1, 2, 3, 4, 5, and 6. Jon Kolbert (talk) 00:26, 19 March 2019 (UTC)
@Jon Kolbert: Without urls is a little trickier, with blogs we add them to AF69; the rest we often just get COIBot to monitor. You can add domains to user:COIBot/Poke and I can feed them into the system from there.  — billinghurst sDrewth 05:42, 19 March 2019 (UTC)

Wikidata weekly summary #356

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Prepare new constraint icons (phab:T191322)
    • View history revisions of entities on new termbox mobile (phab:T210615)
    • Caching termbox output on the Wikibase side (phab:T214679)
    • Fix emojis breaking the termbox layout in Chrome (phab:T217244)
    • Work on multilingual support for schemas (phab:T215387)
    • Implement a length limit for the schema text (phab:T216148)
    • Replace the heading/title for schema pages similar to what Wikibase does (phab:T215759)
    • Deploy the shex-simple website, which can be used to check entities against a schema in the browser, on Toolforge (phab:T217333)
    • Deploy the score data type to production

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #357

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: Stanglavine
    • An open discussion on how to model one-way train routes is now taking place, and everyone is welcome to pitch in
  • Development
    • Update property suggester data (phab:T216270)
    • Add a link to the shex-simple tool to make it easier to check entities against a Schema (phab:T217331)
    • Make the placeholders on Special:NewSchema now match the ones on Special:NewItem (phab:T215386)
    • Check for edit conflicts when editing schemas (phab:T217338, phab:T218300)
    • Enable the parser cache for Schema pages (phab:T218459, phab:T218769)
    • Use the FormatAutocomments hook for Schemas to implement translatable edit summaries (phab:T218889)
    • Implement a proper Wikibase-Termbox-Integration according to the ADR (phab:T214679)
    • Fix the emoji breaking the termbox column layout (phab:T217244)
    • Correctly showing revisions with the new termbox (phab:T210615)
    • Correctly handle user-specific language settings in the new termbox (phab:T218111)
    • Fix an issue for score extension (phab:T218535)
    • Turn off RDF support for entity types that doesn't support it (phab:T213483)
    • Respect nofollow config on wikidata identifier links (phab:T175230)
    • Allow accessing Wikibase entities from multiple (Wikibase) databases (phab:T214557)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Autopatrolled

Thank you! --Gereon Kalkuhl (WMF) (talk) 11:58, 27 March 2019 (UTC)

Question

Hi Billinghurst. I wanted to prevent the spammer Pommys1 and Pommys5 to create more accounts and did this. I'm not sure whether that will help. Can you please check? Trijnsteltalk 12:49, 28 March 2019 (UTC)

@Trijnstel: The regex you probably want is .*\bPommys.* <newaccountonly> (the current one you have doesn't work). It should disallow any username that contains a string that starts with "Pommys", but it allows a username if "pommys" isn't a start of the string. So it should disallow "aaaa Pommyaaaa" but allows "aaaaPommysaaaa". -★- PlyrStar93 →Message me. ← 14:01, 28 March 2019 (UTC)
Thanks, PlyrStar93! Fixed. Trijnsteltalk 15:33, 28 March 2019 (UTC)

Huh?

What are you doing? I don't understand why this is necessary. Trijnsteltalk 22:11, 28 March 2019 (UTC)

@Trijnstel: Template:Unblock declined says "Administrators: This template should be removed when the block has expired." so I am deactivating the old usage. <shrug>  — billinghurst sDrewth 22:16, 28 March 2019 (UTC)
@Trijnstel: paused and waiting. We either change the template and stop the deletions, or we remove. Thoughts?  — billinghurst sDrewth 22:40, 28 March 2019 (UTC)
Well, I'm in favor of changing the template, stopping the deletions and reverting your previous actions. This feels rather useless tbh. Trijnsteltalk 22:44, 28 March 2019 (UTC)
Dead blocks from five + years ago, meh! Just leave them. Will change the template.  — billinghurst sDrewth 23:55, 28 March 2019 (UTC)

Wikidata weekly summary #358

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Work on a dashboard for external identifiers (phab:T204440)
    • Add baserevid to WikibaseLexeme API modules (phab:T217243)
    • Add tests for embed.html (phab:T212649)
    • Improve features for wikibase vandalism detection model (phab:T194737)
    • Improve Property Info cache performance (phab:T218115, phab:T218197)
    • Adding nofollow to external identifiers links (phab:T175230)
    • Hide query helper by default in Query Service (phab:T217886)
    • More work on wb_terms normalization (Phab board)
    • Enable trimming whitespace around Label/Description/Aliases and Schema text (phab:T215761)
    • Prevent moving Schemas between namespaces (and generally) (phab:T219313)
    • Limit the length of Schema labels, descriptions, aliases, and schema text in the frontend (phab:T218867)
    • Add tracking for clicks on the “check entities against this Schema” link (phab:T218899)
    • Disallow importing of Schemas from another wiki or XML files to avoid ID conflicts (phab:T218181)
    • Make sure RTL text is being handled correctly in the Schema labels, descriptions and aliases table (phab:T219136)
    • Add a publish button on mobile termbox: (phab:T218573)
    • Building the wbeditentity request to be fired on save request: (phab:T218577)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Blocking AbuseFilter

Hello. Could you help me, please? I tried to write a new abuse filter on our wiki, that blocks a vandal, using the new sysop user:AbuseFilter. But I can't find how to do this. I can see you've wrote some blocking filters. I'll be glad for a little explanation. Thank you very much in advance, IKhitron (talk) 13:05, 8 April 2019 (UTC)

@IKhitron: Hi. This is simply applying the block function of abuse filters, rather than "using the user". You should see the text (or the Hebrew equivalent of) "Block the user and/or IP address from editing" as a tick box in the Actions section.  — billinghurst sDrewth 13:10, 8 April 2019 (UTC)
Thanks. Exactly. There isn't one. Should it be configured for a wiki or something? IKhitron (talk) 13:12, 8 April 2019 (UTC)
Ah yes, it is something that needs to be turned on in the configuration for your wiki. You will need to get a consensus of your wiki for this to be turned on, and then log a Phabricator site request. Let me dig up the configuration item, I don't remember it off the top of my head.  — billinghurst sDrewth 13:14, 8 April 2019 (UTC)
Great. Thanks a lot for your help. IKhitron (talk) 13:15, 8 April 2019 (UTC)
@IKhitron: Ah, it is shown in a different configuration place. See https://noc.wikimedia.org/conf/highlight.php?file=abusefilter.php and it is the the configuration $wgAbuseFilterActions['block'] (see that explained in mw:Extension:Abusefilter. 13:21, 8 April 2019 (UTC)
So, we can do to it without phab? IKhitron (talk) 13:22, 8 April 2019 (UTC)
Sorry for the extra notification, billinghurst, IKhitron you need to make a request to Phab to add Abusefilter-modify-restricted to the sysop group see AbuseFilter for detail, and see phab:T96542 (Indonesian Wikipedia request) for example.--AldNonymousBicara? 13:24, 8 April 2019 (UTC)
Thank you very much. IKhitron (talk) 13:25, 8 April 2019 (UTC)

Wikidata weekly summary #359

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • More work on documenting and preparing the announcement for the Wikidata External Landscape dashboard (phab:T204440)
    • Improved the documentation of WMDE analytic documents (phab:T219844)
    • Set up translatable schema edit summaries using the FormatAutocomments hook (phab:T218893)
    • Improved right-to-left support on schema pages (phab:T219298)
    • Protected schemas against imports (phab:T218181) and page moves (phab:T219313) and disabled the useless “move” and “create” protections for them (phab:T219980)
    • Improved schema edit conflict detection to allow merging of non-conflicting edits (phab:T218300, phab:T219173)
    • Improved the Extension:WikibaseSchema documentation on mediawiki.org (phab:T219979)
    • Fixed a bug on Lexicographical Data when editing existing grammatical features (phab:T219318)
    • Increased musical notation datatype string length limit to 1500 characters (phab:T218767)
    • Got ready for the last steps of new constraint level for suggestions (phab:T204439)
    • More work on allowing editing of mobile termbox fields (phab:T216987)
    • Let term value fields grow with their content (phab:T220185)
    • More work on migrating away from wb_terms

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #360

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Added Sámi monolingual language codes sia (Akkala), sjk (Kemi) and sjt (Ter), thanks to Jon Harald Søby (phab:T217521)
    • Moving forward with enabling constraints suggestions for everyone and remove beta feature (phab:T220609)
    • Fixing an issue with displaying mapframes for geocoordinate on client (phab:T220122)
    • Make it impossible to set the same content in the same language for label and description (phab:T212869)
    • Catch Exceptions where the entity can not be serialized due to being too big (phab:T217741)
    • Fix the order of value suggestions based on constraint (phab:T220587)
    • Add links on entity suggestions from constraint definitions (phab:T207363)
    • Increase musical notation datatype string length limit to 1500 characters (phab:T218767)
    • More work on making the new mobile termbox editable (phab:T216987)
    • More work on migrating away from wb_terms

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Please delete

Can you delete my userpage on Wikisource? Wikisource:User:Aldnonymous, I want to use global userpage instead. Thank you.--AldnonymousBicara? 04:03, 22 April 2019 (UTC)

Wikidata weekly summary #361

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Improved the external identifiers landscape (phab:T204440)
    • Prepare process and announcement for the wb_terms migration to come
    • Allow configuring WDQS UI without changes to files under version control (phab:T194179)
    • Configure suggestion constraint level on Beta (phab:T221107)
    • Graduate suggestions based on constraints beta feature out of beta features (phab:T209879)
    • Editing of labels and descriptions on mobile (phab:T216987)
    • Editing aliases on mobile (phab:T218690)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Cross Wikimedia COI link spam on hiwiki

Hey, look over here for spam, some little help/assistance necessary here, empty tasks full of spam. Since articles on local hiwiki are protected I'm unable to revert stuff correctly or move with a fluent speed. Please look over this articles' history of Facebook "Narendra6m" is a persistent cross Wikimedia spammer and editor with gulping amounts of COI, high probability of PR team editing involving here. Revert them please. -- 27.60.185.232 12:33, 25 April 2019 (UTC)

Noted. With w:hi:फेसबुक, it is only a light protection, so having an account and editing logged-in would give you suitable rights to edit such a page. I will get a report regenerated for the below domain, so if there are other domains to be investigated, then please let me know.  — billinghurst sDrewth 21:29, 25 April 2019 (UTC)


khojohindime.com

(LinkSearch: meta | en | es | de | fr | ru | zh | simple | c | d | Wikipedias: top 25 · 50 · major wikis · sc · gs)(Search: Google | en (G) | fr (G) | de (G) | meta (G) | backlinks | → links ←)khojohindime.com
(Reports: Report ← track | XWiki | Local | en | find entry)(DomainTools: whois | AboutUs | Malware?)

Wikidata weekly summary #362

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: BRPever
  • Development
    • Displaying mapframes for geocoordinate on client requires preprocessing by the user (phab:T220122)
    • Fixing cursor jumping to next field and overlapping of menus (phab:T172937)
    • Wikidata a focus issue on grammatical features field (phab:T218229)
    • Add language codes rm-rumgr, rm-sursilv, rm-surmiran, rm-sutsilv, rm-vallader, rm-puter for Lexemes (phab:T210293)
    • Align RTL languages in glosses to right (phab:T203081)
    • Add new monolingual codes: qya + sjn, el-cy, syc, abq, hbo) (phab:)
    • Fix a bug with NewLexeme suggester menu (phab:T199409)
    • Created a dedicated Phab board to help tool builders with the changes on wb_terms
    • More internal work to get the first version of mobile termbox ready for deployment

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Global message delivery/Targets/Wikidata

@Billinghurst: Did you want to remove yourself ? (diff). So you unsubscribed someone else, one line below. May be that's what you wanted (you still want the subscription and removed a user that asked for it or blocked/removed/renamed). Check this deletion. Janet verdy_p (talk) 15:20, 30 April 2019 (UTC)

Thanks for your concern. I am cognisant of what I am doing.  — billinghurst sDrewth 21:08, 30 April 2019 (UTC)

Is there a way to temporarily give up admins power?

Dear Sir, due to recent concern of my conduct in Thai Wikipedia, I personally would like to give up my admin’s power for, say, 6 months. Is there a way to accomplish this? Best regards, --Horus (talk) 18:30, 1 May 2019 (UTC)

replied at User talk:Horus. — xaosflux Talk 19:00, 1 May 2019 (UTC)
@Horus: That is an area where each wiki would have rules that bind local bureaucrats, or otherwise assist the stewards to make that interpretation about pausing and resuming an adminship. There is no global rule in place.  — billinghurst sDrewth 23:05, 1 May 2019 (UTC)

Tool

Hi, Billinghurst. How are you? Well, I'm searching a tool and I think you can help. I'm creating a list of pt.wiki's sysops by number of actions and neither xtools.wmflabs.org/adminstats or xtools.wmflabs.org/ec/pt.wikipedia.org/ is being very useful. The first lists all sysops in X time (one year at most), taking up a lot of time, while the second does not list the actions from older users. So, I remembered a tool, created by Quentinv (I think), which listed the administrative actions that X user had done on all WMF projects. It was widely used to tracking global sysop's activity. Do you know / remember what tool is? Thanks! Érico (talk) 00:07, 5 May 2019 (UTC)

@Érico: Quentinv's tools are long dead. There are now only xtools.wmflabs.org or tools.wmflabs.org/meta tools that do anything in this space that I am aware. It is an unsexy area.  — billinghurst sDrewth 02:29, 5 May 2019 (UTC)
Thanks. But, only for note, the site https://pt.wikiscan.org contains the data I were looking for. Regards. Érico (talk) 01:22, 6 May 2019 (UTC)

Wikidata weekly summary #363

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Closed request for adminship: BRPever, welcome on board!

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


re: "User:Wiglaf~metawiki/runes"

You might have mistaken something. This test page is not created by the user itself but an IP address, please delete it, thank you. -云间守望 04:12, 10 May 2019 (UTC)

You don't know that at all. The page is doing no harm.  — billinghurst sDrewth 04:21, 10 May 2019 (UTC)

Wikidata weekly summary #364

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Finish renaming WikibaseSchema to EntitySchema
    • Investigate how to port Wikibase Selenium tests from Ruby to Node.js (phab:T221638)
    • Include a clear two step process in shex simple tool (phab:T221612)
    • Fix the "edit visually" on the Query Service interface (phab:T222181)
    • More work on wb_terms redesign (see documentation on phab:T221764)
    • More work on mobile termbox
    • Investigate on a bug found on wbeditentity not removing all aliases (phab:T203337)
    • Getting ready for the Wikimedia hackathon

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Special:GlobalBlockList/81.4.107.73

Yes, according to Proxy checker it is an Open Proxy. So 6 months globally as minimum. PS: looks I just missed the meta checkbox while blocking masti <talk> 08:15, 15 May 2019 (UTC)

Can you unblock 109.253.199.58?

He was adding a request, therefore there's no reason to block him. He wasn't inserting Nonsense or Gebbrish. And one last thing, you blocked him for no reason, he didn't did vandalism--109.253.182.111 09:54, 17 May 2019 (UTC)

block expired  — billinghurst sDrewth 07:38, 18 May 2019 (UTC)

Asking for admin action in Thai Wikipedia

May I ask: if I have an urgent request needing admin action (and uncontroversial) in Thai Wikipedia, can I ask for some steward's help here? Because I think sometimes the remaining Thai admins are too slow to respond. Thank you. --Horus (talk) 05:13, 20 May 2019 (UTC)

@Horus: I haven't been a steward for several years, if you have a request for stewards at thWP, then you should make such a request at either SRM or SN, depending on the issue.  — billinghurst sDrewth 08:30, 20 May 2019 (UTC)

Romani Wikipedia

Thanks for filter import. For the adminship I wrote my application here and now I'm waiting for the community. Is everything fine with it or should I apply on SRP now? – Balint36 🚌 bus stop 22:47, 20 May 2019 (UTC)

@Balint36: Leave it for a week, then take it to SRP. If you tell stewards now, they will just put it {{on hold}} for the week.  — billinghurst sDrewth 23:46, 20 May 2019 (UTC)

Wikidata weekly summary #365

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Added lastrevid of entities to JSON dumps – thanks Pintoch!
    • Working to scale the Wikidata Concepts Monitor system (phab:T203366)
    • Imrpove logging in on mobile (phab:T215913)
    • More work on mobile termbox
    • Several developers from the Wikidata team attended to the hackathon, discussed with the community, gathered feedback, hacked on things together with volunteers :)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Block first, revert after

Hi to those watching here. When the idiot vandals are here, then please block first, and then revert, rather than engage in a revert war with an idiot, especially where they are demonstrating having an expertise in mindless idiocy.

If you cannot block, then don't fuss it, someone will see it soon enough and manage it. Plenty watch here.

That idiots get their jollies vandalising this page is of little concern to me whatsoever, and shouldn't overly fuss others. It will be managed.  — billinghurst sDrewth 23:55, 21 May 2019 (UTC)

Britannica searches

Morning Billinghurst

I just wanted to enquire about your addition of Britannica search queries to the spam blacklist (seemingly per this). What prompted this? Was there some history of disruption associated with such URLs? I wanted to put a link to a Britannica search on a talk page on enwiki today, to demonstrate a point I was making. Many thanks Amakuru (talk) 08:56, 23 May 2019 (UTC)

@Amakuru: Spambots utilise it regularly, presumably as one of their means to make their spam urls look to be legitimate. There are a number of otherwise benign domains where they abuse the search function. As the output of search links are variable and generally not part of either a reliable source, a reference, etc. it has been a reasonable means to find a gentler way to prevent the spam.  — billinghurst sDrewth 09:21, 23 May 2019 (UTC)
If you peruse w:special:log/spamblacklist you will generally find a hit pretty often—well you did for quite a while, I cannot say that I have overly checked it more recently]].  — billinghurst sDrewth 09:25, 23 May 2019 (UTC)
Ah OK, thanks for the reply. Not a massive deal, I guess, just that I wanted to put a link on a talk page to highlight to others that a particular search query yielded no results in Britannica. I can see that a search query would never be a useful link for an article though. Amakuru (talk) 10:41, 24 May 2019 (UTC)
@Amakuru: The balance is hard across 770 wikis. The alternate is for you to locally whitelist the url string and then manage its use with an abusefilter, maybe just allow it in the odd numbered talk namespaces, which are less spam-targeted. There are numbers of similar search-type urls that the spambots love that have has similar treatment. The blacklist is a fairly blunt tool, though flooding abuse filter logs is equally problematic.  — billinghurst sDrewth 00:26, 25 May 2019 (UTC)

Need your help

Hello. I opened a Request for comment page but I did not do it properly, I neglected too many things and it is not displayed in Request for comment hub page. Can you amend my page? Thank you in advance --Ruhubelent (talk) 18:41, 23 May 2019 (UTC)

The root page needed to be purged ?action=purge. It is showing for me.  — billinghurst sDrewth 22:24, 23 May 2019 (UTC)
Thank you, it is not shown there. It was not showing at the time I wrote, I thought I did something wrong. I do not know how to do it, that is why I contacted you. --Ruhubelent (talk) 07:04, 24 May 2019 (UTC)
It is not shown there? It is top of the Open RFC list. As I said, the RFC page needed to be purged, and I linked to the description of about purging. Not sure else you would like me to do.  — billinghurst sDrewth 08:10, 24 May 2019 (UTC)
My blunder, I was gonna write it is shown. I do not know how I wrote "not." Sorry and thank you --Ruhubelent (talk) 08:47, 24 May 2019 (UTC)
All sweet. Sometimes my fingers don't obey my fingers either.  — billinghurst sDrewth 09:56, 24 May 2019 (UTC)

Wikidata weekly summary #366

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Past: Wikidata Labs XV in Brazil, with an introduction to lexicographical data (slides)
    • Past: Workshop for experienced editors of nl.wiktionary to explore the possibilities of lexicographical data.
  • Other Noteworthy Stuff
    • The US Library of Congress are integrating Wikidata QIDs into their authority files (blog post)
  • Development
    • Deploy the EntitySchema extension on test.wikidata.org and beta.wikidata.org
    • Remove the remaining beta feature config for constraint-suggestions (phab:T220609)
    • Introduce baserevid for conflict checking in Lexeme (phab:T217245)
    • Fix a bug making impossible to get Lexeme Forms and Senses via the API (phab:T223995)
    • Add Wikidata query service lag to Wikidata maxlag (phab:T221774)
    • Allow accessing Wikibase entities from multiple Wikibase databases (phab:T214557)
    • More work to get termbox ready for deployment
    • Add a login warning on mobile termbox editing (phab:T221831)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.



Thank you for doing admin tasks

I made a process request that an administrator delete a set of redirects so that I could post full content in those places. Within an hour you did that in the way the system is supposed to work.

Thank you for being around, using administer user rights appropriately, executing tasks according to system design, and responding quickly to my request. You make this wiki function as it is supposed to operate. Blue Rasberry (talk) 18:39, 31 May 2019 (UTC)

Hey mate, most welcome; though it sounds like being normal isn't normal. Content isn't my speciality, though where you do excel; so thanks for your part in the glorious game. :-)  — billinghurst sDrewth 07:57, 1 June 2019 (UTC)

Wikidata weekly summary #367

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Specify license of mediawiki/Wikibase/WikibaseLexeme ontology (phab:T216842)
    • Enable bugfix on beta for wbeditentity setting aliases to empty array (phab:T223300)
    • Use correct validator in alias changeop and provide error messages if alias is too short (phab:T223311)
    • More work on the use of special pages Special:SetAliases and Special:SetLabelDescriptionAliases with aliases containing | character (phab:T223270)
    • Add Wikidata query service lag to Wikidata maxlag (phab:T221774)
    • Fix BadMethodCallException wbgetentities when getting Lexeme subentities (forms, senses) (phab:T223995)
    • Scale the machine learning components of the WDCM system w. {text2vec} WarpLDA implementation (phab:T203366)
    • Inspect strange behavior of the WD_percentUsageDashboard (phab:T217994)
    • WDCM dashboards maintenance: eliminating the need to use the wdcm.maintable in Hive, WDCM Geo is now independent of it (with its update engine running Spark instead) and re-designed to match the WDCM standards (phab:T217994, phab:T214586, phab:T217997)
    • Further preparations for the Wikidata Languages Landscape project (phab:T221965)
    • More progress in order to get the mobile service deployed
    • Adding an IP edit warning popup for mobile termbox (phab:T221831)
    • Allowing users to ignore this popup permanently (phab:T221833)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Please delete & hide User special:contributions/220.82.42.69 with offensive language (affront) in Russian language

Good morning! Please delete & hide 2 last topics with offensive language (affront) here https://en.wikipedia.org/wiki/User_talk:Wanderer777 from 220.82.42.69. Cite "отношений со всякими долбоебами (dunсe, fuсkhead) типа Фила Вечеровского". "Долбоеб" = "dunсe", "fuсkheаd" in English, its very strong offense in Russian language. — The preceding unsigned comment was added by 116.125.179.222 (talk) 2019-6-11 09:30:21 (UTC)

I would prefer to hear from the account holder about how they would like to have their page managed, and I think that it would be better that the instruction is given at enWP. I have blocked the particular abusive editor.  — billinghurst sDrewth 09:43, 10 June 2019 (UTC)
    • Thanks! But I want to hide user contributions 220.82.42.69 with offensive language (affront) here https://en.wikipedia.org/wiki/User_talk:Wanderer777.
    • Cite: "отношений со всякими долбоебами типа Фила Вечеровского". "Долбоеб" = "dunсe", "fuсkheаd" in English, its very strong offense in Russian language. This offense is not for Wanderer777, this offense for another user. You blocked IP, but I want to hide and delete offenses!
      I understand what you want. I will take my direction from the account holder.  — billinghurst sDrewth 09:53, 10 June 2019 (UTC)

Wikidata weekly summary #368

Here's your quick overview of what has been happening around Wikidata over the last week.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Hi

On the advice of @Tomybrz:, it's enough to have my user pages & my talk user pages being vandalized because i'm a sysop on the french WP. I'm looking for where asking in one go the definitive Extended confirmed protection for all my pages on all projects. Thx for answering. OT38 (talk) 17:03, 15 June 2019 (UTC)

Addressing at SRM as it has already been taken there.  — billinghurst sDrewth 00:22, 16 June 2019 (UTC)

Protection

Hi. I noticed you protected my talk page due to the vandalism, and then changed it to semi-protection. It seems that just now, a vandal managed to become autoconfirmed somehow to get past this. Therefore, would it be a good idea to increase the protection level on my talk page here? Thank you. Diamond Blizzard (talk) 05:01, 17 June 2019 (UTC)

@Diamond Blizzard: I am reticent to put full protection on a talk page as that means only admins can post there, and you cannot. If you are not undertaking business here, and push people to your WP talk page, then I am happy to further protect that page. If you are likely to do business here, then I can add your talk page to an existing filter, and adapt the filter to catch the garbage that is being added. Please let me know which is the better means to progress.  — billinghurst sDrewth 05:55, 17 June 2019 (UTC)
Thanks for the response. Nothing else seems to have happened so far, so unless something does, I think this level of protection is fine now. But just wondering, does extended confirmed protection exist on this site? Diamond Blizzard (talk) 19:19, 17 June 2019 (UTC)
No, that user right, itself, only exists at enWP, so that is not an available protective option.  — billinghurst sDrewth 21:03, 17 June 2019 (UTC)
@Diamond Blizzard: I have added your user talk page to one of my abuse filters, and I am asking checkusers to do a follow up to see what is possible in that space.  — billinghurst sDrewth 08:05, 21 June 2019 (UTC)

Wikidata weekly summary #369

Here's your quick overview of what has been happening around Wikidata over the last week.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #370

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Beginning of wb_terms migration (phab:T221764)
    • Fixed a bug with phan on Wikibase (phab:T226083)
    • Enable bugfix for wbeditentity setting aliases to empty array (phab:T223303)
    • Fix an issue with pipe character on some special pages (phab:T223270)
    • Fix an issue with removed constraint still displayed on Lexeme (phab:T223372)
    • Make edits to EntitySchema pages autopatrolled (phab:T224495)
    • Work on creating better edit summaries for wbeditentity API endpoint (phab:T224010)
    • Deploy the work environment for new mobile termbox
    • Start setting up the technical environment for Wikidata bridge

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Catanalysis in tool "Meta"

Seems to be down again. Can you help? Thanks. StevenJ81 (talk) 15:52, 28 June 2019 (UTC)

Nope, not a developer. You'll need to log a bug in GitHub.  — billinghurst sDrewth 22:24, 28 June 2019 (UTC)
Sorry. I thought it said you are a maintainer. Apologies for disturbing you. StevenJ81 (talk) 22:49, 28 June 2019 (UTC)

Wikidata weekly summary #371

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • More work on preparing the technical setup for Wikidata Bridge development
    • Implement Feature Flag for Wikidata Bridge (phab:T225935)
    • Discuss the best way to connect template parameter to corresponding Wikidata property (phab:T224832)
    • Improve the documentation for Wikibase sites setup (phab:T218282)
    • Prepare the last steps for reading from new term store implementation (phab:T225603) according to the migration plan (phab:T221765)
    • Fixed a bug and reduced significantly the amount of addUsagesForPage jobs in our jobs queue (phab:T205045)
    • Removed feature flag for the bugfix for wbeditentity setting aliases to empty array (phab:T223305)
    • Decreased EntityUsageTable addUsage batch size to 100 (phab:T225500)
    • Configured query service lag for Wikidata maxlag (phab:T222193)
    • Helped fixing an issue with moving files on Commons (phab:T226672)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #372

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: ZI Jony
  • Other Noteworthy Stuff
  • Development
    • Enabled JSONLD support for entity data (example)
    • Fixed JSON dump issue (phabricator:T226601)
    • Readded qualifier hashes in JSON output that accidentally got lost (phabricator:T227207)
    • Made sure changes on Entity Schema pages by autoconfirmed users are autopatrolled (phabricator:T224495)
    • Looked into issues with partial blocking on Wikidata entities (phabricator:T207893)
    • Adding MediaInfo as an entity type that can be used in the "allowed entity types"-constraint (phabricator:T224362)
    • Investigating an issue with the tours on Wikidata (phabricator:T223999)
    • Initial work for the edit dialog that is needed for editing of Wikidata's data from Wikipedia (Wikidata Bridge)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Poke

Would you or someone else mind deleting the contributions of this IP. The "translations" are just Farsi for "sex" and unfortunately my marking them for deletion put the main page in deletion... Call my an idiot. TonyBallioni (talk) 07:08, 5 July 2019 (UTC)

Already done  — billinghurst sDrewth 23:28, 13 July 2019 (UTC)

Userpage deletion

Hello sir, I'm vanishing from all wikimedia projects. So please delete all my userpages including the local user page in Assamese Wikipedia (as.wikipedia.org).

Also block and delete userpages (in local wiki, i.e. as.wikipedia.org) of সদস্য:Renamed user 2wz4ntr and সদস্য:Vanished user byhrlwopfidu as these accounts are also owned by me.

Thanks.

Vanished user qwerty12345 (talk) 09:03, 5 July 2019 (UTC)

Not done not a global sysop task, especially not from my user talk page.  — billinghurst sDrewth 23:29, 13 July 2019 (UTC)

Wikidata weekly summary #373

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • Structured Data on Commons: RDF output for MediaInfo is now available (example)
    • Edits with the tag #suggestededit-add 1.0 come from the suggested edit feature on Wikipedia's Android app: see the FAQ for more information
    • Property number 7000: DigitalNZ ID is live. This data aggregator has over 30 million records. The proposal was the first from Ambrosia10, a New Zealand editor.
  • Development
    • Create docker image for wdqs version 0.3.2 (phab:T226939)
    • Fix an issue with JSON output lacking qualifier hashes (phab:T227207)
    • Track number of links to schema pages (phab:T218903)
    • Disable Wikidata sitelinks in ProofreadPage namespaces (thanks to Matěj Suchánek) (phab:T227201)
    • Fix a cache issue with the language of the "check entities against this schema" link (phab:T224594)
    • Add EntitySchema extension to wikibase-docker bundle image (phab:T226152)
    • Enable JSON-LD support for Wikidata (phab:T220696)
    • Add baserevid to WikibaseLexeme API module (phab:T225073)
    • Extracting (and logging) Data Bridge parameters from edit links (phab:T226994)
    • Opening a modal with edit this link information (phab:T226996)
    • Showing the current Wikidata value in edit modal (phab:T226997)
    • Disabling interactive elements while saving on mobile termbox (phab:T222886)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #374

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: 1997kB
  • Events
    • Past: IRC office hour, July 16th (log)
    • Upcoming: Wikidata Tainan Meetup in Taiwan, July 31st (Facebook event)
  • Development
    • Fix a bug that was preventing to add multiple glosses (phab:T228080)
    • Show number of senses and forms on page information for WikibaseLexeme entities (phab:T224844)
    • Show number of statements and external identifiers on page information for Wikibase entities (phab:T224842))
    • Track number of external identifiers on Wikidata over time (phab:T224129)
    • Fix a few queries on Grafana (phab:T227788)
    • Update the query host for Grafana (phab:T218710)
    • Add support for "MediaInfo" as value for "allowed entity types"-constraint (phab:T224362)
    • Data bridge: open a modal with edit link information (phab:T226996)
    • Show the current Wikidata value in edit modal (phab:T226997)
    • Extract data bridge parameters from edit links (phab:T226994)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #375

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Re-evaluate supporting dcatap namespace (feel free to give feedback)
    • Data bridge: open modal with edit link information (phab:T226996)
    • Show the current Wikidata value in the modal (phab:T226997)
    • Add editing widget/input to client edit modal (phab:T226998)
    • supporting baserevid request param in lexeme api endpoints (phab:T217245)
    • Fix new store code in order to continue the terms migration (phab:T226008)
    • Fix an issue with broken WikibaseQualityConstraints tests (phab:T228855)
    • Fix issue that used to cause many fatals on production (phab:T227450)
    • Drop wbEntity config in entity pages (phab:T85499)
    • Fix an Internal error in Recent Changes for Lexeme (phab:T228996)
    • Create better summaries for our wbeditentity endpoint (phab:T220696)
    • Respect user's preference for thumbnail sizes on Wikidata (phab:T224189)
    • Allow linking to Schemas in statements (phab:T214884)
    • Fix a bug with Wikidata Tours (phab:T223999)
    • Update accounting for WDQS lag in wikidata maxlag param (phab:T221774)
    • More work on allowing accesing one wikibase instance from another (phab:T214557)
    • Deploy the mobile termbox on test.wikidata.org and fix various bugs
    • Show progress/activity on termbox mobile if a save request is still being processed (phab:T222890)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Documentation for setting up a newly created wikimedia wiki

Hi, Billinghurst. I'm curious... (it'll be the death of me)... Are there any specific documentation pages (or similar helpful links) that you refer to when setting up a new wiki?

I know you did the vast majority of the work setting up wikimania: (i.e. importing templates & MediaWiki:strings, and I believe setting up user-groups, and other?), and I'm trying to get a better understanding of the overall process.

I looked around a bit, and found the Technology-end is covered by wikitech:Add a wiki, but I couldn't find anything at wikitech, meta, or incubator, regarding what the steps after that are.

If there are not any existing pages and it's all in your head (and the heads of other people (??) who've done similar), maybe it'd be worth starting a page of notes?

That's it! Cheers, Quiddity (talk) 23:23, 29 July 2019 (UTC)

@Quiddity: Umm, I just reacted to needs, and brought in old WM201[6-8] stuff I thought relevant as I wanted to ensure that we were building multi-lingual.

You will note that I have next to ZERO content contributions at Wikimania. For templates and stuff it is just watching the needs via Special:SpecialPages. So predominantly reactive, rather than pro-active. I did have a look at the old Wikimanias to see what they had been using and doing, and prepared for similar setup utilising previous translations. For Mediawiki: ns it was kept pretty generic (purposefully to allow for existing translations to rule) and after that it is was Sidebar and Gadgets. Admin side, we have kept pretty simple, again reacting to needs. Wikimania is typically not new users.  — billinghurst sDrewth 23:44, 29 July 2019 (UTC)

Nod, that makes sense. I was asking partially because I'm interested in how new content project wikis get setup (usually after graduating from Incubator), and partially in the context of wmania:2019:Technology outreach & innovation/Building Technical Capacity in Smaller Wikis and similar endeavours - i.e. maybe specific stewards or the SWMT helps with that kind of thing? Or possibly it's all just left up to the new community to figure it out for themselves, based on the notion that they'll have to bootstrap in a dozen other areas anyway? Any thoughts or pointers on who else to ask, would be welcome. :) Quiddity (talk) 00:51, 30 July 2019 (UTC)
Talked to the admins who run incubator? One would think that there is a community of sufficient size to promote from incubator, and a group of people who make an assessment on its move. There are global admins who watch, though we don't normally watch content, though there rae soe in the SWMT team who use a small wiki watch tool specifically.  — billinghurst sDrewth 08:30, 30 July 2019 (UTC)

The usual - COIbot

Sorry to bother you but...! The last one I added to the COI bot has produced the report but not the Xwiki one in maybe 48 hours (it's probably a site that needs BL too)? Equally the previous two I added (non standard domain names?) have had no reports? Hope life is ok - cheers --Herby talk thyme 10:54, 30 July 2019 (UTC)

@Herbythyme: Beetstra has moved it to its new home, and still is tweaking its bits and performance. I suggest that you mention to Beetstra that the poke page is problematic. I have manually fed them to the bot in IRC, so that should generate the reports.  — billinghurst sDrewth 10:57, 30 July 2019 (UTC)
Appreciated and pinging @Beetstra: so that he is aware. Thanks --Herby talk thyme 11:11, 30 July 2019 (UTC)

Plus a bit :) Sorted the nl site one out. The "mail" themed ones are interesting. My gut feeling is that there were a few before these on Commons before I really noticed - not consistent domains but on that theme (and they resolve to the same IP I see). Have you noticed anything? Cheers --Herby talk thyme 11:16, 30 July 2019 (UTC)

@Herbythyme: first and second are both the same spammer Special:WhatLinksHere/User:COIBot/LinkReports/62.210.96.27 and I think we would blacklist. Third looks manual, so probably shake a cage first.  — billinghurst sDrewth 11:21, 30 July 2019 (UTC)
Thanks and will look some more tomorrow probably - cheers --Herby talk thyme 14:30, 30 July 2019 (UTC)
@Herbythyme: I'm not sure what you mean .. poking COIBot is only for producing LinkReports. At the moment I do not have a mechanism for creating XWiki reports from a Poke (is this a request?). --Dirk Beetstra T C (en: U, T) 12:34, 30 July 2019 (UTC)
Oh, it hadn't created Link reports, those only came when I kicked it (though I didn't check the period of time between herby's addition and his ping)>
@Beetstra: - thanks and I didn't know that the poke didn't trigger XWiki - would be nice if it did. The point was really that 2 of my requests didn't work until Billinghurst did the work on IRC (they'd been there for maybe 48 hours?). --Herby talk thyme 14:30, 30 July 2019 (UTC)
@Herbythyme: <copy><paste>s/link/xwiki/sig<save><upload><restart><test>. --Dirk Beetstra T C (en: U, T) 15:15, 30 July 2019 (UTC)
Note: LinkSummary -> report, XWikiSummary -> report + xwiki-report. --Dirk Beetstra T C (en: U, T) 15:16, 30 July 2019 (UTC)
Comment Comment @Praxidicae: had a go, and it didn't appear to trip the XWiki switch. I have added a couple and see that they did feed straight into COIBot. Praxidicae is on the Poke permission list, so is there an additional permission requirement to added for those on the granteduser list? Though I see that Herbythyme's request is completed, and has the same rights in the settings file.  — billinghurst sDrewth 21:43, 30 July 2019 (UTC)
And when I re-add the exact same domain, it feeds straight in. So it doesn't seem to be related to the domain name.  — billinghurst sDrewth 21:47, 30 July 2019 (UTC)

Wikidata weekly summary #376

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Fix logging for errors on wbcontentlanguages requests (phab:T228888)
    • Add request information to request timeout errors (phab:T228885)
    • Show an error message when saving fails on mobile termbox (phab:T222884)
    • Add editing widget/input to client edit modal (phab:T226998)
    • Show the current Wikidata value in the Bridge modal (phab:T226997)
    • EntitySchema datatype (phab:T214884)
    • Reduce the number of ResourceLoader modules that WikibaseClient register: (phab:T203696)
    • Reduce text returned by EntityContent::getTextForFilters (phab:T226216)
    • Fixed a bug with PHP Warning (phab:T229482)
    • Fixing a bug about value pickers being broken (phab:T229604)
    • Fixed BadMethodCallException wbgetentities when getting Lexeme subentities (phab:T223995)
    • Investigate on Graphoid issues (phab:T229236)
    • Fix issues on Wikidata Tours (phab:T214884)
    • Make logging warning or info of not finding entity for revision configurable (phab:T229574)
    • Fix Grafana Datamodel References dashboard (phab:T214894)
    • Move "Wikidata item" link outside of "toolbox" sidebar to "other projects" sidebar (phab:T66315)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #377

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • The open source geocoder w:en:Nominatim used by the OpenStreetMap project is participating in the Google Summer of Code with an internship working on integrating Wikidata as a ranking metric for its search results. Check the development blog.
  • Development
    • Fix a caching problem on termbox (phab:T228978)
    • Investigate options for termbox load testing (phab:T229790)
    • Use thumbnail preferences for thumbnail of Commons media file (phab:T224189)
    • Add tags parameter to Wikibase APIs that edit entities (phab:T229917)
    • Move "Data item" link outside of sidebar toolbox (phab:T66315)
    • Create Maintenance Script to Remove Terms in a Language from Current Revision (phab:T222606)
    • Fix Grafana Datamodel References dashboard (phab:T214894)
    • Add editing widget/input on Bridge (phab:T226998)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Spam questions

Hello Billinghurst! Just a question about how you found the spam of this and this and ordered COIBot to make reports on IRC when I don't see you on Freenode. Is there another spam monitoring channel/network? I'm trying to help out more re: spam and hope to learn from you about this. Best, Vermont (talk) 22:22, 16 August 2019 (UTC)

I found the spam by old-fashioned hard work of following spammers edits, and seeing what else they had added. // I am guessing that you are sitting in the channels to watch spam, though the bot can be controlled from elsewhere, though it is not monitoring spam. I just bossed. // Small Wiki Monitoring Team/IRC is the page with the bossing commands.  — billinghurst sDrewth 22:36, 16 August 2019 (UTC)

Wikidata weekly summary #378

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • In this new section, you can share your favourite tool with the other Wikidata users. You can add some suggestions here.
    • NameGuzzler allows you to automatically add an identical label or alias into many languages (for example, the name of a person or a place). You can define your own custom list of languages that you want to add.
  • Development
    • Fix an issue with the pop up of Wikidata Tours (phab:T223999)
    • Call WikibaseLexeme API with baserevid parameter from the UI (phab:T217245)
    • Fix a bug with CheckConstraintsJob (phab:T227450)
    • Fix a bug with wbgetentities when getting Lexeme subentities (phab:T223995)
    • Add editing widget/input to client edit modal: (phab:T226998)
    • Add tags parameter to Wikibase APIs that edit entities: (phab:T229917)
    • More work on the the production Termbox service
    • tidying up our browser test suite (phab:T229910)
    • adding browser tests for basic editing (phab:T230187)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

abstract algebra links

@Billinghurst: Sorry if this request is misplaced or you are not the proper addressee - but it seems to me that you have been deleting links of my webbook on abstract algebra from several pages. And this has occured several times before. It seems to me that your reason to do so was "no evidence of reliable source or authority". So let me make this very clear: I used to be a member of the mathematical department of the university of Tübingen. I know this stuff. And by the gods, this is mathematics. I give full proof of every single theorem in this text, so why don't you just take a look at it and check it? What is an Open Public License good for if people like you make it impossible to publish texts on the internet, free of charge? So if you don't know the field and are unable to gauge the quality of a text, get a referee who can. I'm sure (s)he will recognize the quality of this work. A.B. Zeidler — The preceding unsigned comment was added by 92.77.160.108 (talk)

That is not how it works for any additions to an encyclopaedia. Please see the relevant help page(s) on the wikipedia on which you are editing to see information about using reliable sources; conflict of interest editing, and the like. If you are uncertain about this, then please discuss this with the communities about how such additions can take place.  — billinghurst sDrewth 11:33, 21 August 2019 (UTC)
I would also suggest that you look to creating an account as that allows communications to take place. When editing from a dynamic IP address there is little opportunity to participate in a conversation, and nothing about us proactively contacting you.  — billinghurst sDrewth 11:34, 21 August 2019 (UTC)

Wikidata weekly summary #379

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming: Next Linked Data for Libraries LD4-Wikidata Affinity Group call: Wikimania recap, 27 August. Agenda
  • Development
    • Deploy mobile termbox, follow-up and bug fixing
    • Deploy then rollback the move of "Wikidata item" link on clients due to cache issues (phab:T66315)
    • Work on adjusting the save button of the Entity Schema editor (phab:T230398)
    • Work on the bridge emitting button (phab:T230326)
    • Introduce a header for the bridge modal (phab:T230328)
    • Produce initial statistics/indicators for the Wikidata Languages Landscape (phab:T223119)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Affiliate-selected_Board_seats/2019/notes

Hi! In this deletion request, you said that I have been told that an updated version of this page will be made available at the same page. Given that it is four weeks later and Affiliate-selected_Board_seats/2019/notes is still a red-link, could you please disclose who gave you this assurance, and what they said about timeline? CC @Bluerasberry. Cheers, Bovlb (talk) 22:30, 28 August 2019 (UTC)

@Bovlb: Thanks for asking. My preference would be that all discussion about this be in public and on-wiki, as is the norm except in unusual circumstances. Blue Rasberry (talk) 22:52, 28 August 2019 (UTC)
@Bovlb: Please talk to the chair of the committee. I am not involved with the committee (or any), and they have their processes.

I am comfortable to prod the person who gave me that assurance. I will also note that it has been Wikimania time, and that is traditionally busy, especially with travellers.  — billinghurst sDrewth 23:05, 28 August 2019 (UTC)

Thanks for responding. When you say "the committee", do you mean the election facilitators listed in Affiliate-selected_Board_seats/2019#Process? If so, how do I tell which one is the chair? Cheers, Bovlb (talk) 00:50, 29 August 2019 (UTC)
Yes, and talk to the board liaison, who is also the person who made the initial deletion request. Excuse my lack of familiarity on the structure, I am away from Wikipolitics these days.  — billinghurst sDrewth 02:51, 29 August 2019 (UTC)
Thanks. I'm not familiar either, hence my confusion. So, I think you mean Ad Huikeshoven, who is the election facilitators' liaison to the board, as opposed to Raystorm, who is the board's liaison to the election facilitators. Presumably they liaise with each other.  :) Cheers, Bovlb (talk) 03:02, 29 August 2019 (UTC)
From this response, it doesn't look like we're getting any updated version. Inasmuch as you were relying on that assurance to support the deletion rationale, that part is now moot. Cheers, Bovlb (talk) 15:03, 29 August 2019 (UTC)
@Bovlb: I have had a response from the intermediary who contacted me, and they are following up.  — billinghurst sDrewth 08:56, 31 August 2019 (UTC)

Wikidata weekly summary #380

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Adjust label of save button of the Entity Schema and add accesskey for easier editing editor (phab:T230398)
    • Get Grafana Datamodel References dashboard back up and running (phab:T214894)
    • Fix an issue in EntitySchema tests that caused some CI failures (phab:T231065)
    • Localize Wikibase API help links (phab:T231269)
    • Support tags parameter on Wikibase APIs that edit entities (phab:T229917)
    • Add in Wikidata support for sitelinks to https://nap.wikisource.org (phab:T212886)
    • Reading property terms from new store in production now (phab:T225053)
    • Adding WDQS lag to maxlag info, to avoid stress on WDQS machines (phab:T221774)
    • Implementing the fallback version of the new better edit summary messages on items through API (phab:T224010)
    • Fixing the issue of an invisible quality constrain violation indicator (phab:T227866)
    • Switching item terms to migration stage of writing to both wb_terms and the new store (phab:T225055)
    • Preparing to run migration of item terms (phab:T219123)
    • Allowing to access Wikibase entities from multiple (Wikibase) databases (phab:T214557)
    • Hiding non-supported languages in old termbox (phab:T227083)
    • Work on a new solution to move "Data item" link outside of sidebar toolbox avoiding the cache issues (phab:T66315)
    • Bridge: saving the Wikidata edit when submitting (phab:T226999)
    • Showing the current Wikidata value in the edit modal (phab:T226997)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


strengthen AF for mihanblog.com

Spammers are now more spreading this use to main ns pages, so it is time to strengthen our defences in that area.  — billinghurst sDrewth 01:47, 26 August 2019 (UTC)

Also further investigate spambot abuse of medium.com, main ns.  — billinghurst sDrewth 01:51, 26 August 2019 (UTC)

Similarly in other filters, look to do something about the removal of <languages/> as an indicator.  — billinghurst sDrewth 23:00, 4 September 2019 (UTC)

Community Insights Survey

Share your experience in this survey

Hi Billinghurst/2019,

The Wikimedia Foundation is asking for your feedback in a survey about your experience with Meta and Wikimedia. The purpose of this survey is to learn how well the Foundation is supporting your work on wiki and how we can change or improve things in the future. The opinions you share will directly affect the current and future work of the Wikimedia Foundation.

Please take 15 to 25 minutes to give your feedback through this survey. It is available in various languages.

This survey is hosted by a third-party and governed by this privacy statement (in English).

Find more information about this project. Email us if you have any questions, or if you don't want to receive future messages about taking this survey.

Sincerely,

RMaung (WMF) 14:34, 9 September 2019 (UTC)

Wikidata weekly summary #381

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming: Next Linked Data for Libraries LD4 Wikidata Affinity Group call: References in Wikidata, 10 September. Agenda
  • Tool of the week
    • moveClaim allows you to move or copy claims from one item to another. This is especially useful when splitting items, or creating lots of similar items.
  • Other Noteworthy Stuff
    • Seventh birthday of Wikidata: you can start thinking about organizing a meetup in your area to celebrate the birthday, or about a present for the community!
    • The first draft of the program of the WikidataCon is now available. The content of the three main session rooms will be live-streamed and recorded for people who cannot participate in the conference.
    • Because of a database switch, Wikidata will be in read-only more on September 10th at 05:00 UTC, for max. 30min (phab:T230762)
    • Recent tool: @Wikidatabot, a Telegram bot that allows you to search for something on Wikidata from Telegram
    • New game: Wikidata Mall, a Telegram management simulation game where content is generated from Wikidata
  • Development
    • Wikidata got a high-resolution logo, thanks to Odder (phab:T230120)
    • New monolingual code languages are added, thanks to Jon Harald Søby: TLI (Tlingit), clc (Tsilhqotʹin), alc (Kawésqar), kld (Gamilaraay), peo (Old Persian)
    • Fixed a bug in constraint violations indicator that was not showing up sometimes (phab:T227866)
    • Make Lua's function mw.wikibase.entityExists return true for redirects (phab:T192462)
    • Reviewed and followed up on highlighting statements when using "#P" in URL (phab:T178745)
    • Wikidata Bridge: saving the Wikidata edit when submitting (phab:T226999)
    • Showing the label for the Property instead of the id (phab:T227759)
    • Overcoming a conceptional oversight between mediawiki and standard language codes (phab:T231833)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Hola Billinghurst

Te puedo pedir un favor

De todas las acusaciones que me hacen por Cuatro Remos y sus compañeros de viaje, puedes hacer lo siguiente:


  • Acusación de Titere : Me hagan un Chech User de todos los titeres que me acusan.
  • Acusación de vándalo: Estudien todas mis conbtribuciones por favor en todos los idiomas.

Esperando tu colaboración como administardor general , un saludo afectuoso --Historiadormundo (talk) 15:49, 12 September 2019 (UTC)

No. I don't involve myself in cross-wiki battles, especially not in other languages where the nuances of language cannot be captured by Google translate. There are simply no winners from those interventions. Unfortunately it can be problematic with power differentials the blocking functions, and online anonymous disputes, however, continuing to battle and fight resolves nothing, and generally worsens the divide. My advice to all people on the losing side, is to find a different wiki, and find something interesting to do and that achieves something. Demonstrate a community aspect, and it rebuilds confidence in your abilities. I work on the Wikisources as I find that it is less battle-prone, and the people are generally supportive, and I get to read old books. Maybe you can edit at Spanish Wikisource and find stuff of value.  — billinghurst sDrewth 21:58, 12 September 2019 (UTC)


Hola billinghurst muchas gracias de todos modos:
Para mi no es una batalla, solo que sepa la verdad en mi actuar.
Que no tengo ningún titere y menos he sido vandalo
Gracias por la invitación para participar en tú proyecto tratare de hacerlo, un saludo afectuoso --Historiadormundo (talk) 18:13, 13 September 2019 (UTC)
@Historiadormundo: Thanks for your consideration. For me I like to bring into life old biographical compilations as they are for people who were notable in their time, though maybe they are forgotten about now. I can also migrate that information neatly into Wikidata. Whereas I know others who work on poetry, others the history, and some the religion. A lot less combative environment, though never completely so. While it is not for everyone, it still is really productive space to work.  — billinghurst sDrewth 23:20, 13 September 2019 (UTC)

I stole your comment!

Hi Billinghurst

This comment of yours is now on my userpage under the title "Words of wisdom". I liked it so much, and just wanted to let you know! Cheers.—Ah3kal (talk) 09:40, 13 September 2019 (UTC)

lived experience! If we can stop doing blame, and try to understand what and why, then we have a better chance of a better resolution. There is n English maxim of "putting yourself in someone else's shoes". If we just ignore the other person and their differences, who has their eyes shut?  — billinghurst sDrewth 09:45, 13 September 2019 (UTC)

Wikidata weekly summary #382

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Hauki lets you browse existing Lexemes, add Senses to them, and easily create new Lexemes for common languages and lexical categories.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Reminder: Community Insights Survey

Share your experience in this survey

Hi Billinghurst/2019,

A couple of weeks ago, we invited you to take the Community Insights Survey. It is the Wikimedia Foundation’s annual survey of our global communities. We want to learn how well we support your work on wiki. We are 10% towards our goal for participation. If you have not already taken the survey, you can help us reach our goal! Your voice matters to us.

Please take 15 to 25 minutes to give your feedback through this survey. It is available in various languages.

This survey is hosted by a third-party and governed by this privacy statement (in English).

Find more information about this project. Email us if you have any questions, or if you don't want to receive future messages about taking this survey.

Sincerely,

RMaung (WMF) 19:14, 20 September 2019 (UTC)

Answering your question

About this question. I'm a bot of ru:user:MBH. I automatically reverts edits that I find destructive, like ClueBot in enwiki. This my edit was reverting of edit that deletes some content from page due to bug, related to using Flagged Revisions and visual editor on the same site. Wiki with installed Flagged Revisions (improved patrolling) can "stabilize" article, so unregistered and new users view not last page version, but last patrolled/reviewed version. But if this user edits this article using visual editor, he make his edits in outdated version and save it, effectively reverting article back to several dozens of edits. My bot detected such edit and reverted it. Рейму Хакурей (talk) 09:11, 21 September 2019 (UTC)

@MBH: Thanks. I will just leave that all alone.  — billinghurst sDrewth 11:53, 21 September 2019 (UTC)

Template:Protected page text/cascade

Can you please full-protect this page as it's going to be used on MediaWiki:Cascadeprotected? Thanks! IPad365 (talk) 02:13, 23 September 2019 (UTC)

@IPad365: I don't think that the template needs to exist. Further, adding the template to a Mediawiki page in that manner is not a wise way to progress. So no.  — billinghurst sDrewth 02:16, 23 September 2019 (UTC)
Oh. I just wanted to simplify the code. IPad365 (talk) 02:17, 23 September 2019 (UTC)

Hey

Hi, you broke my signature. Please remember that my precious signatures should not be broken. Thanks. User:IPad365/siggy 03:41, 23 September 2019 (UTC)

Please don't use signature pages, especially those with broken code.  — billinghurst sDrewth 03:47, 23 September 2019 (UTC)
Okay. IPad365 (talk) 03:52, 23 September 2019 (UTC)
Or if you do, then always substitute the output, not leave it dynamic.  — billinghurst sDrewth 08:20, 23 September 2019 (UTC)

Wikidata weekly summary #383

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Namescript fills in labels, descriptions and aliases of items about names, making it easier to create such items (you only need to provide a few statements).
  • Development
    • Wikidata Bridge: add an edit tag parameter when saving (phab:T227003)
    • Adapt buttons' texts to UI language (phab:T228259)
    • More work on setting up the technical background to work on tainted references
    • More work on reducing the resources needed to load pages
    • Create a dependency graph of existing RessourceLoader modules (phab:T232728)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #384

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • This Recent changes tool allows to get a list of unpatrolled Wikidata changes with enhanced filters that are more adapted to Wikidata than the standard Recent Changes page. Available actions include mass patroling and easier revert interface.
  • Other Noteworthy Stuff
    • The state library of Berlin is using Wikidata to display a map of pictures from their architecture journals: Berlin um 1900 - eine fotografische Zeitreise
    • Edit summaries coming from the wbeditentity API (for example from the mobile termbox) will be improved from October 2nd (announcement, ticket)
    • You can nominate your favourite Wikidata and Wikibase projects for the WikidataCon Award until October 7th
  • Development
    • More work done on removing some resource loader modules in order to speed up the load of pages
    • Wikidata Bridge: add an edit tag parameter when saving (phab:T227003)
    • Adapt buttons' texts to UI language (phab:T228259)
    • research regarding permissions/protection (phab:T231209)
    • More preparation work for improving references

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Help

Hi. Any idea how to stop this from happening again? —MarcoAurelio (talk) 10:49, 2 October 2019 (UTC)

@MusikAnimal and Kaldari: we have some vandalism with combining diacriticals, the \u0300+ range. I have done an ugly catch at special:AbuseFilter/223 which I can show works for some, though there must be a better way. Can you please make suggestions. I tried rlike for \u0301 and others but that was a fail, and unicode is not my special skill. Thanks if you can help.  — billinghurst sDrewth 11:29, 2 October 2019 (UTC)

Reminder: Community Insights Survey

Share your experience in this survey

Hi Billinghurst/2019,

There are only a few weeks left to take the Community Insights Survey! We are 30% towards our goal for participation. If you have not already taken the survey, you can help us reach our goal! With this poll, the Wikimedia Foundation gathers feedback on how well we support your work on wiki. It only takes 15-25 minutes to complete, and it has a direct impact on the support we provide.

Please take 15 to 25 minutes to give your feedback through this survey. It is available in various languages.

This survey is hosted by a third-party and governed by this privacy statement (in English).

Find more information about this project. Email us if you have any questions, or if you don't want to receive future messages about taking this survey.

Sincerely,

RMaung (WMF) 17:04, 4 October 2019 (UTC)

Wikidata weekly summary #385

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • soweego links Wikidata to large third-party catalogs. Together with its friend Mix'n'match, it helps Wikidata to become the universal linking hub of open data.
  • Development
    • Continue work on removing and optimizing resource loader modules
    • Wikidata Bridge: obey wgEditSubmitButtonLabelPublish (phab:T228260)
    • Canceling the modal (phab:T231282)
    • Research regarding permissions/protection (phab:T231209)
    • Investigation to ensure editing with the same credentials (phab:T231887)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Rollback

Hi. There has been many IP vandalism on this wiki, and I want rollback rights. Thank you! IPad365 (talk) 04:42, 8 October 2019 (UTC)

You are not getting them from me at this point of time. I would say that you are a long way of getting them judging by your standard of editing.  — billinghurst sDrewth 07:46, 8 October 2019 (UTC)

Wikidata weekly summary #386

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • ShowTalkLabels: with this script enabled, when a talk page is shown on your watchlist or similar pages, the label of the related entity is shown.
  • Development
    • Abuse filter has been improved so saving an edit should be a bit faster now. (phab:T156095)
    • A new Lua function is providing the site's global ID of the wiki where this function is used (phab:T194023)
    • Wikidata Bridge: test data for the demo system (phab:T224834)
    • Research regarding permissions/protection (phab:T231209)
    • Investigate of the purging strategy (phab:T227758)
    • Restyling of mobile termbox (phab:T223452)
    • Adding "fewer languages" button at the end of the expanded list of "all entered languages" (phab:T232595)
    • More work on reducing the resource loader modules
    • More work on tainted references

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

szl.wikipedia.org

Thank you for help. :) Lajsikonik (talk) 07:39, 17 October 2019 (UTC)

URGENT: Please sign new Wikimedia confidentiality agreement for nonpublic information now

This is a reminder to acknowledge and sign the new Confidentiality agreement for nonpublic information. As you know, your volunteer role in Wikimedia projects gives you access to secure and sensitive information.

The new version includes one major change.

  • There is a change regarding the way personal data may be released. Accordingly, functionaries must notify the Wikimedia Foundation at check-disclosure(_AT_)wikimedia.org before releasing data, in order to obtain a written approval for doing so. The Foundation will respond within 10 days. However, for emergencies, such as cases involving threats of violence, functionaries may release the personal data without such explicit permission, but they should notify the Foundation immediately following the disclosure. If they choose not to disclose the data, the request for disclosure should be forwarded to the Foundation's emergency email address (emergency(_AT_)wikimedia.org).

There are also some wording changes that were made to more closely align the language with evolving industry norms, best practices and laws. The most notable of these has been the change of the term "nonpublic information" to "nonpublic personal data". None of these changes are intended to make fundamental changes to the scope or practice of the policy but we know they could appear as such, hence wanted to flag them.

The aforementioned changes require users that have already signed the previous version of the policy to sign the new version as well.

We therefore ask that you to sign the updated version. Signing the agreement is tracked on Phabricator's Legalpad. An online guide is available to help you with signing the agreement: Confidentiality agreement for nonpublic information/How to sign. If you wish you can sign it directly at https://phabricator.wikimedia.org/L37. The exact policy is located here: Access to nonpublic personal data policy. The text of the confidentiality agreement is located here: Confidentiality agreement for nonpublic information

If you have already received this message and signed the updated agreement, you need not sign it again. Once is sufficient. In this case, we ask that you respond to Samuel (WMF) letting him know when (date) and how (method/process of signing) you have signed it so that we can update our own records.

Note: please bear in mind that if you still haven’t signed the updated version of the Confidentiality Agreement by February 13, 2019 your rights will be removed.

Thank you for your understanding,

Samuel Guebo (User:Samuel (WMF)), Wikimedia Foundation

Posted by the MediaWiki message delivery - 15:15, 11 January 2019 (UTC)

This section was archived on a request by:  — billinghurst sDrewth 03:50, 24 January 2019 (UTC)

URGENT: Please sign new Wikimedia confidentiality agreement for nonpublic information now

This is a message from the Wikimedia Foundation.

This is a reminder to acknowledge and sign the new Confidentiality agreement for nonpublic information. As you know, your volunteer role in Wikimedia projects gives you access to secure and sensitive information.

The new version includes one major change.

  • There is a change regarding the way personal data may be released. Accordingly, functionaries must notify the Wikimedia Foundation at check-disclosure(_AT_)wikimedia.org before releasing data, in order to obtain a written approval for doing so. The Foundation will respond within 10 days. However, for emergencies, such as cases involving threats of violence, functionaries may release the personal data without such explicit permission, but they should notify the Foundation immediately following the disclosure. If they choose not to disclose the data, the request for disclosure should be forwarded to the Foundation's emergency email address (emergency(_AT_)wikimedia.org).

There are also some wording changes that were made to more closely align the language with evolving industry norms, best practices and laws. The most notable of these has been the change of the term "nonpublic information" to "nonpublic personal data". None of these changes are intended to make fundamental changes to the scope or practice of the policy but we know they could appear as such, hence wanted to flag them.

The aforementioned changes require users that have already signed the previous version of the policy to sign the new version as well.

We therefore ask that you to sign the updated version. Signing the agreement is tracked on Phabricator's Legalpad. An online guide is available to help you with signing the agreement: Confidentiality agreement for nonpublic information/How to sign. If you wish you can sign it directly at https://phabricator.wikimedia.org/L37. The exact policy is located here: Access to nonpublic personal data policy. The text of the confidentiality agreement is located here: Confidentiality agreement for nonpublic information

If you have already received this message and signed the updated agreement, you need not sign it again. Once is sufficient. In this case, we ask that you respond to Samuel (WMF) letting him know when (date) and how (method/process of signing) you have signed it so that we can update our own records.

Note: please bear in mind that if you still haven’t signed the updated version of the Confidentiality Agreement by February 13, 2019 your rights will be removed.

Thank you for your understanding,

Samuel Guebo (User:Samuel (WMF)), Wikimedia Foundation

Posted by the MediaWiki message delivery 16:49, 16 January 2019 (UTC)

This section was archived on a request by:  — billinghurst sDrewth 03:50, 24 January 2019 (UTC)

URGENT: Only 3 weeks left to sign the new Wikimedia confidentiality agreement for nonpublic information

This is a message from the Wikimedia Foundation.

This is a reminder to acknowledge and sign the new Confidentiality agreement for nonpublic information. As you know, your volunteer role in Wikimedia projects gives you access to secure and sensitive information.

The new version includes one major change.

  • There is a change regarding the way personal data may be released. Accordingly, functionaries must notify the Wikimedia Foundation at check-disclosure@wikimedia.org before releasing data, in order to obtain a written approval for doing so. The Foundation will respond within 10 days. However, for emergencies, such as cases involving threats of violence, functionaries may release the personal data without such explicit permission, but they should notify the Foundation immediately following the disclosure. If they choose not to disclose the data, the request for disclosure should be forwarded to the Foundation's emergency email address (emergency@wikimedia.org).

There are also some wording changes that were made to more closely align the language with evolving industry norms, best practices and laws. The most notable of these has been the change of the term "nonpublic information" to "nonpublic personal data". None of these changes are intended to make fundamental changes to the scope or practice of the policy but we know they could appear as such, hence wanted to flag them.

The aforementioned changes require users that have already signed the previous version of the policy to sign the new version as well.

We therefore ask that you to sign the updated version. Signing the agreement is tracked on Phabricator's Legalpad. An online guide is available to help you with signing the agreement: Confidentiality agreement for nonpublic information/How to sign. If you wish you can sign it directly at https://phabricator.wikimedia.org/L37. The exact policy is located here: Access to nonpublic personal data policy. The text of the confidentiality agreement is located here: Confidentiality agreement for nonpublic information

If you have already received this message and signed the updated agreement, you need not sign it again. Once is sufficient. In this case, we ask that you respond to Samuel (WMF) letting him know when (date) and how (method/process of signing) you have signed it so that we can update our own records.

Note: please bear in mind that if you still haven’t signed the updated version of the Confidentiality Agreement by February 13, 2019 your rights will be removed.

Thank you for your understanding,

Samuel Guebo (User:Samuel (WMF)), Wikimedia Foundation

Posted by the MediaWiki message delivery 17:05, 23 January 2019 (UTC)

This section was archived on a request by:  — billinghurst sDrewth 03:50, 24 January 2019 (UTC)

URGENT: 2 weeks left to sign the new Wikimedia confidentiality agreement for nonpublic information

This is a message from the Wikimedia Foundation.

This is a reminder to acknowledge and sign the new Confidentiality agreement for nonpublic information. As you know, your volunteer role in Wikimedia projects gives you access to secure and sensitive information.

The new version includes one major change.

  • There is a change regarding the way personal data may be released. Accordingly, functionaries must notify the Wikimedia Foundation at check-disclosure@wikimedia.org before releasing data, in order to obtain a written approval for doing so. The Foundation will respond within 10 days. However, for emergencies, such as cases involving threats of violence, functionaries may release the personal data without such explicit permission, but they should notify the Foundation immediately following the disclosure. If they choose not to disclose the data, the request for disclosure should be forwarded to the Foundation's emergency email address (emergency@wikimedia.org).

There are also some wording changes that were made to more closely align the language with evolving industry norms, best practices and laws. The most notable of these has been the change of the term "nonpublic information" to "nonpublic personal data". None of these changes are intended to make fundamental changes to the scope or practice of the policy but we know they could appear as such, hence wanted to flag them.

The aforementioned changes require users that have already signed the previous version of the policy to sign the new version as well.

We therefore ask that you to sign the updated version. Signing the agreement is tracked on Phabricator's Legalpad. An online guide is available to help you with signing the agreement: Confidentiality agreement for nonpublic information/How to sign. If you wish you can sign it directly at https://phabricator.wikimedia.org/L37. The exact policy is located here: Access to nonpublic personal data policy. The text of the confidentiality agreement is located here: Confidentiality agreement for nonpublic information

If you have already received this message and signed the updated agreement, you need not sign it again. Once is sufficient. In this case, we ask that you respond to Samuel (WMF) letting him know when (date) and how (method/process of signing) you have signed it so that we can update our own records.

Note: please bear in mind that if you still haven’t signed the updated version of the Confidentiality Agreement by February 13, 2019 your rights will be removed.

Thank you for your understanding,

Samuel Guebo (User:Samuel (WMF)), Wikimedia Foundation

Posted by the MediaWiki message delivery 17:49, 30 January 2019 (UTC)'

This section was archived on a request by:  — billinghurst sDrewth 23:18, 30 January 2019 (UTC)

The Affiliate-selected Board seats process welcomes your support

Hello. You are receiving this message because you are active in the field of translations <3 The movement needs you! The Nominations phase has started for the ongoing selection process of two Board members, and the timeline is quite tight.

A Translation Central is available to help translators figure out what's been covered and what's left to do. Over the course of the next few weeks, your attention on candidates' profiles is particularly welcome.

While there are four languages that are especially relevant for multiple affiliates (namely Arabic, French, Russian and Spanish), you can also add others. If you can't help: please see if you know anyone in your circle who could, and spread the word :) Thank you! Elitre (WMF) and Facilitators of ASBS 2019, 13:20, 18 April 2019 (UTC)

This section was archived on a request by:  — billinghurst sDrewth 04:32, 19 April 2019 (UTC)

Wikidata weekly summary #387

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • The Wikidata Wor(l)dmap is showing translations of the same concept on a world map. To use it, type a word (for example "water") in the search field, then observe the map. You can zoom in the map. The data comes from Wikidata item labels and the coordinate location property of the language.
  • Other Noteworthy Stuff
    • Wikidata won an Open Publishing Award (description).
    • Panandâ, a mobile app powered by Wikidata (and Wikimedia Commons), was selected as one of the five finalists in the App for Social Good category in the Android Masters 2019 competition organized by Google Developer Group Philippines. The final event will be held on November 16.
    • Issue with Wikidata Query Service: aggregate variables can no longer reuse the names of other variables (T235540).
    • You can translate labels in the background image of Wikidata front page by adding translation to this file
  • Development
    • Fixed the DuplicateReferences gadget that was broken due to refactoring work needed to make pages load faster and development easier (phab:T234094)
    • Wikidata Bridge: restricting the length of string value inputs (phab:T229241)
    • research delayed kicking in of Bridge (phab:T233305)
    • enable/disable save button depending on Bridge state (phab:T230342)
    • More work on reducing the resource loader modules
    • More work on tainted references

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #388 & Wikidata Birthday

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • MachtSinn is a game to easily add Senses to Lexemes, based on suggestions from Items labels. It helps improving the data about languages in Wikidata.
  • Development
    • Wikidata Bridge: Create progressive disabled version of save button (phab:T235055)
    • Save original revision data in store (phab:T235052)
    • Add interface for tracking/logging (phab:T236233)
    • Make app change button attributes depending on state of store (phab:T235056)
    • More work on reducing the resource loader modules
    • More work on tainted references

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Thanks

Hi, I've seen now that my problem was fixed, thank you very much! Sorry if I'm responding just now, but in the last few days I've had some connection problems.--L2212 (talk) 12:57, 31 October 2019 (UTC)

WMF communications re ASBS notes

At Meta:Requests_for_deletion/Archives/2019#Affiliate-selected_Board_seats, you mentioned a conversation with the WMF being relevant to the page's deletion. Could you clarify on that a bit? Did the conversation involve communication of some relevant and confidential information? Or just some arguments in favor of deletion, based on already-available information? I'd like to know for certain that this wasn't a case of the WMF unilaterally demanding deletion based on their own understanding, if possible. I'm very confused by the situation, as the notes themselves seemed to indicate that they would be made public, and that the participants (including nominator User:Ad Huikeshoven himself) seemed to support publishing the notes, so I'm quite confused by the reversal. Was this a result of WMF interference? --Yair rand (talk) 00:34, 1 November 2019 (UTC)

@Yair rand: Hi. The nomination was declined initially. A WMF person, who I have not identified, contacted me and asked that I reconsider the request, and it was agreed that I would delete conditional upon replacement text coming fro the group. If you check the archives of this page, you will see that I was again queried about this, at which point I prodded the WMF person about the condition, this being around the time of Wikimania, I was told that it was busy for all, that it would occur, and to please accept apologies and they would follow up. I believe that the notes issue sits with the group itself, not with WMF, though I am not on the inside, just what you see in the request, and two general email requests. Once I have finished this post, I will again prod that WMF person. In lieu of the page appearing in an updated form, I would contemplate undeleting the page (with suitable notice and without full undelete conversation) if a request appeared on the appropriate page. People shouldn't make idle promises or try and game the system with passive aggressive.  — billinghurst sDrewth 09:38, 4 November 2019 (UTC)

Wikidata weekly summary #389

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • SPARQL RC is showing the recent changes on items that are listed from a specific query. It is very useful to monitor the changes on a specific subset of data, for example data that you recently imported in Wikidata.
  • Development
    • Made the Lua functions mw.wikibase.getBestStatements and mw.wikibase.getAllStatements faster if called more than once for the same statement on a single page
    • Fix a bug on the mobile termbox (phab:T236677)
    • Update Wikibase Lua documentation (phab:T225497)
    • Highlight individual statements when selecting them in the URL (phab:T234079)
    • Add monolingual language code "sa-Sidd", "pi-Sidd", tnq (Taíno), car (Kalinago) and bdr (phab:T230881, phab:T220284, phab:T234330)
    • Make it possible to collapse the "All entered languages" section when at the end of the section (phab:T232595)
    • Cache php.getEntityStatements in mw.wikibase (phab:T236491)
    • Tracking Wikidata Bridge openings by Datatype in Grafana (phab:T231204)
    • Not showing Bridge edit pens when the editor cannot edit the article (phab:T235152)
    • A bugfix to only show scrollbars where they are supposed to be shown (phab:T235622)
    • Enabling/Disabling the Save button depending on the bridge state (phab:T230342)
    • More work on tainted references

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Forenotice

On wikisource admin noticeboard two vandals will be reported please do not interfere.

Whatever I do at English Wikisource will be inline with established protocols and within scope. If there is abuse, it will be managed appropriately; if it is in scope, it will be left.  — billinghurst sDrewth 12:08, 10 November 2019 (UTC)
judging by your history of reverts nothing is ever with scope, especially with new users as wikimedia has policy to treat them worse than crap...

Wikidata weekly summary #390

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Speedpatrolling is a tool to easily patrol Wikidata recent changes, typically on mobile devices.
  • Development
    • In order to decrease the size of what we store in caches we stopped storing the actual EntityUsage objects in ParserOutput and now just store minimal identifier strings (phabricator:T236749)
    • Investigated why Termbox broke on an update (phabricator:T235261)
    • Removed auto jump of focus from Property field to value field (phabricator:T234322 - thanks to Envlh for the patch)
    • Removed non-functional site link groups for other Wikibase installations that don't need them (phabricator:T232248)
    • Continued working on the migration of the wb_terms table to address scalability issues
    • Continued working on the shortened version of edit summaries for edits made through the mobile termbox (phabricator:T224013)
    • For the Wikidata Bridge we are not showing edit pens when the user can not edit the article anymore (phabricator:T235152)
    • Working on viewing existing references in the Wikidata Bridge (phabricator:T233397)
    • Worked on showing an information popup when clicking the tainted reference icon to tell you what went wrong and how to solve it.
    • Worked on defining first version of Federation for wikis outside Wikimedia
    • Commons search have stopped indexing statements (structured data) since 30 October 2019 (phabricator:T237849)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Your message on bnwikipedia

Hi, I've seen your message on Bangla Wikipedia about a page with problematic sources. This was actually a copyvio and I deleted the page. Thanks for noticing. — T. 10:25, 15 November 2019 (UTC)

Konkani Wikipedia filter request

Hello Billinghurst, we had interacted earlier on the Stewards' noticeboard. Since then, I have studied the instances of spam, but since I'm not well-versed with writing abuse filters, please could you help by writing a local filter with the following conditions? If you could get us started, I'll try to maintain the filter myself later on.

  • Filter group: Flow
  • user_age==0 (Unregistered editors)
  • board_namespace==3 (User talk pages)
  • It should check that at least 40% of the text should be Cyrillic characters

It appears that we are dealing with real people and not bots, therefore, warnings will not be sufficient.

I have also noticed that at least a couple of the IP addresses have been reported as forum spammers, so perhaps later on, if necessary, we can create a separate filter using sfs_blocked that checks whether the IP address is blocked using the stopforumspam.com list and more stringent criteria regarding the contents.

I have created a comprehensive list of the Russian spam instances.

Thanks for your help, The Discoverer (talk) 05:02, 18 November 2019 (UTC)

Wikidata weekly summary #391

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming: Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Recap of WikidataCon and WikiConference North America, 19 November. Agenda
  • Tool of the week
    • The Mix'n'Match gadget displays on an item all unconfirmed matches on Mix'n'match, allowing to quickly add them.
  • Development
    • Tainted references: Show warning icon if statement value is changed but reference is not changed in the same edit (phab:T231728)
    • Make WikibaseQualityConstraints link using SpecialMyLanguage (phab:T233003)
    • Work on the issue of property labels not showing up on some pages (phab:T237984)
    • Track Bridge openings by property datatype (phab:T231204)
    • Viewing existing references in the Bridge (phab:T233397)
    • Attaching the link listener sooner, so the user gets a bit less often wrongly forwarded to wikidata (phab:T235765)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikiquote: I created page for WikiLMubber because it is a suspicious sockpuppet of WikiLumber; why did you say that that page is a candidate for speedy deletion because LTA?

I created page for WikiLMubber because it is a suspicious sockpuppet of WikiLumber; why did you say that that page is a candidate for speedy deletion? I am sorry if I disobeyed Wikiquote policy. Josephine W. (talk) 11:36, 20 November 2019 (UTC)

@Josephine W.: Sure it is a known sock for the LTA, known by that name and tens of others (maybe hundreds of others). Account is locked, why would we want to have a monument?  — billinghurst sDrewth 11:39, 20 November 2019 (UTC)

Об администраторах Википедии tg.wikipedia.org

Уважаемый User talk:Billinghurst. Обращаюсь к Вам по поводу бездействия некоторых администраторов таджикской википедии adminstats/tg.wikipedia.org. Администраторы Darafsh, Omid_Jeyhani, Ibrahim не проявляют желания выполнять обязанности администраторов.

* Поставить вопрос о голосовании в сообществе я не могу. Причина отсутствие активных участников в Википедии tg.wikipedia.org. Active users list
* Просьба к Вам рассмотреть обсуждаемую проблему.

--Шухрат Саъдиев (talk) 06:17, 22 November 2019 (UTC)

@Шухрат Саъдиев: I think that the appropriate to raise this issue is with the stewards at Stewards' noticeboard as they have some authority to act and guide, and they manage the process around inactivity. I am just a person with an opinion though no authority, and my opinion can be had at that page.  — billinghurst sDrewth 06:26, 22 November 2019 (UTC)
thanks for the answer --Шухрат Саъдиев (talk) 07:05, 22 November 2019 (UTC)

Wikidata weekly summary #392

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
  • Cradle enables editors to create a new item by completing a form. You can create a new form on the Cradle help page. Cradle forms can be used as templates to ensure that similar new items are structured the same way. This can be especially helpful for specific WikiProjects or datathons, and is a great timesaver if you are creating many similar items by hand.
  • Other Noteworthy Stuff
    • 570k VIAF identifiers have been added to Wikidata items in an effort of synchronisation between the two databases, thanks to Bargioni. In order to report errors in VIAF an apposite page has been created. More information here.
    • Query Service lag now affects maxlag. You may need to retry/reset error multiple times when you run QuickStatement or OpenRefine in busy hours.
    • Wikidata now documented more than six million people, more than the number of articles in English Wikipedia
    • New documentation page: Wikidata:Map data
  • Development
    • Add Wikidata query service lag to Wikidata maxlag (phab:T221774)
    • More work on tainted references and getting the feature ready to be tested
    • Fix a bug with Wikibase test builds (phab:T238575)
    • More work on improving the edit summaries (phab:T224013)
    • Bridge: Viewing existing references (phab:T233397)
    • Preserving native behavior on key+click (phab:T234060)
    • Speeding up initialization, by attaching link listeners sooner (phab:T235765) and reducing the size of the init module (phab:T235771)
    • Recording metrics for bridge opening performance (phab:T237368)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Request for arz.wikipedia

How can we add the https://www.mediawiki.org/wiki/Extension:NewUserMessage to arz.wikipedia.org to auto welcome new registered users — The preceding unsigned comment was added by HitomiAkane (talk)

@HitomiAkane: To have an extension added to a wiki, the community would need to reach a consensus that it is a desired extension, then lodge a site request on phabricator:. Any extension to be added would need to pass WMF security team's review, and that often is noted on the extension if it has been reviewed previously.  — billinghurst sDrewth 10:53, 28 November 2019 (UTC)
Thank you HitomiAkane (talk) 10:56, 28 November 2019 (UTC)

Just FYI

c:Commons:Administrators'_noticeboard#FYI regards, --Achim (talk) 17:05, 30 November 2019 (UTC)

Thanks. Done  — billinghurst sDrewth 01:44, 1 December 2019 (UTC)

Filter req

Hi, After looking on all of the range contribs on hiwiki it looks like /32 catches them. So when you create a filter including /32 would be best. ‐‐1997kB (talk) 01:27, 18 November 2019 (UTC)

Update: They are also doing the same over simple wiki. Also recently they started to add some mobile numbers into articles. This is the same guy Bidhan Singh (AF/46) we talked about. ‐‐1997kB (talk) 04:56, 3 December 2019 (UTC)

Wikidata weekly summary #393

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming: Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Gadgets, 3 December. Agenda
  • Tool of the week
    • Alt Labels displays item labels in other languages when there is no label in your default language. You may click a label to add it as the label for your language. This tool is very helpful for labels for people, books, articles, or films that do not need their labels to be translated.
  • Development
    • Fix security issues impacting the Query Service GUI (more details)
    • Work on a a new Parser function (commaSeparatedList) (phab:T224013)
    • Implement Shortened version for edit summary (phab:T224013)
    • Add user agent to Wikidata Query UI code examples (phab:T226709)
    • Add label and description collision detectors for new terms store (phab:T232040)
    • Wikidata Bridge: showing a loading bar during initialization (phab:T232468)
    • Showing an error dialog if users can’t edit on Wikidata (phab:T235154)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #394

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • overpass: Embeds a map displaying features tagged with the current item in OpenStreetMap. Powered by overpass turbo. It helps check if the Wikidata object is mapped in OSM and also if it's correct.
  • Other Noteworthy Stuff
  • Development
    • Implement Shortened version for edit summary (phab:T224013)
    • Add monolingual language code WLS (Wallisian) (phab:T239411)
    • DumpRDF for MediaInfo entities loads each page individually (phab:T222497)
    • Add user agent to Wikidata Query UI code examples (phab:T226709)
    • Wikidata Bridge: Showing a loading bar during initialization (phab:T232468)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Weekly Summary #395

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Recoin displays information about the relative completeness of a Wikidata item by comparing its statements with those found on other similar items. Especially useful for editors working in a knowledge area that is new to them.
  • Development
    • Work on deploying the first version of tainted references on test Wikidata
    • Bridge: show an error dialog if users can’t edit on the repo wiki (phab:T235154)
    • Set up a shared Vue component library for Wikibase (phab:T240329)
    • More work on the new term store
    • Add Wikidata support for mnwwiki" (phab:T235745)
    • New languages for monolingual strings: mfa, ckt, abq-Latn, dag
    • Help identifying an issue with QuickStatements when one user is blocked on Wikidata (phab:T240316)
    • Hide non-supported languages in the termbox (phab:T227083)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Filtre global 181

Bonsoir. Il me semble que certains filtrages récents (pas tous) sur la page de discussion wp-FR de Lomita ne sont pas justifiés. Upunumu 44 : OK, mais Jean-Michel Gigault, Horacedx, Normandie Equitable et 109.23.11.73 : non. Hégésippe | ±Θ± 19:13, 16 December 2019 (UTC)

Hi @Hégésippe Cormier:. Thanks for the ping. It is a filter to protect some people who are targeting Lomita cross wiki, and the filter had excluded Lomita's frWP user talk page at frWP. However, as the whole page was moved to an archive, the means to exclude moved with the archived page. I have updated that aspect which will temporarily hold, and I will look at other means imminently to exclude that page.  — billinghurst sDrewth 20:43, 16 December 2019 (UTC)
I have made a permanent change though the impact is that it will flow through to all French language wikis, so it will be less effective. There is no language- or sister- specific parameters unfortunately. I will email Lomita to communicate the change.  — billinghurst sDrewth 21:30, 16 December 2019 (UTC)

Xwiki reports from COI?

And apologies if I've bugged you with this before - only intermittently active. The Xwiki reports from the COI bot seem slower than I recall? A couple of mine are due and one at least looks like it should be on the BL but I was waiting for the report. Sorry to bug you and seasonal wishes of course - trust life is acceptable :-) Cheers --Herby talk thyme 11:22, 28 December 2019 (UTC)

Appreciated - will look at where I went wrong! --Herby talk thyme 11:48, 28 December 2019 (UTC)

Wikidata weekly summary #396

Here's your quick overview of what has been happening around Wikidata over the last 2 weeks.
  • Tool of the week
    • The revised version of the very powerful PetScan offers to edit or create items based on Wikipedia categories, search, SPARQL, links with filters by label or properties
  • Development
    • Worked on better error dialogues for the Wikidata Bridge
    • Investigated and fixed labels for some Properties not being shown (phabricator:T237984)
    • Continued working on the new database tables that replace wb_terms
    • Expanded documentation for 3rd party Wikibase installs
    • Continued working on making sure components in different areas of Wikibase can easily be shared to make development easier (phabricator:T240329)
    • Enjoying the holidays. Hope so are you :)
Retrieved from "https://meta.wikimedia.org/w/index.php?title=User_talk:Billinghurst/2019&oldid=25861351"