Meta is just going to come online with a large instance with millions of users. It’s kind of hard to judge all of meta users at once, as an instance provider. So, I guess instances who don’t want meta, don’t get meta. Fair.
That’s one course of action Meta could take.
Another option would be for Meta to open ten or twenty or however many different instances (Facebook alone has 36 domains, so it’s not like they’re not already doing this) and thus attempt to vastly complicate every effort to filter or block them. They could say they’re trying to direct people to instances curated to their specific interest, for example, and then use their bots and AI to populate them with some content. In other words, Meta could literally “Metastasize” itself throughout the Fediverse with no advance notice, no opting out, suddenly they’re just there.
And then when other instances and users get upset because suddenly Meta is fucking everywhere, Meta goes, “We told you we were coming in, what’s the problem? Are we not allowed to have as many instances as we like? You do, why can’t we?” and continue to flood the Fediverse.
I am genuinely sorry to throw that possibility out there, but thinking Meta will play fair, and content themselves with a single instance, when they can so easily propagate themselves freely across the Fediverse with endless cash and servers and bots like the cancer they are is not realistic, IMO, given their behavior since the outset.
Allero@lemmy.today 10 months ago
There will be a blocklist, then.
But fundamentally we can do very little to prevent the inflow of random instances - if only instances will implement whitelist federation, but that obviously hurts decentralization and adds a lot of headache