Hello Tumblr 👋
Today, Tumblr’s owner, Verizon Media, announced that Automattic plans to acquire Tumblr. Automattic is the technology company behind products such as WordPress.com, WooCommerce, Jetpack, and Simplenote—products that help connect creators, businesses, and publishers to communities around the world.
We couldn’t be more excited to be joining a team that has a similar mission. Many of you know WordPress.com, Automattic’s flagship product. WordPress.com and Tumblr were both early pioneers among blogging platforms.
Automattic shares our vision to build passionate communities around shared interests and to democratize publishing so that anyone with a story can tell it, especially when they come from under-heard voices and marginalized communities.
We look forward to continuing to create products that empower your self-expression and sense of community and that build a better, more inclusive internet.
We’re excited for our future together!
<3 Tumblr
Some things staff won’t tell you [link]:
- They’re dumping it for–in the grand scheme of things–almost nothing
- No, Automattic *isn’t* ending the NSFW ban
- ‘As for what this means for WordPress, executives from both Tumblr and Automattic will “look for ways WordPress.com and Tumblr can share services and functionality.” We wouldn’t expect any immediate changes, though.‘
I think my main reaction to this is to trust WordPress a bit less. The main appeal of the place for me is that it *isn’t* Tumblr, a separate platform with separate interests.
I’m going to continue my project to create a more stable copy of my Tumblr on WordPress. I’ll probably even continue my plan to start giving them money this winter (what better way to give people an incentive not to screw you over?).
But I’ve been wavering, lately, on whether to *also* look into self-hosting. Not as a Plan A, you understand: I’d *rather* not go through the effort of running the whole infrastructure myself. But I have put (am putting, will put) a lot of effort into making a specifically *Wordpress-compatible* version of my Tumblr, and this WordPress-compatible version is probably distinct enough to deserve its own backup. (After all, if I *did* end up self-hosting one day, that’s probably the software I’d use.)
WordPress export files don’t include images, which would make it a massive pain to re-instantiate my blog using only an export file (not *impossible*–all of the images are also stored elsewhere–but painful, and if I wanted possible-but-painful I’d just re-instantiate from a tumblr-utils scrape), but perhaps a tiny, local server to receive site-to-site exports, not to be made outward-facing unless necessary.
I’m not sure yet what the most practical option is, and how exactly one goes about it. I’ll have to look into it. But I *am* going to look into it.
Tags:
#in which Brin is paranoid #(but what else is new) #101 Uses for Infrastructureless Computers #PSA #Wordpress #The Great Tumblr Apocalypse #reply via reblog #oh look an update






