Nathan Labenz: uncertainty

Transcript context

…Computer and then I am pushing it to GitHub, which I'm starting to rethink recently based on some of the issues that they've been having security wise. But yeah, it is all as of now, it's all in the Super light database. The one pain point that I had and it's, you know, for people who haven't done this kind of thing before, it's an amazing experience to just sit there and be like, can you code your own tool to go get access to whatever? More often than not, even in January, you know, it had no trouble coding up the tools. And then some real Eureka moments for me were like when it would talk me through how to go to Google Cloud and create my own app and what the settings needed to be for my own app and how to add my own account as a tester so that I didn't even have to put it through Google Review. And I could just immediately have access to all my stuff, which is all I really wanted anyway, you know, giving me button by button clicks on click, directions on how to go through those interfaces. It's like if this thing can take me through Google Cloud set up, you know, I think it might, that might be AGI qualification. Slack is the same way. I mean that the difficulty of finding what you need in Slack. And there's one Gabby out there, which is I think the level of access that I gave myself was somewhat contingent on me being an admin of the organization. So not everybody in every Slack that they're in is going to be able to have the kind of full extract in the way that I did. They might have some conversations about, you know, getting that sort of access opened up. But again, it was just the number of permissions in there just like absolutely insane. But it's ability to talk me through it all was incredible. The only time that I had a sort of, Oh my God, why did you do that moment was with Slack. And the problem was, you know, I was very much like iterating through this, right, because I didn't want whole company slack over, you know, however many years. I kind of wanted everything that I had been involved with think for a company would maybe want to structure it differently. But for me, I was like, I want my DMS. I want like threads that I contributed to. We also have like logging stuff in slacks that are. That's a whole other thing like I've seen. You definitely stumble on these things as you go where you're like, oh, there's like 2 log channels that are in fact like 80% of all Slack data, you know, don't want that, right? So now once you're in the kind of special casing, now you're like special casing more and more. Even in Gmail, some interesting findings were like a naive sort order might be like put the longest things that I wrote to the top. But interestingly, when I did that, what I found was that often it was an AI output that I had sent to a friend was actually the longest thing. So now I'm like, oh, wait a second, I got to be. he top. But interestingly, when I did that, what I found was that often it was an AI output that I had sent to a friend was actually the longest thing. So now I'm like, oh, wait a second, I got to be. So I actually had to kind of caveat some prompts around classifying, you know, especially for the writing sample thing. But even just in general, one of the things that Flash does is try to indicate, is this actually Nathan's original writing or is it AI? And I'm not trying to hide, you know, when I do send those things to friends, I'm not like trying to hide that it's AI. So it's, you know, typically, like I'm saying to them, like here's what Claude told me about this or whatever. But I still want to, you know, need to make sure that like that's not kind of leaking into my writing sample and, you know, teaching whatever to sound like Claude as it attempts to sound like me. Anyway, the one thing that I had where it actually like did a data delete that it was actually kind of painful was predicated on the fact that Slack's rate limits, if you're just kind of a indie hacker, are insanely low Gmail, you know, you fly through and it took me a, you know, I don't know, a couple hours for the script to run. But like they're, you know, they can support and they do support, you know, not insignificant use of the API. Slack is like really limited if you're, you know, just creating your own personal token or whatever. So it took days, maybe even a couple weeks to kind of go through everything, especially with a couple different, you know, strategies and rounds federation. And there was one time where it was like it didn't realize that. And you know, the sort of lack of proper sense of time that models don't have, you know, very apparent in this moment because it wouldn't have been that hard conceptually to just rerun all the API calls and get all the data back. But it didn't realize that we had spent like a week, you know, constantly hitting rate limits to get the data that we did have. And it was just like, I'll just drop that part of the database and refetch it. It was like, no, oh, it's going to be a week. That's the only time that that has happened. But it was definitely notable that, you know, you see these things on the line and you know one kind of. They can happen super.…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.