@ticky Federation with other instances is planned, it's just whitelist-basd instead of blacklist-based.
@ticky And to be honest, after having seen enough jerks on other instances in the rest of the fediverse, federating solely to mastodon.social is attractive to me! I know that's maybe not a good thing in the long haul but I genuinely see it as a feature and not a bug. I like Mastodon when it's less stressful than Twitter, and an intentional and cautious approach to federation is one of the things that makes it that way.
@ticky It wouldn't block you, to my understanding of how federation works; your awoos would be delivered to anyone who follows you, and you would receive mentions from anyone who follows you.
@ninjawedding @ticky @dog The basic issue lies in how boosts work: boosts are copied and reposted on the remote server, which means anybody they federate with can suddenly see posts, since domain blocks are not propagated with the boosted post.
This creates a problem where one would expect an instance to not be able to see or interact with posts and suddenly can. Interactions won't show up in the author's notifications, however.
@ninjawedding @ticky @dog The general policy right now is: let me know if you want to federate with us, and I'll walk you through the criteria more privately, because there are some places we don't want to indirectly federate with. I know it's a little nitpicky but I'd rather develop a working relationship with folks on this basis instead of blatantly trust people won't abuse a platform that federates with us.
@ninjawedding @ticky @dog I'm sorry if things are kind of confusing as far as how our policies work. It's intentionally this way to try to avoid attention from the people I don't really want to deal with as far as awoo.space goes.
