#automattic

[photomatt]

You gonna do anything or make any statement about the rampant transmisogyny on this hellsite, especially in cases like predstrogen recently? Or yall gonna stay silent and keep letting/making us get pushed off of it.

I have a number of asks about this, so this is to address all of them, I won't do each individually.

We generally do not comment on individual cases, but because there seems to be mass misinformation around this, I will make an exception and comment on predstrogen.

First, Tumblr has a number of LGBT+ including trans people on staff, and they see things from the inside fully, and they're not protesting this case.

Why do we wrongly have a transphobe reputation? We did have an external contract moderator last year that was making transphobic moderation (and also selling moderation, criminally). As soon as we were aware that person was fired, and we later terminated the entire relationship with that contracting firm and have brought almost everything in-house (at great cost). I have previously commented on this publicly, several times.

I am not aware of any Automattician (people who work at Automattic and Tumblr) who has made any transphobic moderation actions. If it's reported it is investigated immediately, if anything were found that person would be terminated for cause immediately.

Predstrogen's account was suspended for:

Repeated mis-tagging of adult content against Tumblr's community guidelines. This has nothing to do with clothed transition photos, she had 20+ other blogs and multiple accounts with names so explicit I can't post them here without a mature tag.

Multiple cases of harassment of other Tumblr users, not just me.

Multiple threats of violence, not just the one I share below.

These represent a breach of our Terms of Service, and we've exercised our right to refuse service.

Threats of violence are never okay. Threats of violence are not protected speech. We will work with police and FBI where appropriate, though to be clear prestrogen's case hasn't warranted that so far. I'm referring to what we may potentially do for other threats. I just got a death threat yesterday from someone mad about predstrogen, and that account was immediately terminated.

So regardless of whether you still think Tumblr staff is somehow a bunch of transphobes, know that threats of violence or death are still not acceptable and will result in immediate and serious action. Know that when you rile people up, they can do dumb things with possibly permanent consequences.

(2 hours later update: I have changed instances of the pronoun "they" or "their" to "the account" because I am unaware of pronoun preference in this instance and don't want to misgender anyone. Thank you for the people who reported this as an issue. Update 2: "She" is apparently better, the post now says that. Sorry for the mistake.)

Here's one (of many!) examples of the harassment violations, this one targets me but there are others targeting other users on the site.

The second part seems to indicate she wanted to be suspended, I'm unaware of why, perhaps to create this sort of uproar. I agree the hammers feel silly, but the start, "i hope photomatt dies forever a painful death" is a violation of Tumblr's community guidelines and terms of service.

The car part did hit close to home as I have almost died twice in car accidents.

Update 2: Added this text to the adult content part: This has nothing to do with clothed transition photos, she had 20+ other blogs and multiple accounts with names so explicit I can't post them here without a mature tag.

[sheepgirlmaidtummy]

My friend Rita has been harassed by TERFs, and bullied by Tumblr staff for the better half of a year now. Afew hours ago they nuked her off the website after threatening her with the FBI

the "threat of violence" in question:

Rita's name has been dragged in the mud and the literal CEO of tumblr decided to join in too.

please consider helping her out. she's a disabled sex worker just trying to get by and anything you give would go a long way.

paypal / cashapp: £MoiraHopz

[squidhominid]

I told @strange-aeons that I had a dream that Matt Mullenweg announced Tumblr was going to be shut down on February 2nd of next year, and she demanded I make a post about it.

Here's the post. Let's see if I get hit with the ball of prophecy.

[reachartwork]

the latest in insane matt mullenweg news

[n7punk]

Tumblr Backup Options: None of them do everything

Cheeky but true. I'll go through what's good and bad about each option though so you can decide which balances out for you.

Covered: native export, WordPress (kinda), TumblThree, tumblr-utils (kinda)

Native Export

If you go to "https://www.tumblr.com/settings/blog/yourblogname", at the bottom of the page is an export option

Once you hit the button to start the request, it will start processing. Feel free to log off, this is going to to take a few hours. You don't need to keep it open. ~22k posts took roughly a day for me. If you have a small number of posts and get stuck, you're probably broken.

When it's done processing, you can hit that download backup button and then wait some more as you wait for the zip file to download. Mine failed the first time after like twenty minutes, and then I had to start over. I think it took 1-2 hour(s) and I'm almost certain that was on Tumblr and not my internet. And that was the zip file! So make sure your computer can be on for a while before getting this started.

So what do you get?

A media folder, conversations folder, and posts folder

Media folder: Every single photo, gif, and video that has ever been on your blog or in your DMs. There is no context data attached (except for dm images which do say which conversation they're from at least), but they seem to be in chronological order because they seem to be titled by the post's ID (the string of numbers in the address bar after "/post/"). They look like "100868498227", "100868498228_0", "100868498228_1"

When you see something end with "_0" and up that means the photos are in the same post, so _0 represents the first image in the post, _1 represents the second, etc (at least, I think).

Conversations folder: HTML export files of every DM history you have on your blog. These are actually pretty well formatted, see example here.

Posts folder: html subfolder and posts_index.html file

posts_index.html: File listing every single post on your blog by post ID on its own line with no other context. Example of a line: "Post: 780053389730037760". The ID number will link to the post in the html folder

html subfolder: contains a submissions subfolder and stripped html file versions of every post on your blog. See below first what the post looks like on Tumblr, and second what the post looks like in the html folder

The way you seem to be intended to use this is to open the file index, select a post ID, and be jumped to where that post is saved as an html file, but I don't know why you would bother when the index doesn't provide any information about the posts inside it. The posts all have extremely minimal formatting. See a reblog chain below.

Notice I said ALL posts on your blog. Photo posts without a caption will just have a broken image icon and then the date and tags. Theoretically, it might be that if you unzip the entire export folder that allows it to automatically link to the image saved in your media folder. I have no fucking idea, unzipping the folder was estimated to take two hours so I didn't do it. Let me know if you do though so I can update this post!

The submissions folder is such a rabbithole I made a post just on it but long story short it's asks you haven't replied to

What do I see as the main reasons to opt for this option? 1) you don't want to download any programs or files from the internet just to backup your blog, 2) your blog is relatively small, so digging through the ID files isn't a big deal, 3) you mostly just want to download either the images (which will be browsable via thumbnail previews in the media folder if you unzip it) or conversation history, which are fairly well formatted, 4) you don't need to update your export often/ever, because you'd have to request it from the start and download the entire thing all over again, 5) you want to be able to read your text posts clearly and don't care about preserving the full formatting, and/or 6) you don't plan to reupload this information elsewhere (say on... a WordPress blog)

