Follow

Fediverse meta 

I've seen a demand "We need to scale content moderation" with a proposal for "a content mod coop (or a federated network of multiple such coops) that can be hired/contracted by larger instances"

These proposals have great intentions, but their premises—that there must be high profile users, that they will be brigaded by abuse from instances that can't be instance-blocked, that moderation must be quasi-professionalised—seem to design against the grain of the federated platform.

Fediverse meta 

I'm not the world's most cynical person, but the idea a worker-owned co-op will pay a fair wage for effective and instance-attuned content moderation and other services, on a contract or incident basis, across diverse instances, sounds a lot like creating the tiny online equivalent of a G4S or Serco "essential service provider" with a left wing gloss about the possible ownership structure.

Fediverse meta 

It would be preferable if individual instance admins were getting improved tools to detect and share information safely about bad actors, subscribe in a supervised way to each other's instance blocks, and collaborate and share moderation workload directly, rather than with a mediating business entity, however apparently benevolent.

Fediverse meta 

@attentive if big platforms eg flickr or tumblr join activitypub, then they will engage in some professionalised moderation. how about the opposite q: what obligations do such professionalised moderation activities have to openly provide their outputs as a common resource?

Fediverse meta 

@mikarv@someone.elses.computeRight! I foresee it being possible to make moderation more efficient with safe sharing of layers of moderation activity via API—more granular information than the "fediblock" hashtag currently circulates.

And I can imagine temporary instance blocks if for example a brigade of trolls is co-located. Any feature like that's going to come with the attendant politics and problems of a federal structure, but it'd be great to explore these things without kneejerk centralisation.

Fediverse meta 

@attentive i think to stop spam, there’ll need in the end to be an allowlist not a blocklist system, which could be somewhat algorithmic: do not allow federation from brand new accounts unless they meet some network or longevity condition (followed by some users from your instance? or enough users your instance people follow? etc). will make cold starts harder but given how easily activitypub instances can be spun up, hard to see steady state otherwise.

Fediverse meta 

@mikarv Yeah, the comparisons to mailservers are probably fruitful, where real-time blocklist sharing, spam traps are all norms and are relatively effective.

A time delay on post federation would be one reasonable idea perhaps …

Sign in to participate in the conversation
Assemblag.es

assemblag.es is a Mastodon instance for people interested in thinking creatively and critically about technology, in the broadest sense. The only requirement is that you keep to the code of conduct! Note: we've paused new signups for a few days while we deal with the #twittermigration influx - please do request an invite, but be aware that for now functions more like a 'waiting list' than a knock on the door, until our numbers stabilise again :-)