just been cycling through them over and over again, if someone wanted to block them for curation, they should not have had a problem to do so by now. And I do have plenty that I don’t post from for comm making.

It’s good that you’ve narrowed it down, but cycling through them will continue to cause people to think you’re somehow a spam network.

You’d be surprised, Ive definitely had people ask me about instances that I’ve posted from. Especially funnier named ones like toast.ooo

I’m not asking for hard data, to be clear, but I would still argue that for the amount of people that see your posts (a lot, since you post a lot), the amount of people asking you questions about your instances is tiny. Most users don’t even comment, so the math there doesn’t really add up.

A big reason a crosspost won’t show, is if the other post is on a comm that isn’t federated with your instance or hasn’t pulled that specific post yet

But leaving a link to the original post would always show. Just like boost automatically does. You can see an example in this post: https://infosec.pub/post/40397999

basically by interconnecting instances I mean I’m encountering comms that the instance hasn’t federated with yet because nobody has subscribed from their instance to it. And nobody on that instance can see content from that comm until someone subscribes to it

I mean, that’s fine, but you don’t need to post from the account do to that. It doesn’t even need to be named with your username since you’d never post with it to begin with. It’s already an invisible action. So again, it’s not necessary to make your username seemingly associated with negative views such as spam networks or ban evasion to help instances with this. The cons still outweigh the pros.

Yea, but a big difference is, none of my accounts are actually banned from anywhere

It’s a low bar, to be honest.