WordPress Automatic Ex/Import

Move your post's from Matt's right hand to his left! WordPress (another product of Automattic) has a native Tumblr importer found under your WP Admin dashboard for your site under Tools > Import > Tumblr.

How does this work? No idea! I hit import 2 days ago and it has done nothing. Maybe I'm stuck, maybe it's permanently broken. It says to contact support if it's been over 24 hours but they don't make that easy. I disconnected from Tumblr (you can only port over a blog you have the login of) and reconnected and it still said it was importing. I don't think it's ever going to do anything.

Presumably it's supposed to 1:1 import every post on your blog onto the WordPress site, which will result in a whole lot of stolen art because there's no way to select just your original posts. Also, you'd need enough storage on your webhost to house all the posts (this honestly might be my problem, but I was planning to delete all the non-original posts once it imported.... anything and backfill what it didn't get to). The one thing I'll say about this option is that it's the only one I've seen so far that exports drafts and queues as well.

I mean, if it exported anything. If this ever does anything I'll update this post, but either my blog is too large or this tool isn't totally functional anymore.

TumblThree

(previously TumblTwo, etc)

TumblThree is an all-in-one program requiring no extra downloads beyond the main Zip, and was last updated fairly recently at the time of this post. In order to run it, unzip it into one folder and run the main .exe. It has a full UI interface with lots of very descriptive helper text to help you select the right options for you without looking at the wiki. I think it's user-friendly for non-tech people.

There are a lot of options in TumblThree to change what output it gives you, but I'm going to start with the largely universal parts first:

Everything from one blog will be exported to one folder, no subfolders or sorting. As a result, the output is very messy and difficult to wade through, but post metadata and the photos are named in the same way so you can scroll, see an image preview, and then click on the metadata txt for that post and read the caption.

Depending on your settings, you can export all photos, videos, text posts, etc as their own files or exclude them from the export entirely. For the different types of media posts, you can independently select if you what to download just the media, just the metadata for it (everything that surrounds the post when you see it on Tumblr, such as the caption, OP, tags, etc), or both.

Master txt file: For every type of media metadata you export, a correspondingly named txt file will be created (images.txt, answers.txt, etc) that contains the text/metadata of every post of that type in one txt file. This is also the default behavior for exporting text posts.

Note: for text posts (which includes asks/answers), it only creates a master txt file if you do not select "Save texts as individual files", in which case it will only save each text as an individual txt file and not make a master file.

The formatting on these files is so brutal I won't even give examples, but they're unreadable. Being a .txt file, there is no native formatting, so it exports in html formatting.

Example: instead of a post that says "I want to go swimming", it exports: "I want to go < b >swimming< / b >" (minus the spaces around the b) as the post body, which is a big part of what makes it unreadable, because there are a lot of hyperlinks in all the header information listed below.

Each post in the master txt exports with: Post ID, date, post URL, slug, reblog key (no idea what that is), reblog URL, reblog name, title, [the text/caption itself], and tags.

