Just checking in to say this is certainly still happening today, i can't really get through 1 min of editing on my bot before the session gets lost.

Hi @Harej !
Could you please share the input you provide on the form?
Thanks!

taken from https://grafana.wikimedia.org/d/000000290/wikidata-query-service-ui?orgId=1

Asked @Lydia_Pintscher about the data on usage of this feature:

I now get this error:

[6aab8836cf02dc6764ce8a29] 2024-11-14 19:19:54: Fatal exception of type "Lcobucci\JWT\Signer\Key\FileCouldNotBeRead"

Change #956446 had a related patch set uploaded (by DCausse; author: DCausse):

[wikidata/query/rdf@master] Remove BC support for old whitelist config option

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

Wikibases are now in a shared index and there is no overhead.

ES still happy enough; let's decline

We quickly looked at this today and didn't see a stand out reason why didn't also get deleted from the queryservice but we can confirm (for example) that L3 is still there.

Another is using the following regex to replace "regex1" to avoid the _need_ to use EXTRA in schemas used for form generation:
<([^/<>]+)>(?:\s+EXTRA\s+.*?)?\s*\w*\s*\{(.+?)

One idea floated is to remove "wd" from this line so that any prefix ending t: may be used in a schema to identify a direct property reference, not just wdt:. This would reduce the need for a "Cradle-compatible" schema (vs. original prefixes which plays into e.g. T335448 for custom prefixes (e.g. sdct: for Structured Data on Commons).

@Charlie_WMDE QuestyCaptcha is only effective if users configure their own questions. Spam bots easily solve the default questions we provided.

@Anton.Kokh the 320px are the reccomended min width by Codex and even before Codex that has been the smallest size we made sure to support because of accessibility reasons. You can read more about this WCAG requirement here.

hey @Anton.Kokh the proposed solution looks good to me 👍

We have a separate ticket for results coming from Wikidata: T317109
What are the other problems that this ticket is supposed to solve? In Github I see a mention of namespaces configured like on Wikidata, while Cloud uses different namespace IDs.
Anything else?

Hey @Anton.Kokh , do I understand correctly that Questy Captcha is adding no additional protection unlike we intended? If that is the case I think we should have a look to see whether we can improve QuestyCaptcha in any way so that it does its job properly or consider deactivating it in lieu of a more effective alternative.

Hey @Anton.Kokh ! it doesn't overlap but to make it more clear i will change the title of this ticket to be more precise!

https://github.com/wbstack/ui/pull/923

Patches related to this backporting effort can be found with the rest-api-1.43-backports topic