S1: Welcome to Unsupervised Learning, a security, AI and meaning focused
S1: podcast that looks at how best to thrive as humans
S1: in a post AI world. It combines original ideas, analysis,
S1: and mental models to bring not just the news, but
S1: why it matters and how to respond. All right, welcome
S1: to unsupervised Learning. This is Daniel Miessler, and this is
S1: a big episode. I've been wanting to do this for
S1: a number of months now, and I finally got all
S1: the pieces together to be able to do it. So
S1: let's jump in. Okay, so this is a post called
S1: How My Projects Fit Together. It is a follow up
S1: to a previous post called What I'm Doing and How
S1: It's Going, and I think that came out about a
S1: year ago, something like that. But what this post does
S1: is it essentially answers the question that I get asked
S1: most often, which is people looking at the various projects
S1: that I put out over the last year and basically saying, look,
S1: I see you doing fabric, I see you doing substrate,
S1: and you keep talking about this thing called human 3.0.
S1: What exactly is all of this? Like, what are all
S1: these different projects? How do they fit together? Are they
S1: all related? What is going on? And the answer is yes,
S1: they are all related. And I'm going to talk about
S1: how in this post. Okay. So I like to start
S1: everything with a problem. Right? I don't like to talk
S1: about solutions which all of these are solutions to something. Right?
S1: All of these different projects here, they're all solutions to something.
S1: And I don't like to jump immediately into talking about
S1: the solutions. I'd rather talk about the problem that we're
S1: trying to solve first. So these are roughly the major
S1: problems that I'm trying to solve currently with all my
S1: different work. So WP stands for World Problem. And WP
S1: one is humans are suffering from a lack of purpose
S1: and meaning in their lives, which is causing mental health
S1: and societal problems. So lack of meaning, I would say
S1: if we had to make this, um, three words lack
S1: of purpose or lack of meaning, I would say is
S1: number one. Okay. Second one. Humans do not understand and
S1: are not prepared for the sophistication and speed of introduction
S1: of AI into our society, which will cause major work
S1: disruptions and exacerbate our lack of purpose. So this is
S1: essentially the introduction of AI, exacerbating the problem of number one. Okay.
S1: So number one is the lack of purpose or meaning.
S1: Number two is AI is going to make it way worse.
S1: And number three is humans are not trained to become
S1: full spectrum people, but rather to become economically useful to
S1: a materialistic and transactional economy. Okay, so this one's a
S1: little bit different. Very related though all three of these
S1: are related. So essentially my work is centered mostly around
S1: solving those issues right now. And I actually have multiple
S1: other problems to find, which in my telos file. I
S1: also have associated with other strategies and solutions and projects
S1: and stuff like that. But these are the core. These
S1: are the top three. So next thing to say is
S1: that I am a security person. I've always been a
S1: security person since the mid to late 90s, and I
S1: always will be. So I am going to continue doing
S1: security work. I think about everything in terms of security.
S1: It's just part of my DNA. I can't unsee it.
S1: Every time I see any system, I think about how
S1: transparent it is. I think about ways to fix it.
S1: Break it. Um, I'm always red teaming everything, right? So
S1: another way to think about this is that I view
S1: AI as containing security. Right? I feel like it contains security,
S1: because if you think about it, security is actually is
S1: one of my favorite things about security is that it's
S1: Latin and it means C, which is without, and cura
S1: which is worry. So without worry. And if you think
S1: about the problems here, I am worried about these. I
S1: believe humans, consciously or unconsciously are worried about these things.
S1: So I'm trying to remove the worry from these things
S1: so people can go on and be extremely productive and
S1: have meaningful lives. Right. So ultimately, this is all kind
S1: of the same thing. It's all kind of a giving
S1: people security so that they can thrive. I mean, that's
S1: that's ultimately what this is all about. Now, um, there
S1: are two main ways that I'm basically pursuing this, uh,
S1: continuing to pursue this on the security side, tangible ways, like,
S1: I'm going to do it all the time. I'm still advising,
S1: I'm still consulting, I'm still doing assessments. But in terms
S1: of actual projects, these are my two main projects that
S1: I still have going and I continue to upgrade as well.
S1: So one is called Helios, which is continuous attack surface monitoring,
S1: which I'm now starting to add AI stuff to as well.
S1: But essentially I've been running this for years and years.
S1: I still have paying customers on it and I just
S1: love attack surface management. I love automatically quickly discovering vulnerabilities
S1: and then being able to find the weaknesses there, or
S1: finding attack surface, and then being able to find the
S1: weaknesses in the attack surface, and then going on to
S1: exploitation and then reporting on that, alerting very quickly. That's
S1: a thing that I just love. And I think it
S1: very much applies to like the world around me. I
S1: basically want Helios for everything. So that's like basically the
S1: platform that I'm building there. But this one specifically is
S1: just for information security attack surface, and it's an actual
S1: product that, you know, customers can actually sign up for.
S1: This next one is called domain. And this one is
S1: a relatively new it's basically Security program management using the
S1: Telos infrastructure, which I'm going to talk about later. And
S1: this is an actual project, um, in an actual product
S1: as well. Okay. So those are the two main security
S1: projects that I'm going to be focused on and will
S1: continue to be focused on. So now let's get into
S1: the main core ones that are more closely tied to
S1: the problems that we just talked about. So the projects
S1: are substrate fabric, Telos, daemon and human 3.0, which is
S1: kind of the centerpiece for all of these. So we're
S1: going to look at each one individually first and then
S1: how they work together. So I have a full explainer
S1: video here on substrate which we'll put a link to
S1: there at the top. And also this will all be
S1: in the description for the video, but substrate has its
S1: own video, it's got its own full blog page and
S1: everything full description. But it is an open source framework
S1: for increasing human understanding, meaning and progress. So it's basically
S1: designed to make things that matter to humans more transparent, discussable,
S1: and ultimately fixable. Um, and I've got an example here
S1: that I, that I put in just to remind you
S1: from the actual page. So it's basically a map to
S1: explain things and solve problems, and it's so big that
S1: it's kind of abstract. So it's better to use an example.
S1: So here's an example of an argument component. In fact
S1: I'm going to pull up an actual argument component which
S1: I submitted, which is even better. But think of an
S1: argument you might hear on any given day about whatever topic. Right.
S1: So I don't know why you recycle. It's a total
S1: waste to cost so much to recycle. You know, the
S1: programs are poorly run or whatever. So this is an
S1: argument that you would hear in normal life, right? So
S1: what I'm trying to do is I'm trying to make
S1: it easier for humans to communicate with each other using tangible,
S1: transparent things, not just throwing out random claims which are
S1: opaque and you can't possibly research them. And it's just
S1: a whole bunch of like, mini claims inside of one
S1: big claim. And then you basically have just rhetoric being shot,
S1: you know, between two people, and it's just a total waste.
S1: So we're confronted by this type of thing constantly about recycling,
S1: but things that matter a lot more than that, you know,
S1: other type of political things. But what substrate can do
S1: is it can take all these have I wrapped around them, right.
S1: So they're not I by themselves. It's actually mostly text components.
S1: Is is what all of these are mostly based around. Okay.
S1: Text this this is my religion text. That's why I
S1: love vim so much. I love clarity of thought, clarity
S1: of understanding, clarity of articulation of problems, solutions. Can you
S1: give it to me in ten paragraphs? Awesome. Can you
S1: give it to me in ten sentences? even better. Can
S1: you give it to me in ten words? I want
S1: to be able to go from three words to ten
S1: words to ten sentences to ten paragraphs to ten chapters,
S1: which is a book or whatever, to ten books to
S1: ten libraries full of whatever, all explaining one concept, right?
S1: I'm just obsessed with this, and so much of what
S1: I'm doing here has to do with this simple concept
S1: of being able to explain things perfectly clearly. There's no
S1: such thing as perfect, but extremely clearly explain concepts in
S1: a way that's tangible. And you could sort of like
S1: communicate efficiently as a result of both of you having
S1: a crystal clear idea of what the conversation is in
S1: both of your minds. Okay. So this is the biggest
S1: part of substrate is having universal things that you can
S1: point to, which are the transparent components that are used
S1: to assemble a conversation. Assemble a discussion. Okay. When somebody
S1: proposes a solution. Okay. They're proposing something. They're like, I
S1: believe I can solve this problem. If you elect me,
S1: I will. Whatever. We will have ice cream for lunch
S1: every day at the at the at our middle school. Right.
S1: I think that was Napoleon Dynamite or whatever. It was
S1: a some kind of thing where he was like making
S1: these promises. But the point is, I can put all
S1: the promises in text. I could say it's going to
S1: happen by this time. I could say, we're going to
S1: raise our test scores by this much. If we do this,
S1: we're going to have more fun based on this fun meter, right?
S1: So we can have like metrics, we can have KPIs,
S1: we can have all these things and they're all published.
S1: And then the promise at the bottom says something like,
S1: if I don't raise these numbers by this time, then
S1: you should vote me out. And now this is published.
S1: This is the platform, right? You could do this for politics.
S1: You could do this for all sorts of things anyway,
S1: so that that just shows you how powerful the text
S1: is and why I'm so on about it. Okay, so, um,
S1: what you could do with that once you have it set, right.
S1: Watch this. This is actually an argument, okay? This is
S1: the substrate thing, but this is an actual argument broken
S1: out in mermaid JS. And if you zoom in to
S1: actually go into this image, it's actually showing the relationship
S1: between all the claims, whether or not they're valid or not.
S1: And the better, I guess it's going to be able
S1: to go in independently, research all these different claims and
S1: light up these different boxes as like green or red
S1: or orange or whatever. Right? So now it's like as
S1: somebody talking, I mean, this is not too far away.
S1: You have like an AR interface. And as somebody is
S1: talking and they're like, oh, and that's why. And then
S1: this thing happened and the conspiracy and then they plan
S1: to kill me and then blah, blah, blah. And you
S1: just see all these claims popping up, and then you
S1: see your AI in the background. It's going to research.
S1: That claim comes back. Bullshit. Turns it red. Okay. Like
S1: this little node right here will turn red. Dink didn't happen. Nope. Already,
S1: you know, debunked. And so the bottom also turns red.
S1: And it's like chances of this person being full of
S1: shit 94%. Okay, this is the type of thing we
S1: will be able to do very quickly, very soon because
S1: of all the ways that tech is advancing, not just AI,
S1: but lots of different tech is advancing. And so we're
S1: going to be able to have interfaces that like detect
S1: lies and detect deception and, you know, find interesting arguments.
S1: And it's not just adversarial, it's not just finding bullshit.
S1: It's also when someone starts talking, your AI can remind
S1: you they're talking about stuff that you really like, right?
S1: And you don't need an AI for that. You're obviously
S1: going to know that yourself just by hearing. But let's
S1: say you're having a conversation that's boring with some business partner,
S1: but right next to you in the Starbucks or whatever,
S1: your eye is also listening to that conversation next door.
S1: It's a public conversation. They are being loud, no big deal.
S1: But it's like, hey, you should probably close things down
S1: with this person you're talking to and go talk to
S1: her instead because she's trying to solve X problem, which
S1: is related to your Y problem. And that's probably a
S1: much more interesting and fruitful conversation, right? Anyway, lots of different.
S1: Like there's just so much here and there's so many
S1: different components to substrate, but that's essentially what it is, right?
S1: Shared understanding and problem solving. So when people meet each other,
S1: discuss things, disagree or whatever, various components of the proposal
S1: or conversation can be made visible and transparent. Okay. Proposals. Problems. Solutions,
S1: arguments entered into I as a context which point research
S1: edit at which point research can be done or analysis
S1: can be done. Counterpoint generation, progress tracking. It's just insane. Really,
S1: really excited about this project. Oh, and I wanted to
S1: show you an argument, um, because we actually have an argument.
S1: So just put it up recently. So if we go
S1: to okay, if we go to arguments, I just put
S1: this one in recently. It's the first one actually. So
S1: you see the structure here is uh, are 212934. That
S1: was random. So I just randomly made that. And then
S1: I have a quick top level summary using underscore connections.
S1: So it's all one word. But if we go into
S1: this thing look at this. Eyes are capable of understanding
S1: I've got a claim here, which is what that is
S1: argument style. It's a deductive argument, which means building claims
S1: that lead to a conclusion. And if you want to
S1: disagree with the conclusion, you have to find a problem
S1: with the previous statements. Right. And then I've got a
S1: series of statements that result in the conclusion, which is
S1: number eight. Therefore, AIS are capable of understanding in a
S1: way that matters to us as humans. So this is
S1: a very basic, you know, markdown structure or pure text structure,
S1: whatever you want to call it. And that's an example
S1: of an argument inside of substrate. Okay. So let's go
S1: to the next one fabric. Okay. Fabric you probably heard
S1: the most about. If you haven't that's fine. If you're
S1: brand new here. Welcome. And there's lots to talk about
S1: with fabric. Um, I would say a couple of hundred
S1: people have made other YouTube videos around fabric. So there's
S1: like tons of, uh, introductory videos. I've got an introduction
S1: to fabric, actually. That's this one here. Um, introducing the
S1: whole concept, which I'm also going to talk about here
S1: as well. But the probably the best two are the
S1: one from network, Chuck. That's an extraordinary one. Actually, it's
S1: this one here. And then also David Bumble. I did
S1: an interview with him and with network Chuck. So both
S1: of those intro videos are really, really good. Plus I've
S1: got this one here and essentially what it is, it's
S1: an open source framework for augmenting humans using AI. So
S1: the problem is that there's so much AI out there.
S1: There's so many websites, so many mobile apps, so many
S1: everything out there that it's like, okay, what do I use?
S1: How do I solve this problem that I have? So
S1: what fabric is it's a collection of problems and solutions.
S1: So I'm actually just going to go into um, yeah.
S1: Let's go into the GitHub page. So when you go
S1: into the patterns, which is what these things are called,
S1: these patterns are actually um, they're actually problems. Okay. Analyze
S1: their actions to take on a problem. Okay. Analyze email headers,
S1: analyze incident. Analyze logs, analyze personality. You could put like
S1: you could put like people's social posts in here. You
S1: could put like whatever you want in there. And it
S1: will like do an analysis of their personality, analyze pros
S1: to fix your writing, analyze threat reports a whole bunch
S1: of information security stuff in here. Secure by design questions.
S1: Also security related um, create aphorisms, create a formal email,
S1: create a hormozi offer. This is a business creation thing.
S1: You could visualize anything. You can create an MPC for
S1: a role playing game. Like all of these. These solve
S1: very specific tasks that humans need to solve during the
S1: course of a day. So rather than trying to make
S1: up prompts like all of these are prompts, okay, but
S1: they're all custom tuned in a very clear format to
S1: solve a very specific problem. So now what you do
S1: is you call fabric and you could use that in
S1: a text interface. We've got a UI that you can use.
S1: It's designed to be mostly command line. But now we
S1: have a UI, a web UI that you can use.
S1: And there's also a raycast support. So I'm going to
S1: take this whole page that I just that I'm actually
S1: doing this video on right now. Right. So I'm going
S1: to copy this and then I'm going to do raycast
S1: and I'm going to do Extract wisdom. And then it's
S1: already highlighted. So I'm going to tab over I'm going
S1: to paste and I press enter and look at this boom.
S1: It's doing fabric extract wisdom. Or actually in this case
S1: it's doing it's extract ideas I think. No no this
S1: is extract wisdom. Yep yep that's the raycast one I did. Okay.
S1: So look these top ones are the ideas. Now it's
S1: insights quotes. Look it's doing the quotes that came from
S1: the page. So now instead of having to go into
S1: the command line I can now invoke this fabric project
S1: from raycast which is pretty cool. So that's essentially what
S1: this is. So it's everyday things right? Learning, studying, self-improvement,
S1: problem solving, all these different things are things that you
S1: could do inside of fabric. Okay. So let's look over here.
S1: I'm in the command line now. And we can blow
S1: this up a little bit for you. And we are
S1: looking at the fabric patterns. This is a better way
S1: to look at it than the web page actually. So
S1: you scroll through here, look at this, look at all these.
S1: And I added like a lot of these initially I
S1: added all of them. But now I mean this is
S1: all open source. All of these things are open source.
S1: Like probably over 100 of these have been submitted by
S1: the community from all over the world. There's like over
S1: 100 developers on this thing. At this point. I think
S1: we got like 23,000 stars or something. And these are
S1: all specific problems that you can solve using fabric right
S1: on the command line in the GUI or in raycast.
S1: And there's lots of other ways to interface with it
S1: as well. So that's the concept. You have specific things
S1: that you want to get done. There's a million AI
S1: tools out there. There's a million different prompts that you
S1: can use with the million different tools. So this is
S1: a way to use one framework that uses prompts specifically
S1: to solve different problems. So you just do fabric, the
S1: name of the problem you're solving and boom you get
S1: back your answer. So that's the idea there. So next
S1: one Telos. This is a relatively new launch. I've been
S1: doing this actually for years just in text, you know,
S1: just with regular cards. And I've been actually managing security
S1: programs like this for years and years and doing security
S1: assessments like this for years and years. But now with AI,
S1: it's getting even more powerful. So this is a full
S1: project based around this concept. So essentially it is creating
S1: a deep context about things that matter to humans. and
S1: you're going to notice that there is natural interaction and
S1: overlap with substrate and with fabric. And in fact, the
S1: way they work together is just insane. Because guess what?
S1: It's all based on text. I loves text, it's it's
S1: insane how all these work together and dynamically play off
S1: each other and like, magnify each other. So let's go
S1: into this, articulate the mission of this thing. Articulate deep
S1: context about the things that matter to humans. Okay, open
S1: source framework for creating deep context about things that matter
S1: to humans. The framework allows us to use AI to
S1: manage entities of any size, from individuals to teams to
S1: organizations to companies. I mean, honestly, it's like countries, planets,
S1: you know, solar systems. It doesn't matter how big the
S1: thing is, you can manage it in this way. Just
S1: a question of like, how big does a file get
S1: and how much are you abstracting away the different components. Um,
S1: so the GitHub page, I mean, I've only got a
S1: couple of things in there right now. In fact, we'll
S1: just go in there. So what I have in here,
S1: I actually have a published full telos file for this
S1: fictional company called alma, which is something I do in
S1: a lot of my security talks. I use this as
S1: the example. But look at this. We got a company
S1: mission for this fictional company called alma. We've got a
S1: company goals. We've got company KPIs. Most importantly, because the
S1: security oriented we have the security team mission. Look at
S1: this SM one. Each one of these are tagged with
S1: a specific thing so that the I can cross reference
S1: the context and understand the whole thing. And if you've
S1: not seen my my videos on how I understands, you
S1: definitely want to go check that out because it heavily,
S1: heavily relates to Telos but also to substrate and basically
S1: all this stuff. But look at this. So security team
S1: mission Security team goals. Look at this. This is what
S1: we're trying to do. This is how we measure our success.
S1: This is our risk register. This is what we're really
S1: worried about. We've got all these narratives. We've got current risk.
S1: We've got strategies. We got like how we're doing, which
S1: we've just sort of written out. And I've got a
S1: video coming out soon. I'm still doing this as a
S1: paid talks around the world. So I'm not releasing this yet.
S1: But at some point I'm going to release maybe an
S1: abridged version of this. And by the way, I am
S1: releasing it inside the UL community. So, uh, if you're
S1: already a member of the community or you want to
S1: sign up, you're going to have a version of this
S1: full paid talk very soon. Um, look at this team members.
S1: What they're good at, how much money they make. Nadia
S1: is doing well. Check her out. Projects, project name. Like,
S1: who's actually running it? Um, the schedule, uh, the time frame,
S1: all the different stuff. And then look at this. This
S1: is the list of metrics that are happening, right? Updates
S1: to the metrics and using this. I don't want to
S1: go too far into this, but using this I can
S1: manage the entire program. It is absolutely insane. So that's
S1: what we have in Telos so far, and I've only
S1: uploaded the corporate one. This is how I manage my
S1: own life. Actually, I do everything with a telos file.
S1: My whole life is in a telos file. I have
S1: my traumas, I have relationships, I have my business goals.
S1: I have my personal goals. I have my eulogy goals.
S1: I have everything in there. My favorite mental models, my
S1: ideas that I've come up with, which we're going to
S1: talk about in the daemon part, all this different stuff.
S1: It's all in one context. You feed that to an AI,
S1: and by the way, be careful what you put in
S1: your telos file. If you're sending it to a cloud thing.
S1: I have mine, you know, fairly safe and sanitized. So
S1: I'm not like, uh, airing any laundry or something like
S1: that Besides, everyone kind of has the same problems. So
S1: I'm not super worried about, like, I'm a special snowflake
S1: and I hope nobody finds out about this or whatever,
S1: so I'm not really concerned about that. But be careful.
S1: If you put something in your telo's file and then
S1: you upload it somewhere. Just something to think about. Not
S1: not something to panic about, just something to think about. Um,
S1: but because I have everything in there, all my goals,
S1: all my aspirations, what I hope somebody would say at
S1: my eulogy when I die, when I'm 137, when my
S1: human body dies, I'm not actually going to die when
S1: my human body dies. Um, so when that happens, what
S1: are they supposed to say? Are they going to be like, uh.
S1: I mean, he made a good chicken tortilla. Uh, you know,
S1: he he really likes salsa. Like, I don't want people
S1: to say that at my eulogy. I want them to
S1: say nice things that I've done. Well, guess what? I
S1: have to do those things.
S2: Before.
S1: That time. Right. So this kind of stuff I put
S1: in my telos file and, um, it's just really, really powerful.
S1: So it doesn't matter if you are managing an ice
S1: cream truck or you are trying to run a family,
S1: or you're trying to get your life on track and
S1: have purpose in your life, which we're going to come
S1: back to that. That's like the central theme. Doesn't matter
S1: what you're managing, if you get promoted to galactic ruler
S1: of the Milky Way, you need something like this. Okay.
S1: Hopefully it's still text. Hopefully you're still using vim when
S1: you get that promotion, I would be. Um, but, uh,
S1: you basically can manage anything like this from the smallest thing,
S1: a personal workout routine all the way to. You are
S1: the director of the Milky Way. Okay. Um, got some
S1: additional context in here. I've got the link here to
S1: the corporate telos, which we just looked at. I'm going
S1: to be uploading soon. A template.
S2: For.
S1: The personal telos and different templates for different types of
S1: organization or entity. So that's, uh, that's telos, so personal. Well,
S1: not personal, but deep edit, so deep context about things
S1: that matter to humans again at all scales. Okay. Ourselves, teams,
S1: organization companies, etc.. Now, um, one last piece on this
S1: in terms of application. So once the eye sees everything,
S1: this is what we were talking about before. Once the
S1: eye sees everything purpose, goals, challenges, strategies, KPIs, now we
S1: can start asking questions. We can start taking actions. What
S1: mistakes are we making that are holding us back as
S1: a company, as an ice cream truck business, right? If
S1: this happens, what should we do? Absolutely insane. I've got
S1: examples of doing this for security program. I have it
S1: in this talk. It's absolutely insane. What's the biggest thing
S1: I could do right now? To be more efficient? To
S1: better pursue my goals? Right. Explain how so and so
S1: expert would look at my relationships, explain how so and
S1: so expert. I have a favorite fitness person that I love,
S1: and I would love to see what he thinks about
S1: my workout program. So I could just ask that question. Okay.
S1: And then if he's also a psychologist, he can just
S1: look at my entire thing and be like, hey, here's
S1: what I think you should do. So analyzing your life
S1: and your goals and your strategies for achieving them in
S1: the mind of Richard Feynman or, um, Naval Ravikant or
S1: whoever your favorite person is, you could use their eyes
S1: to look at your stuff and give you analysis. Why?
S1: Because it's all in one place. This is a thing
S1: that so few of us have, and Telos is the
S1: structure for allowing you to have it as well. Okay.
S1: Next one here, Damon. This one is brand new. This
S1: one came out when I wrote this, uh, article or
S1: this post. This collection post here. However, I have been
S1: talking about it forever. In fact, since 2016, in the
S1: real Internet of things, which I don't think I have
S1: it linked here, but you can find it on Amazon.
S1: It's called the Real Internet of Things. The concept for daemon,
S1: an open source framework for personal APIs. Now it's actually
S1: any API. It's more like entity APIs. But I decided
S1: to use the word personal. Might change it. Not sure.
S1: The concept here is that when you have a Telos file,
S1: or you have a web page, or you have whatever,
S1: and you have listed your individual ideas that you've come
S1: up with, you have listed your individual preferences, your favorite foods,
S1: your favorite movies, um, who you're looking for in a
S1: relationship or whatever. These are just API endpoints. And because
S1: of I. And because of not just I, but like
S1: the tech that we have now, things like postman, I mean,
S1: it's absolutely insane. You could parse a telos file, have
S1: a section called Private and Public and be like, look
S1: for all the public ones, post these, make these available
S1: as a public API of my favorite books. And guess what?
S1: It spawns. And on the endpoint slash books or slash
S1: favorite underscore books, someone can just pull that. And the
S1: whole purpose of this, if you check out the book
S1: The Real Internet of Things, Your daemon. This is my
S1: prediction going back all the way to then your daemon
S1: will know you intimately because of your telos file actually,
S1: and it will be parsing all of the daemons around
S1: us business daemons, individual daemons, cars, objects, whatever. Okay, They're
S1: all publishing like the trees, current water level, the trees,
S1: current happiness level. Like is it drooping or whatever. And
S1: maybe you could see that, but you can't see it from,
S1: you know, across the city. So I could I could
S1: ask the question, how healthy are all the trees and bloom?
S1: That was actually a query to the API. Or maybe
S1: they pushed it, but maybe it was a pull type
S1: of query. Anyway, the point is, you can ask a
S1: question of a city how happy are we? Okay, and
S1: now we just live hit the API for all these
S1: different people who have it published and are okay with
S1: putting their current mood out there or whatever. So now
S1: we have a live beacon of what is happening inside
S1: of a room, inside of a small city, a small town,
S1: a village or a planet. Right? My favorite case of
S1: this is you walk into a Starbucks. Okay, I'm just
S1: going to pull this up. I'm gonna pull this up. Um,
S1: give me a second. Here, eyes. Yeah. Here we go. Predictable. Yeah.
S1: So watch this. The stuff is all related. Okay. I
S1: actually should have put this in, um, in the post.
S1: I'm glad it's in this video. So this is an
S1: illustrated 9000 word version, updated version of essentially the book
S1: that I did in 2016. Okay. Um, so what part
S1: are we on? Um, so we have digital assistants. Everything
S1: gets an API. Yeah, this is it. Okay. So everything
S1: gets an API. Damon. Aura. So I called it Damon
S1: for this GitHub project. So watch this. Eyes will understand
S1: things by what they broadcast. So look at this. Got
S1: some art for it. I spent so long on this
S1: post like please go read it. Um, okay. Which I
S1: call a Damon, which is Greek for spirit. So don't
S1: think demon, although everyone will, of course, but, uh, businesses, uh, people. Whatever.
S1: Look at this for a restaurant. Here's your Damon menu.
S1: Our staff. So, look. Watch this. You're moving through the world. Okay?
S1: This is you moving through the world. Your Da, which
S1: is your personal AI on your iOS device or your
S1: Android device or whatever. Your meta glasses, whatever it is,
S1: it knows everything about you. It's constantly aware and awake
S1: and constantly reading news for you and presenting things to you. Um,
S1: most importantly, it's reading all the demons around it. Okay?
S1: It's parsing. Oh, there's a, uh, free biscuit over here
S1: at this little restaurant. Oh, this Thai place. You love
S1: that Thai place. And Sarah just said it's the best ever.
S1: And you should go there. And the the owner really
S1: wants to see you. He hasn't seen you in a while. Whatever.
S1: A plant over here needs watering, right? You can take
S1: some water that's in your thermos and go water that plant.
S1: All this stuff is available to the Da. There are
S1: thousands of demons running in this picture. Okay. Thousands. You're
S1: trying to have a conversation with your friend who's standing
S1: right next to you. This is them. Okay. You can't
S1: be interrupted. You don't. You're not going to pull up
S1: a list of demons and be like, oh, I'm going
S1: to go look at the menu for this restaurant. I'm
S1: not going to happen. Your eye is going to do
S1: it for you. Okay. So watch this catalog about this
S1: is for businesses, right. Every business becomes an API okay.
S1: The catalog the about the contact how to do whatever.
S1: Why contact. Because you could just say Holy crap, these
S1: headphones just broke. Hey, um, Darcy, which is the name
S1: of my, uh. My eye. Hey, Darcy. Um, tell this company, like,
S1: I'm really upset that this just broke. Guess what? Darcy does.
S1: Guess what my eye does. My eye queries their contact thing,
S1: or queries their support thing and submits a thing and
S1: actually takes a little piece of my voice or a video.
S1: Takes a little video. I'm like, hey, see this? Look
S1: at this cable. This cable is like it's frayed. I
S1: got this thing two days ago. You could see. Here's
S1: the receipt. Boom. Darcy sends the receipt and boom. I
S1: didn't do anything. I didn't hit an API. My da,
S1: my digital assistant, my da. Darcy, hit it for me
S1: because everyone has these available, okay? And if you're a
S1: person and you're trying to date, you might have, like
S1: a dating thing that's open. It's like, oh, this person, like, um,
S1: you know, likes climbing the same way you do in
S1: her top. You know, three books are the same as yours.
S1: Look at this. People will have demons, auras, right? Demons, auras, whatever.
S1: Who knows what it's going to be called? Like, I'm
S1: not going to be able to control that. I'm going
S1: to call it a demon. I think that's a cool name. Plus,
S1: it's Greek and it sounds like demon, but it's not demon. Anyway, um,
S1: look at this, look at this. When people have demons displayed,
S1: it'll be objects as well, because the object might show
S1: it's working or it's not working, or it's like it's
S1: overwhelmed or it's not overwhelmed. But watch this for a person. Look,
S1: I'm looking through glasses. Eventually it'll be contact lenses, and
S1: after that it'll be a brain implant like Neuralink. The
S1: first iteration is going to be glasses, right? I'm looking
S1: at this person in a Starbucks and they've got. This
S1: is what Darcy is showing me. Darcy is using an
S1: interface to interpret their demon and display it in this form. Maybe.
S1: Maybe they want it, um, to display it in this form.
S1: Or maybe my Da Darcy chose to show it to
S1: me in this form. Okay. But regardless, it's going to
S1: look different, okay? Because, um, this one might, for example,
S1: it might indicate extreme creativity. So I'm going to be like,
S1: oh crap, you're awesome. I know you're awesome. I'm looking
S1: at your aura right now. Like, what are you into?
S1: And then they're like, oh, I love writing about this.
S1: I love doing that. So like, just so much potential here.
S1: This one here. I already did a post about this one.
S1: I already did a video, so I can't. I can't
S1: go into it. I'm already overexcited. Let's move on. Bottom
S1: line here for Damon, everything will be broadcasting an API.
S1: All of the projects that I'm talking about in this video, Telos, fabric, substrate,
S1: all of these different things. A lot of it focuses
S1: on self articulation, self understanding and presentation out to people. Okay.
S1: Not because you're trying to be an influencer. You know,
S1: forget influencers like influencer is like it's such a it's
S1: an anti-pattern. It's a toxic version of the thing that
S1: I am talking about, which we're going to get to,
S1: which is human 3.0. Okay. But but you're going to
S1: see how this is all forming together. So watch this.
S1: People should be broadcasting. People should be showing what they're into. Okay.
S1: We already do this with the clothes that we wear,
S1: with the accessories that we carry, with the conversations that
S1: we have with our facial expressions, with whether or not
S1: we smile or or do whatever when we look at people.
S1: So the point is, being an influencer is like artificially
S1: opening up this, this spigot that has been closed because
S1: we've been in human 2.0 for too long, which is
S1: basically human 2.0 is basically saying, look, if you want
S1: to talk about your skills with your company, that's fine,
S1: but I don't need to know about it. Right. And
S1: anybody who wants to talk about what they're into and
S1: share what they're into, you must be a narcissist. You
S1: must be an influencer type who just wants to be
S1: famous or whatever. No, listen to me. Humans are designed.
S1: Here's my argument. Humans should be sharing with other humans
S1: everything about you. I'm not talking about private stuff, Okay.
S1: I'm talking about everything about you. You love gardening. You
S1: love reading. You love all these things. This is meant
S1: to be shared. Okay. Not because you're an influencer, but
S1: because you care about these things and you want to
S1: connect with other people who care about these things. That
S1: is a human thing. Forget tech. Okay. I want to
S1: remind you about something. Everything in here, all this stuff.
S1: This is not tech. I don't want you to think
S1: about tech. And you damn sure shouldn't be thinking about AI.
S1: AI is nothing but intelligence. Okay? Forget any of that.
S1: This is all human based stuff. Everything about this. You
S1: see this person in the middle. Forget this bubble around him.
S1: That's an API. Nobody cares. What I care about is
S1: walking into a coffee shop and having my da go, hey,
S1: I know you're reading, but, uh, this guy who just
S1: walked in, he is reading the same book as you
S1: and it is listed as his number two book in
S1: his books, endpoint on His daemon. And, um, he's also
S1: doing a little side business that looks like this. And yeah,
S1: I think you'd really enjoy talking to him. Do you
S1: want me to ping his da? Um, so my da
S1: pings his da, and we look at each other and
S1: we're like, hey, what's up? You want to get a coffee?
S1: Let me buy you a coffee. So that is a
S1: human thing. That is not a tech thing. That is
S1: tech enabling human things. Everything here, substrate, fabric, it's all
S1: the same. Fabric is not tech problems. Fabric is full
S1: of human problems. Telos is not capturing tech stuff. It's
S1: capturing a business. It's capturing a person. It's capturing a
S1: program to do something better than it was done before. Okay,
S1: all of this is humans. Look at this mission for
S1: Damon Broadcasting. Forget influencers. The fact that only influencers are
S1: sharing anything about themselves is evidence of a broken society.
S1: That's the problem. That's what human 3.0 is undoing that. Okay,
S1: so what's this mission? Share yourself with humanity. That's. That's it.
S1: Share yourself with humanity. It doesn't have to be everything. Okay?
S1: You put what you want in your demon, and you
S1: can even have it blocked off and everything. Like, the
S1: better the tech gets, the more you're going to need
S1: authentication to get to certain ones. And only friends can
S1: see it. Like all that will come. But essentially what
S1: this is starting with is a structure for defining your
S1: personal API. Okay, so that's what it's going to be.
S1: It's a schema. And essentially what I'm doing here. And
S1: this is pretty early on for this one. What I'm
S1: going to do here is I'm going to have the schema.
S1: I'm going to have the templates for the schema for
S1: people to fill in. I'm also going to have um,
S1: collectors that go and get it from your content. If
S1: you want to run that, you just run it yourself.
S1: It goes and collects all your different stuff, and then
S1: it puts it in there, and then of course you
S1: can edit it. And then I'm going to have like
S1: a Docker container, I'm going to have like a domain
S1: setup or something like that where it all connects together
S1: and you press go and boom, it spins up. And
S1: on a particular domain that is associated with you, you
S1: will now be broadcasting your daemon. And then as people
S1: start to spin up their Das and when people meet
S1: each other. So for example, you could have like on
S1: your necklace thing or in a, in a daemon broadcast
S1: that is actually local or on an arm patch that
S1: is a QR code. Those can all be URLs to
S1: your actual daemon. So when your personal, um, tech that
S1: you're working with has a camera on it, which is
S1: absolutely coming, absolutely coming very soon, I mean, meta glasses
S1: already do, but I'm talking about a continuous camera. When
S1: it sees somebody's QR code walking by, broom. It pulls
S1: the thing, assuming it's not already broadcasting and can't detect
S1: it in a different way. The point is, we're going
S1: to move through the world seeing each other, broadcasting. It's
S1: going to be absolutely beautiful. Seeing each other, broadcasting, seeing
S1: each other surrounded in these auras of of purple and
S1: pink and like, you know, equations floating over somebody or
S1: like they're wrapped in vines. We know they love plants. Like,
S1: it's just going to be extraordinary. And don't think at
S1: all about the tech. Think about the connection to humanity
S1: that we will have enabled by tech. Tech should disappear. Okay,
S1: if I'm walking through the world and I see somebody
S1: and they look awesome, and they're smiling and they appear
S1: to be wrapped in plants, and the plants are, like,
S1: moving and like, you know, they they just look like
S1: one with nature or plants or whatever. I'm not thinking
S1: about tech. I'm like, I'm thinking they really like plants
S1: and so do I. So I'm going to talk to them.
S1: Me as a human going to talk to that person
S1: as a human. And we're going to talk about plants
S1: and soil and stuff. All right. That's Damon personal API broadcast. Okay. Now,
S1: this brings us to the big one. Human 3.0. I've
S1: been talking about this. I've been mentioning it. I've been
S1: saying the word for a very long time, and, uh,
S1: it's time to talk about it. So human 3.0 is
S1: a framework and platform for upgrading humans, both a framework
S1: and a platform. We're going to go into this. Its
S1: purpose is to help people transition from being a detail
S1: in the legacy corporate based economy to a new model
S1: of success based on self articulation and expression. Okay. Quite
S1: different from the others because it's basically the container for
S1: all these other ones. So all these other ones are
S1: moving towards this thing which hopefully you've been picking up.
S1: As I've been talking, it's all moving towards this bigger
S1: thing of human to human connection and actually an economy
S1: and society that is based on that, which not only
S1: do I think would be nice, okay, I'm not basically saying, oh,
S1: wouldn't it be nice if this was happening? Wouldn't it
S1: be nice if this were true? I am saying that,
S1: but I'm mostly saying the thing we're currently doing is
S1: not going to work anymore, because the economy that we
S1: have is based on humans mostly doing human 2.0 stuff
S1: in a very materialistic and shortsighted economy, where you spend
S1: from nine in the morning to 5:00 in the evening
S1: doing something basically inane, which drives you insane, makes you
S1: crave the weekend, and absolutely dread Monday coming up. I
S1: don't know what percentage of the world is like that,
S1: but it's a lot. Why do we got a thumbs up?
S1: What happened? Dreading Monday is not a thumbs up. I
S1: don't know why I did that. Listen, um, sounded like Biden. Listen. Listen, folks. Okay,
S1: so another way to state this is it's infrastructure that
S1: can make human 3.0 happen. Okay. All right. So now
S1: let's talk about the the core philosophy here of human 3.0.
S1: So here are the main concepts. Again there's a platform
S1: component of this as well. So it's an actual thing
S1: that you can go and do. And you could sign
S1: up for and actually go through. That's not what we're
S1: talking about here. First we're talking about the philosophy and
S1: the framework itself. Number one, humans have been trained over
S1: the last 150 years to become corporate workers and to
S1: primarily identify ourselves as corporate workers. Okay. This was never
S1: ideal for humans. And it's time has now passed. So
S1: AI is about to remove or disrupt most knowledge work
S1: and arguably a lot of other work once robots come
S1: as well. But either way, we have to get ready
S1: for what's coming next. And what I believe is coming
S1: next is becoming self-actualized, full spectrum humans that can create
S1: and offer value to other humans. Okay. Other humans. This
S1: transition requires a different way of thinking about how we
S1: learn things and how we define and pursue success. And
S1: it also involves becoming radically self-aware, becoming continuous learners who
S1: have the creative and financial freedom to spend their time
S1: doing purposeful work that they enjoy. That is the philosophy
S1: for human 3.0. Okay. And I'm going to update this.
S1: I'll continue to improve. I'll add some things, remove them.
S1: But ultimately this is the core of it. So here
S1: are the components. Okay. This is for the actual platform. Okay.
S1: So I want you to think of this. Human 3.0
S1: is a vision that I'm saying it's a thing that
S1: we should be thinking about. It's what I believe the
S1: future is. This has nothing to do with a platform.
S1: It has nothing to do with tech. I believe this
S1: is a changing of old to new, from legacy to
S1: what is coming. And importantly, I think there's a chasm
S1: in between these two things. Okay. I'm worried that we're
S1: being hit with AI and it's about to wreck hundreds
S1: of millions, no billions of people. It's about to wreck
S1: billions of people, especially the hundreds of millions who work
S1: in knowledge work. So we have legacy human 2.0. We have.
S1: I think that was going bad anyway because of the
S1: loss of religion. And for a lot of other reasons,
S1: we are already sort of steering into a bad place
S1: with a lack of meaning. And this is like five,
S1: ten years ago. Okay. It's already going to a bad place.
S1: And then you got social media. You got tech. Tech
S1: is causing more problems, but ultimately it comes down to
S1: we lost community and we lost religion and it was
S1: just taking us in a bad place. Now bring AI in.
S1: And one of the core things that gives us meaning
S1: as humans is actually our work. The fact that we
S1: feel like we're making some sort of contribution or work,
S1: somebody appreciates what we're doing. We're obviously having some sort
S1: of positive output. Otherwise they wouldn't be paying us. Okay,
S1: so that's a vibe. That's a thing that does give
S1: some meaning to people's lives. Now AI is coming to
S1: crush that. Not actually not on purpose, but it will.
S1: It will have the effect of removing or massively disrupting
S1: hundreds of millions of jobs. That's my belief. It's a
S1: belief of a lot of experts. Some people don't agree.
S1: Doesn't doesn't really matter. Let's assume it's 10% worse or 90%
S1: worse or better. It doesn't matter the actual numbers. Directionally,
S1: you should believe this. It is true. That's my claim. Now,
S1: given that the disruption is going to be extraordinary to society,
S1: to everyone, I have no idea what's going to happen.
S1: The number of variables are far too large. Anyone who
S1: tells you they can predict specific implementations of technology, they
S1: are lost and you should not listen to them. What
S1: I'm trying to predict is based on human desires, based
S1: on what humans want and have always wanted. So I'm
S1: trying to make some somewhat like evergreen, except for future
S1: looking predictions that are based on what we know humans
S1: need and how they're going to get that from the world.
S1: So that's essentially what I'm trying to do here, and
S1: what I'm principally worried about. If you go back to
S1: WP one, it's the loss of meaning. And WP two
S1: is the loss of meaning exacerbated Baited by AI taking jobs.
S1: So that's what it comes down to. Now the second
S1: piece is a platform that I'm building, an actual platform,
S1: a tech platform that helps you figure out what human
S1: 3.0 is, and it takes you through a giant series
S1: of steps. It's a guided walkthrough of steps in a curated,
S1: you know, organized way. So it's a full set of
S1: video courses, like, I even built all this stuff yet fully.
S1: I'm still working on the curriculum, but it's essentially a curriculum.
S1: It's videos. It's all this different stuff. This is not
S1: the pitch for that. So I'm not going to go
S1: into that here, but it shows you like how to
S1: use Telos, how to build your telos file yourself. Um,
S1: how to use fabric to look at your telos file,
S1: how to build your demon. It's like basically a walkthrough
S1: of how to actually go and implement all this other stuff.
S1: But here's the point. You don't actually need this thing
S1: that I'm building, Okay. You don't need it. All you
S1: have to do is look at all the other projects,
S1: which are the core projects. You could actually just go
S1: get them. Use them the way I talk about in
S1: the videos and you're already doing it. You're already moving
S1: towards human 3.0. And I'm going to make the assessment
S1: like the assessment is going to be available also open source.
S1: So it's like you could do all this stuff without
S1: the platform 100%. Like that's the way it's designed. But
S1: some people they want to be walked through it. They
S1: want it to be walked through it in an organized way.
S1: And that's why I'm building the human 3.0 platform, which
S1: is called H3. So yeah, all the different stuff shows
S1: you how to build online presence, shows you how to
S1: have like lots of different income streams and all that
S1: kind of stuff. Oh, here we go. I actually answered this.
S1: Why make a platform? You can honestly get what I'm
S1: offering here by going watching every video. This is exactly
S1: what I was just saying, right? You can do all
S1: of that. In fact, a lot of people already have,
S1: so they're already on the path, if not already achieved. Uh,
S1: human 3.0. The platform is just a guided version of it.
S1: So that's all it is. Um, all right, so I
S1: got a section here. Why? Listen to me. This is
S1: mostly because of the platform. Because they're like, yeah, why
S1: am I going to do a platform? Like, who the
S1: hell is this person? I'm not going to go into this.
S1: It's kind of gross. It's just like, I did this,
S1: I did that, blah, blah, blah blah. Some people need
S1: to see this before they will listen. So that's what.
S1: And that's why I have it way down here because
S1: it's like not important. It's just, man, I'm going to
S1: throw up in my mouth just looking at it. Um, yeah.
S1: How to charge for it? Not sure yet. It's going
S1: to be some kind of subscription. Maybe pay for the courses,
S1: I don't know. Um, that's on the platform side. I'm
S1: not worried about it. Again, you don't need the platform.
S1: All right. Component summary. So here's what we're going to do.
S1: We're going I'm going to summarize in a couple of
S1: different ways all of this different stuff okay. Everything that
S1: we've talked about so far. So, um, substrate, shared library
S1: of transparent objects that matter to humans. Oh, yeah. And
S1: I'm putting this free and open source, all of it.
S1: Fabric shared library of AI prompts that solve human problems.
S1: Also free and open source. All these free open source
S1: telos structure for capturing deep context about something humans care about.
S1: Free and open Source daemon system for publishing an entity
S1: to the world as an API and presenting that content
S1: on a website. Oh yeah, that's the other thing about daemon,
S1: which I forgot to mention. I'm actually going to use
S1: the daemon structure for the API to also be a
S1: website navigation structure. So you know how when you go
S1: to a website, it's like, oh, there's pull downs for
S1: like projects or about or whatever? Well, all of those
S1: I'm actually going to source out of Telos and the
S1: daemon so that those are available, so that when you
S1: update your Telos file or you update your source of truth,
S1: wherever that is, That can then propagate to your website
S1: as well. So it's like you have this vibrant like
S1: always aware sort of broadcast of yourself. And then human
S1: 3.0 is the platform for upgrading yourself. It's a paid program.
S1: It's the program piece. But the human 3.0 concept is
S1: actually just the combination of all of these put together,
S1: which doesn't require, um, any platform whatsoever. It's just like
S1: all concepts and all open source projects. All right. So
S1: summary unify my work around a central mission, which is
S1: helping people transition to this concept of human 3.0. Multiple
S1: components substrate, fabric Telos, daemon all focused on helping people
S1: and organizations, not just people, articulate what they are about
S1: so they can better improve themselves. Common themes here clarity, transparency,
S1: continuous optimization, and most importantly, purpose. Purpose. Absolutely important. It's
S1: it's in the WP one through three right. They all significant.
S1: This one's important. They all significantly feature I because of
S1: its ability to see patterns across multiple contexts. So here's
S1: what's really crazy. You could take your telos file. You
S1: could take your daemon. You could take all all this
S1: stuff and put these into context and send them to fabric.
S1: I do this all the time. I do this multiple
S1: times per day. And then that same content can be
S1: part of your daemon, right? And then those different components
S1: can be broken off and put into substrate. All of
S1: those go into another context. Those get sent to I.
S1: And you can ask all sorts of interesting questions and
S1: take actions, all based on all this being unified into context.
S1: And when you think about I, context sizes are getting
S1: bigger and bigger. Rag is getting bigger and bigger, but
S1: essentially you're going to be able to have your entire
S1: life and Apple is working on this. That's what they're
S1: working on with their AI, which is going to take
S1: a while to develop. Same with Google. Google is going
S1: to have it as well. Meta is going to have
S1: it as well, and a whole bunch of third parties
S1: are going to have it. Right. You're going to have
S1: the ability to have every image you've ever taken, every
S1: thought you've ever had, every idea you've ever had that was,
S1: you know, uh, original and cool, all your writing, every everything,
S1: everything about you all in one place. And by the way,
S1: security wise, this is going to be nasty. These things
S1: are going to get compromised. It's going to be really gross,
S1: no question about that. But the value that it's going
S1: to bring is going to be so immense and so
S1: much more than the risk that one these breaches will happen. Two,
S1: they will be really bad. And three, we will just
S1: continue on and do it anyway. That's just a fact
S1: of the matter. For anyone who's security oriented and you're
S1: wondering about this, that's what it is. And the final
S1: piece is a framework called human 3.0 brings it all together,
S1: both a framework for thinking about progress and a platform.
S1: But just for the sake of this video, just think
S1: about the framework that unifies it all. So what am
S1: I hoping you got from this page and from this video?
S1: One I hope you understand what I'm working on, how
S1: all these projects go together and why. And, um, that's
S1: number one. I just want you to see why I'm
S1: working on these things, why I'm so excited about them,
S1: how they all work together, how it's all tech based,
S1: and how they all play into this, this vision of
S1: what I'm seeing happening for human 3.0 and why I
S1: want to help people get there. That's my number one thing,
S1: is helping people get there. So if they get there
S1: through the open source projects, they get there through watching
S1: all the videos. Um, that I assume that's how most
S1: people are going to get there. And then people are
S1: just like, show me, make it for me, guide me
S1: through it. And so I'm going to make a platform
S1: that does that. Second piece is I want to encourage,
S1: also known as shame you into doing the same thing.
S1: This post here, not the projects themselves, but this post here.
S1: What I've done is I've basically taken all of my
S1: work over the last year and a half really, almost
S1: basically since going independent, maybe two years, two and a
S1: half years, I've taken all that work and I've brought
S1: it together into a cohesive explanation of why I'm doing
S1: that work, what problems that I'm setting out to solve
S1: when I talk to people, this is what I want
S1: to hear from them. I want to hear from them
S1: when I say, hey, what are you working on? I
S1: would love. This is one of the things I talked
S1: about recently. I love a particular sentence, I believe. Watch
S1: this sentence. Very powerful. Great for parties, great for like explaining,
S1: especially professional parties. I believe that one of the biggest
S1: problems in the world is this. Which is why I
S1: am building this. I believe that it will do this
S1: for the world. Which is why I'm doing it. So
S1: I've defined the problem, I've defined what I'm trying to do,
S1: and I've defined how I think it's going to help. Right.
S1: And you can mention KPIs there, or it could be
S1: something more amorphous. But I love the clarity of this, right?
S1: I love the clarity of like, what are we actually
S1: doing here? What are we actually doing here? And this
S1: is a central theme for every single one of these projects. Clarity.
S1: Because clarity, once you lock that in on a purpose,
S1: that is what gives you fulfillment. That is what gives
S1: you the ability to, like, take all this damage from
S1: the world, right? Experience all the suffering, which I massively
S1: learned from Viktor Frankl. If you are locked on on
S1: this distant purpose and you're taking damage, it can actually
S1: feel good. It can actually feel good to struggle, right?
S1: If you're locked on this thing. So the second piece
S1: of this is I want to encourage you, right. You're
S1: out there, you're working every day. You're putting stuff on
S1: social media to sometimes maybe depending on who I'm talking to,
S1: your stuff is out there. Can you describe it crisply?
S1: Can you clarify what problems you're trying to solve? Can
S1: you crystallize it down to 15 words? My favorite length
S1: for summarizations of this type? Can you crystallize it to
S1: 15 words? Can you articulate it to a person as
S1: I am doing this work because I believe it solves
S1: this problem, and that's why I'm doing these projects, right? I,
S1: I think it's just beautiful. I think it's beautiful. And
S1: part of this is to get my stuff out there, right?
S1: I mean, this is the thing you have to do.
S1: You have you have to talk about your work. You
S1: got to get it out there. I want people to
S1: be excited, all of that. But this second piece is
S1: just as important I want to see yours. Now show
S1: me yours. Go and make this something like this. Half
S1: a page, whatever. It could be a set of bullets.
S1: I'm working on this because of this. I'm working on this.
S1: Because of this. Here are the problems I'm trying to solve.
S1: Send them to me, Daniel at Daniel Morcombe. Send them
S1: to me. I want to see what you're working on.
S1: And I want to see why. And, uh, look forward
S1: to seeing you in the next one. Take care. Unsupervised
S1: learning is produced and edited by Daniel Miessler on a
S1: Neumann U87 AI microphone using Hindenburg. Intro and outro music
S1: is by zombie with a Y. And to get the
S1: text and links from this episode, sign up for the
S1: newsletter version of the show at Daniel missler.com/newsletter.
UU: We'll see you next time.