Theoretically this means you could ctrl+f "cybertrucks" in the master txt file and then browse all your posts making fun of Tesla owners by tabbing through the returns. This is not possible with any of the previous options, and only is possible because it's all in one file, as ridiculous as it is, which is why getting that master file is so important.

For the trick to get both the individual text posts and master text.txt & answers.txt file, as well as my recommended settings and details on how updating backups works, see the read more at the end of this post.

The images.txt includes all the information listed above, but with the following additions: photo url (NOTE: this is the url on Tumblr, not a link to where it is in your folder), photo set URLs, photo caption, and "downloaded files" (NOTE: this is the name of the file it has downloaded)

The video.txt is similar to the above

The use case for this would be similar to what I described for text posts above: search keywords from captions, tags, etc and when you find what you think is what you want, copy the name from "downloaded files" and search your folder to find the actual image

I really hated TumblThree's output the first time I looked at it and then I realized the single file is the only way to make browsing tags workable, because otherwise you would have to have a folder for every tag, and posts with multiple tags would have to be duplicated between them. I'm not pressed on finding a txt to HTML converter right now but it could be an option in the future if you wanted to make things more readable.

Okay, let's get into the non-universal stuff you can customize in settings, because it's like, everything:

File names: We've already established you can search with the downloaded file name for images, but what will that be? Whatever you fucking want. Post date, reblogger name, post ID, post title, original file name, you can make it any and all of these in any order you want! You can have actually useful file names! Personally I like %e_%p_%q_%i_%x which exports as DateTime_PostTitle_BlogOriginName_PostID_IteratingNumber (note: you need some kind of unique iterator to be valid so two files don't have the same name, such as multiple photos from one post). Look how much searchable information that gives me, in chronological order! It decreases your need for the master txt file.

Tip I wish I thought of before doing my massive export: make one of the unique headers from the master txt file part of the exported file name so it's easy to search for it after identifying it in the master file.

Files scanned: this is the only method I've found that lets you back everything up, remember what it backed up, and then lets you add any new posts since that date without having to download the whole thing again. That's a game changer, but see the read more below for limitations.

You also have the option to rescan the entire thing if you want.

Post type: T3 (I'm abbreviating it now) also lets you export just your original posts, just reblogs, etc - again, giving you the most control of any options. It also lets you export replies. I, uh, would not do this because if you have any popular post on your blog it might have hundreds, or thousands of replies but hey, you can do it!

You also have the option to only download posts with a certain tag.

Blog options: You can export literally any blog you have the URL of. In fact, if you copy a blog URL while it's open, it will automatically add that blog to its UI and create an empty folder for it. It makes it easy, no private key required. I do have mixed feelings about the concept of exporting someone else's blog... but I'm also planning to do it to some of Crew-ra's blogs so... my digital horde must grow.

You can also queue blogs up and leave it to run through a lot of them. It is a lot faster than Tumblr's native export, I started this import well after I started typing this post and it took a few hours, probably not all that much longer than just downloading Tumblr's export took (and that's while running it alongside other data copy operations because I'm backing up a lot of stuff right now).

I do recommend doing a test export with a sideblog, I was able to use wild-bitchofthenorthwoods as a test import since it only has one post and it has media, so it was super quick.

(I do want to note, I think the number of downloadable items starts out matching the number of posts on your blog without scanning them until you start the export - but if you choose to export everything as its own file, you're going to end up with way more than that because a post with three images would be multiple files)

Things T3 cannot export:

Since in its simplest form it's just accessing the public upload of your blog, it cannot export your drafts, queue, or conversations

It cannot export posts as HTML files, and thus cannot export them with readable formatting natively

What do I see as the main reasons to opt for this option? 1) you don't care about exporting your DMs/conversations, 2) you want the ability to export only certain kinds of posts (original, photos, using a tag, etc), 3) you want to control the titles of the exported files 4) you don't mind wading through massive folders, 5) you want the ability to search tags (using the txt files), 6) you want the ability to update your export without starting over from the beginning, 7) you either don't want to reupload this information somewhere else, or you want to upload it somewhere that supports automatic HTML conversion (for instance, you can switch a Tumblr post from a rich text format to HTML, same with AO3, so you can put it in as HTML and then hit post to see it turn into a rich format. This techically makes T3 the most versatile/useful export option if you're planning to do anything with it other than browse your own files).

tumblr-utils

Full disclosure: haven't tried this one. But others have! tumblr-utils is a no-UI, python-based backup software. This means in order to use it you have to type commands into the terminal. If you don't know what I just said, don't use this one.

If you do, you'll need to separately download python and youtube-dl just to get this one running. You'll also need to give it your personal Tumblr API key and feed it commands deciphered from the wiki page I linked. Here are two different guides people have written on how to use it. Output:

