Regarding this "feature", none of 1, 2 or 3 are solved at all by what I'm talking about. I'm saying that I would actively join another instance and my old identity is duplicated there, with duplicated posts being merged, not that my posts propagate automatically to every node in the federation. All the advantages of gating off your instance are preserved, plus you avoid duplicated post spam in the federated view.

> I would advise not doing this, as we will start to block all your accounts. Attempting to chorus-spam the federated timeline will show up very quickly.

This was entirely my point. If you want to maintain a presence on multiple instances, the only way to post content relevant to multiple instances is to duplicate it, and it is not your choice whether or not multiple accounts of yours show up in the federated view of other instances. Echoing your posts is the hack that I'm sure people will try, some instances will ban it, others will put up with it, I imagine enforcement will be imperfect.

> It can be frustrating when you as a human have to maintain outsized attention on two or more locales.

Yes, to the extent to which clients and other hack-y behaviors do not solve this problem, what it means is that all the "spoke" timelines will die out and you'll concentrate on a few huge mega-instances, and you might as well have not bothered to move off twitter in the first place. If it's very easy for someone to exist both in their "home" node and in another node, the major disadvantages that come with being on smaller instances will fall away.