Twitter's new shared blocking feature is poorly implemented, requires CSV export and import; block lists can only be shared through a third-party service
The Glaring Hole In Twitter's New Shared Blocking Feature — Last week Twitter announced a new tool to stem online harassment …
Context & Ripple Effects
Six days after Twitter unveiled shared block list imports as an anti-harassment tool, Wired's critique lands on the gap between the promise and the plumbing: there is no native sharing mechanism, so users must export block lists as CSV files and pass them through a third-party service to circulate them at all.
That implementation choice matters because it defines who the feature actually serves. The coverage that follows shows the same pattern recurring — opaque report handling by 2017, abusive Lists persisting for years before a reporting option arrived, and eventually Twitter formally endorsing outside moderation apps like Block Party through its Twitter Toolbox. The 2015 CSV workaround was an early instance of the platform delegating its safety layer.
First-order effects
- Users targeted by harassment who want to act on a curated block list must handle raw CSV exports and imports themselves, or route the file through a third party — a workflow that excludes exactly the less technical users most exposed to abuse.
- Any third-party service hosting shared lists instantly becomes load-bearing infrastructure for Twitter's safety tooling, without a contractual relationship with Twitter.
Second-order effects
- Independent developers gain a durable niche building moderation utilities the platform won't ship natively, a market Twitter later legitimized by surfacing apps like Block Party, Bodyguard, and Moderate inside its own web app.
- Every subsequent abuse complaint — anonymous-account reports handled opaquely in 2017, derogatory Lists in 2019 — lands harder because the native tooling remains partial, pushing more users toward those third-party intermediaries.
Third-order effects
- If the pattern holds, trust-and-safety on open platforms structurally migrates to an ecosystem of external tools and volunteer-maintained lists, with the platform acting as a distribution surface rather than the primary moderator — raising questions about accountability when the intermediary is neither regulated nor contracted.
The trend: Platform safety is shifting from first-party moderation features to a delegated ecosystem of third-party tools, with each half-shipped native control widening that gap.