[06:06:21] A test to convert 30000 minutes in days and hours ... [08:46:18] Hello! Here's an update to the futuristic zids situation: https://phabricator.wikimedia.org/T410895 (re @u99of9: @genocation What are you working on at Z30009? It looks like this will take the Z30000 ZID. That seems a bit premature because t...) [11:24:16] Determinant of a matrix? (re @u99of9: Speaking of Z30000, does anyone have something amazing in mind that we can try to drop when the time comes?) [11:24:52] Sunrise at location QID on date? (re @u99of9: Speaking of Z30000, does anyone have something amazing in mind that we can try to drop when the time comes?) [11:25:21] Moonrise? (re @u99of9: Sunrise at location QID on date?) [11:25:42] Phase of moon on date? (re @u99of9: Moonrise?) [11:26:10] Eigenvalue spectrum? (re @u99of9: Determinant of a matrix?) [11:28:35] Timezone of location QID? (re @u99of9: Speaking of Z30000, does anyone have something amazing in mind that we can try to drop when the time comes?) [11:29:30] Correlated colour temperature from RGB? (re @u99of9: Speaking of Z30000, does anyone have something amazing in mind that we can try to drop when the time comes?) [11:35:10] Is Qid1 a wdt:P279*/wdt:P31 of Qid2? (re @u99of9: Speaking of Z30000, does anyone have something amazing in mind that we can try to drop when the time comes?) [11:35:44] I like this one. I feel it demonstrates the wider utility of embedded functions in a Wikimedia context whilst respecting the value of locality. It would be great if it could adjust for altitude! (re @u99of9: Sunrise at location QID on date?) [11:45:38] Altitude doesn't seem too hard if we have that data. I'm more keen to get it into the location's timezone, but that requires a bunch of helpers and a new type! [11:50:59] Maybe in seconds before local noon, so (almost) everyone is equally confused? 😏 (re @u99of9: Altitude doesn't seem too hard if we have that data. I'm more keen to get it into the location's timezone, but that requires a b...) [11:54:01] There might be good options in the fragment/languages space? [12:05:59] An extremely ambitious interlingual replication of https://en.wikipedia.org/wiki/Template:Cite_Q ? [12:24:06] Isn’t that what GrimRob is working towards? It’s a must-have for “Wikicore”, of course, but references remain switched off 🤷‍♂️ (re @u99of9: An extremely ambitious interlingual replication of https://en.wikipedia.org/wiki/Template:Cite_Q ?) [21:56:27] Grammatical types relevant to language? Likely structurally useful, but maybe not much fun to play with. (re @u99of9: There might be good options in the fragment/languages space?) [22:07:50] Maybe better for Z40000 then (re @Al: Isn’t that what GrimRob is working towards? It’s a must-have for “Wikicore”, of course, but references remain switched off 🤷‍♂️) [22:11:27] How about a language-configured sentence version? "Sunrise in Epping tomorrow is at 6:15am." (re @Al: I like this one. I feel it demonstrates the wider utility of embedded functions in a Wikimedia context whilst respecting the val...) [22:15:36] It’s certainly a lot of work! (re @u99of9: Maybe better for Z40000 then) [22:18:51] Maybe… but we’d have to worry about caching with a word like “tomorrow” 🤔 (re @u99of9: How about a language-configured sentence version? "Sunrise in Epping tomorrow is at 6:15am.") [22:23:15] Yes, one with the arbitrary date written out is more general anyway. I think we could write the tomorrow function by sending a today_date argument, which should be left blank for embedded calls. (re @Al: Maybe… but we’d have to worry about caching with a word like “tomorrow” 🤔) [22:26:01] The tense for the arbitrary date one might be tricky. (re @Al: Maybe… but we’d have to worry about caching with a word like “tomorrow” 🤔) [22:36:06] “Sunrise at on is/will be/was , earlier/later than on .”? (But let’s not forget daylight saving time changes) (re @u99of9: Yes, one with the arbitrary date written out is more general anyway. I think we could write the tomorrow function by sending a t...) [22:45:19] sunrise comparisons... meta! I'd stick to "Sunrise at on is/will be/was at ." Where the tense is determined by comparison with (embedded blank) date_today (and language?). Or do we need to directly pass in a tense to help other languages? (re @Al: “Sunrise at on is/will be/was , earlier/later than on [22:45:19] .”? [22:45:19] (But let’s not forget da...) [22:48:14] Again giving the time in the local timezone would help, perhaps we'd better quickly write a lightweight-enum timezone proposal? [23:04:36] Maybe not a tense as such… but whether the sunrise is/was prospective when the time was determined 🤔 (re @u99of9: sunrise comparisons... meta! I'd stick to "Sunrise at/in on is/will be/was at ." Where the tense is d...) [23:23:05] For a Timezone enum, do we want to list former timezones (e.g. Q20828349)? Here's a long-list of possibilities (including duplicates but with IANA redirects already removed): `https://w.wiki/GJUo` [23:46:22] Broken link? I suspect we want at least two separate enumerations: the comprehensive and the canonical (re @u99of9: For a Timezone enum, do we want to list former timezones (e.g. Q20828349)? Here's a long-list of possibilities (including duplic...) [23:51:07] Yes, I am coming around to that idea too. Sorry, this should work. It looks like some on-wikidata work would be useful before choosing the initial "comprehensive" (then it would be important to remain editable). _https://w.wiki/GJVy_ (re @Al: Broken link? I suspect we want at least two separate enumerations: the comprehensive and the canonical)