I’ve set up a Lemmy instance and tested federation by commenting with my Mastodon account on the lemmy instance, which worked.
But I broke the test instance and had to start over (not even once).
The productive instance runs now, but after a few days I figured out that there is still the old post from the old installation on Mastodon and over Mastodon I can’t see the new post and no new comments?
It is the same link (older Mastodon post, old Mastodon post, new Lemmy post), but the content is different.
- The post itself doesn’t update (it is completely different)
- The comments don’t update (different comments)
How to solve this problem? Is it even solvable?
Might it be a good idea to to just copy the post so it gets a higher ID, which wasn’t used before? Because the productive system is already running and has a lot of content and a new reinstall might even block more IDs.
if it were me right now with Lemmy 0.18.4, I’d take the server offline, do a PostgreSQL dump file - keep a copy, then hand-edit the sequence numbers in the dump file - and do a restore.
you probably only had a few users, so I would set user to 100, person id can be higher because of federation - but jump ahead to 10000 maybe. Post and comment set ahead to 10000 … and community set ahead to 10000 because that gets federated
the PostgreSQL sequence numbers should only get used on newly created objects here-forward.
That sounds complicated and I am afraid something could break (again). The last days I tried to fix something in the db, which led to other problems.
It is complicated. It’s surely a damned-if-do damned-if-don’t situation. It doesn’t sound like you had all that much in terms of local users, communities, posts, comments - so at least that’s in your favor.
