| 1 Feb 2023 |
 TravisR | Voice messages have a text fallback which isn't alt text 😛 | 18:29:29 |
 Nico | I mean that making something not notifying is a visual thing and often adds a visual highlight or the opposite of that | 18:30:10 |
| Nico | Then you said it doesn't apply to voice messages | 18:30:21 |
| TravisR | Red highlight is not a characteristic of an event, but rather push rules. The "automated event" flag is to hint to clients that it's an automated event, and they can do whatever they want with that information. | 18:30:37 |
|  omkara joined the room. | 18:30:39 |
| Nico | Now what does apply to voice messages is adding a description for people who can't hear. Same as it does for images or videos for people who can't see | 18:31:07 |
| TravisR | The replacement push rule for notices is not currently aiming to blanket-apply to all automated messages, but rather just text messages. | 18:31:13 |
| TravisR | In reply to @deepbluev7:neko.dev
Now what does apply to voice messages is adding a description for people who can't hear. Same as it does for images or videos for people who can't see The text fallback can be a transcription for a voice message. Alt text is more applicable for images/video than text fallback. It's a very subtle distinction around accessibility and purpose. | 18:32:06 |
| Nico | Well, I am going to buy dinner now, so I don't really have time to argue, but I am also not that convinced, that the line of allowed Mixin and not allowed isn't very blurry. And it does feel like it would cut out useful features to draw it in the first place | 18:34:28 |
| Nico | But that feedback is a bit late now anyway :p | 18:34:53 |
| TravisR | There is no such thing as a text-based mixin right now, deliberately 😛 | 18:35:22 |
| TravisR | the m.caption content block is used by multiple different event types though | 18:35:38 |
| TravisR | Alt text I think is also somewhere in a proposal, but also not considered part of the critical path | 18:35:53 |
| * TravisR makes a note to clarify how file captions are meant to work in the respective MSCs | 18:39:32 |
 Lozenge | In reply to @cat:feline.support
Ok so The feature Cinny has i would need to see a event to tell how they are doing it it doesn't do anything special event-wise. It just let you type a message when you want to send files and then send those as two different messages. | 22:35:18 |
| 2 Feb 2023 |
|  Ronny Ruhe changed their profile picture. | 11:19:00 |
|  @royills:matrix.org joined the room. | 18:09:16 |
 Robert Long | Can someone clarify what timezone timestamps are supposed to be in? I'm guessing UTC? https://spec.matrix.org/v1.5/#timestamps | 22:30:29 |
| Nico | They are milliseconds since epoch | 22:31:12 |
| Nico | https://en.wikipedia.org/wiki/Unix_time | 22:31:13 |
| Nico | (which is UTC, yes) | 22:31:31 |
| Robert Long | Ok epoch specifies UTC TIL | 22:31:41 |
| Robert Long | Thanks! | 22:31:45 |
| Nico | nw :3 | 22:31:55 |
|  Administrator banned @royills:matrix.org (spam). | 22:58:17 |
| 3 Feb 2023 |
 amnesia | Finally submitted draft PR of this beast of a MSC 🎉 https://github.com/matrix-org/matrix-spec-proposals/pull/3963 | 01:19:14 |
| amnesia | Just don't tell anyone that I had to force-push to my fork 10 times in a row to get the commit amended right, signature and all 😠| 01:20:25 |
| amnesia | Some days you wake up and git just hates you | 01:20:49 |
 zestylemonade | > Finally submitted draft PR of this beast of a MSC 🎉 https://github.com/matrix-org/matrix-spec-proposals/pull/3963
amnesia as far as i can tell, this is just rolling your own proxy and baking it into matrix? | 01:37:07 |
| zestylemonade | there's only really 2 benefits i can see with this, which is that it can strip unnecessary headers like user-agent and that it's built into matrix | 01:37:58 |
