Hi, I am intending to restart work on salting discourse, which has been blocked for years by two things: * Migration to vb5 * Fixing the database in vb4 I know there has been some progress on vb4 database fix, but vb5 migration seems to be blocked on auth which would likely be easier to fix by just migrating to discourse right away, since it uses a system we have integrated in other apps in the project already. The problem I am facing is that since the vb4 fix isn't public right now, any attempt at database migration testing I could perform on discourse is not gonna be done on the same state of the database as we would get after applying the fix. How should we proceed then? From my personal pov, setting up a duplicate vb4 setup and fixing a database, so that we can properly test it and apply those fixes back into the main instance is the best way to solve this issue. From there we can just work on migrating to discourse, with testing that actually tests the correct state of the database. Alternatively I'm sure we could find a Nextcloud plugin to replace forums with Nextcloud too, I'm sure that would solve all the problems ;) LCP [Sasi] https://lcp.world/