I always promote the idea that we should be empowering users to shape their own experiences as they prefer, so #Federation should always be the default.
Let users block instances if they want, but I'd rather keep admins out of the position of dictating what users can and can't see.
That extends to #Meta as well.
If they want to provide a lot of new content to us, then great! If you or I don't want to see that content, also great, let us make that decision and block at the user level.
Otherwise, a lot of people sick of having algorithms set their experience will be on #Fediverse where someone else will be setting their experience.
I think a good way to think of it is like email.
It's one thing for you to say that you do or you don't want to see any emails from some particular company, Walmart or the DMV, or whoever. You can mark it as spam, and you can work with your email client to sort out what is spam and what is important and all of that.
But it takes it to an entirely different level if whoever operates your email server decides for themselves that you don't get any of the messages from some particular domain.
Same thing here. It's one thing if you get to choose whether, say, Facebook content shows up for you, but entirely different if the person operating your instance makes that decision for you and blocks it for you so you don't even have the choice.
Let's say that you are an Amazon subscriber and get useful emails from Amazon. It would really stink if your email server administrator up and decided to block all email from Amazon, even the stuff that you actually really needed to see.
@volkris @stux I don't have deep knowledge about how the Fediverse works technically...is blocking sites something that ordinary users can do for themselves here, and how would that work ..where can we go to find out about that sort of function? I'm still pretty new to Mastodon, and quite new to Calckey which I have been looking at as well.