| 25 Jun 2019 |
 @thejpster:matrix.org | it's a static binary compiled with Rust, deployed as a Flatpak application. I've not used Flatpak before, but it was straightforward-ish. | 20:00:02 |
 J. Ryan Stinnett | In reply to @jschievink:matrix.org
*looks (why can't you edit messages here?) Editing and reactions will be available in Riot in a few weeks. You can try out the development version which allows enabling a preview of the features in top left menu -> Settings -> Labs. | 20:02:44 |
 @jschievink:matrix.org | J. Ryan Stinnett: aah I see, thanks! Someone said editing was possible in the regular Rust matrix room, so I assumed it was configured wrongly. | 20:04:00 |
 TimSmall | * jschievink: No idea what the timeline on RiotX is tho'. I believe that the Dendrite replacement home server in Go is only ~30% done. | 20:07:01 |
| TimSmall | jschievink: Yep, that works thanks. | 20:07:18 |
| TimSmall | * J. Ryan Stinnett: Yep, that works thanks. | 20:10:08 |
|  @freenode_theJPster:matrix.org left the room. | 20:54:53 |
| @thejpster:matrix.org | night all | 20:54:59 |
| Room Avatar Renderer. | 21:10:03 |
| Room Avatar Renderer. | 21:21:27 |
 @paulvt:matrix.org | gn thejpster! | 21:34:03 |
| 26 Jun 2019 |
|  Matrix Traveler (bot) joined the room. | 07:18:04 |
|  @chris:cooperteam.net joined the room. | 07:19:25 |
| @chris:cooperteam.net left the room. | 07:21:14 |
| TimSmall | So this room was created a couple of months ago, and at that time the default Matrix "room version" was v1, to maintain backwards compatabilty with older federated servers. I've taken some advice over on #matrix:matrix.org about this, and the guidance was to upgrade the room version sooner rather than later if we're going to get a lot more users here (more features are available, and the users won't be prompted to upgrade - some clients don't do that massively easily, but with RIOT it's pretty seemless, but still). | 07:57:13 |
| TimSmall | In the not too distant future "later v5 will be default and v1 rooms will get a prompt to upgrade", so I think it's probably best to jump first before things get busier here. | 08:01:37 |
| TimSmall | adamgreig: adamgreig (or other WG members) if you're OK with that, I'll go ahead and do that. | 08:04:08 |
| TimSmall | I created a test room and went through the upgrade procedure. What effectively happens is that this room gets recreated as a new room version, and the current room gets marked read-only. Users get a promp saying "go here to continue", and this old room just basically maintains chat history to date only. | 08:08:03 |
| TimSmall | BTW, v4 is now the default for newly created rooms. | 08:10:26 |
 @freenode_disasm_:matrix.org | TimSmall: are these new rooms compatible with outdated clients? | 08:10:31 |
| TimSmall | disasm_: The prompt says "Room upgrades usually only affect server-side processing of the room. If you're having problems with your Riot client, please file an issue with https://github.com/vector-im/riot-web/issues/new/choose." | 08:11:51 |
| TimSmall | When I asked the same question on #matrix:matrix.org earlier, I got the response "I think it doesn't affect clients, only servers" | 08:14:20 |
 disasm | That's good | 08:14:32 |
 @therealprof:matrix.org | TimSmall: | 08:19:29 |
| @therealprof:matrix.org | I think we should do that. | 08:19:36 |
| TimSmall | therealprof: OK, shall I go ahead now? | 08:20:40 |
| TimSmall | The advice I was given was: | 08:21:44 |
| TimSmall |
v5 over v1 has:
- fixed state resolution (bans, power levels and such shouldn't get unexpectedly reset)
- event ids based on hashes instead of arbitrary strings
- added federation signing key validity checking
| 08:21:48 |
| TimSmall | Not sure what the implications of the last two bullets are, but the first one sounds like it's nice to have 🙂 | 08:22:46 |
| @therealprof:matrix.org | TimSmall: Yes please. Now's the best time for experiments and updating to the latest and greatest. | 08:27:13 |
