Tumblr to move its half a billion blogs to WordPress

Original Article ↗ Hacker News Discussion ↗

WordPress, Automattic, and Strategy

  • Many are surprised WordPress remains so dominant yet “invisible” to most users.
  • Several see the move as Automattic folding Tumblr into its core product and boosting its “% of the web” marketing metric.
  • Debate over counting Tumblr’s blogs: some argue it’s “one site,” others note each blog/subdomain/custom domain is effectively a separate site and would significantly increase WordPress’s footprint.
  • Some view the announcement as explicit marketing for WordPress; others frame it as a standard post-acquisition infra consolidation.

Tumblr’s History and Adult Content

  • Commenters argue the article downplays a key event: Verizon’s crackdown on adult content, which allegedly triggered a mass user exodus (especially to Twitter, also Reddit).
  • People discuss how adult content surfaces across platforms (Twitter, Reddit) and how search/settings and algorithms affect visibility.
  • There is a lengthy, contentious subthread on Twitter’s CSAM and moderation, with conflicting claims and demands for evidence; no consensus is reached.
  • Tumblr has reportedly re-allowed adult content if self-tagged NSFW, after earlier overzealous AI moderation that deleted many benign posts.

Scope and Technical Difficulty of the Migration

  • Clarification: Tumblr will keep its own front end and UX, using WordPress.com as a backend/infrastructure layer, not converting to wordpress.org-style self-hosted blogs.
  • Some think it’s “just” moving databases or media and should be straightforward; others, including people citing past internal knowledge, stress enormous scale, sharding, caches, and the fact Tumblr is a social network, not just blogs.
  • Unclear whether only the public blog network or the entire Tumblr backend will be migrated.

Developer Experience and Alternatives

  • Several criticize WordPress as painful to develop on: inconsistent schema, “magic” functions, footguns, plugin complexity.
  • Defenders emphasize backward compatibility, massive ecosystem, and the fact most users never see the database.
  • Alternatives mentioned include Ghost, Craft CMS, headless/“content backend only” systems, and custom-built CMSes.

User Impact and Sentiment

  • Some are excited or impressed by the scale and “very cool” nature of the project.
  • Skeptics expect breakage, downtime, possible data loss, or security issues; they doubt “you won’t notice a difference.”
  • Others note Tumblr is still active in some communities, question how many blogs are “zombies,” and worry current instability (e.g., RSS 403s) may reflect neglect ahead of the move.