I think there are good reasons to not let corporate interests join the space we built to escape them, but I guess every instance is free to (de)federate with whomever they want.

So let’s say my instance (mander.xyz) defederates from Meta but another Lemmy instance that meander.xyz federates with (let’s say “misguided.ml”) does not. What happens when someone from Meta comments on a post from misguided.ml and others from misguided.ml comment on that comment? Will I see the comments on the meta comment, but not the original meta comment itself? Or will I not see the entire thread?

  • Carlos Solís@communities.azkware.net
    1·
    1 year ago

    I wish that all federated software had an easy way to migrate your user, with all and posts, to another server whenever required. That way you’d be able to jump ship elsewhere if you disagree with your current admin’s defederation policies. Mastodon is really dragging the feet on that one, and both Lemmy and Kbin don’t even allow exporting your list of subscriptions yet.

    • notsofunnycomment@mander.xyzOP
      1·
      1 year ago

      Is there resistance against it on Mastodon? I thought it was just a technical issue? (I mean specifically post migration).

      • Carlos Solís@communities.azkware.net
        2·
        1 year ago

        There are several hurdles specifically regarding post migration:

        • How can an instance handle a truckload of new posts that were originally posted elsewhere, especially as they might cause a flood of notifications to old followers
        • How to ensure that all references to old accounts and old timestamps are correctly migrated
        • How to properly prove that the old account and the new one are one and the same, as malicious imports may be used for plagiarism purposes
        • And last but not least, how to handle imported posts that may be violating the terms of service of the new instance!