/
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
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

The Fact And Fiction Of Sam Sethi

So Sam Sethi, former TechCrunch UK editor, announced the closing of his Blognation blog network today.  Hey lays 100% of the blame for the failure on me personally.  And while I agree with Mathew Ingram, Techfold and others that it isn't appropriate to lay blame on others for your own failure.

CrunchNotes Mike

Context & Ripple Effects

The collapse of Blognation has moved from a business failure to a public feud. Sam Sethi, who was put in charge of TechCrunch UK before it went on hold a year earlier, had already told his team on December 8 that funding took longer than expected, and signed off with a farewell to the startups he covered on December 13.

Now the closing announcement comes with an accusation: per this CrunchNotes post and Mathew Ingram's parallel write-up, Sethi lays 100% of the blame for the network's failure on Michael Arrington personally. Ingram, Techfold and others are pushing back publicly, arguing that blaming someone else for your own venture's failure is not appropriate — making the dispute itself the story.

First-order effects

  • Blognation is shut down and its contributors are out of a publishing home, with Sethi's own December 8 post having already flagged the funding shortfall to his team.
  • Arrington is now defending himself against a direct personal-blame claim from a former TechCrunch UK editor, aired on the same day the network closed.

Second-order effects

  • Mathew Ingram and Techfold's public rejection of the blame-shifting turns the tech-blog community into the arbiter — reputation, not litigation, is where this dispute gets settled.
  • Startups that used Blognation for launch coverage lose a channel at exactly the moment TechCrunch's own network is absorbing attention, tightening the concentration of early-stage coverage.

Third-order effects

  • If single-founder blog networks keep failing on funding and personality disputes, event- and network-based coverage models look structurally fragile compared with solo blogs backed by established platforms.
  • The episode hardens a norm in the blog ecosystem: founders who publicly assign blame for their own failures pay a credibility cost with the very community they need next time.

The trend: Ad-supported blog networks built around one founder's fundraising and relationships are proving fragile, with failures settling into public reputation battles rather than quiet wind-downs.