@mint @dcc @sysrq

> As I said before, this is a non-issue unless you're trying to build up an echo chamber with minimal amount of discourse your clique disapproves of.

It's still wrong, for three reasons, one of them practical.

There are posts you want to see and posts you do not care about. You cannot put all of them in, so you have to prioritize somehow. "People on this server want to see this" is a pretty good criterion for whether or not you store something on the server.

If your server is populated by people that only want to see things they agree with, sure, you'll get an echo chamber, but you already had a shitty collection of people to begin with. I try to eat food that's reasonably healthy and tastes good, because there's finite space in my stomach. It's stupid to eat only candy like a hugbox instance, but it's also stupid to insist that a person should eat equal amounts of good food and poison. Someone replies to something, they (hopefully) put some thought into it, even if they disagreed, and those posts federate. A wrench-spammer puts zero thought into spamming wrenches and doesn't even read the posts that he's indicating his displeasure about: have I built some sort of echo chamber if I don't want to go out of my way to fetch shit even he didn't want to read?

Not just that, but the stupid hivemind "get a load of this guy" pile-on is exactly the echo chamber you are concerned about. The biggest echo chambers that exist here are the canceldon instances and places like nicecrew.digital and that kind of place thrives on reinforcing the echo chamber by engaging in the "two minutes' hate".

You are worried about a problem that does not exist on a server that is due to be replaced and in the mean time does not do anything to stop this problem.

> relays,

Well, you've heard what I have to say about relays. They're not super useful. I put FSE on a shit-ton of relays in 2019 to try to see something besides Gab on TWKN; TWKN was worse for it, it was flooded with shit nobody cared about.

> instance-wide relay

This kind of thing is useful, though.

> same mindset that contibuted to Akkoma

Akkoma is terrified that a member of the public might be able to see a public post. This is not the same as declining to go out of your way to get posts no one cares about.

> I was under the assumption that if an activity gets rejected by MRF, its referenced object never gets fetched to begin with.

Maybe it has been fixed since; rejected activities still pass through the pipeline. "Announce" activities from deactivated users still cause posts to federate here.

> by converting them into likes you're contributing

No, Pleroma federates Likes that originate on the server, but it doesn't pass them along second-hand.

> perceived problem.

TWKN has gone downhill; if I have perceived a problem, that's my perception, but that's more real than a perceived hypothetical non-problem.