

404 Media co-founder Jason Kepler discusses Proton’s internal push to use AI for software development, alongside reports of a fear-based culture and security tradeoffs. The episode also shifts to Sam’s reporting on the AO3 outage and community fallout, including attempts to create “AO3 clones” during downtime.
Jason Kepler (404 Media co-founder; interviews and reporting on Proton). Sam (mentioned as joining later; AO3 reporting is attributed to Sam, but no further guest bio appears in the transcript).
Proton CEO Andy Yen told staff to “stop thinking” about being slower and called dissent “loser thinking,” urging faster AI-assisted coding and de-emphasizing penetration testing. Employees described public berating and a “culture of fear.” Proton tracked AI usage; CTO Bart Butler said 90% of October code was AI-written. A leaked plan cited underperformance and “insufficient velocity” as reasons to create a “FAST team” and accelerate AI adoption.
Slack exchange where an employee urged pen-testing AI-written code; Yen’s “that’s bullshit and loser thinking” reply. Company-wide “re-interviews” threatened “continued employment,” later canceled after publication.
AO3 went down for weeks after initially being described as maintenance, then as a “security incident.” No deletion was reported, but readers feared loss. Community members shared downloaded works via Reddit/Discord.
AO3.life, a scraped “clone” built with AI agents that charged for AI “audiobooks,” triggered mass takedowns and was shut down after backlash.
Written by AI. May contain mistakes.
Overview of Proton and the context of the AI re-interviews among employees.
“But right now, I'm joined by 404media co-founder Jason Kepler.”
Details on Proton's re-interview process and its implications for staff.
“You want to start there and then we can back into the kind of bigger story that you ended up publishing.”
Exploring the culture at Proton and the fear surrounding AI implementation.
“And of course, when that many people from a company reach out, essentially unprompted, there is obviously something else going on here.”
Discussion on the trade-off between rapid AI integration and security risks.
“as possible in large part because of Andy Yen.”
Insight into Proton's shift towards AI and its impact on company structure.
“And I mean that by the companies trying to secure against these attackers are also using AI.”
Learn about Proton's transformation as it hires for AI development.
“They're actually going to hire engineers at all.”
Explore the irony in Proton's anti-big tech stance while embracing AI.
“So some employees I spoke to had a pretty hard time sort of squaring that circle.”
Discuss insights from leaked documents revealing Proton's internal culture.
“But this document, talking about AI in part, and also the creation of the FAST team, says that Proton, due to insufficient velocity, it is not on track to meet its annual recurring revenue target by the end of the year.”
Hear about employee reactions to the leadership's handling of company changes.
“It's definitely not unprecedented, but it's not great.”
Understand the fallout from the published story and Proton's subsequent actions.
“For me, the more interesting fallout of this is that Proton then organizes an all-hands meeting on Friday, I think a day after we publish this.”
Delve into the implications of Proton's internal AI manifesto and its context.
“The other thing is there was this interesting arc where people were like, this is crazy, I'm canceling Proton, that sort of thing.”
Discussion about employee concerns regarding workplace conditions at Proton.
“And I mean, I think it's also just like, I don't know, the loser talk is like, I know that we've kind of gone back and being like, oh, we're being aggressive again with our employees and stuff.”
A detailed discussion on the Archive of Our Own's downtime and its impact on the fan fiction community.
“We're going to be talking about the AO3 shit show.”
Explore how fanfiction writers and readers are coping with the AO3 outage.
“And then NaNoWriMo is formerly, formerly known as NaNoWriMo.”
Discuss the effects of the outage on authors and their audience in the fanfiction community.
“Like obviously, it's like November is a time where people challenge themselves to write every single day and finish a whole novel or just to write a lot during this month.”
Examine alternative platforms fans are considering while AO3 is down and their feelings towards them.
“with still like with their connections that they've made on as talking to them there and of course Reddit has like the AO3 subreddit has like a mega thread of people sharing updates, sharing drives.”
Discuss the controversial AO3 clone site and its impact on the fanfiction community.
“And I'm like, I remember Wattpad being the thing that you did and also being shitty and like a joke.”
Reflect on the implications of the AO3 outage and its impact on ownership and community response.
“I think that this is something that we have seen AI enable ever since like Shrimp Jesus, et cetera, where I was writing about how people were latching onto these American conversations.”
Explore the 18-year journey of AO3 from beta to official launch.
“It's links, it's Drive links, it's Google Doc links that they're, I think, trying to be transparent and saying, hey, this is where I got this stuff from if your work is in here and you're curious.”
Discussion about the upcoming subscribers-only section of the podcast.
“And when we come back, we are going to talk about my story in the subscribers only section.”

