11:00 | <ryzokuken> | something i know might help a bunch of folks here: https://github.com/element-hq/element-meta/issues/1090#issuecomment-2010330567 |
11:01 | <ryzokuken> | plus the latest version of element nightly put in (atleast a) minor redesign so it looks and feels better too |
15:38 | <dminor> | Just a quick reminder for anyone interested in speaking at the standards session at Future Frontend the day after the Helsinki TC39, that if you haven't already, please get in touch with me with your proposed topic so I can pass them along to the conference organizers. I'll be speaking with them again next week. |
17:15 | <bakkot> | one week to get topics on the agenda |
17:15 | <bakkot> | it is extremely light so far |
17:18 | <Michael Ficarra> | one week to get stage advancement topics on the agenda |
17:19 | <Michael Ficarra> | other topics can still be added any time up until the agenda approval at the start of the meeting |
17:55 | <rbuckton> | Does esmeta not report line/column information for errors? It's awfully hard to determine where the error is located in such a large file. |
18:37 | <bakkot> | it reports the algorithm and step number, I believe |
18:37 | <bakkot> | but it can be confusing sometimes |
18:37 | <bakkot> | also sometimes it has bugs |
18:37 | <bakkot> | feel free to ignore it for now if you'd like and the editors can look into it |
18:59 | <Justin Ridgewell> | something i know might help a bunch of folks here: https://github.com/element-hq/element-meta/issues/1090#issuecomment-2010330567 |
19:00 | <ryzokuken> | Tauri based!? I had missed it somehow, will try it out soon, thanks! |
19:04 | <nicolo-ribaudo> | I wish it had a screenshot in the readme |
19:06 | <nicolo-ribaudo> | Ohh it's nice |
19:07 | <nicolo-ribaudo> | And it also has a web client https://app.cinny.in/ |
19:07 | <nicolo-ribaudo> | It's very nice |
20:08 | <ljharb> | trying it now; so many things are still marked unread :-/ seems nice to far tho |
20:38 | <Michael Ficarra> | cool technology we've got here |
20:49 | <ljharb> | for that you have to open your session on element and find sessions in settings, and start verification, so you can sync your keys to the new client |
20:49 | <ljharb> | see, isn't this so much more user-friendly than irc? |
20:56 | <Anthony Bullard> | Why didn’t we just use an open source normal chat client like Mattermost? I wasn’t here when the move to Matrix happened. I really want to like Matrix, but all of the clients have many problems. |
21:29 | <Justin Ridgewell> | for that you have to open your session on element and find sessions in settings, and start verification, so you can sync your keys to the new client |
21:33 | <ljharb> | it's very important we all encrypt our super secret spec discussions |
21:33 | <ljharb> | wouldn't want anyone hacking us and finding out about proposals |
21:35 | <bakkot> | I have literally never heard of mattermost so probably that's why |
21:37 | <Anthony Bullard> | I have literally never heard of mattermost so probably that's why |
21:37 | <bakkot> | oh we'd have to host it ourselves? |
21:37 | <bakkot> | presumably that's why then |
21:37 | <Anthony Bullard> | oh we'd have to host it ourselves? |
21:38 | <Anthony Bullard> | Figured ownership might be a benefit to us, but they have options. Might even be open to a discount for an open source / standards org (I don’t speak for them in anyway) |
21:38 | <bakkot> | looks like it's $10/user/month? that's also not gonna be feasible |
21:39 | <Anthony Bullard> | That’s commercial rate, but hey it’s just another option to consider exploring |
21:42 | <Chris de Almeida> | Why didn’t we just use an open source normal chat client like Mattermost? I wasn’t here when the move to Matrix happened. I really want to like Matrix, but all of the clients have many problems. |
21:42 | <bakkot> | the "unable to decrypt message" thing Michael shows above has happened to me a few times also |
21:44 | <Chris de Almeida> | the "unable to decrypt message" thing Michael shows above has happened to me a few times also |
21:44 | <Anthony Bullard> | aside from the stuck notifications (which has largely improved), what other problems have you observed with Element? |
21:44 | <Chris de Almeida> | I get crazy sync issues. Sometimes entire parts of the channel history disappear completely |
21:45 | <Chris de Almeida> | web, desktop, os, etc |
21:45 | <Anthony Bullard> | Case in point |
21:45 | <Chris de Almeida> | whoa |
21:45 | <Anthony Bullard> | Mobile is the worst, and the one I use the most |
21:46 | <Anthony Bullard> | I don’t know if I’ll ever see that convo I had with @bakkot again |
21:46 | <Chris de Almeida> | well I haven't seen that, but WOMM is a scarcely a comfort |
21:48 | <Anthony Bullard> | I’d show you my new state, but the mobile app won’t let me give it access to the new screenshot |
21:49 | <Anthony Bullard> | Not the biggest deal, but definitely is concerning if this happens a lot. I take solace in thinking that it’s probably eventually consistent |
21:49 | <Anthony Bullard> | And all of the conversations are actually persisted |