After a discussion with Lydia, we decided to drop the ticket :) We don't change the link.

The reason from our side is: Help:Sources is very broad (it's a general documentation page about references) and is not providing any information about tainted references (because the feature is not an official feature on Wikidata yet - later we should probably add something in the doc).
So people looking for help or info about the tainted reference notification will find no help on this page. That's why we want to link to Wikidata:Mismatched reference notification input where they will find a presentation of the feature.

I'd not close this task until we're absolutely sure that the issue got fixed.
As far as I understand, the issue exists for a long time, and I don't see any piece of code that was deployed to solve it. What makes you think that the problem is solved?

Yes, the fact that the language doesn't appear in the list is a known bug and we have a ticket for that.

@Bugreporter That seems unlikely. QuickStatementsBot is blocked since October 28th, and daily users of the tool only started reporting this issue yesterday.

So basically the API is sending wrong information? Weird. @Ladsgroup could you have a quick look and see if you can reproduce?

Thanks all for your feedback. Can you somehow check, in your QS interface, if the edits are about to be made with your individual account or the QuickStatementsBot account? Eg if the OAuth authentication worked or not?

Update of the timeline was done, update with the link to test system will come this week.
Please note that the announcement will take place on this discussion page: I won't post it on Wikipedias. I find it both more efficient and engaging that news on Wikipedias are posted by community members who follow the topic (eg Jeblad for nowp). I'll kindly ask you to share the info (in your language) on your Wikipedia.

Announcement made on the example queries talk page, on project chat, and with a different and more 3rd-parties-oriented version on wikidata-tech ML and Wikibase ML.

In our case, we need to indicate two different things:

1. the fact that the data that people are about to edit is stored in Wikidata, which means
   1. it's centralized in one place
   2. it's reused by plenty of other wikis
   3. changing this piece of information will change it in all the other wikis
2. the fact that the data is in CC0
   1. unlike the rest of the content of Wikipedia that is in CC BY-SA 4.0.
   2. by editing data, the user accepts to place their contribution under CC0

For information & inspiration, here's how it is at the moment on Commons:

Announcement done here, indicating a deployment this week, no veto so far, for me everything is good to go!

@Moebeus Can you add a link to the item when you add a screenshot? Thanks :)
Did you try Ctrl+Maj+R for purging?

@Lydia_Pintscher @Gehel Could you look at this? Which team could help?

In T221774#5694863, @Pintoch wrote:

I will try to implement a responsible throttling strategy in OpenRefine, hoping that others will do the same.

OK cool, thanks for the answer, I think it's fine.

Oh, then my edit fixed both. It's still happening in https://www.wikidata.org/wiki/Q62286808 for height and width

The issue is still happening on https://www.wikidata.org/wiki/Q62286812 . Purging doesn't fix it. When making an edit to the statement, the labels are back. Can we do some kind of reload so people don't have to edit all the statements?

@Lydia_Pintscher Can we raise the priority of this ticket, as it's blocking some editing workflows?

Thanks for creating the ticket 👍

@PKM Can you add the links of a few pages where this happens?

I guess @johl and @elal can answer better than me :)

I'll make an announcement for this, to make sure that people currently working with the autojump understand why we did this.
When will it be deployed live?

Yep, just let me 1-2 days to ping people in case there are some left cases, and then you can close :)

@Tpt Thanks a lot for answering :) @ChristianKl mentions "It's still down. To reproduce: If you have the gadget activated and click on Random Primary Sources item on the left side you get shown an error." Could you have a quick look?

This issue is still happening these days on P195, eg https://www.wikidata.org/wiki/Q12418#P195

I'm pretty sure there is another ticket for this but I couldn't find it, feel free to merge if you have a clue.

Announcement done on the mailing-lists noted above and the Wikibase Telegram group.

This issue was mentioned again here, with the case that the correct image doesn't show up at all in the suggester's list. Could we look at it again?

Hey @Gehel, could you look at this? :)

Thanks for your comment. Please be reassured that as soon as we have updates, we will share them on the Mediawiki page. As an example, an update of the prototype should come this week.

Is everyone fine to change the datatype of P7007 (Wolfram Language unit code) to external ID as well? (discussion)

FYI, a new "AOL spam attack" started yesterday on the wikidata mailing-list. I tried to counter it by changing the subscribe_policy parameter to "confirm", but that didn't have an impact, hundred of new fake addresses still subscribing.

@Ladsgroup What is needed from our side to fix the problem?

Hello all,
We are working on fixing this issue. Thanks for your patience.

@Effeietsanders Yep, that was a similar pattern for me: a name that seems "normal" followed by a 5 digits number. I got several thousands suddenly subscribing to the Wikidata ML in May-June this year and all of them automatically removed by Mailman a few weeks later. I don't think I reported in on Phab, my bad :)

I'm wondering if this is somehow related to the massive spam attack we had a few months ago on some mailing-lists (hundred of fake AOL email addresses subscribed to the Wikidata mailing-list, and were bounced out a few weeks later)

Thanks, now I see the same issue.

@Tfrancart Can you add a screenshot about how it looks like for you? I just checked and everything is fine for me, the list is correctly displayed, starting with cats.

The fallback version will be deployed on October 2nd. Announcement is done on Project Chat and mailing-lists.

Comment and more testing added here

Thanks to everyone working on fixing this :) I'm actually not sure if I should give a lot of details in an announcement, we don't want to give people ideas to dig further into security breaches, right?

FYI @Gehel

Happened again this week :)

We're going to move forward with this. Next steps:

• update and improve task description
• get details about how we can enable arbitrary access without coupling it with enabling sitelinks

@Ayack As far as I understand, Graphoid currently doesn't have a maintainer (see T211881). If no one is willing to take over, I think the option of marking it as obsolete and stop using it should be considered.

Hey @Lucas_Werkmeister_WMDE, I tried to reorganize the task desc a bit with our usual template. Would you have a look, add what's missing or clean up things? Then we can move it to ready to estimate :) Thanks!

Hello everyone,

@Lydia_Pintscher Can we consider removing the automatic jump to next field and let the users decide when they are finished with filling out a field?

@Lydia_Pintscher @WMDE-leszek Could we have a look at this, and see if it is something we can pick up?

Hello @RolandUnger, this task is present in our (quite huge) to-do list and we didn't forget about it. However, it is currently blocked on solving a bug (T192462). This task should be picked up soon. Thanks for your patience.

FYI, 0-edits are not required, purging the cache by adding "?action=purge" at the end of the page URL works as well to make the new link appear.

Hello, and thanks for reporting this issue. As Roland mentioned, editing the page to purge the cache may be necessary. I now see the link appearing on https://de.wikisource.org/wiki/J%C3%B6ns_Jakob_Berzelius . Do you have another example where the issue happens?

@RolandUnger Can you give me an example of a page where the old link is gone and the new link didn't appear yet?

FYI T66315#5430357 " the "t-wikibase" id is not only used in style sheets but in JavaScript scripts, too. Maybe the new wb-otherproject-wikibase-item class has to be added to other style sheets"

@RolandUnger Thanks for you feedback. We are going to look at this as soon as possible.
The change was announced in last week's TechNews, but you're right, we should have announced it on every wikis.

I guess admins (or interface admins only?) can access to the menu bar content and add this "random Lexeme" link :)

Hey! Do anyone of you would like to present the work you accomplished on translating documentation during the hackathon showcase? It would be awesome to have it represented there (and show that a hackathon is not only about programming ;) )
The list of slots is here: https://etherpad.wikimedia.org/p/Wikimania_hackathon_showcase_2019
The showcase will take place on Sunday from 14:30 to 15:30.