Get the gist, explore an idea or ask about something said.
On The 404 Media Podcast, what are the key points of this episode?
Automatic transcript. May contain errors.
0:00Sam: This episode is brought to you by Indeed. You're ready to level up your business, but the pressure to find the right person to make that happen is intense. Indeed Sponsored Jobs can help carry the load. It boosts your job post to help it reach quality talent fast. Cut through the chaos with Indeed Sponsored Jobs. Get a$75 sponsored job credit at Indeed.com slash podcast. Terms and conditions apply. Hiring now? Then this is a job for Indeed Sponsored Jobs.
0:34Hello, and welcome to the 404 Media podcast, where we bring you on the parallel access hidden worlds, both online and IRL. 404 Media is a journalist-founded company and needs your support. To subscribe, go to 404media.co. As well as bonus content every single week, subscribers also get access to additional episodes where we respond to their best comments. Gain access to that content at 404media.co. Also, do remember to subscribe to our YouTube channel where you can watch all of our episodes. Subscribe at youtube.com slash at 404media.co. I'm your host, Joseph. Sam will join us in the second section.
1:16But right now, I'm joined by 404media co-founder Jason Kepler. Hey, what's up? We are going to be talking about your banger of a story and series of stories. So I will read the title and get into it. The main story that we're talking about is called Manifesto's Fear and Loser Thinking Inside Proton's AI Reckoning. This is a story about Proton, which is the Switzerland-based cybersecurity company. They make ProtonMail, they make ProtonDrive, they make some authenticator apps, They make a few other security-focused products like a VPN, for example. And I feel like this was a big investigative feature that sort of started with a smaller story that you did about Proton wanting to re-interview employees to see if they were using AI properly.
2:11You want to start there and then we can back into the kind of bigger story that you ended up publishing. Yeah, so last week, I think on Monday, Proton emailed its staff saying, hey, we are going to hold these re-interviews essentially company-wide. And those interviews would be about how are you using AI, what you're using AI for, how do you want to use it in the future. But the clear implication was that if you don't do well in these interviews, you might lose your job. The email specifically used the phrase, quote, continued employment. So that obviously rattled quite a few Proton employees.
2:52One reached out to me, showed me a copy of this email. And then I published that story somewhat quickly on Monday. On Tuesday, I received messages from many, many more Proton employees. I think in the end, it was something like eight current Proton employees and one former one as well. And of course, when that many people from a company reach out, essentially unprompted, there is obviously something else going on here. And I mean, what we found is way, way more than I expected or anticipated from the initial emails about the re-interview process. Yeah. So you basically ended up with this unprecedented look inside Proton, which is a company I have known for a long time and used some of their products and that sort of thing.
3:45So I've been very familiar with it, but I haven't been super familiar with how it works on the inside. and I think one thing that really stood out to me is like this is probably happening to some degree at a lot of software companies right now where there's this big shift to AI and there's some people who support it and some people who don't what I thought was really interesting about this is that it's about a security company where obviously like AI is changing cyber security but also still AI if you're pushing vibe coded code and that sort of thing there could be potential security issues with you know rushing and so you start off with this anecdote that I thought was like pretty alarming you want to talk about how the story starts out yeah and I chose this exchange which happened on Proton's internal slack for that exact reason in that I mean we'll get into the comments from Andy Yen, the CEO of Proton later, and the culture affair and all of that.
4:45But I chose this one because it does seem to be specifically talking about the security of Proton. And of course, as a privacy and security focused company, that is Proton's currency, the trust that its users have in the security of this product. And I say that as someone who's obviously used Proton since it launched way back when after the Edward Snowden revelations as well. So there's this conversation in Slack towards the end of August, and they're talking about using AI to write code. And one employee in this exchange is urging the company, hey, this at least take a few days to pen test newly written code before pushing it live.
5:29Pen test meaning penetration testing, as in you do some sort of offensive tests to figure out, okay, this is free of not just bugs, but free of security vulnerabilities as well, a very standard and important part of writing secure code, especially for a security company. To that sort of urging, Yen replies in Slack, quote, that's bullshit and loser thinking. Of course, it's possible to be fast and secure. Yen then goes on to say, quote, stop thinking always of how to be slower and focus more on how to be faster. He reiterated that, you know, thinking like this, or rather having those thoughts, only losers think like that.
6:11And he told his team, ultimately, stop lovingly handcrafting all our code and use AI more. And that's obviously one anecdote, but it was a constant theme throughout the Slack messages and the other documents I got as well that this company is barreling towards AI use and trying to do it as quickly and aggressively as possible in large part because of Andy Yen. Yeah, so I think that there are basically two things going on here. There's like a company that is trying to transform itself into an AI first company, which a lot of software companies are doing. A lot of cybersecurity companies are doing.
6:54a lot of just companies in general are trying to do this. But then you also have maybe the world's not best communicator. You have the tone that this is all taking and the culture of fear that's described to you where people are afraid to talk up about their concerns with Andy N because he berates them and often in public. So I think let's start there and then we can talk about the pivot to AI and then we can like sort of tie it all together to see if these two things are connected or talk a bit about the response to this. But what did employees describe to you and what was the tenor of these some of these Slack conversations?
7:38Yeah, I mean, just to keep it on those Slack chats, because it's actually part of the same conversation. You know, another employee, I think, adds that, quote, AI won't magically solve our problems because security is low in our prioritization at present. Yen doesn't respond to that directly, but then he goes to insult one of the employees again, saying that this person is, quote, saying his usual BS of we can do it, we'll be even slower than we are today. And I'm saying only losers think like that. He said that simply the engineers should prompt better. And this is the vibe that you get from Proton, both from reading the Slack messages, but then also talking to people inside the company, that if you post something or say something or hold a belief that Yen doesn't like or doesn't want to hear, there's a very real chance that you are going to be berated, mocked, belittled, whatever, in front of basically the entire company.
8:37This conversation that happened at the end of August, that was in the public security channel, which is basically accessible to anybody inside Proton. The way that other people described it to me was that, you know, it's 100 % a culture of fear. It is very unusual for people to speak back to him. And in the end, at least for some employees, they just shut up and they get on with their work, you know, like they don't want to have to deal with this sort of thing. So you have that chat. And then also with the re-interviews we mentioned, they come up again, sort of in this context. Someone says that, you know, maybe this isn't the best way of going about it, of emailing everybody in the company and saying like, you may lose your job at this re-interview and that sort of thing.
9:27Yen was pretty blunt in the response in Slack. He said, quote, let's put it this way. We already know more or less who is behind. If we're going to give up on them, we will not bother with this process. This employee then replied, the messaging is fear-based, which is probably why I suspect there are dozens of other employees watching us talk about this live, except for one other employee, and no one else is chiming in. They continued, people shouldn't be scared to talk about this in public and to push back on you and leadership. A fear-based culture feels like a cancer to me it is the opposite of engineering you need to talk about things even uncomfortable things and that was very unusual in that not only was someone talking back to yen but it explicitly referenced this culture of fear that i had actually already heard about from you know another couple of sources and then when i got more and more information about this i kept going to you know this nearly 10 sources in the end right and asking them do you think there is a culture of fear?
10:26If not, how would you describe it? And the vast majority were like, oh yeah, absolutely. This is what is like living inside Proton. Now, as a journalist, I've seen a lot of crazy Slack chats from CEOs. We did a bunch of reporting on the Citizen app. I've seen all of that stuff before. I'm more interested in the impact of this sort of culture and these messages. And here, it's interesting because it is explicitly about security, where these people do have reservations about, well, if we're using a ton of AI and we're not doing proper code review or anything like that, that could actually theoretically impact the Proton product and the security of it.
11:09And that's what's most interesting to me is that, yes, CEOs and founders can be really, really abrasive people. We've seen that a million times. This is that, but also the security element as well. Well, I think so. I think so. But also, when calling people losers, that sort of thing in front of each other is not good. And what it leads to is this culture of fear that's described in the piece. And then in that same Slack, there was one other employee who spoke out and they said, it's about the culture you instill people don't want to feel like they're on a tightrope and yes we understand you want to move fast but there needs to be a balance people also need support not everyone is the same and I think that is that's about security and the culture and also this culture of fear that I think comes back to security because what people are talking about here is they are afraid to speak up saying that if we're moving too fast, we may be sacrificing security.
12:08And that is a conversation that at least your sources and people in the Slack feel is not being had. And that's a conversation that's happening across all of Silicon Valley right now. I mean, this is a Swiss-based company, but a tech company is like, what is the trade-off between speed and efficiency and writing code very fast and patching things very fast? because you're in this space where a lot of attackers are using AI, a lot of AI defenders. And I mean that by the companies trying to secure against these attackers are also using AI. But if you move too fast, you might introduce new vulnerabilities and that sort of thing.
12:51And that seems to be some of the concern here. And this all sort of comes alongside of this broader shift into AI at Proton. Let's talk about some of the other things that they're doing. And then we can talk maybe more about how these two things are related. So basically, how do we know that Proton is so interested in AI-ifying how it works? I mean, a big part of it is Yen's comments, but it's not just that. It's the actual actions that the company and Yen has taken. So recently, he set up an email address for employees to contact. And I think that goes directly to him and some other people in leadership as well, in case they come across anything blocking adoption of AI or Proton.
13:33So leadership can, quote, ruthlessly smash everything that stands in the way of AI philosophy. Proton did install software that tracks sort of AI usage across the company. And then Bart Butler, the company's CTO, said that in October, 90 % of the code inside Proton written that month was written by AI. So this is absolutely happening now. Yen says this is like the last year. They're actually going to hire engineers at all. Instead, it's now going to be hiring people to build stuff with AI instead. So this transformation is already happening, at least by the use of AI and that sort of thing. It's now really come to a head when the company is re-interviewing these employees.
14:23And then you take that with all of the security concerns as well. that some people have raised, it's like, oh yeah, they really are super aggressively trying to bring up this technology. And some of the employees I spoke to brought up this, I guess, somewhat irony in that Proton positions itself very much as anti-big tech. Of course, anti-Google, which provides Gmail, email service. Proton provides an end-to-end encrypted alternative. But when it comes to stuff like AI as well, They have their own privacy-centric LLM that doesn't train on your data and apparently doesn't log your queries and that sort of thing.
15:04At the same time, they are spending, it appears, a ton of money on Claude as well. So some employees I spoke to had a pretty hard time sort of squaring that circle. But I think really it's more for customers of Proton. What Proton actually is inside and what it's doing, I think is really, really different to people's public perception of this omnipotent, all-caring, benevolent organization. It's not. It's a tech company that is really, really aggressively leaning into AI. Yeah. And there's a pretty interesting interview that Andy Yen did with Andy Greenberg at Wired a few months back, where he talks about how the backlash to Google, like Gemini and AI overviews and all that sort of thing has been an opportunity for Proton.
15:59He definitely doesn't say like, I'm anti-AI, but he is very much like I'm anti-big tech AI. And that's very much on the record, this pretty big interview he did a few months ago. You also got another document that That maybe gives a bit more insight into why this company is so aggressively pushing AI on its employees. Maybe even more so than other companies that are like, Oh, we need to just do AI. There's a specific reason that Proton is pushing this way. Yeah, this was probably, I think, the most interesting leak I got. Of course, the CEO comments are very, very interesting. And they do paint this horrible, horrible culture inside the company.
16:39but this one sort of explained the why behind it. And it was a document laying out Proton's intention to build what it calls a fast team, which is sort of a smaller group of employees who will get paid a little bit more in a bonus. They'll have other benefits as well. There are some questions about how this sort of gels with Europe's labor laws, especially, especially when it's asking these people to ask many, many more hours as well. I'm not a labor lawyer, so I'll sort of leave that to the side. But this document, talking about AI in part, and also the creation of the FAST team, says that Proton, due to insufficient velocity, it is not on track to meet its annual recurring revenue target by the end of the year.
17:28Its year-over-year growth is also, quote, far away from what the market today considers to be good, end quote. and another quote at the end that kind of sums it up. By all metrics that matter, we're an underperforming company. I think a lot of Proton users will be shocked that this is how Proton is talking. It gives the image of a company that is just here to provide privacy for its own sake, for its human rights value or whatever it might be. But inside, no, it is a cold, calculated business. And I'm not even saying that's a bad thing, necessarily. I'm just saying the reality is that it's a business.
18:12It knows this. It says this out in this document. And it lays out very, very clearly, we need to make these changes to our structure. We need to make a fast team. We need to use AI because we need to make more money. which I know it's a little strange because it isn't really, you know, succumb to the normal pressures of investors and that sort of thing. It's owned by the Proton Foundation board with people like Sir Tim Berners-Lee on there. Andy Yen is on there as well. The majority owns Proton. But it's not like, as far as I know, a bunch of, you know, VC or private equity investment or anything like that.
18:52So there's still a question to me about why this pressure. But as they say in black and white in this document, that is the reason that they're really pushing for this AI, at least in part. Yeah. So let's talk a little bit about the fallout from this story. I knew when I was editing it, it's like this is a big story because you kind of rarely get such insight into how a company is transforming. And then also, frankly, it's like the CEO yelling at his employees in front of people on Slack and things like that. This is not how most companies behave. It's definitely not unprecedented, but it's not great.
19:36We've seen this before. And usually when there's things like this, it's like, this is not usually the best way to lead a team. And so we published the story. Well, you reach out to Proton. They give you a statement. I thought they give you a couple of statements. I thought that their final one before we published was quite interesting. And then their response after we published was also pretty interesting. Yeah. So I send them one request for comments. They give sort of a normal-ish statement, sort of just acknowledging what is going on. But then the second one where they didn't dispute any of the reporting.
20:12And I'll say that you don't send a copy of the article to them beforehand. That would be deeply inappropriate, just for people who don't know how this works. You send them a very detailed list of, we are reporting that Andy Yang said blah, blah, blah, blah, blah, or that security is being deprioritized. Is this accurate? Blah, blah, blah, blah, blah. And you give them an opportunity to refute any of that or provide sort of counter evidence, and they didn't do any of that. Instead, what they said was that, quote, it's clear that some people at Proton are unhappy with our direction or misunderstand it, and many people are anxious.
20:47In our determination to move fast, we have sometimes been too blunt or too slow in explaining ourselves to our people. We will work on that as their questions are the ones we most need to answer. I mean, obviously, that's a veiled reference to Jens' Slack messages, right um but we get that statement we publish then i mean it's hard to kind of sort of keep up with all of the fallout the proton's official account got on reddit uh and then said kind of the same statement and yen got on reddit as well and said some of the slacks were taken out of context and then you read them as i know they're perfectly in context he gets downvoted like more than a thousand times or something.
21:31There's all of this stuff and all of these discussions going on and all of that sort of thing. I'm not really interested in that. For me, the more interesting fallout of this is that Proton then organizes an all-hands meeting on Friday, I think a day after we publish this. Obviously, I get audio of that meeting. I speak to six employees who are in that meeting as well. and Yen announces that they're cancelling the re-interviews. And the reason being, according to Yen in this meeting and the audio I listened to, is that, well, they've already served their purpose. Because now that we told everybody we're going to re-interview everybody, you're all thinking about AI now.
22:14So it's actually served its purpose. I then spoke to a ton of other employees about their reaction to this. And, you know, a couple were like, hey, this is progress. This is something. Maybe this is the end of the story. Others were, I think, pretty dismayed and, you know, pretty beaten up about there should have been more accountability for Yen. Nothing has really changed. This culture is still going to be here. Like that doesn't just evaporate overnight, right? But the re-interviews have been cancelled. We'll see what happens now. But the message from Yen in that meeting is still, we are going ahead with this plan.
22:54He even mentioned new reorgs and that sort of thing. We'll see what happens there. But yeah, it was a very sort of crazy couple of days in and around Proton, I think. I want to talk briefly about some of the arc of how this has gone after publication. Because one, it is very rare to see a company put out a statement like that, where they were like, it's clear that there's anxiety within our company and that sort of thing. That has been... It's been a while since I've seen something like that. Proton itself is not disputing any of our reporting or the characterization of it or any of that. And them just being basically like, we need to listen to our employees.
23:39It's pretty... I'm not saying that they have done the right thing necessarily. That's up to the employees who work there and that sort of thing. But it is interesting to see a company that didn't really take a combative tone or ignore it. They did address it publicly, which I find to be increasingly rare these days. The other thing is there was this interesting arc where people were like, this is crazy, I'm canceling Proton, that sort of thing. And then there were a few Reddit posts and tweets that you don't need to talk about, but I'll talk about, where it's basically like proton employees saying, this isn't the company that I know.
24:21I feel like people have taken this either out of context or blown it up beyond what it's supposed to be. A lot of people in Silicon Valley and AI executives and tech COOs and things like that have looked at this AI manifesto that you published and said, there's nothing wrong with this, that sort of thing. All tech companies are adding AI features, are imploring their software developers to use AI, are fighting against AI threats, that sort of thing. And I understand why people who like AI and are developing and changing their own companies are like, well, you have to move fast. That's how things need to go.
25:11So, but they're also like ascribing something to our article that we never said and never reported. It's like, this is a complicated story with a lot of different sourcing in it. And so this AI manifesto that you published, that was published internally at Proton that we obtained and then we republished, we didn't publish that thinking like, oh, this is a crazy smoking gun. And this shows that this company is asking its employees to do crazy things. We're doing that so people can read the fuller context of how these changes are happening. The fact that there was an internal AI manifesto published isn't a scandal.
25:58And we didn't pitch it as a scandal. But the fact that the CEO of the company is calling people, asking to push the brakes like losers and bullshit thinking and all of this sort of thing, that's super relevant. And so we publish all these different anecdotes and parts of it. And you need to read the full article and understand it to have a clear view of what's happening here, I think. And I think that once something goes viral like this, people pick out one little part and they say, oh, well, this actually didn't have anything to do with security or this manifesto wasn't that crazy. And why are they calling it a manifesto in the first place?
26:41It's like, well, he called it a manifesto. I should... Yeah. For those who haven't seen it, the manifesto was written by the CTO, Bart Butler. And it reads like everything you would expect. where somebody says, LLMs are coming for your jobs, it's going to be your responsibility as an engineer to oversee LLMs. Stuff that we've seen, the language that we've seen from lots and lots of other companies. But it's notable here, as you say, not because it's in a scandal in its own right. And I did see plenty of people taking that. Frankly, people who, I don't know, don't have the brainpower to read a 3 ,700-word article, probably.
27:25But this manifesto is important because it puts all of that other stuff into context. It puts the rushing into context. It puts the apparent deprioritization of security into context as well. It puts Jens' comments into context as well. So I don't know. I think it's pretty good that we obtained a manifesto. And I spent a lot of time retyping it to publish it so people can see for themselves. But you're right in that. But that's just a feature of investigative journalism where people will pick just a paragraph or something and be like, oh, this is the story. This is the whole basis for the story.
28:03It's like, it's not, man. Try reading a whole thing. Yeah, exactly. And I mean, I think it's also just like, I don't know, the loser talk is like, I know that we've kind of gone back and being like, oh, we're being aggressive again with our employees and stuff. But it's just not a good workplace environment to be subjected to that sort of thing. And so it's relevant. It's relevant for this big company for people to know that's what it's like inside. And you can make your own conclusions from that. But it's like, at least for some of the employees there, they say that they feel like they have real concerns with how this company is operating and feel like they can't say anything about it.
28:55So the fact that then there's a few employees who are like, actually, I'm happy here. That's kind of how it goes at any big company. It's like there's going to be some people who are happy, some people who are not. I don't think we really blew anything out of proportion or took anything out of context. There's lots and lots of context in the article. Yeah, absolutely. The last thing I was just saying is like, I touched on this, but when eight or nine people reach out to you from a company, that's not nothing. You know, like clearly people have real concerns to the point where they're going to reach out to a journalist.
29:33Many, many of them are going to do that. That's a lot. It is a lot. Justin, I mean, it's like maybe eight or nine people is not a lot for a hundreds or thousands of person company. Like, yes, there are many employees at big tech companies, but it is rare that eight or nine are willing to talk to you about this thing and serve as sources. Like two tops normally. Yeah. Yeah, yeah, exactly. Yeah. All right, we'll leave that there when we come back after the break. We're going to talk about one of Sam's stories. We'll be right back after this.
30:09The thing about hosting for the holidays is that people are actually coming over to your real house. You can't just blur the background like you're on a video call. At some point, you have to clean. Blueland makes household cleaning products designed to reduce single-use plastic, including dishwasher tablets with a plastic-free, microplastic-free formula. They tackle baked-on, burn-on stains with no rinse aid needed. Put one in the main detergent dispenser and run the dishwasher as usual. They also have a limited edition Holidays at Home hand soap kit with brown butter, rosemary, mint, and mulled cranberry scents.
30:43It makes 10 full bottles of foaming hand soap. Fill the reusable bottle with water, drop in a tablet, and let it dissolve. I've been using Blueland for the last few months. And honestly, I love having made the switch from the less environmentally friendly competitors. I really like Blueland's detergent and their dish soap, as well as their dishwasher tabs. Blueland is a certified B Corp and Leaping Bunny Cruelty Free certified. Their formulas are EPA Safer Choice certified, and many products have also earned Cradle to Cradle's Gold Material Health Certificate. Blueland has a special offer for 404 Media listeners.
31:18Right now, get 15 % off your first order by going to blueland.com slash 404. You won't want to miss this. blueland.com slash 404 for 15 % off. That's blueland.com slash 404 to get 15 % off. Maybe you've had this experience like I have. There's a specific panic that happens when you successfully ask a question in another language, and then the person answers. You've spent minutes rehearsing your one sentence that you know, and then they're under the impression that you can now have an entire conversation. This used to happen to me all the time. I would think, okay, how do I ask this question? I ask it, and then I don't know what to say after that.
31:55That's where Babbel comes in. Babbel is built using the real conversations you need. Ordering food, asking for directions, actually understanding the answer. Babbel is designed by more than 200 language experts with lessons focused on words and phrases people actually use. And the lessons are short enough to fit into a coffee break or 10 minutes just before bed. People who use Babbel just 10 minutes a day can start having real conversations in a new language in as little as three weeks. There's also a 14-day money-back guarantee. I've been practicing Spanish for a lot of years. When I picked Babbel back up, my Spanish got so much better just from a few lessons.
32:32I really like their podcasts. I can listen to them while I'm walking my dog. Go to babbel.com slash 404. Start learning a new language today with Babbel. Right now, listeners can save up to 60 % off at babbel.com slash 404. That's babbel.com for up to 60 % off. Rules and restrictions may apply. So for fun, I googled myself last week and found my home address, my phone number, and a relative I'm fairly sure I've never met, all on directory sites I never signed up for. That's the data broker economy. They scrape your info, package you up like a trading card, and sell you off to whoever's paying, which is exactly how identity thieves go shopping.
33:13Bad look when your entire job is not getting doxxed. That's why we use Incogni. Instead of you spending hundreds of hours filling out opt-out forms across 40 browser tabs, Incogni gets to work by sending legal removal requests to over 420 harmful data broker sites. It's independently verified by Deloitte, resubmits requests every 30 to 60 days as brokers try to quietly relist you, and you can track every request right from the app. On the unlimited plan, the exposure scanner digs up the weirder stuff across the wider web, like old forums or random blogs or obscure directories. It surfaces all your exposed profile links right in your dashboard, where you simply select which links you want taken down, and Incogni's team of human privacy experts will handle the manual corporate takedowns for you.
33:59Take your personal data back with Incogni. Use code 404media at incogni.com slash 404media to get 60 % off an annual plan. That's incogni.com slash 404media. They can't harm you if they can't find you.
34:14Okay, and we are back. We're going to be talking about the AO3 shit show. Sam has done a handful of stories about this. It is the massive fan fiction site Archive of Our Own. Let's start from the beginning because the story has evolved quite a lot. But what is Archive of Our Own and what happened last week?
34:35Sam: So it was on Thursday, early Thursday. the Organization for Transformative Works, which is a nonprofit organization that owns Archive of Our Own, posted on its status page that it was down for site maintenance and it might be a couple hours. And then a few hours later, it updated and said it was going to be at least 12 hours. And then by the afternoon, it said it might be around two weeks, but could take up to a month, which is not ever what you want to see with a status page, that they are updating it to be longer and longer as the updates roll in. I guess if you're not familiar, just to back up a little bit, Archive of Our Own is a fanfiction repository.
35:14Sam: So if you're writing fanfic, you are going to Archive of Our Own more than likely to post those works. If you're into reading, you know, whatever, whatever kind of fanfic that you're into, you're probably going there. and it's huge. It's like 18.5 million works are on Archive of Our Own, which is crazy. I didn't actually even realize before I started writing this that it was that big and it was big, but like 18 million is so much. 82 ,000 fandoms and counting is what it encompasses. I also, I went on there not that long ago because you're writing about it somewhat regularly. And so I was like, what does AO3 look like these days?
36:01And I went on there. And as someone who is not a consumer of fanfic, but has used many websites, it's a very complicated website. It's just like there's so much going on there. As you said, there's just millions of works and parsing through them and figuring out what is where I found to be quite difficult. But maybe that's because I'm a Rube. I'm not sure. But it's just like a big sprawling website with tons and tons of content on it.
36:32Sam: Yeah, it's definitely... I mean, it's huge. It's daunting. There's just the scale of it is so much. It's not even complex. It's just kind of like if you're in a fandom, you eventually know or get the learning curve pretty quick that the tagging system is a lot. So if you're into a certain kind of fanfic, you'll tag... like it's almost like inside jokes in some cases. Sometimes it's very straightforward. You know, it's like enemies to lovers. If you're into that, you're reading that tag or you're into like Hermione, which is Draco and Hermione, which is a really popular one. Pacific Rim is really popular, which I didn't know until recently.
37:10Sam: People are doing a lot of Pacific Rim. That's wild. I had no idea. I'm kind of like after this, I'm like, I need to get into it. I'm also kind of a casual. I've been on the site. I've read the site on my own quite a bit, but I'm not like following any specific work. or author. So after this, I'm kind of like, maybe I should jump in there and see what's up. But it feels a little scary because people do get obsessed. People get really into it. And that's why people are reacting very emotionally to this. I also, I want to, I guess, before we get even further into it, when I was on there, I was like quite astounded by the length of some of these stories.
37:46Like we're not like many of them are book length or frankly, probably like need an editor. They're longer than book length. They're like anthologies in some cases. We're talking hundreds of thousands of words. And so this website's been around forever. It predates generative AI. I imagine that they have had some battles with AI on the site, which maybe we can get into as we talk about how the story evolved. But basically, site goes down. Do we know why it went down. Site maintenance is so vague. And for such a long period of time, this seems like a pretty extreme thing to have happened.
38:28Sam: Yeah. So eventually, they did say, I think it was Friday, early Friday morning, they said it was a security incident. It wasn't maintenance. I think everyone knew it wasn't maintenance pretty immediately because it's like maintenance is something that's scheduled. They do it over time. The site doesn't go completely down usually for weeks during maintenance. It was a security incident, but they haven't said more than that. I'm sure it's tricky to say more than that right now because I don't know. It's like, what if it was a hack and stuff is still in process, but they announced that it was a security incident, but nothing had been deleted.
39:01Sam: So no data had been deleted. I think that's something that people were really worried about initially was like, oh my God, did we just lose? I hate the Library of Alexandria comparison that everyone does, but this would be the most apt example of losing the Library of Alexandria online. All the slash fic is gone. Yeah, exactly. It's like, where am I going to get my Twilight slash fic? There's VeggieTales slash fic, which is in the most recent story that I wrote. So that's exciting. But it's a lot of writing. It's a lot of work. It's a lot of human creativity, which I think, as you mentioned, it's like, I'm sure AI has tried to get in there, but it's pretty well maintained.
39:39Sam: It's all volunteer run. So they're pretty on top of this stuff, but it's also, it's impossible to monetize anything on the site. So there's not a reason like there would be on Twitter or X, I guess, or like any like Instagram to flood it with your AI trash because there's no way you're going to make any money doing that because you can't monetize, in most cases, fan fiction because it's someone else's IP. You can write it, you can produce it open, you know, freely, but you can't make any money off of it, which is something that they are very strict about. So I wonder if that's kept AI from really infiltrating the site over the years.
40:18Can I read a sentence from your first story about this and you can tell us what it means? Because the timing of this is quite bad. There's not that there's ever a good timing for this, but you write, the status update means AO3 is expected to be down during much of Hoa Hoa Hoa season, most of Aquatar new book release week and on the cusp of the month, formerly known as NaNoWriMo. Okay, let's go one by one. What is ho-a-ho-a-ho-a season?
40:47Sam: So that's like... There's a song in Twilight, which I was just listening to the other day, where the song is like, ho-a-ho-a-ho-a-ho-a. It's like... It's a noise from Twilight that became a meme. And Twilight is very popular. Twilight, I think, probably was a fanfic originally. It was like a Harry Potter-related spinoff of some sort, right? It was... I'm blanking on... Sorry if we're wrong. No, it's... Fifty Shades was a fanfic of Twilight. Did not know. Did not know. So, yeah. I mean, obviously, Fifty Shades got extremely monetized. But, you know, E.L. James really took that one the whole way.
41:37Sam: But it was a transformative work of Twilight originally. originally. So that, that's that one. What was the next one? Akatar. Akatar, A-C-O-T-A-R. Yeah. Akatar is a court of Thorns and Roses, which is a series that a new book just came out last week and it was huge. It's like people were like lined up outside of stores to do like, and there were like book parties and book release parties. And there's a ton of fanfic about that. It's like a romanticy book. And then NaNoWriMo is formerly, formerly known as NaNoWriMo. NaNoWriMo is National Novel Writing Month, which used to be November, but NaNoWriMo shut down last year and has not returned.
42:20Sam: So it was like, NaNoWriMo was like, you write a book in a month. And that was kind of like the goal. And it's also, I didn't include this in the first story, but it's, it also happened at the very end of Kinktober, the climax of Kinktober. So Kinktober is the month of October where you get a prompt that's like a kink prompt and then you incorporate that into your like original content and your fanfics have to follow that kinky prompt so people were like rushing to finish their kinktober works when this happened they were like about to post a bunch of works that were on a theme and it went down then and people were kind of like um people were saying that maybe it was because because people hated kinktober that it was hacked or a lot of people said php was the reason but archive didn't run on Like PHP, it's on Ruby on Rails.
43:07Sam: So it wasn't that. So it's kind of a mystery right now why anyone did this. Yeah, but I've seen people doing NaNoWriMo still. Like obviously, it's like November is a time where people challenge themselves to write every single day and finish a whole novel or just to write a lot during this month. Okay, so you spoke to some folks on Friday evening. We published this pretty late. The article is called Wake Up Call, Fan Fiction Writers and Readers React to AO3 Outage. We just talked a little bit about what happened, the specifics, but where has this all left to the fan fiction community of both writers and readers?
43:51It's like, are there alternative places? What's happening with... If I want to access my favorite story, what do I do? How are authors reacting? What's going on?
44:03Sam: I mean, right now, the primary thing people are doing is sharing drives and files on Reddit and Discord of works that they had downloaded. So it's stuff that they don't own, or they were just like fans of, or they had a collection of that they had downloaded. In cases of something like this, it's like you kind of, you save it just to have in your own collection, not necessarily to like publish yourself. But people are doing that, which relates to the story we published this morning. But before we get into that, people are like, people are, I don't know, there's, it's kind of hard to, to tell between like the like overblown, like, oh my God, my fanfic kind of reaction and like actual serious authors who actually have like really big followings on AO3 and are writing like releasing chapters on like a schedule or like people are waiting for their next installment of something.
44:54Sam: um so i think people who take it very seriously and who are actually like um building sort of a community of people who follow their works are really bummed it sucks it's like you don't really have a good way to like there was no way to prepare there's no way to like port those followers to another community to like start a new group i know some people are like on tumblr right now with still like with their connections that they've made on as talking to them there and of course Reddit has like the AO3 subreddit has like a mega thread of people sharing updates, sharing drives. I think people are bummed that they they feel like they've left readers waiting or hanging.
45:31Sam: But I've not seen anyone express any frustration with either AO3 or OTW or the authors themselves. It just is like a shitty situation. And again, it's like all everyone working on the site is a volunteer. So everyone's just kind of like you know, Godspeed to the volunteers. We hope that they are okay and are surviving this. And the people that I've talked to have repeatedly said that they feel like they appreciate the site more now. Like they're going to miss it and it's going to be sad to not have it regularly for the next couple of weeks. Maybe less, hopefully less. It doesn't have to be a month, but we'll see.
46:11Sam: But they're saying like, I appreciate what the site was giving me in my writing practice, my reading practice, and we're going to take it less for granted when it comes back, which is cool. It's nice to see that. But yeah, I don't know. People are distraught. People are sad, especially initially. It was really shocking to see up to four weeks. I obviously don't know anything. You're the one who's been doing the reporting on this, but I see a website of this size go down for a security-related incident and then maintenance and then the timeline getting longer and longer and the timeline being up to four weeks.
46:50And I get really concerned that it... Is it going to come back? Is it going to come back in the same form? I mean, I don't want to sow more concern, but I am not super familiar with other sites that have needed to come down for such an extended period of time. It's a pretty wild thing.
47:15Sam: It's really crazy. And they've said they've been pretty transparent about the process. Like there hasn't been a lot of updates. I'm sure they just don't have a lot to say other than we're trying. But the updates so far, so far have been like it will come, it might come back sooner in a degraded state, which I don't know what that is going to look like. The community and the ecosystem of AO3 is very complex and there's a lot going on there. But the site itself is... It's a pretty lightweight site. It's words. It's text and some frames. So I don't even know what a degraded version of this would look like.
47:47And then you have people saying that they're maybe going to try other...
47:50Sam: There's space battles. There's fanfiction.net. There's other sites that you could do this on, but they're not as good. Mostly because people aren't on them as heavily. And also, every time I've talked to someone about this, they're like, we're not doing Wattpad. And I'm like, I remember Wattpad being the thing that you did and also being shitty and like a joke. So I had to Google why people hate Wattpad in the process of this. It's also hard to get an answer on. But it sounds like it just got like really inshittified. It was hard to moderate. It was a lot of really young people, which is great, but also hard to have a quality writing community when you're dealing with 13-year-olds.
48:34Sam: And I guess they added a lot of ads into the site. So people are like, fuck Wattpad. We're not doing that. But we'll just wait and see how AI3 grows, which it could be a long wait. I don't know. So I want to talk about the opportunists who have shown themselves after this chaos happened. There's a story that you published. We're recording this Tuesday. You published a Tuesday morning about an AO3 clone called AO3.life that was vibe-coded. What was AO3.life? And I say was because it existed for approximately one day. Yeah. Just immediately like nuked from orbit by authors. Really good. AO3.life was a site where somebody had scraped the internet for any instance of where someone was posting AO3 works.
49:27Sam: So again, it's like these people who are posting drives, it's like they mean really well and they're trying to share something or, you know, they're posting like, I think Ellipses is like another word processing link sharing sort of platform. So people were doing that. And this site the whole time was like scraping those out of the internet with a swarm of AI agents, which is what the person who built the site said. A swarm of AI agents controlling 40 virtual machines were scraping the internet for all drives, scrapes, and sources. Not good. I don't know. It's like people have really mixed feelings about the drive sharing thing because people are sharing things that aren't theirs.
50:05Sam: and when you're on AO3, you have a little bit of control over who sees the work. Like you can archive lock it, you can make sure only people logged in can see it. You're talking to a specific community about that work with the tags and often it's very niche. And then people are sharing it on Reddit and saying like, I downloaded all these. And it's like, if your stuff is in there, maybe you don't feel comfortable having the entire internet looking at it. So that was problematic to begin with. But then you have this site, this person come along and say, I've scraped it all and I'm turning them into audiobooks, which using AI, I don't even think they said outright that they...
50:43Sam: Actually, yes, he did. He said he was making AI slot audiobooks. But he was charging... The first three minutes of listening to the audiobooks was free and then the site was charging you after that, which again is like, you can't do that. You can't actually monetize this stuff without asking for a lawsuit from the people who actually own the IP, which in some cases are very, very, very big companies. So that was going around. People were really upset. People were saying, I didn't consent to my works being in this. The process for getting your work taken off of this site was to email some legal email.
51:20Sam: So then at that point, you have to like, again, share more information with this person that you don't know who they are. And the process was to put on your author page on AO3, some kind of flag or notification that you are the owner of that work to speak directly to like AO3.life to say, hey, this is my work. I'm flagging this. But you couldn't do that because the site's down. So how are people supposed to actually go in and edit their author pages or their works without accessing the site? It's totally down. So anyway, it was a huge, huge fucking mess. But the person who set up AO3.life took the site down.
51:59Sam: I started getting... I was refreshing it earlier on Monday. After they got like 2 ,000 complaints. Yeah. Many, many, many complaints. 2 ,000 takedown notices, which they were like, I can't actually deal with this. So the site went down and then a notice went up on the site and the notice is what's up there as of us reporting this, but it says that they didn't, the person who made the site didn't realize that this would be received so negatively. They said, it was never my intention to hurt so many authors. And I'm truly sorry to you all. There's no way to show my sorry better than taking this site down.
52:40Sam: And then they go on to talk about how expensive it was to run the server. And that's why they were charging. Which, again, it's like, you shot yourself at the foot here. So I don't know why you're complaining about the expense. You didn't have to do this. Nobody wanted this. But they were like, I fucked up. And I'm sorry. And the site is now down. and they signed off. Yours truly, a 17-year-old from India that thought they were doing something good. This is extremely, I'm sorry, trying to delete it. Yeah. Like literally, I'm sorry, trying to delete. Yeah. I think that Big Yikes is correct. I think that this is something that we have seen AI enable ever since like Shrimp Jesus, et cetera, where I was writing about how people were latching onto these American conversations.
53:36And AO3 is obviously an international website. But in particular, the Facebook slot that was going viral, the Instagram slot that was going viral, were people in other countries trying to specifically reach American audiences. And I don't know exactly what was happening here. But I sort of doubt that this 17-year-old had a sense for how much AI is rejected in these types of fanfic communities. And I almost feel bad for him. I think it's just like a yikes situation. Just like an unfortunate situation.
54:16Sam: Just stepped on a landmine. Like had no idea. Like the teenage aspect of it than anything. It's just like some teenager did this probably. And that's something that AI has enabled because it's like, probably could spin this up in like 20 minutes. I don't know how much time he spent on it, but it's something that you can make really fast that can go viral really fast. And then the backlash was just extreme and warranted backlash, but it happened so quickly. And it's just like, okay, site's here. Never mind. Site is gone. Site is gone. but it's like, sorry, sorry, sorry. Yeah, it's rough. I mean, it's, yeah, again, it's like, it's cool to see people have a really visceral, like immediate response to this.
55:01Sam: People meaning like authors and readers who immediately were like, fuck no, not this. We're not doing this. And for not just people to be really outraged by it, but for the person who made the site. And we see this all the time. It's like we write on, we write about these kind of like totally misguided projects, kind of with some frequency. And a lot of the time comes down to ownership and who owns what they're posting. But when people respond and say, actually, I didn't realize that this was really bad and I'm sorry, is the right response. That's you did something, you made a mistake, you did something harmful and then you took it down.
55:42Sam: And that's okay. That's fine. Like, please just stop. Now, I think at this point, this site is showing who was on the site originally. Ganesh, the kid who made it, updated it with a link of sources where there are over 70 ,000 of them. It's links, it's Drive links, it's Google Doc links that they're, I think, trying to be transparent and saying, hey, this is where I got this stuff from if your work is in here and you're curious. Which again, I think is probably the right move to say, your stuff was in here. If you want to go look, sorry. Yeah. A couple of things briefly. AO3 launched 18 years ago.
56:28So it is literally older than the teen who made this ripoff. That makes me feel like dust. Yeah, I know. And then I just learned this from wikipedia.com. But AO3 was in beta technically until April of this year. when as an April Fool's joke, they removed the beta from it. And then on April 2nd, they said, actually, we are exiting open beta. So the site only officially launched back in April. As in, I think it started as this beta project back in 2008. But then it just stayed in beta, this open beta forever. And then earlier this year, they're like, okay, now we're ready to launch. and now they've had this downtime.
57:18Sam: God, I didn't realize that. That's really crazy. Yeah, that's nuts. I mean, the Organization for Transformative Works is really interesting. They do a lot of interesting works in the archiving space and legal advocacy. So definitely check them out in the meantime. That site is... Their site is still up. The OTW website is still around. It wasn't affected, but it's archived. It's been affected, but they're a cool organization. So support them. I think they're also... They're fundraising a little bit. So maybe check that out too. But yeah, cool stuff. But yeah, that's crazy. I didn't know you could just be in beta for 17 years.
57:56I'm sure there's many such cases. If you go to like... Just like random, like freeware and software and things like that. But in any case, I guess let's leave that there. You're going to continue to follow this. I also just realized you're wearing an MRDUX hoodie, which is so funny. Shout out to MRDUX. Shout out Ocean City, Maryland. Anyways, we'll leave that there. And when we come back, we are going to talk about my story in the subscribers only section. Okay. Thank you. Thank you. As a reminder, 404 Media is journalist founded and supported by subscribers. If you do wish to subscribe to 404 Media and directly support our work, please go to 404media.co.
58:48You'll get unlimited access to our articles and an ad-free version of this podcast. You'll also get to listen to the subscribers only section, where we talk about a bonus story each week. This podcast is produced by Alyssa Midcalf. Another way to support us is by leaving a five-star rating and review for the podcast. That stuff really, really does help us out. This has been For a Full Media. We'll see you again next week.
Take your personal data back with Incogni! Use code 404MEDIA at the link below and get 60% off an annual plan: incogni.com/404media
We start this week with Joseph’s investigation into Proton’s culture of fear and the company’s massive push towards AI. A lot to unpack there. After the break, Sam tells us about the AO3 outage and its fallout. In the subscribers-only section, Jason explains: we’re not tech support.
Manifestos, Fear, and ‘Loser Thinking’: Inside Proton’s AI Reckoning
‘Wake Up Call:’ Fanfiction Writers and Readers React to AO3 Outage
ChatGPT Keeps Telling People 404 Media Can Solve Their Tech Support Problems
Subscribe at 404media.co
Learn more about your ad choices. Visit megaphone.fm/adchoices