-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrating from mautrix-facebook #3260
Comments
I've added a link to that documentation in #3254, but have been unsuccessful in completing it. A few issues:
At this point, I'm very curious about people who have made the switch already, did you get any message history without db migration? A meta bridge issue mentions backfill, does that pull in old messages? |
Migration did not work for me and i had to manually remove each room from my matrix element session and then re-add the chats... it was painful but fine in the end |
@Joshndroid But did you get chat history? 😱 |
@jswetzen no I lost all history. I am not too concerned with the Facebook messages history though so was okay. I was more annoyed that I ran everything and it never did the clean up/out. It was weird at first as I thought that the new bridge was broken until I realised that it was the old Facebook bridge rooms and I needed to find the new ones created by the new meta bridge and delete the old ones |
I lost all history as well, but got hundreds of extra rooms. The old bridge only created rooms as they were used, this one pulled out to I think at least 6 months. |
I've started preparing to run migration, but didn't take the plunge yet. I think these configuration variables will be needed to match the old bot username etc. at least.
I needed version because db migration wasn't enabled in the meta_messenger version used by default. Good luck @MrAnno ! |
Hi,
Last week, a migration path from mautrix-facebook to mautrix-meta was published by upstream:
https://github.com/mautrix/docs/blob/master/bridges/go/meta/facebook-migration.md
I couldn't find anything similar in the playbook, so I thought it might be worth opening an issue and discussing the current migration method.
The text was updated successfully, but these errors were encountered: