The file has a local description page. Normally the uploader will be shown if a file has the right templates.

Got my first error 45 minutes ago, has been going on since.

Is this still needed? I think most tests were handled pretty okay with http://elastic-wikidata.wmflabs.org/wb.html.

What about symmetric qualifiers like https://www.wikidata.org/wiki/Property:P1706?

I've used http://wikidata.wikiscan.org during the dispatch issues.

In T174345#3559262, @Urbanecm wrote:

I think that discussion about "should this be enabled" should be off-wiki (and preferably before opening the ticket at phab).

What error will be shown when for example a user connects a Wikipedia page to one in another language via the client widget? I bet most of those don't have enough edits to be autoconfirmed on Wikidata.

In T173753#3555948, @Bugreporter wrote:

Duplicate with T167864: Enable support for the creation of new items?

In T170927#3553623, @Andrew wrote:

Blocked by https://phabricator.wikimedia.org/T174182

You could use for example https://www.wikidata.org/wiki/Special:Nearby#/page/Q685779.

That's not working for me on other items. The affected properties are also not able to be searched.

Side-effect of T171460, I think something with the cache.

The dispatch decreased a lot since yesterday, but is increasing again since botimport for cebwiki and svwiki started again. I hope the above patch helps with keeping the dispatch steady.

In T170775#3494740, @Smalyshev wrote:

The switch to ElasticSearch will fix this.

If there are proper names/aliases, of course. Accent folding and such should probably take care of most Latin diacritics, but won't do transliterations and such.

You are welcome to test on http://elastic-wikidata.wmflabs.org/wb.html if it works better with ES and complain if it doesn't :)

To be clear: this is not related to the property/entity suggester. The switch to ElasticSearch will fix this.

But the pill does look like the input field could handle multiple values. This would be interesting for values(!),but confusing for properties.

This seems resolved now, impact not that big.

I stil get tabbed to "add qualifier", seems related to T102607 then.

In T112075#3485122, @Jan_Dittrich wrote:

Gut feeling: I like two fields better because it makes it a bit clearer that you are selecting an existing item for the unit and can't just type anything.

I'd agree with this "semantics" approach.

(like the drop downs not being removed when you go to the widget or not being able to save pressing enter in the widget)

@Sjoerddebruin, @Agabi10 : Thanks for sharing! Do you know if there is an issue for these problems?

User has just been blocked on Wikidata. https://www.wikidata.org/w/index.php?diff=528859918&oldid=528787115&rcid=561908372

In T112075#3484323, @Agabi10 wrote:

@Sjoerddebruin, you can go to the input of the widget using the tab. There are many things that aren't nice with this (like the drop downs not being removed when you go to the widget or not being able to save pressing enter in the widget) but I usually do it only with the keyboard and there are no major problems other than a few usability improvements that I noticed.

At least make the interface better for keyboard users. I don't think you can easily add one statement with only keyboard that has a widget?

Still interesting spikes happening. The stalest wiki is wikidatawiki for some reason, is that normal?

I'm keeping track of my experiences on https://www.wikidata.org/wiki/User:Sjoerddebruin/Cirrus now, it seems that not all exact matches are always showed.

In T125500#3468439, @Smalyshev wrote:

I've made a page for search comparison: http://elastic-wikidata.wmflabs.org/wb.html
(despite it being hosted on elastic-wikidata, the data comes from www.wikidata.org).

Note that descriptions for Elastic search are now broken, due to T162292, as soon as that is done descriptions should be fine.

More good progress in the last 24 hour. Will notify the community when things are really down, then we need to keep watching if the dispatch increases too fast again. Editing speed of users is visible here.

Just some little advice: next time, mention the skin you are using.

Mentioned in project chat: https://www.wikidata.org/wiki/Wikidata:Project_chat#Move_gadget_is_not_working

That's not to a random user to decide.

We indeed lowered the amount of edits to at least try to make the process go faster. Let's hope this is a wakeup call for all of us.

The lag might be related to the dispatch in the last few days.

Yeah, and there are still some missing. Maybe we can improve the "blacklist" if we fix this bug first.

Probably for every property that gets removed from the suggestions file, see P5495.

In T168434#3430460, @Esc3300 wrote:

That makes sense for additional suggestions, but it still doesn't explain why P31/P279 aren't offered at all.

Try adding a statement to any item on these reports: https://www.wikidata.org/wiki/Category:P641_only_reports

In T168434#3430396, @Esc3300 wrote:

Is the below related ?

It seems that P31/P279 gets suggested on items that only have coordinates (P625), but not on items that only have P641 (sport). I'd expect it to appear on any item that lacks it.

Talk page is using #property, intended behavior.

The hack is still in place on frwikivoyage, making the work of stewards harder.

Error in template (old interwiki outside noinclude), also moved the template interwiki link to the correct Wikidata item.

Note that OTRS volunteers already receive messages of people who can't even read the current captcha.

I'm mostly not even noticing the image, because my view is just too small to show the sitelinks on the right (I'm mostly working with two windows, one at each half of my screen). How wide will they be then?

I've locked 200 spambots myself today. What's the best way to achieve consensus for this? RfC linked in tech news?

Seems like some media attention helped.

One of the first news articles, says that the Apple in the Netherlands is aware of the issue now.

It is very similar yet. The "story" is now spreading fast (for example on a popular Dutch sharing website), there might be some media attention coming up.

In T136148#3388106, @Cyberpower678 wrote:

I can't find any.

In T168434#3367629, @thiemowmde wrote:

I think we can consider this a bugfix. Why do you think it needs announcement in advance?

I would love to help testing this. :)

Oh yes, sorry. I mean that indeed.

Are you actually deciding on making all titles uppercase? I still think that is a ugly design choice.

In T166426#3338276, @Halfak wrote:

Seems fair. I have no idea why I created this task. It must have been when I was sitting down with @Sjoerddebruin. Maybe he knows what I was thinking! :S

"Item by title" is now removed from the sidebar.