Right now the fediverse is nipping at the heels of the silos.
They know we are here, and they perceive us as a threat. We know this from leaked emails from facebook.
That said, they could attack us in an oblique manner with any number of poisoned waterhole attacks.
Earlier today someone predicted one or more of those platforms just integrate activitypub and crush us by incorporating us.
Another pointed at the potential for procedurally generated instances that just harvest data, or overwhelm our ability to suspend all of the instances they throw up.
When these attacks are adapted to... they'll get concerned, and will try to frame us as part of "the dark web(tm)"...
That's how we'll know we're winning.
I'm interested in brainstorming immune system defenses
beyond our strength as actually real people who can tell the difference between fake and person, usually pretty obvious
I am interested in this as well.
I feel like some sort of new instance registry may be necessary if we see these sorts of co-opting efforts occurring...
Like a low speed probationary period or something...
@mirzaba @thegibson @Food The most elegant solution I saw someone propose (can't remember who though :s) was to auto-block instances hosting more than N users to force decentralisation –and avoid the fate of emails.
But the problem is that we already have too big instances like mastodon.social or pawoo.net. So maybe we're doomed.
Also, if you have a link or source regarding those leaked Facebook emails about federation I'd be interested.
@mirzaba @rick_777 @lertsenem @thegibson @Food Maybe the default is muted by default: new instances can follower whomever they like (so long as the account they want to follow isn’t on a strict whitelist instance) but manual approval is necessary for posts and replies from the new instance to reach existing instances.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!