Obviously I'm guessing based on the documentation, but one thing that is nice is this tool allows you to save each post in its own folder. Presumably each post is multiple files like we saw with T3, so this would make it easy to group them, but it also means you'd have to look in every single folder to find anything.

It seems to break posts up into timestamp folders by month, again, helping with management to narrow down where you have to search

It allows you to save only certain kinds of posts at a time like T3

It allows you to backup posts only from a certain time period (so if you keep a little .txt note of the last time you backed up, you can easily add only the new posts into your backup without having to start over from the beginning)

It allows you to only save posts under a certain tag like T3

It allows you to save only original posts

It's the only one I've found that lets you back up your liked posts

What do I see as the main reasons to opt for this option? 1) you don't care about exporting your DMs/conversations, 2) you want the ability to export only certain kinds of posts (original, photos, using a tag, etc), (okay now we get to the points that aren't also covered by T3), 3) you want posts to export already broken into folders, whether by post or by month, 4) you want to back up your likes, 5) you don't care what file names look like, 6) you're comfortable with the command line/coding and don't need a UI.

Summary:

None of these options are ideal for reuploading your files anywhere (except WordPress), but I do think TumblThree is the best of the options because of the written HTML formatting in the txt files being useful for websites that support automatic conversion (or require HTML input).

For starting another blog, WordPress wins. If it works. I'm trying to be generous here.

For searchability, T3 wins again.

For versatility... yeah you know it's T3, but tumblr-utils has a lot of the same features, too!

For sentimentality (aka conversations), it has to be the native export. There literally is not any other option.

For queues and drafts, the only theoretical option is WordPress. If it works.

For likes, the only option is tumblr-utils.

Every option does something the others don't, so theoretically to cover everything, you have to do all four options. Actually I would say do the native export if you don't have a lot of posts and aren't a freak like me, check it out, and if it doesn't work (I know it's finnicky) or you don't like the export, go with TumblThree. This also means you'll at least have your conversations even if you don't end up using the native export any other way.

And I wish it could go without saying, but don't repost people's shit, y'all. I'm backing up everything for my records only and it will never be shared with anyone else, or even browsed as long as using Tumblr instead is an option.

TumblThree adding to old backup quirks, recommended settings, & master file backup solution:

Adding to backup quirks:

From my tests, when you scan a blog you've already backed up to just add new posts to it, it does not update the master file, so if you want to update it, you'll have to do the steps I list at the end of this post. It might be possible it does update if you force rescan, but I highly doubt it.

If you scan a blog you previously backed up under more restrictive settings - say you only backed up original text posts as one file before and now you've selected to back up absolutely everything - it will only download up until the time you last backed up that blog. It will not blow past where you last downloaded to download all the photos and videos it didn't get before just because they're selected now. This is great for doing after using the master file solution I'm showing below, but if you do need to download everything after doing a more restrictive scan, you can once again follow the first few steps below to do so.

Recommended settings:

This will obviously vary by what you're trying to do, but one or two things weren't immediately obvious to me and I did say I think this was the best solution for less technical users, so I want give my personal recommendations. Settings can obviously be found under the settings button at the bottom of the screen (you may need to use the scrollbar on the UI for, which is separate from the scrollbar on the blogs panel), but when you click on a blog, when you click "Details" in the right sidebar, you can also see your most important settings at a glance and adjust them to whatever you want them to be "per blog". I believe TumblThree remembers what you last used for the blog and applies the things in settings only to new/other blogs.

The thing that is going to vary the most is how many different types of posts you want to back up (text, video, reblogs included, etc), so I'll leave that up to you. If you're going to export a media type, though, I generally recommend exporting the metadata too.

I already gave my preferred file names above and again that's going to be something that varies a lot by people. Hover over the "Filename template" box and it will give you all the options in the legend you can combine via underscores.

Leave "Skip .gif files" off unless you're hurting for hard drive space. This removes all the gifs from your download, and the reason this is provided as a separate setting is because gifs have relatively massive files (at least compared to a text file)

I'll be honest I haven't seen a difference between turning on and off "Group photo sets". Because of the way file names work, most conventions will naturally lead to photos from the same post all being in a row.

"Save texts as individual files": if you only want texts to be saved as their master text.txt and answers.txt files, uncheck this. If you want the individual files I highly recommend you also download the master file for searching purposes, in which case my recommendation is this:

1) Select to export texts only, leaving off all media options, and uncheck the "Save texts as individual files" option. 2) Export the blog. This will only result in two files, answers.txt and texts.txt. 3) Move these files elsewhere on the computer to save them. 4) With T3 closed, delete the folder for the blog and the blog's Indexes (see instructions at the end of this post for finding these). 5) Reopen T3, which shouldn't remember it ever saw the blog and create a new folder for it. Turn on the "Save texts as individual files", as well as any other media posts you want to download. 6) Export the entire blog again. 7) Move the texts.txt and answers.txt file back into the blog's folder.

