But are we on a wave of some sort of massive reverse engineering movement here, where we're gonna go back in and look at all these legacy apps and kinda modernize them, and this becomes, you know, a new trillion-dollar business?

Potentially, absolutely.

This is...

I'm fascinated by this article.

Great article, by the way, uh, featuring, uh, a lot of good interviews, including with Futurum's own friend of the show, Mitch Ashley, um, and others.

Really good insight.

Um, you know, the next generation of frontier models are so much better at, at being able to intuit, uh, and that's playing into a lot, and getting accurate reverse engineering up front.

Andy, um, is this maybe, you know, something that the open source community's gonna drive? Because if anybody's out there, you know, saying, "Hey, we have a vested interest in making sure that there's no proprietary code," it's those guys.

So is it going to be possible at some point in the future or maybe now to trace back the source of some sort of campaign and information or whatever it is that was generated to where it was coming from? If the original source for this thing is some, you know, obscure server sitting in the middle of Africa that Russia is using to launch a campaign, maybe people should know that and we can surface that.

Yeah, I mean, look, notwithstanding Utah's attempt to ban VPNs, which has recently been struck down by a federal court as literally impossible, this is absolutely knowable.

This is observable, if I may.

Look, we know this is true.

We saw what happened when Twitter and whatever it's called... decided to all of a sudden show where people were logging in from.

And all of a sudden, we realized that half of Twitter was logging in from Kazakhstan, Uzbekistan, literally from Russia, from Crimea, all over the place.

And they quickly backed that off, right? And Section 230 of the Communications Act, exactly, Robert, we've got the tools even to be able to deal with this if we want to.

Is that defensible?