After some troubleshooting and investigating, we've migrated over to the latest alpha release for #Bonfire. It seems that we've figured out the root cause with the queue problem, which was causing every instance to receive notice of every follower our accounts had during the migration process, leading to lots of fan-out. Anyway, we should be all caught up now, lesson learned, bug squashed!
1 Boost
3 Likes
@coin@fedi.space Debating it. I know it's possible, you can apparently import the entire Outbox JSON from a previous account hosted elsewhere.
I think it's a worthy experiment, but will preface with the statement that I'm not sure if it will break something.
@coin@fedi.space my main concern is the fan-out that could happen when federating a lot of details across a lot of different places. Federation deliveries go up exponentially when you do stuff like that, and there's still no "story" of how ActivityPub implementations should handle this situation.
Sure, there's some speculative work such as LOLA for ActivityPub data portability, and some platforms like Hubzilla have had some version of this floating around forever. It's that last mile of making it work for everybody that remains hard.
@deadsuperhero@fedizen.net @coin@fedi.space we don't federate those
@deadsuperhero i'll be probably trying this on a test instance soon.
@deadsuperhero do you plan to import your post history from the previous instance in this account ? I'm very interested how it would look if it can be done.