@ShadowJonathan@tech.lgbtOne bug I already found:
Moves (account migrations) could fail for observing akkoma instances if the migrated-to user has set their "also known as" (aliases) for that user less than 24 hours ago, *and* that akkoma instance has fetched and cached that user less than 24 hours ago. It doesn't properly evict cache when processing the move activity.
With that, a move activity would be a dud, and not move over follows from that instance.
@ShadowJonathanSo the advice I can give for anyone already is to wait exactly 24 hours between setting their alias on their new instance, and pressing "migrate" on their old instance.
@ShadowJonathan@tech.lgbt this maybe explains why some people on 0w0 couldn't get the migration to work?
@ShadowJonathan@smitten maybe, im noting it down in my todo to chase down and file bugs for, but im hot-shooting it on fedi right now cuz i think a lot of people would wanna know about it
@ShadowJonathan@tech.lgbt well either way it's good to have a potential lead. we were stumped last time
@yassie_j@labyrinth.zone@ShadowJonathan Ah! This explains a lot! It took about a week-ish after I originally set the aka for it to actually work
@emlove@void.lgbt@ShadowJonathan This explains so much
@ShadowJonathan @ashten@woem.men is this maybe the issue you had with migrating? (I think you had issues with migrating, right?)