| 07:20 | <annevk> | Matrix threads, at least as implemented on app.element.io are terrible. There's always unread notifications and nowhere to find them. The experience is so much worse than Slack. :/ |
| 07:30 | <sideshowbarker> | “There's always unread notifications and nowhere to find them” — exactly that, yeah. I often end up just setting the entire room to ”mark read“, because it’s still showing that the unread-messages dot— but even after checking, I can’t find any thread that has unread messages… |
| 07:35 | <sideshowbarker> | In general it seems like the UI/UX of app.element.io and the Element desktop app are worse in pretty much every way than Slack and Discord too. Stuff “just works” in the Slack and Discord UIs, but in Element makes even the simple things difficult. Before I had hoped that Element UI/UX would eventually get better but it’s been this bad for so long now that at this point it seems pretty clear it’s never going to really improve significantly |
| 07:56 | <Domenic> | I wish there were a way to disable threads for a room |
| 08:10 | <annevk> | I think I found what you have to do to get rid of the dot. Next to the (i) in the top right corner there's a threads button. But all the threads in there have a dot as well, despite having gone through those at least once in the past. I suspect it simply doesn't remember across sessions or some such. It's just bad. |
| 08:11 | <annevk> | Anyway, Domenic will you be around for a while? I just remembered it's Monday and were supposed to attempt a rollout of spec-factory. |
| 08:12 | <Domenic> | I will not, sadly. Gym for 30 minutes then out for the night. |
| 08:13 | <Domenic> | Tomorrow should be doable |
| 08:13 | <annevk> | Domenic: okay, I guess I'll do the RDs without spec-factory then. Sounds good. |
| 09:49 | <chargeitall> | Is there a specific label you use for this kind of PRs? If so, what is it? |
| 10:08 | <chargeitall> | The meaning is not clear to me yet. I require more time to understand it. |
| 10:12 | <chargeitall> | https://infra.spec.whatwg.org/#algorithm-params |
| 10:17 | <chargeitall> | I have a question about the term resource. Is it referring to a variable name or a function name? And why do we have to write it in two different ways, one normal and one italicized? I could not find the formating rule behind it |
| 10:21 | <annevk> | It's a type followed by variable name for the type. |
| 11:39 | <zcorpan> | If it was a JS template string instead, it would be: and the example below has for the navigationType param: type="boolean" |
| 16:45 | <chargeitall> | is there a link that defines the type resource? with examples? |
| 16:49 | <chargeitall> | real examples of algorithms that use the “resource” type, |