I leave all other options on the Details tab off, except for:

"Force rescan" scans past the point it last backed up and searches the whole blog again. If you have a big blog, this is going to burn time. This is needed for the number of downloaded items in the panel to be accurate but I don't know why you would care or turn this on unless it lets you skip steps 3-4 above, but my blog is too big to burn through testing that, so if you try it, let me know and I'll update this post!

Master file backup solution:

See my 7 steps from above to skip having to do this, but if you accidentally do things out of order and then realize you still need the master files for texts post after backing everything else up, here's how you get it with minimal pain:

T3 will make an "Index" folder in both the main folder for the program where the exe is located and the destination folder where you have your blogs backing up (note: these were two very different places for me, if you just have it back up to the automatic Blogs folder within T3's folder, it might not create a second Index folder).

To make T3 "forget" what it has backed up previously so it goes through to the beginning and makes a master file that includes everything, all you have to do is remove the Index file(s) for the blog while it's closed so it doesn't remember it anymore. I backed my index up in another folder.

Check off for it to only download text posts, and then uncheck the "Save texts in individual files" option. This will cause it to only create the master answers.txt and texts.txt file on the rescan.

The combination of only going for one post type and only downloading one file for it means this rescan is relatively fast. When you look at your Blogs folder, you'll find a new folder has been created for your blog name (in my case, there was "n7punk" and "n7punk_2) and your output is in the new folder. I just moved it over to the original folder.

At this point you can restore the indexes, though I've only gotten it to half recognize them. I can get it to recognize my original n7punk folder so everything can stay there, but the total downloaded items is stuck at what it was when I did just the text posts. I don't really care, it was mainly the folder thing I wanted to fix. If you have lag between your last full backup and your master-only backup, this might cause some issues? I don't know because I made sure there wasn't lag, so I recommend doing another backup to add any missing items before doing this method.

You can also use this technique if you want to download only your original posts and then download everything else to a second folder. Adjust the setting to only download original posts, download the whole blog, close T3 and delete the indexes, rename the folder to whatever you want ("n7punk_original", etc), and then reopen T3 and set it to download everything and run it again from the start.

[joehills]

Omg I’m on page 24 of today’s federal injunction of WP Engine Vs. Automattic?!

I’ve been following this case for a while, so I was reading this after dinner and was startled to realize I’m in the injunction!

https://www.courtlistener.com/docket/69221176/64/wpengine-inc-v-automattic-inc/

[tinystepsforward]

autocrattic (more matt shenanigans, not tumblr this time)

I am almost definitely not the right person for this writeup, but I'm closer than most people on here, so here goes! This is all open-source tech drama, and I take my time laying out the context, but the short version is: Matt tried to extort another company, who immediately posted receipts, and now he's refusing to log off again. The long version is... long.

If you don't need software context, scroll down/find the "ok tony that's enough. tell me what's actually happening" heading, or just go read the pink sections. Or look at this PDF.

the background

So. Matt's original Good Idea was starting WordPress with fellow developer Mike Little in 2003, which is free and open-source software (FOSS) that was originally just for blogging, but now powers lots of websites that do other things. In particular, Automattic acquired WooCommerce a long time ago, which is free online store software you can run on WordPress.

FOSS is... interesting. It's a world that ultimately is powered by people who believe deeply that information and resources should be free, but often have massive blind spots (for example, Wikipedia's consistently had issues with bias, since no amount of "anyone can edit" will overcome systemic bias in terms of who has time to edit or is not going to be driven away by the existing contributor culture). As with anything else that people spend thousands of hours doing online, there's drama. As with anything else that's technically free but can be monetized, there are:

Heaps of companies and solo developers who profit off WordPress themes, plugins, hosting, and other services;

Conflicts between volunteer contributors and for-profit contributors;

Annoying founders who get way too much credit for everything the project has become.

the WordPress ecosystem

A project as heavily used as WordPress (some double-digit percentage of the Internet uses WP. I refuse to believe it's the 43% that Matt claims it is, but it's a pretty large chunk) can't survive just on the spare hours of volunteers, especially in an increasingly monetised world where its users demand functional software, are less and less tech or FOSS literate, and its contributors have no fucking time to build things for that userbase.

Matt runs Automattic, which is a privately-traded, for-profit company. The free software is run by the WordPress Foundation, which is technically completely separate (wordpress.org). The main products Automattic offers are WordPress-related: WordPress.com, a host which was designed to be beginner-friendly; Jetpack, a suite of plugins which extend WordPress in a whole bunch of ways that may or may not make sense as one big product; WooCommerce, which I've already mentioned. There's also WordPress VIP, which is the fancy bespoke five-digit-plus option for enterprise customers. And there's Tumblr, if Matt ever succeeds in putting it on WordPress. (Every Tumblr or WordPress dev I know thinks that's fucking ridiculous and impossible. Automattic's hiring for it anyway.)

