[02:37:10] Natural language [02:37:11] * Wikimedia language tag [02:37:13] * + BCP 47 language tag [02:37:14] * + BCP 47 language subtag [02:37:16] * + BCP 47 script subtag [02:37:17] * + whether BCP 47 script subtag is explicit or implicit [02:37:19] * + writing mode horizontal/vertical-lr/rl [02:37:20] * + Wikidata item (re @Feeglgeef: The problem with adding a new key is that you need to manually adjust every use of the type. This is why the type approval proce...) [11:31:20] I know it has been over a year, but I think the Abstract Wikipedia use cases make the requirement clearer. If we are constructing content from multiple statements, we need a way to refer to a particular statement as an object in its own right—whether for sourcing, reuse, or expressing that it is structurally related to some other referenced statement. [11:31:20] Subject/property/value com [11:31:20] parison is not sufficient for that purpose, particularly when the value is itself a complex object, rather than being a simple reference. [11:31:22] I don’t know what happens when a statement is updated in Wikidata, but we will need to know precisely which statement was modified or replaced in order to assess the editorial implications of that update in the articles that referenced the previous version. (re @David: If there are other use cases, let's consider whether they outweigh the concerns expressed above. If so, [11:31:22] it wo [11:31:23] uld still be possi...) [12:30:05] No, we haven't prioritized that work, as it seems that new type proposals don't have the volume that would make that necessary yet. I agree that it should happen, but so far other things have been more important. (re @Feeglgeef: Has any progress been made on allowing the community to control the type creation process? I do not believe giving all functione...) [15:17:03] *Abstract Wikipedia Newsletter 243* [15:17:04] * Community proposals for capturing meaning [15:17:05] * Hiccups in Abstract Wikipedia and embedded function calls [15:17:07] * Recent Changes in the software [15:17:08] * News in Types: Complex numbers [15:17:10] * Wikifunctions presentation at WikiCon Australia on 11 April [15:17:11] * Volunteer’s Corner upcoming on 13 April 2026 [15:17:13] * Fresh Functions weekly: 68 new Functions [15:17:14] https://www.wikifunctions.org/wiki/Wikifunctions:Status_updates/2026-04-10 [15:38:05] Hi all! Our next *Volunteers' Corner* will be held on Monday, April 13, at 17:30 UTC. (https://zonestamp.toolforge.org/1776101400) [15:38:05] If you have questions or ideas to discuss, or you want to get in touch with the dev team, please join us! The link to the meeting is https://meet.google.com/xuy-njxh-rkw [15:38:07] Hope to see you there! [15:38:09] (re @Sannita: Hi all! Our next Volunteers' Corner will be held on Monday, April 13, at 17:30 UTC. [15:38:10] If you have questions or ideas to discuss, ...) [17:25:28] As pointed out on-wiki, the "tool" created to edit abstract articles is mass-vandalizing. This is, of course, unsurprising, given what technologies were used to create it. [17:30:00] Here are just some of the vandalized articles : https://tools-static.wmflabs.org/bridgebot/d805f3f6/file_79315.jpg [19:31:37] I’ve only looked at a few examples but I see no evidence of vandalism. It is, of course, disappointing to see many content pages being broken by a repeated error but I believe that most pages can be fixed by the contributor. (re @Feeglgeef: As pointed out on-wiki, the "tool" created to edit abstract articles is mass-vandalizing. This is, of course, unsurprising, give...) [20:24:16] Some of the hardcoded implementations may obviously need an extra line too. (re @Al: In principle, it’s very simple indeed; you are just adding an element to the list in the persistent function call. I think that’...) [20:55:59] I find it a bit weird that the latest status update ( https://www.wikifunctions.org/wiki/Wikifunctions:Status_updates/2026-04-10 ) says that failure to show the output of a function in an embedded page is a "current hiccup". This has been happening for a very long time. [20:56:36] I mentioned it here last January, but it started happening much earlier. (re @amire80: There are a few more. All of them show me "⏳ Funkcija se poziva..." ("⏳ Function is being called…")) [21:13:08] Previously it was unpredictable and slow. But now every embedding always fails, even the simplest. (re @amire80: I find it a bit weird that the latest status update ( https://www.wikifunctions.org/wiki/Wikifunctions:Status_updates/2026-04-10...) [22:33:39] @vrandecic your "tip" in the 3-26 status update would cause rendered content to confuse screen readers. Do you intend this to be the long term solution, and if not (which I hope), perhaps you could have included a clarification about the accessibility concerns? [23:24:58] When I open abstract wikipedia on a mobile device with the Wikipedia app installed, I get thrown into the app and an error. Is there a ticket for this?