Feasible conduit db > 13 migration path

[Korvox]

I've only gotten down this rabbit hole of Conduit being effectively abandonware into Conduwuit forking from it to now Tuwunel. I recognize there is no way to roll back a rocksdb conduit database to an old version, and sadly the database fork (around version 13) was like a year ago and that is a lot of chat history to lose.

So my question now is given the reality that upstream Conduit is probably not going to see meaningful development going forward and thus I (and others who have been on conduit for years but are now realizing they do have to eventually make the painful break) have to eventually bite this proverbial bullet, what are methods to avoid losing as much as possible? It would be nice to have a guide of eg root encryption keys to salvage or how to make sure a foreign account is in every relevant room so you can rejoin them after wiping the database and starting over.

Because I'm sure I'm not the only person who was just running conduit for years without realizing what happened, but eventually the deprecation of Element / broken sliding sync and media auth etc is going to force us to do something.

[jevolk]

This should be implementable without very much effort. We can use this issue to document what exactly needs to be updated to reestablish Conduit ➜ Tuwunel migration at this point.

Migration from Conduit to conduwuit/Tuwunel only began to diverge with the last round of schema changes made by Conduit. We already have migration code for all other schema changes during the last year. I believe it's currently broken on something to do with media and the format for MIME-types as they're stored in the database. I'll report back here with something more exact.

As background, we considered these ongoing schema changes a nuisance after June had already implemented the MIME feature without reciprocal collaboration from Timo, so she decided to draw the line at that point; that's why the current divergence exists. Going forward I'd be happy to collaborate with Matthias on any future schema changes, as our second-generation maintainer relationship doesn't carry the same animus as June and Timo's.

As a footnote for anyone reading this who isn't aware, it is not possible to migrate from Tuwunel ➜ Conduit, or even from Tuwunel 0.5.0 ➜ 0.4.7 so don't try it.

[mmahdium]

Any updates on the migration from Conduit to Tuwunel?

I've been running a homeserver with ~400 users and Conduit has proven to be quite buggy.

Tons of bugs and sluggish development have made me more concerned about keeping the server up and running reliably. I'm wondering if there has been any progress or roadmap updates on this front.