Automattic devotes a chunk of its employees toward developing Core, which is what people in the WordPress space call WordPress.org, the free software. This is part of an initiative called Five for the Future — 5% of your company's profits off WordPress should go back into making the project better. Many other companies don't do this.

There are lots of other companies in the space. GoDaddy, for example, barely gives back in any way (and also sucks). WP Engine is the company this drama is about. They don't really contribute to Core. They offer relatively expensive WordPress hosting, as well as providing a series of other WordPress-related products like LocalWP (local site development software), Advanced Custom Fields (the easiest way to set up advanced taxonomies and other fields when making new types of posts. If you don't know what this means don't worry about it), etc.

Anyway. Lots of strong personalities. Lots of for-profit companies. Lots of them getting invested in, or bought by, private equity firms.

Matt being Matt, tech being tech

As was said repeatedly when Matt was flipping out about Tumblr, all of the stuff happening at Automattic is pretty normal tech company behaviour. Shit gets worse. People get less for their money. WordPress.com used to be a really good place for people starting out with a website who didn't need "real" WordPress — for $48 a year on the Personal plan, you had really limited features (no plugins or other customisable extensions), but you had a simple website with good SEO that was pretty secure, relatively easy to use, and 24-hour access to Happiness Engineers (HEs for short. Bad job title. This was my job) who could walk you through everything no matter how bad at tech you were. Then Personal plan users got moved from chat to emails only. Emails started being responded to by contractors who didn't know as much as HEs did and certainly didn't get paid half as well. Then came AI, and the mandate for HEs to try to upsell everyone things they didn't necessarily need. (This is the point at which I quit.)

But as was said then as well, most tech CEOs don't publicly get into this kind of shitfight with their users. They're horrid tyrants, but they don't do it this publicly.

ok tony that's enough. tell me what's actually happening

WordCamp US, one of the biggest WordPress industry events of the year, is the backdrop for all this. It just finished.

There are.... a lot of posts by Matt across multiple platforms because, as always, he can't log off. But here's the broad strokes.

Sep 17

Matt publishes a wanky blog post about companies that profit off open source without giving back. It targets a specific company, WP Engine.

Compare the Five For the Future pages from Automattic and WP Engine, two companies that are roughly the same size with revenue in the ballpark of half a billion. These pledges are just a proxy and aren’t perfectly accurate, but as I write this, Automattic has 3,786 hours per week (not even counting me!), and WP Engine has 47 hours. WP Engine has good people, some of whom are listed on that page, but the company is controlled by Silver Lake, a private equity firm with $102 billion in assets under management. Silver Lake doesn’t give a dang about your Open Source ideals. It just wants a return on capital. So it’s at this point that I ask everyone in the WordPress community to vote with your wallet. Who are you giving your money to? Someone who’s going to nourish the ecosystem, or someone who’s going to frack every bit of value out of it until it withers?

