/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Help us nail spammers

Today we've added another tool to our spam fighting toolbox that will give users the ability to flag bad accounts on Twitter.  —  Folks can now help us conquer spam by calling our attention to a profile they find questionable.  Click the “Report as spam” …

Twitter Blog Jennadawn

Context & Ripple Effects

Spam on Twitter has until now been a do-it-yourself problem: the most visible fix was Twerp Scan, a third-party script from April 2008 that helped users identify and block follower spam because the platform itself offered no reporting path.

With the new "Report as spam" button, announced October 13, 2009, Twitter is pulling that job inside the product — every user becomes a sensor that can flag a questionable profile straight to the company, rather than relying on outside tools built against an undocumented API.

First-order effects

  • Twitter users gain a one-click way to flag suspect profiles, shifting spam defense from manual blocking and third-party scripts like Twerp Scan to a native reporting channel.

Second-order effects

  • Each report feeds Twitter a labeled corpus of what users consider spam, letting the company tune its own filters instead of leaving detection to volunteer-built tools whose accuracy depends on reverse-engineered behavior.

Third-order effects

  • If the pattern holds, crowdsourced flagging becomes standard infrastructure: platforms absorb the moderation work their communities were doing informally, and third-party safety utilities survive only where the official tools stay thin.

The trend: Platforms are internalizing community-run spam and abuse defense, turning user reports into first-class training data for their own moderation systems.