| 15:58 | <rbuckton> | littledan: would it make sense to set up a matrix channel for TG4 discussions outside of the scheduled meetings? |
| 15:59 | <Chris de Almeida> | #tc39-tg4:matrix.org |
| 16:00 | <rbuckton> | Ah! Thanks |
| 17:16 | <snek> | is there a matrix client that makes threads good |
| 17:41 | <rkirsling> | is there a matrix client that makes threads good |
| 17:42 | <rkirsling> | it's like "how many times do I have to refresh this page before you'll be willing to tell me I don't have new messages" |
| 17:42 | <rkirsling> | I hate this site so much lol |
| 18:25 | <shu> | down with threads |
| 19:16 | <Chris de Almeida> | is there a matrix client that makes threads good |
| 19:40 | <Chris de Almeida> | down with threads |
| 19:40 | <Chris de Almeida> | maybe at Sept plenary we can ask for consensus to ban threads in TC39 rooms... 🌶️ does anyone like threads? I think one or two changes could redeem them and make them usable, but until that happens, they are annoying. I keep finding myself semi-inadvertently starting them due to cognitive momentum from using them in slack and forgetting how annoying they are in element |
| 19:58 | <Michael Ficarra> | I want to like threads but they make a mess out of notifications |
| 19:58 | <Michael Ficarra> | but I definitely do want a way to ignore side conversations I don't care about, which is the point of threads |
| 20:00 | <bakkot> | IIRC slack/discord only count threads as "unread" for the purposes of the notification dot(s) when you've participated in them, which is the behavior I want |
| 20:02 | <Chris de Almeida> | slack behavior is that you don't get notified about any thread activity until and unless: 1. you've deliberately subscribed or 2. you've deliberately participated, e.g. replied in the thread it also helps that slack has a thread view, almost like a thread channel, rather than forcing you into the right sidebar only. there was a time before that feature existed but that made threads more bearable in slack |
| 20:03 | <Chris de Almeida> | indeed... just look at this insane issue re: notifications/threads https://github.com/vector-im/element-web/issues/24392 |
| 20:07 | <Chris de Almeida> | oh, and in slack you can also unsubscribe to a particular thread. that's a big one too |
| 20:28 | <shu> | yet you started a thread the other day. curious. |
| 20:29 | <shu> | what thread did i start |
| 20:33 | <Chris de Almeida> | what thread did i start |
| 20:33 | <shu> | huzzah, i am exonerated |
| 20:40 | <shu> | i knew i was innocent all along because i actually do not know how to start new threads |
| 20:57 | <ljharb> | i love threads. i hate the notification issues. i don't think banning threads is justified by them. |
| 21:18 | <Chris de Almeida> | what client do you use? |
| 21:32 | <shu> | i don't know |
| 21:33 | <shu> | Matrix |
| 22:07 | <ptomato> | +1 in favour of threads as well. would be nice if they worked properly, but I'd rather mark them read manually than scroll past all the side conversations |
| 22:08 | <ptomato> | BTW, I'd seen that tracking issue before; they basically identified the root cause as having moved threads out of beta too early. seems like they're working pretty hard on it; hopefully the usability fixes make it into a release soon |