(It's worth noting here that Automattic is funded in part by BlackRock, who Wikipedia calls "the world's largest asset manager".)

Sep 20 (WCUS final day)

WP Engine puts out a blog post detailing their contributions to WordPress.

Matt devotes his keynote/closing speech to slamming WP Engine.

He also implies people inside WP Engine are sending him information.

For the people sending me stuff from inside companies, please do not do it on your work device. Use a personal phone, Signal with disappearing messages, etc. I have a bunch of journalists happy to connect you with as well. #wcus — Twitter I know private equity and investors can be brutal (read the book Barbarians at the Gate). Please let me know if any employee faces firing or retaliation for speaking up about their company's participation (or lack thereof) in WordPress. We'll make sure it's a big public deal and that you get support. — Tumblr

Matt also puts out an offer live at WordCamp US:

“If anyone of you gets in trouble for speaking up in favor of WordPress and/or open source, reach out to me. I’ll do my best to help you find a new job.” — source tweet, RTed by Matt

He also puts up a poll asking the community if WP Engine should be allowed back at WordCamps.

Sep 21

Matt writes a blog post on the WordPress.org blog (the official project blog!): WP Engine is not WordPress.

He opens this blog post by claiming his mom was confused and thought WP Engine was official.

The blog post goes on about how WP Engine disabled post revisions (which is a pretty normal thing to do when you need to free up some resources), therefore being not "real" WordPress. (As I said earlier, WordPress.com disables most features for Personal and Premium plans. Or whatever those plans are called, they've been renamed like 12 times in the last few years. But that's a different complaint.)

Sep 22: More bullshit on Twitter. Matt makes a Reddit post on r/Wordpress about WP Engine that promptly gets deleted. Writeups start to come out:

Search Engine Journal: WordPress Co-Founder Mullenweg Sparks Backlash

TechCrunch: Matt Mullenweg calls WP Engine a ‘cancer to WordPress’ and urges community to switch providers

Sep 23 onward

Okay, time zones mean I can't effectively sequence the rest of this.

Matt defends himself on Reddit, casually mentioning that WP Engine is now suing him.

Also here's a decent writeup from someone involved with the community that may be of interest.

WP Engine drops the full PDF of their cease and desist, which includes screenshots of Matt apparently threatening them via text.

Twitter link | Direct PDF link

This PDF includes some truly fucked texts where Matt appears to be trying to get WP Engine to pay him money unless they want him to tell his audience at WCUS that they're evil.

Matt, after saying he's been sued and can't talk about it, hosts a Twitter Space and talks about it for a couple hours.

He also continues to post on Reddit, Twitter, and on the Core contributor Slack.

Here's a comment where he says WP Engine could have avoided this by paying Automattic 8% of their revenue.

Another, 20 hours ago, where he says he's being downvoted by "trolls, probably WPE employees"

At some point, Matt updates the WordPress Foundation trademark policy. I am 90% sure this was him — it's not legalese and makes no fucking sense to single out WP Engine.

Old text: The abbreviation “WP” is not covered by the WordPress trademarks and you are free to use it in any way you see fit. New text: The abbreviation “WP” is not covered by the WordPress trademarks, but please don’t use it in a way that confuses people. For example, many people think WP Engine is “WordPress Engine” and officially associated with WordPress, which it’s not. They have never once even donated to the WordPress Foundation, despite making billions of revenue on top of WordPress.

Sep 25: Automattic puts up their own legal response.

anyway this fucking sucks

This is bigger than anything Matt's done before. I'm so worried about my friends who're still there. The internal ramifications have... been not great so far, including that Matt's naturally being extra gung-ho about "you're either for me or against me and if you're against me then don't bother working your two weeks".

Despite everything, I like WordPress. (If you dig into this, you'll see plenty of people commenting about blocks or Gutenberg or React other things they hate. Unlike many of the old FOSSheads, I actually also think Gutenberg/the block editor was a good idea, even if it was poorly implemented.)

I think that the original mission — to make it so anyone can spin up a website that's easy enough to use and blog with — is a good thing. I think, despite all the ways being part of FOSS communities since my early teens has led to all kinds of racist, homophobic and sexual harm for me and for many other people, that free and open-source software is important.

So many people were already burning out of the project. Matt has been doing this for so long that those with long memories can recite all the ways he's wrecked shit back a decade or more. Most of us are exhausted and need to make money to live. The world is worse than it ever was.

Social media sucks worse and worse, and this was a world in which people missed old webrings, old blogs, RSS readers, the world where you curated your own whimsical, unpaid corner of the Internet. I started actually actively using my own WordPress blog this year, and I've really enjoyed it.

And people don't want to deal with any of this.

The thing is, Matt's right about one thing: capital is ruining free open-source software. What he's wrong about is everything else: the idea that WordPress.com isn't enshittifying (or confusing) at a much higher rate than WP Engine, the idea that WP Engine or Silver Lake are the only big players in the field, the notion that he's part of the solution and not part of the problem.

But he's started a battle where there are no winners but the lawyers who get paid to duke it out, and all the volunteers who've survived this long in an ecosystem increasingly dominated by big money are giving up and leaving.

Anyway if you got this far, consider donating to someone on gazafunds.com. It'll take much less time than reading this did.

[sreegs]

the post-automattic tumblr employees (automatticians, iirc) that are publicly posting as staff and trying to argue with tumblr users who vehemently hate the site are so adorable. this is how it's always been. users pretty much hate staff. this is why, in the old days, it was discouraged to identify as staff unless you had the stomach to put up with a bunch of hate mail and arguments.

you're also not going to win over any users by describing tumblrinas as ungrateful for the site's existence, or unreasonably angry over recent changes. you're just gonna look like a 30+ year old engineer taking pot shots at teenagers.

tumblr's current owner (automattic) got some trust back early in the acquisition when they greenlit some changes users had wanted, and ad-free went over mostly smoothly, but any trust you had was shattered with Tumblr Live. The snarky posts from automatticians are making it worse, the worst offender being the person you have running emporium.

this is how tumblr users have always acted before automattic came in and bought tumblr. this is not new. this is why users say things like "staff is out of touch".

y'all need to understand this before you try to snap back at angry users, or before you make vagueposts insinuating the tumblrinas are ungrateful.

maybe examine why tumblr users are angry, what they're angry with, accept they're valid reasons to be angry, and question why these business decisions are being made. like, "hey yeah why is tumblr live still there if everyone hates it?" or "why does moderation seem worse these days?".

then maybe if you understand what's causing the anger when users say "fuck staff" and you'll know not to take it personally. maybe you can take the urge to post snarky replies and redirect it to questioning your bosses' decisions to go ahead with these features that are universally hated

learn, adapt, overcome.

read, comprehend, post.

or just stop posting

[madhattersez]

Oof.

Welp, I was a part of the 16% that was laid off from Automattic / Tumblr this week. On a positive note, I am happy to be able to make time again to be posting on here, and I've really missed using Tumblr personally rather than vastly just behind-the-scenes stuff.

I have a feeling of... "It's good to be home again." Is that weird?

Hi again, friends. <3

[maybetheyregiants]

[unwrapping]

Tumblr's parent company, Automattic, has announced layoffs — about 16% of its employees. TechCrunch is reporting 281 Automattic employees have lost their jobs. It's unclear how many of those Automattic employees are Tumblr @staff.

[netscapenavigator-official]

I mean… if Tumblr is actually dying, then… what’s harm in unbanning porn and porn art? What’s gonna happen?

Worst case scenario, advertisers leave the site, and Mastercard & Visa start blocking payments. The site dies just like it otherwise would’ve. The same outcome, but at least they tried. Now all the Tumblr users know how unsuccessful their pleas for porn actually would’ve been and Matthew is proven right once and for all.

Best case scenario, artists actually come back to the site. The influx of content and users gives Tumblr its positive reputation back and puts it back on the map as the Twitter exodus continues (and TikTok’s second ban date looms). The TikTok-given popularity of the site only increases. Tumblr gets back on its feet. Premium features start selling well because new users have a more positive opinion of the site and are more willing to give it money. Advertises want dash space. Real advertisers. Those good mainstream ones. No longer the porn giant it was in the 2010s, the risk of Mastercard or Visa stopping payments is unlikely. Tumblr finds financial stability and heads toward sustainability.

So the two options are “what was always gonna happen” and “success.” Tumblr quite literally only has room to go up, financially. How Automattic can look at artists on other platforms desiring to return to Tumblr and social media users across the internet constantly being displaced and not try to appeal to them in any meaningful way is beyond me.

You can give the site a new UI all you want. The UI isn’t the problem. The brand image and community trust are. Tumblr can’t expand its userbase because it acted hostilely towards its userbase in the past and continues to do so in many ways, today. Ask any Tumblr user what they think of Tumblr’s management and their opinion is likely negative. That energy and stigma makes its way into the minds of new potential users, too. If Automattic wants to see this platform have success, they’re going to have to repair their relationship with the existing userbase, so they can begin building one with new potential users, as well.

And until artists and trans people feel comfortable on this website, that ain’t gonna happen.

[macmanx]

Automattic confirmed to TechCrunch that when the migration is complete, every Tumblr user will be able to federate their blog via ActivityPub, just as every WordPress.com user can today.

Running Tumblr’s back end on WordPress would allow for greater efficiencies, while not changing the interface and experience that Tumblr’s user base has grown to love.

[tinystepsforward]

okay i am pretty fucking triggered by it but today's "how is there more matt mullenweg shit happening", quite apart from the (comparatively minor) bullshit he himself has been up to today, is learning that he has allegedly trafficked at least one woman

because that's what this sounds like to me

i'm also a bit upset about the tone that the easiest website to find both complaints on takes, where it's all about matt's mother as a gotcha against him. like it's approaching things entirely sideways, in terms of the seriousness of what's alleged by each complaint. it's (unfortunately) par for the course for people caring for the elderly, especially once there's cognitive decline, to be exposed to bigotry. it's not acceptable for there to be money laundering and falsifying arbitration agreements as is implied in those complaints, and it's certainly not fucking acceptable to engage in human trafficking. so like. i don't actually care what this man says about how smart he is or how rude he is on twitter any more. justice for these two women, and may the truth come to light. jesus fucking christ

(also, if you do go look at the complaints: know that there's a hell of a lot of homophobic, transphobic, and incredibly racist content documented, as well as significant sexual harassment. read with care.)

[racefortheironthrone]

According to this article, they're discussing an opt-out model of harvesting data, which is definitively worse than an opt-in model (because a lot of people are not going to go through the logistical hurdles to avoid their stuff getting stolen) and very much a bandaid on a open wound.

Needless to say, everyone should be screaming about this to @staff because the more friction the better, and backing everything up if they need to shut shit down rather than have their work be "legally" stolen by a bunch of Silicon Valley vultures who are all going to lose their shirts in a couple years.

Not exactly sure what Plan B I'm going to go with yet, but needless to say my interest in getting an independently hosted wordpress.org blog (because that's distinct from wordpress.com) and/or checking out Squarespace or the like has just gone way up.