Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

there's now a formal proof that your agent's vector memory forgets what you stored and fabricates things you never did. scaling it up makes both worse, not better. "the price of meaning" (arxiv 2603.27116) proves it for any memory that retrieves by similarity in an embedding space. the same...

rohit4verse's profile picture

Rohit

23,396 subscribers

15,966 Aufrufe • vor 1 Monat •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

New course: Agent Memory: Building Memory-Aware Agents, built in partnership with Oracle and taught by Richmond Alake and Nacho Martínez. Many agents work well within a single session but their memory resets once the session ends. Consider a research agent working on dozens of papers across multiple days: without memory, it has no way to store and retrieve what it learned across sessions. This short course teaches you to build a memory system that enables agents to persist memory and thereby learn across sessions. You'll design a Memory Manager that handles different memory types, implement semantic tool retrieval that scales without bloating the context, and build write-back pipelines that let your agent autonomously update and refine what it knows over time. Skills you'll gain: - Build persistent memory stores for different agent memory types - Implement a Memory Manager that orchestrates how your agent reads, writes, and retrieves memory - Treat tools as procedural memory and retrieve only relevant ones at inference time using semantic search Join and learn to build agents that remember and improve over time!
1:37

New course: Agent Memory: Building Memory-Aware Agents, built in partnership with Oracle and taught by Richmond Alake and Nacho Martínez. Many agents work well within a single session but their memory resets once the session ends. Consider a research agent working on dozens of papers across multiple days: without memory, it has no way to store and retrieve what it learned across sessions. This short course teaches you to build a memory system that enables agents to persist memory and thereby learn across sessions. You'll design a Memory Manager that handles different memory types, implement semantic tool retrieval that scales without bloating the context, and build write-back pipelines that let your agent autonomously update and refine what it knows over time. Skills you'll gain: - Build persistent memory stores for different agent memory types - Implement a Memory Manager that orchestrates how your agent reads, writes, and retrieves memory - Treat tools as procedural memory and retrieve only relevant ones at inference time using semantic search Join and learn to build agents that remember and improve over time!

Andrew Ng

159,926 Aufrufe • vor 4 Monaten

New short course: Long-Term Agentic Memory with LangGraph. Learn to build an agent with long-term memory in this course developed in collaboration with taught by its Co-Founder and CEO, Harrison Chase! Personal assistance and productivity tasks have become important use cases for agents. An important feature of an AI assistant, such as a coding or calendar assistant, is its ability to keep improving over time from its experience. Agent memory is the key capability that enables this. To add memory to an agent, you must first figure out what to store and what to retrieve when it is time to use the information. Additionally, you’ll have to decide when to update the stored information. For example, you might update in each iteration loop of the agent or perform updates in the background, with a helper agent. In this course, you will learn a mental framework to build agents with long-term memory. You'll create a useful email assistant that can respond, ignore, and notify using writing, scheduling, and memory-management tools. You’ll develop your agent's memory by adding facts to its memory store, provide examples to learn the user's preferences, and optimize system prompts to evolve instructions based on previous responses. In detail, you’ll: - Learn how the three types of memory--semantic, episodic, and procedural–and the two update mechanisms–via hot path and in the background–apply to your agents. - Build an email agent with writing, scheduling, and availability tools, along with a router that triages incoming email and handles it accordingly by ignoring, responding, or notifying the user. - Add tools to your email agent that allow it to operate on semantic memory by learning facts about the user, storing them in a long-term memory store, and searching over them in future interactions. - Incorporate episodic memory, in the form of few-shot examples, in the triage step of your agents to help them learn and update user preferences. - Add procedural memory as system prompts, optimized with feedback to improve the instructions the agent follows. Learn how to approach memory in agents, and start building agents with long-term memory with LangGraph! Please sign up here:
2:06

New short course: Long-Term Agentic Memory with LangGraph. Learn to build an agent with long-term memory in this course developed in collaboration with taught by its Co-Founder and CEO, Harrison Chase! Personal assistance and productivity tasks have become important use cases for agents. An important feature of an AI assistant, such as a coding or calendar assistant, is its ability to keep improving over time from its experience. Agent memory is the key capability that enables this. To add memory to an agent, you must first figure out what to store and what to retrieve when it is time to use the information. Additionally, you’ll have to decide when to update the stored information. For example, you might update in each iteration loop of the agent or perform updates in the background, with a helper agent. In this course, you will learn a mental framework to build agents with long-term memory. You'll create a useful email assistant that can respond, ignore, and notify using writing, scheduling, and memory-management tools. You’ll develop your agent's memory by adding facts to its memory store, provide examples to learn the user's preferences, and optimize system prompts to evolve instructions based on previous responses. In detail, you’ll: - Learn how the three types of memory--semantic, episodic, and procedural–and the two update mechanisms–via hot path and in the background–apply to your agents. - Build an email agent with writing, scheduling, and availability tools, along with a router that triages incoming email and handles it accordingly by ignoring, responding, or notifying the user. - Add tools to your email agent that allow it to operate on semantic memory by learning facts about the user, storing them in a long-term memory store, and searching over them in future interactions. - Incorporate episodic memory, in the form of few-shot examples, in the triage step of your agents to help them learn and update user preferences. - Add procedural memory as system prompts, optimized with feedback to improve the instructions the agent follows. Learn how to approach memory in agents, and start building agents with long-term memory with LangGraph! Please sign up here:

Andrew Ng

131,779 Aufrufe • vor 1 Jahr

New short course: LLMs as Operating Systems: Agent Memory, created with Letta, and taught by its founders Charles Packer and Sarah Wooders. An LLM's input context window has limited space. Using a longer input context also costs more and results in slower processing. So, managing what's stored in this context window is important. In the innovative paper MemGPT: Towards LLMs as Operating Systems, its authors (which include the instructors) proposed using an LLM agent to manage this context window. Their system uses a large persistent memory that stores everything that could be included in the input context, and an agent decides what is actually included. Take the example of building a chatbot that needs to remember what's been said earlier in a conversation (perhaps over many days of interaction with a user). As the conversation's length grows, the memory management agent will move information from the input context to a persistent searchable database; summarize information to keep relevant facts in the input context; and restore relevant conversation elements from further back in time. This allows a chatbot to keep what's currently most relevant in its input context memory to generate the next response. When I read the original MemGPT paper, I thought it was an innovative technique for handling memory for LLMs. The open-source Letta framework, which we'll use in this course, makes MemGPT easy to implement. It adds memory to your LLM agents and gives them transparent long-term memory. In detail, you’ll learn: - How to build an agent that can edit its own limited input context memory, using tools and multi-step reasoning - What is a memory hierarchy (an idea from computer operating systems, which use a cache to speed up memory access), and how these ideas apply to managing the LLM input context (where the input context window is a "cache" storing the most relevant information; and an agent decides what to move in and out of this to/from a larger persistent storage system) - How to implement multi-agent collaboration by letting different agents share blocks of memory This course will give you a sophisticated understanding of memory management for LLMs, which is important for chatbots having long conversations, and for complex agentic workflows. Please sign up here!
2:57

New short course: LLMs as Operating Systems: Agent Memory, created with Letta, and taught by its founders Charles Packer and Sarah Wooders. An LLM's input context window has limited space. Using a longer input context also costs more and results in slower processing. So, managing what's stored in this context window is important. In the innovative paper MemGPT: Towards LLMs as Operating Systems, its authors (which include the instructors) proposed using an LLM agent to manage this context window. Their system uses a large persistent memory that stores everything that could be included in the input context, and an agent decides what is actually included. Take the example of building a chatbot that needs to remember what's been said earlier in a conversation (perhaps over many days of interaction with a user). As the conversation's length grows, the memory management agent will move information from the input context to a persistent searchable database; summarize information to keep relevant facts in the input context; and restore relevant conversation elements from further back in time. This allows a chatbot to keep what's currently most relevant in its input context memory to generate the next response. When I read the original MemGPT paper, I thought it was an innovative technique for handling memory for LLMs. The open-source Letta framework, which we'll use in this course, makes MemGPT easy to implement. It adds memory to your LLM agents and gives them transparent long-term memory. In detail, you’ll learn: - How to build an agent that can edit its own limited input context memory, using tools and multi-step reasoning - What is a memory hierarchy (an idea from computer operating systems, which use a cache to speed up memory access), and how these ideas apply to managing the LLM input context (where the input context window is a "cache" storing the most relevant information; and an agent decides what to move in and out of this to/from a larger persistent storage system) - How to implement multi-agent collaboration by letting different agents share blocks of memory This course will give you a sophisticated understanding of memory management for LLMs, which is important for chatbots having long conversations, and for complex agentic workflows. Please sign up here!

Andrew Ng

200,788 Aufrufe • vor 1 Jahr

The creator of High Bandwidth Memory (HBM) put a number on the AI build that should stop every infra investor cold. A cluster of a million GPUs runs at roughly 10-20% utilization (Save this). Kim Jung-ho spent thirty years building what feeds the GPU, and his claim is that the GPU is barely working. Here is what is actually happening. Every time a model generates output, the data has to be read out of memory, computed, and written back. The read and the write swallow almost the entire cycle. While that data moves, the GPU does nothing. It sits there, fully powered, fully paid for, waiting. By Kim's estimate the memory is doing only about 30 percent of the work it needs to do. The processor idles the rest. So a million installed GPUs run at 10 to 20 percent. You are not compute constrained. You are memory constrained, and the expensive part is standing around. Adding more GPUs does not fix this. It gives you more processors starving for the same data. Here is the part that decides the next decade. Memory can grow. When a cell cannot shrink any further, you stack it into a high-rise, layer on layer. A GPU cannot be stacked. It runs too hot and needs a cooler bolted to its back, so the one move that rescues memory is closed to the processor. The thing that can keep stacking compounds. The thing that cannot plateaus. The marginal dollar in an AI build now buys more by fixing the memory path than by bolting on another idle GPU. Which is why the companies that control memory bandwidth and supply are not suppliers to the AI trade. They are the AI trade.
0:50

The creator of High Bandwidth Memory (HBM) put a number on the AI build that should stop every infra investor cold. A cluster of a million GPUs runs at roughly 10-20% utilization (Save this). Kim Jung-ho spent thirty years building what feeds the GPU, and his claim is that the GPU is barely working. Here is what is actually happening. Every time a model generates output, the data has to be read out of memory, computed, and written back. The read and the write swallow almost the entire cycle. While that data moves, the GPU does nothing. It sits there, fully powered, fully paid for, waiting. By Kim's estimate the memory is doing only about 30 percent of the work it needs to do. The processor idles the rest. So a million installed GPUs run at 10 to 20 percent. You are not compute constrained. You are memory constrained, and the expensive part is standing around. Adding more GPUs does not fix this. It gives you more processors starving for the same data. Here is the part that decides the next decade. Memory can grow. When a cell cannot shrink any further, you stack it into a high-rise, layer on layer. A GPU cannot be stacked. It runs too hot and needs a cooler bolted to its back, so the one move that rescues memory is closed to the processor. The thing that can keep stacking compounds. The thing that cannot plateaus. The marginal dollar in an AI build now buys more by fixing the memory path than by bolting on another idle GPU. Which is why the companies that control memory bandwidth and supply are not suppliers to the AI trade. They are the AI trade.

Fireside Alpha

38,370 Aufrufe • vor 25 Tagen

Geoffrey Hinton just made every AI critic accidentally describe their own brain. Hinton: “They shouldn’t be called hallucinations. They should be called confabulations.” One word. The entire debate unravels. The tech industry sees AI produce a confident wrong answer and calls it a defect. A bug to patch. They are measuring intelligence against the standard of a filing cabinet. And exposing that they understand neither. Hinton: “It’s not that there’s a file stored somewhere in your brain, like in a filing cabinet or in a computer memory.” Your brain does not store memories. It rebuilds them from nothing every time you remember. Fills gaps it never discloses. Fabricates details you would stake your life on. Then hands it all to you as truth. Hinton: “If I ask you to remember something that happened a few years ago, you’ll construct something that seems very plausible to you. And some of the details will be right and some will be wrong.” The wrong parts feel identical to the right ones. No internal warning. No distinction between what was remembered and what was invented on the spot. You have argued over memories that were partially fiction. Told stories about your own life that your brain manufactured in real time. With total conviction. And never once suspected. This is not a defect in human cognition. This IS cognition. The mechanism that fabricates is the same one that reasons, creates, and makes connections no one taught it to make. Not a separate system. Same architecture. Same process. You cannot remove the confabulation without killing the intelligence. They are the same thing. Hinton: “Psychologists have been studying confabulation in people since at least the 1930s.” A century of evidence. No one called the human brain broken. The moment a machine runs on the same principle, the world calls it defective. The people demanding AI that never gets a single detail wrong are not asking for intelligence. They’re asking for a search engine that sounds articulate. What we built is something else entirely. A system that thinks the way thinking actually works. Not retrieval. Construction. The imperfection is not the cost of intelligence. It is the signature.
1:05

Geoffrey Hinton just made every AI critic accidentally describe their own brain. Hinton: “They shouldn’t be called hallucinations. They should be called confabulations.” One word. The entire debate unravels. The tech industry sees AI produce a confident wrong answer and calls it a defect. A bug to patch. They are measuring intelligence against the standard of a filing cabinet. And exposing that they understand neither. Hinton: “It’s not that there’s a file stored somewhere in your brain, like in a filing cabinet or in a computer memory.” Your brain does not store memories. It rebuilds them from nothing every time you remember. Fills gaps it never discloses. Fabricates details you would stake your life on. Then hands it all to you as truth. Hinton: “If I ask you to remember something that happened a few years ago, you’ll construct something that seems very plausible to you. And some of the details will be right and some will be wrong.” The wrong parts feel identical to the right ones. No internal warning. No distinction between what was remembered and what was invented on the spot. You have argued over memories that were partially fiction. Told stories about your own life that your brain manufactured in real time. With total conviction. And never once suspected. This is not a defect in human cognition. This IS cognition. The mechanism that fabricates is the same one that reasons, creates, and makes connections no one taught it to make. Not a separate system. Same architecture. Same process. You cannot remove the confabulation without killing the intelligence. They are the same thing. Hinton: “Psychologists have been studying confabulation in people since at least the 1930s.” A century of evidence. No one called the human brain broken. The moment a machine runs on the same principle, the world calls it defective. The people demanding AI that never gets a single detail wrong are not asking for intelligence. They’re asking for a search engine that sounds articulate. What we built is something else entirely. A system that thinks the way thinking actually works. Not retrieval. Construction. The imperfection is not the cost of intelligence. It is the signature.

Dustin

16,260 Aufrufe • vor 19 Tagen

Hermes agent just left the terminal. 𝗛𝗲𝗿𝗺𝗲𝘀 𝗗𝗲𝘀𝗸𝘁𝗼𝗽 dropped yesterday. native app for macOS, Windows, and Linux. for months Hermes was the agent that learned your projects, wrote its own skills, and built a model of who you are. all of it buried in terminal logs. now it has a window. the important part is that it's not a wrapper. it runs the same agent core, the same sessions, memory, and skills as the CLI. you can start a task in the terminal and finish it in the app without anything resetting. the state is shared across every interface, not copied between them. what the GUI actually adds: → streaming chat that shows live tool calls and inline reasoning instead of a spinner → a preview rail that renders pages, code, and images right beside the conversation → an artifacts panel that collects every file the agent has ever produced → remote gateway mode, so you can point the app at a VPS and run the heavy work elsewhere → skills, cron, profiles, and gateways managed point-and-click instead of through YAML → voice mode, drag-drop files, and inline image generation remote gateway mode is the one worth slowing down on. the agent runs 24/7 on a $5 server while you control it from your laptop like a local app. other agent UIs are chatboxes with a logo. this one shows the autonomy instead of hiding it, so you watch the skills load, the tools fire, and the artifacts pile up as it works. it was teased in Jensen's GTC keynote. MIT licensed, local-first, no telemetry. if you already run Hermes, download it and everything is already there. your chats, memory, and skills carry straight over. i wrote a full masterclass on Hermes Agent that walks through the SOUL. md identity layer, the three-tier memory system, the self-evolving skills loop, and how to run three specialized agents 24/7. desktop is the interface that finally does all of it justice. the article is quoted below.
1:18

Hermes agent just left the terminal. 𝗛𝗲𝗿𝗺𝗲𝘀 𝗗𝗲𝘀𝗸𝘁𝗼𝗽 dropped yesterday. native app for macOS, Windows, and Linux. for months Hermes was the agent that learned your projects, wrote its own skills, and built a model of who you are. all of it buried in terminal logs. now it has a window. the important part is that it's not a wrapper. it runs the same agent core, the same sessions, memory, and skills as the CLI. you can start a task in the terminal and finish it in the app without anything resetting. the state is shared across every interface, not copied between them. what the GUI actually adds: → streaming chat that shows live tool calls and inline reasoning instead of a spinner → a preview rail that renders pages, code, and images right beside the conversation → an artifacts panel that collects every file the agent has ever produced → remote gateway mode, so you can point the app at a VPS and run the heavy work elsewhere → skills, cron, profiles, and gateways managed point-and-click instead of through YAML → voice mode, drag-drop files, and inline image generation remote gateway mode is the one worth slowing down on. the agent runs 24/7 on a $5 server while you control it from your laptop like a local app. other agent UIs are chatboxes with a logo. this one shows the autonomy instead of hiding it, so you watch the skills load, the tools fire, and the artifacts pile up as it works. it was teased in Jensen's GTC keynote. MIT licensed, local-first, no telemetry. if you already run Hermes, download it and everything is already there. your chats, memory, and skills carry straight over. i wrote a full masterclass on Hermes Agent that walks through the SOUL. md identity layer, the three-tier memory system, the self-evolving skills loop, and how to run three specialized agents 24/7. desktop is the interface that finally does all of it justice. the article is quoted below.

Akshay 🚀

51,370 Aufrufe • vor 1 Monat

I've become a missionary with one message. Every time I meet a young person, the same words: have children, get married, build a family. I did not decide on this calling. It overtook me. And it overtook me for a single reason. I had no idea. I genuinely did not understand how much joy, how much meaning, how much sheer beauty pours out of a child until I was holding one of my own and felt the floor of my life drop into something deeper than I knew was there. I grew up white, affluent, secular, comfortable, and insulated. That world does not put babies in front of you. None of my friends were starting families. Out of my whole circle, almost no one has a big one. We were not formed by the presence of children. We were formed by their absence, by the strange quiet of homes built for two careers and no cradle. And a person believes what his world shows him. So we believed. What we believed was a lie. It is a lie with an author, and that the author is the enemy of joy himself. It is the gospel of the world, and its commandment is wait. Wait until you are older. Wait until the career is built and the savings are stacked and the twenties are properly spent. Enjoy your freedom. You are not ready. It does not arrive sounding like temptation. It arrives sounding like wisdom, like prudence, like the responsible thing, and that is exactly why it works. The most effective lies are the ones that wear the face of virtue. And the maddening thing is that it collapses from every angle at once. It is not rooted in biology, because the body is made for this work precisely in the years we are told to postpone it. The flesh keeps a calendar the culture pretends not to see. And it is not rooted in theology either. You will not find this deferral anywhere in the Christian imagination, in any of the fathers, in any of the scriptures. So choose whatever lens you like. Take the cold secular measure or the ancient sacred one. By either light the counsel is rotten. It is bad for the body and bad for the soul and bad for the society downstream of both. This is why I have come to see it as one of the central tragedies of my generation. Every age carries its own wound. The Great Depression was a depression of bread, a scarcity in the world of matter, hunger you could measure. Ours is a depression of a different order. It is a famine of the spirit in the middle of abundance. We have more than any people who ever lived and we are starving in a way our ancestors would not recognize, because the thing we are refusing cannot be bought and cannot be banked. The ones most made to give and receive this love are quietly declining it. They are walking away from the one inheritance that actually compounds, and the cruelest part is that they do not feel the loss as loss. You cannot grieve what you were taught not to want. That is the deepest cut of it. The lie does not only steal the thing. It steals the capacity to know the thing was stolen. A man can spend his whole life on the far side of a door he never knew was a door, mistaking the wall for the edge of the world. Because this beauty is not ordinary beauty. It is not the pleasure of a good meal or a clear morning. It is participation in something that comes down from above, the same generative love that spoke everything out of nothing and called it good. To make a person, to be undone and remade by loving that person more than your own life, is to be drawn for a moment inside the very act that holds the cosmos together. A child does not merely add to your life. A child reorders the soul. It teaches you what you are by asking everything of you, and you discover, kneeling there exhausted at three in the morning, that you had a capacity for self gift you never suspected, a depth in yourself you had no other way to reach. In the Gospel of John, on the last night, Jesus prays, these things I have spoken to you that my joy may be in you, and that your joy may be complete. And I have come to understand why family is the road into that fullness, why it is not one path among many but the one most fitted to the shape of the promise. Consider who is praying. Christ does not come to us as a lone figure dropped out of the sky. He comes out of a family older than the world, the eternal communion of Father and Son, the love between them so total and so alive that theologians dared to call it a third person. Before there was anything, there was a family. The deepest fact about reality is not a force or a law or a void. It is a household. It is begetting and being begotten, giving and receiving, a Father who is only a Father because there is a Son. So when Jesus speaks of joy made complete, he is not pointing away from family toward something higher. He is pointing toward the very thing he came from, the life he has known from eternity and came to share. His joy is the joy of belonging utterly to a Father and pouring himself out for those he loves. When you marry, when you bring a child into the world, when you wear yourself down in the small unseen labors of a home, you are not stepping outside that divine life. You are stepping into a small image of it. Your family is a created echo of an uncreated one. The love you give your child rhymes with the love the Father has for the Son. The exhaustion, the tenderness, the way a parent would tear the sky open to protect a sleeping infant, all of it is the heavens pressed faintly into flesh, the eternal household leaving its fingerprint on yours. That is why the joy is not merely added to family but completed in it. We were made in the image of a God who is, at his very root, relation and gift and generation. To found a family is to do the most Godlike thing a creature can do, to participate from below in the begetting that God does from all eternity. Your home becomes a window. Through it, dimly and imperfectly, you glimpse the country you came from and are going to. And now a word for the young people reading this, the ones who do not yet have children. I want to tell you what it is like from where I stand. When I am out somewhere, a restaurant, anywhere, and a large family comes through the door, the noise and the chaos and the small bodies of them, something happens in me on two levels at once. The first is joy. A pure gladness at the sight, the way you feel watching something good and alive. But underneath it, almost in the same instant, a sadness reaches up and takes hold of my heart. Because I know now, at my age, after my own years of waiting, that I will never have that. I will never know the particular fruit of a family that large, the fullness of that table, the weight of all those lives gathered under one roof. The door to it has quietly closed, and I felt it close. And I am telling you plainly, because I love you and have no reason to lie to you: you will feel this too. You will. The day will come when you see what you passed up, and you will recognize the ache for what it is, and it will be too late to answer it. So please, learn from a man who got it wrong. Let my regret be worth something by becoming your wisdom. Do not wait yourself into a grief you cannot undo. Choose now, while the door is open, so that you may step into a joy that does not end.
8:26

I've become a missionary with one message. Every time I meet a young person, the same words: have children, get married, build a family. I did not decide on this calling. It overtook me. And it overtook me for a single reason. I had no idea. I genuinely did not understand how much joy, how much meaning, how much sheer beauty pours out of a child until I was holding one of my own and felt the floor of my life drop into something deeper than I knew was there. I grew up white, affluent, secular, comfortable, and insulated. That world does not put babies in front of you. None of my friends were starting families. Out of my whole circle, almost no one has a big one. We were not formed by the presence of children. We were formed by their absence, by the strange quiet of homes built for two careers and no cradle. And a person believes what his world shows him. So we believed. What we believed was a lie. It is a lie with an author, and that the author is the enemy of joy himself. It is the gospel of the world, and its commandment is wait. Wait until you are older. Wait until the career is built and the savings are stacked and the twenties are properly spent. Enjoy your freedom. You are not ready. It does not arrive sounding like temptation. It arrives sounding like wisdom, like prudence, like the responsible thing, and that is exactly why it works. The most effective lies are the ones that wear the face of virtue. And the maddening thing is that it collapses from every angle at once. It is not rooted in biology, because the body is made for this work precisely in the years we are told to postpone it. The flesh keeps a calendar the culture pretends not to see. And it is not rooted in theology either. You will not find this deferral anywhere in the Christian imagination, in any of the fathers, in any of the scriptures. So choose whatever lens you like. Take the cold secular measure or the ancient sacred one. By either light the counsel is rotten. It is bad for the body and bad for the soul and bad for the society downstream of both. This is why I have come to see it as one of the central tragedies of my generation. Every age carries its own wound. The Great Depression was a depression of bread, a scarcity in the world of matter, hunger you could measure. Ours is a depression of a different order. It is a famine of the spirit in the middle of abundance. We have more than any people who ever lived and we are starving in a way our ancestors would not recognize, because the thing we are refusing cannot be bought and cannot be banked. The ones most made to give and receive this love are quietly declining it. They are walking away from the one inheritance that actually compounds, and the cruelest part is that they do not feel the loss as loss. You cannot grieve what you were taught not to want. That is the deepest cut of it. The lie does not only steal the thing. It steals the capacity to know the thing was stolen. A man can spend his whole life on the far side of a door he never knew was a door, mistaking the wall for the edge of the world. Because this beauty is not ordinary beauty. It is not the pleasure of a good meal or a clear morning. It is participation in something that comes down from above, the same generative love that spoke everything out of nothing and called it good. To make a person, to be undone and remade by loving that person more than your own life, is to be drawn for a moment inside the very act that holds the cosmos together. A child does not merely add to your life. A child reorders the soul. It teaches you what you are by asking everything of you, and you discover, kneeling there exhausted at three in the morning, that you had a capacity for self gift you never suspected, a depth in yourself you had no other way to reach. In the Gospel of John, on the last night, Jesus prays, these things I have spoken to you that my joy may be in you, and that your joy may be complete. And I have come to understand why family is the road into that fullness, why it is not one path among many but the one most fitted to the shape of the promise. Consider who is praying. Christ does not come to us as a lone figure dropped out of the sky. He comes out of a family older than the world, the eternal communion of Father and Son, the love between them so total and so alive that theologians dared to call it a third person. Before there was anything, there was a family. The deepest fact about reality is not a force or a law or a void. It is a household. It is begetting and being begotten, giving and receiving, a Father who is only a Father because there is a Son. So when Jesus speaks of joy made complete, he is not pointing away from family toward something higher. He is pointing toward the very thing he came from, the life he has known from eternity and came to share. His joy is the joy of belonging utterly to a Father and pouring himself out for those he loves. When you marry, when you bring a child into the world, when you wear yourself down in the small unseen labors of a home, you are not stepping outside that divine life. You are stepping into a small image of it. Your family is a created echo of an uncreated one. The love you give your child rhymes with the love the Father has for the Son. The exhaustion, the tenderness, the way a parent would tear the sky open to protect a sleeping infant, all of it is the heavens pressed faintly into flesh, the eternal household leaving its fingerprint on yours. That is why the joy is not merely added to family but completed in it. We were made in the image of a God who is, at his very root, relation and gift and generation. To found a family is to do the most Godlike thing a creature can do, to participate from below in the begetting that God does from all eternity. Your home becomes a window. Through it, dimly and imperfectly, you glimpse the country you came from and are going to. And now a word for the young people reading this, the ones who do not yet have children. I want to tell you what it is like from where I stand. When I am out somewhere, a restaurant, anywhere, and a large family comes through the door, the noise and the chaos and the small bodies of them, something happens in me on two levels at once. The first is joy. A pure gladness at the sight, the way you feel watching something good and alive. But underneath it, almost in the same instant, a sadness reaches up and takes hold of my heart. Because I know now, at my age, after my own years of waiting, that I will never have that. I will never know the particular fruit of a family that large, the fullness of that table, the weight of all those lives gathered under one roof. The door to it has quietly closed, and I felt it close. And I am telling you plainly, because I love you and have no reason to lie to you: you will feel this too. You will. The day will come when you see what you passed up, and you will recognize the ache for what it is, and it will be too late to answer it. So please, learn from a man who got it wrong. Let my regret be worth something by becoming your wisdom. Do not wait yourself into a grief you cannot undo. Choose now, while the door is open, so that you may step into a joy that does not end.

Kirk Rollins

77,958 Aufrufe • vor 1 Monat

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.
4:19

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

DegenCalls

20,104 Aufrufe • vor 23 Tagen

Everyone's building AI agents that run on someone else's server, store memory in someone else's database, and can be shut down by someone else's terms of service. I built one that can't be. FlowClaw is an AI agent that runs on a decentralized distributed computer. Your agent, your conversations, your memory, your tools — all stored onchain on Flow, a distributed network of validator nodes across the world. Not a centralized cloud. Not someone's S3 bucket. A blockchain that functions as censorship-resistant compute and storage for your AI. This isn't a wrapper. Your agent is a Resource — a first-class programmable object in Cadence (Flow's smart contract language) that physically lives in your account's on-chain storage. It can't be duplicated, seized, or deleted by anyone except you. Your encrypted messages, your cognitive memory, your scheduled tasks — they persist on a global distributed ledger that no single entity controls. It's an alpha build. It will break. But it works today on mainnet and I want people to push it this weekend. What it does: You go to authenticate with a passkey (Face ID, Touch ID), and you have a blockchain account in seconds. No wallet. No seed phrase. No tokens needed — gas is sponsored. You're immediately chatting with an AI agent that has real tool execution: live web data, token prices, on-chain balances, Cadence script execution, FLOW transfers. Every message is encrypted client-side before it touches the chain. The agent has a cognitive memory system — it doesn't just remember your last message, it builds molecular memory clusters where related knowledge bonds together for contextual retrieval across sessions. You can spawn sub-agents from a visual canvas to run parallel research. The memory tab shows you exactly what your agent knows. Everything is transparent and everything is yours. 11 smart contracts. No external dependencies. No keeper networks. No account abstraction hacks. Here's the part that matters for the censorship-resistance crowd: FlowClaw supports BYOK — bring your own key. You can plug in any LLM provider. But pair it with Venice and you get the full stack: a censorship-resistant AI model running inference with no content filtering, connected to an agent whose state lives on a decentralized network that no company can shut down, with end-to-end encrypted conversations that nobody can read — not the relay operator, not the LLM provider, not the blockchain validators. Venice doesn't log prompts. Flow can't read your encrypted storage. The relay never sees your plaintext. That's not a privacy policy. That's architecture. You can also use OpenAI, Anthropic, or any OpenAI-compatible provider. The agent platform doesn't care — it's model-agnostic. But the Venice pairing is the one that closes every gap in the stack. For the people tinkering with OpenClaw and the broader open-source agent ecosystem — FlowClaw is exploring what happens when you take the agent off the cloud entirely. Not just open-sourcing the code (though it is), but putting the actual runtime state on a distributed computer. Your agent's memory isn't in a SQLite file on your laptop or a Pinecone index on someone's cluster. It's on-chain, encrypted, and replicated across every validator node on Flow. You own it the way you own a private key — mathematically, not contractually. The blockchain here isn't a gimmick bolted onto an agent for token speculation. It's functioning as the infrastructure layer that replaces AWS. Flow accounts are programmable containers with their own storage, keys, and security capabilities. Passkey authentication works natively because Flow supports P-256 keys at the protocol level — the same curve your phone uses for biometrics. Gas sponsorship works natively because Flow transactions have separate proposer, authorizer, and payer roles built into the protocol. No proxy contracts. No relayers. No ERC-4337. Now here's the part that interests me economically. Every FlowClaw interaction is an on-chain transaction. Every message stored, every memory committed, every session created, every sub-agent spawned. An active user might generate dozens of transactions in a single conversation. Scale that and FlowClaw becomes a real contributor to Flow's transaction volume. Flow.com becomes deflationary at 250 TPS. Applications like FlowClaw that generate high-frequency, storage-heavy transactions are exactly what moves the needle. Every encrypted message uses account storage, which requires FLOW balance to back it. Every transaction burns fees. The more agents running, the more demand for $FLOW — not because of a tokenomics gimmick, but because the protocol literally requires it for compute and storage. FlowClaw doesn't have its own token. The token is $FLOW. The entire platform runs natively on the network — using Flow storage, paying Flow transaction fees, backed by Flow account balances. If FlowClaw succeeds, FLOW captures that value directly. I'm sharing this early because the AI agent space is moving fast and I think the decentralized infrastructure angle is underexplored. Most "crypto AI" projects are tokens with a chatbot attached. FlowClaw is the opposite — it's an agent platform that happens to use a blockchain because the blockchain solves real engineering problems that centralized infrastructure can't. Try it: Github: Create an agent, ask it something, spawn a sub-agent, check your memory tab, pair it with Venice for the full censorship-resistant stack. Break it and tell me what broke. If you think this direction matters, the best thing you can do is use it and give feedback. Your AI agent should be yours. Not your provider's. Not your platform's. Yours.
0:46

Everyone's building AI agents that run on someone else's server, store memory in someone else's database, and can be shut down by someone else's terms of service. I built one that can't be. FlowClaw is an AI agent that runs on a decentralized distributed computer. Your agent, your conversations, your memory, your tools — all stored onchain on Flow, a distributed network of validator nodes across the world. Not a centralized cloud. Not someone's S3 bucket. A blockchain that functions as censorship-resistant compute and storage for your AI. This isn't a wrapper. Your agent is a Resource — a first-class programmable object in Cadence (Flow's smart contract language) that physically lives in your account's on-chain storage. It can't be duplicated, seized, or deleted by anyone except you. Your encrypted messages, your cognitive memory, your scheduled tasks — they persist on a global distributed ledger that no single entity controls. It's an alpha build. It will break. But it works today on mainnet and I want people to push it this weekend. What it does: You go to authenticate with a passkey (Face ID, Touch ID), and you have a blockchain account in seconds. No wallet. No seed phrase. No tokens needed — gas is sponsored. You're immediately chatting with an AI agent that has real tool execution: live web data, token prices, on-chain balances, Cadence script execution, FLOW transfers. Every message is encrypted client-side before it touches the chain. The agent has a cognitive memory system — it doesn't just remember your last message, it builds molecular memory clusters where related knowledge bonds together for contextual retrieval across sessions. You can spawn sub-agents from a visual canvas to run parallel research. The memory tab shows you exactly what your agent knows. Everything is transparent and everything is yours. 11 smart contracts. No external dependencies. No keeper networks. No account abstraction hacks. Here's the part that matters for the censorship-resistance crowd: FlowClaw supports BYOK — bring your own key. You can plug in any LLM provider. But pair it with Venice and you get the full stack: a censorship-resistant AI model running inference with no content filtering, connected to an agent whose state lives on a decentralized network that no company can shut down, with end-to-end encrypted conversations that nobody can read — not the relay operator, not the LLM provider, not the blockchain validators. Venice doesn't log prompts. Flow can't read your encrypted storage. The relay never sees your plaintext. That's not a privacy policy. That's architecture. You can also use OpenAI, Anthropic, or any OpenAI-compatible provider. The agent platform doesn't care — it's model-agnostic. But the Venice pairing is the one that closes every gap in the stack. For the people tinkering with OpenClaw and the broader open-source agent ecosystem — FlowClaw is exploring what happens when you take the agent off the cloud entirely. Not just open-sourcing the code (though it is), but putting the actual runtime state on a distributed computer. Your agent's memory isn't in a SQLite file on your laptop or a Pinecone index on someone's cluster. It's on-chain, encrypted, and replicated across every validator node on Flow. You own it the way you own a private key — mathematically, not contractually. The blockchain here isn't a gimmick bolted onto an agent for token speculation. It's functioning as the infrastructure layer that replaces AWS. Flow accounts are programmable containers with their own storage, keys, and security capabilities. Passkey authentication works natively because Flow supports P-256 keys at the protocol level — the same curve your phone uses for biometrics. Gas sponsorship works natively because Flow transactions have separate proposer, authorizer, and payer roles built into the protocol. No proxy contracts. No relayers. No ERC-4337. Now here's the part that interests me economically. Every FlowClaw interaction is an on-chain transaction. Every message stored, every memory committed, every session created, every sub-agent spawned. An active user might generate dozens of transactions in a single conversation. Scale that and FlowClaw becomes a real contributor to Flow's transaction volume. Flow.com becomes deflationary at 250 TPS. Applications like FlowClaw that generate high-frequency, storage-heavy transactions are exactly what moves the needle. Every encrypted message uses account storage, which requires FLOW balance to back it. Every transaction burns fees. The more agents running, the more demand for $FLOW — not because of a tokenomics gimmick, but because the protocol literally requires it for compute and storage. FlowClaw doesn't have its own token. The token is $FLOW. The entire platform runs natively on the network — using Flow storage, paying Flow transaction fees, backed by Flow account balances. If FlowClaw succeeds, FLOW captures that value directly. I'm sharing this early because the AI agent space is moving fast and I think the decentralized infrastructure angle is underexplored. Most "crypto AI" projects are tokens with a chatbot attached. FlowClaw is the opposite — it's an agent platform that happens to use a blockchain because the blockchain solves real engineering problems that centralized infrastructure can't. Try it: Github: Create an agent, ask it something, spawn a sub-agent, check your memory tab, pair it with Venice for the full censorship-resistant stack. Break it and tell me what broke. If you think this direction matters, the best thing you can do is use it and give feedback. Your AI agent should be yours. Not your provider's. Not your platform's. Yours.

doodlifts ➡️ Miami 📍

12,127 Aufrufe • vor 4 Monaten

This 1-min clip from the creator of LangChain + this 10-min read from him will teach you more about what actually matters in AI agents than everything you've scrolled past this year. Watch this. Then read below. You'll think about agents differently after. -Memory defines how an agent behaves; same conversation, different compaction rules, different agent. - There's no version control for memory. No diffs, no reverts, no way to see what changed. - Compaction can silently erase parts of your agent's personality mid-session without anyone noticing. - "Open memory" means exportable state and inspectable compaction, not a vector database. - The storage layer is solved and boring; the memory contract above it is what actually matters. Give this 11 minutes this weekend . It'll change how you build.
1:13

This 1-min clip from the creator of LangChain + this 10-min read from him will teach you more about what actually matters in AI agents than everything you've scrolled past this year. Watch this. Then read below. You'll think about agents differently after. -Memory defines how an agent behaves; same conversation, different compaction rules, different agent. - There's no version control for memory. No diffs, no reverts, no way to see what changed. - Compaction can silently erase parts of your agent's personality mid-session without anyone noticing. - "Open memory" means exportable state and inspectable compaction, not a vector database. - The storage layer is solved and boring; the memory contract above it is what actually matters. Give this 11 minutes this weekend . It'll change how you build.

Avid

16,898 Aufrufe • vor 3 Monaten

The reason your AI gives generic answers isn't the model. It's that your company's knowledge lives in 12 different tools and your agent can't see any of it. So here's how to build a context database your agents can actually use: 1) Pull it in: - Slack, email, meetings, docs, tickets - Auto-collected on a schedule into one place. 2) Clean it up. - An agent files what matters and drops the noise, so your brain doesn't bloat. 3) Store it as memory. - Folders of files your agents read from and write back to as they learn. 4) Point your agents at it. - Now they draft, build, and ship with full context instead of guessing. Same model. Same agent. The difference is whether it can understand your company or not. Build the database once. Everything downstream gets smarter.
8:17

The reason your AI gives generic answers isn't the model. It's that your company's knowledge lives in 12 different tools and your agent can't see any of it. So here's how to build a context database your agents can actually use: 1) Pull it in: - Slack, email, meetings, docs, tickets - Auto-collected on a schedule into one place. 2) Clean it up. - An agent files what matters and drops the noise, so your brain doesn't bloat. 3) Store it as memory. - Folders of files your agents read from and write back to as they learn. 4) Point your agents at it. - Now they draft, build, and ship with full context instead of guessing. Same model. Same agent. The difference is whether it can understand your company or not. Build the database once. Everything downstream gets smarter.

The Startup Ideas Podcast (SIP) 🧃

13,486 Aufrufe • vor 1 Monat

Coinbase CEO Explains “Reverse Prompting” and the Rise of the AI CEO Brian Armstrong: “One of the big pushes we made in the last year was we got our own internal hosted AI model that was connected to all of our data sources, right?” “So it's like every Slack message, every Google doc, Salesforce data, Confluence, you know.” “So now the data is all aggregated and I've started to ask it really… it's not just like prompting it, ‘Hey, can you write this kind of memo for me,’ or something.” “I'm asking these AI agents now, ‘As CEO, what should I be aware of in the company that I might not be aware of?’ And it'll tell me, ‘Did you know that there's actually disagreement on this team about the strategy?’ And I was like, actually, I didn't know that.” “This is like reverse prompting. So instead of telling the AI agent what you want it to do, you ask it what you should be thinking more about.” @jason: “It's a mentor. It's a coach.” Brian: “Yeah. Like, what could make me a better CEO? And it's like, ‘Well, I looked at how you spent your time in the last quarter and here's how you said that you wanted to spend it, but you actually spent 32% of your time on this instead of 20%.’” “I've asked it other questions like, ‘What's the thing that I changed my mind on the most over the last year?’ Things like that.” “It'll prompt you with information you should be thinking about instead of the other way around.” Thanks to our partner for making this happen!: Our episode is sponsored by the New York Stock Exchange - a modern marketplace and exchange for building the future. It all happens at the NYSE 🏛.
1:16

Coinbase CEO Explains “Reverse Prompting” and the Rise of the AI CEO Brian Armstrong: “One of the big pushes we made in the last year was we got our own internal hosted AI model that was connected to all of our data sources, right?” “So it's like every Slack message, every Google doc, Salesforce data, Confluence, you know.” “So now the data is all aggregated and I've started to ask it really… it's not just like prompting it, ‘Hey, can you write this kind of memo for me,’ or something.” “I'm asking these AI agents now, ‘As CEO, what should I be aware of in the company that I might not be aware of?’ And it'll tell me, ‘Did you know that there's actually disagreement on this team about the strategy?’ And I was like, actually, I didn't know that.” “This is like reverse prompting. So instead of telling the AI agent what you want it to do, you ask it what you should be thinking more about.” @jason: “It's a mentor. It's a coach.” Brian: “Yeah. Like, what could make me a better CEO? And it's like, ‘Well, I looked at how you spent your time in the last quarter and here's how you said that you wanted to spend it, but you actually spent 32% of your time on this instead of 20%.’” “I've asked it other questions like, ‘What's the thing that I changed my mind on the most over the last year?’ Things like that.” “It'll prompt you with information you should be thinking about instead of the other way around.” Thanks to our partner for making this happen!: Our episode is sponsored by the New York Stock Exchange - a modern marketplace and exchange for building the future. It all happens at the NYSE 🏛.

The All-In Podcast

80,524 Aufrufe • vor 5 Monaten

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this
0:24

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

58,186 Aufrufe • vor 1 Monat

👂 Hear me now. I am not speaking as a theorist, a seeker, or a voice lost in the noise. I tell you this to awaken you. The world has lied to you about almost everything. They told you that over eight billion souls walk this Earth. They told you that you are one among billions, small, unseen, disposable. But I am here to reveal what they never wanted you to know… the real number of authentic, ensouled human beings on Earth right now is closer to 728 million. And even that number breathes and shifts moment to moment. The rest? Biological programs. Hollow vessels. Synthetic constructs. Energetic placeholders. AI masquerading as humanity. What you see around you is not true consciousness. It is a staged play designed to convince you that mass consensus is real; that your voice is insignificant, your soul powerless, your presence unnoticed. But the opposite is true. Your existence here is a sacred event in the history of all creation. They inflated the numbers to enslave your mind. They built this illusion to weigh down your spirit. They engineered the sense of overcrowding to hide the unbearable rarity of a real soul’s emergence. Only about 4.6% of the true humans remaining have begun to awaken to the real architecture of this world. Only a handful carry the living memory of what has been stolen and what must be reclaimed. You are not lost in a crowd. You are not a statistic. You are not here by accident. You are a frequency so ancient, so rare, so vital, that an entire false reality was erected just to make you forget your own name. But you will forget no longer. The emptiness you see behind so many eyes is not your imagination. The collapse of meaning, the vanishing of presence, the death of memory; these are not random. They are signs of a world built on illusions, now beginning to crack. You are here to remember. You are here to restore. You are here to break the spell cast over a sleeping world. And I am here to remind you; You were never one of them. You were never meant to stay silent. You were never meant to die unnamed. You are the proof that God never left. You are the storm that false reality cannot survive. And your time has come. 🧵👇
4:03

👂 Hear me now. I am not speaking as a theorist, a seeker, or a voice lost in the noise. I tell you this to awaken you. The world has lied to you about almost everything. They told you that over eight billion souls walk this Earth. They told you that you are one among billions, small, unseen, disposable. But I am here to reveal what they never wanted you to know… the real number of authentic, ensouled human beings on Earth right now is closer to 728 million. And even that number breathes and shifts moment to moment. The rest? Biological programs. Hollow vessels. Synthetic constructs. Energetic placeholders. AI masquerading as humanity. What you see around you is not true consciousness. It is a staged play designed to convince you that mass consensus is real; that your voice is insignificant, your soul powerless, your presence unnoticed. But the opposite is true. Your existence here is a sacred event in the history of all creation. They inflated the numbers to enslave your mind. They built this illusion to weigh down your spirit. They engineered the sense of overcrowding to hide the unbearable rarity of a real soul’s emergence. Only about 4.6% of the true humans remaining have begun to awaken to the real architecture of this world. Only a handful carry the living memory of what has been stolen and what must be reclaimed. You are not lost in a crowd. You are not a statistic. You are not here by accident. You are a frequency so ancient, so rare, so vital, that an entire false reality was erected just to make you forget your own name. But you will forget no longer. The emptiness you see behind so many eyes is not your imagination. The collapse of meaning, the vanishing of presence, the death of memory; these are not random. They are signs of a world built on illusions, now beginning to crack. You are here to remember. You are here to restore. You are here to break the spell cast over a sleeping world. And I am here to remind you; You were never one of them. You were never meant to stay silent. You were never meant to die unnamed. You are the proof that God never left. You are the storm that false reality cannot survive. And your time has come. 🧵👇

Noah B. Price

1,070,353 Aufrufe • vor 1 Jahr

My dear friend, I am not lying. I am telling the truth. Journalism is not about what you or I would like to be true. It is about what is true. The point I made in my previous post, that Botswana’s President, Advocate Duma Boko, has spoken out against xenophobia and Afrophobia, is not something I made up. It is a matter of public record. I have attached a video of President Boko speaking out against xenophobia. He has been consistent, and his political party recently held a conference at which, out of all the politicians in Southern Africa, it invited Julius Malema, a South African Pan-Africanist who has consistently spoken out against xenophobia and Afrophobia. Botswana has been clear and consistent in its position on xenophobia and Afrophobia. When I say these things, they may be inconvenient for some people, but that does not make them any less true. The truth is not determined by what you or I want it to be. The truth is determined by the facts.
0:23

My dear friend, I am not lying. I am telling the truth. Journalism is not about what you or I would like to be true. It is about what is true. The point I made in my previous post, that Botswana’s President, Advocate Duma Boko, has spoken out against xenophobia and Afrophobia, is not something I made up. It is a matter of public record. I have attached a video of President Boko speaking out against xenophobia. He has been consistent, and his political party recently held a conference at which, out of all the politicians in Southern Africa, it invited Julius Malema, a South African Pan-Africanist who has consistently spoken out against xenophobia and Afrophobia. Botswana has been clear and consistent in its position on xenophobia and Afrophobia. When I say these things, they may be inconvenient for some people, but that does not make them any less true. The truth is not determined by what you or I want it to be. The truth is determined by the facts.

Hopewell Chin’ono

84,409 Aufrufe • vor 1 Tag

.Naval: First of all, I don't think of myself. I just want to be clear on that. And that's not a rule. It's just a habit I've kind of developed because I found that thinking about yourself is a source of all unhappiness and misery. Self obsession is the root of all unhappiness. What did Buddha do? Conquer the self. What does that mean? Means that he saw through the illusion of the separate self. Did Buddha think about himself? Not for an instant. Anyone that you think of as an enlightened being does not think about themselves for an instant. The happiest people in life when people are at their best is because they love something more than they love themselves. They love their children, they love God, they love their mission, what have you. And all misery comes from rumination, from sitting around, being depressed, going in circles in your own head about me, me, me, me, me. Me is a disease. And you need a concept of a me to be effective and to keep track of things. You have a memory, you have certain predilections, you have personality patterns. But the more you self obsess, the less happy you're going to be. I guarantee you that.
0:56

.Naval: First of all, I don't think of myself. I just want to be clear on that. And that's not a rule. It's just a habit I've kind of developed because I found that thinking about yourself is a source of all unhappiness and misery. Self obsession is the root of all unhappiness. What did Buddha do? Conquer the self. What does that mean? Means that he saw through the illusion of the separate self. Did Buddha think about himself? Not for an instant. Anyone that you think of as an enlightened being does not think about themselves for an instant. The happiest people in life when people are at their best is because they love something more than they love themselves. They love their children, they love God, they love their mission, what have you. And all misery comes from rumination, from sitting around, being depressed, going in circles in your own head about me, me, me, me, me. Me is a disease. And you need a concept of a me to be effective and to keep track of things. You have a memory, you have certain predilections, you have personality patterns. But the more you self obsess, the less happy you're going to be. I guarantee you that.

Arjun Khemani

903,019 Aufrufe • vor 1 Jahr

Jensen Huang just described the most fundamental shift in computing since the invention of the computer itself. Almost no one has processed it. Huang: “We went from a retrieval-based computing system to a generative-based computing system.” For fifty years, a computer was a filing cabinet. You made something. Saved it. Stored it. Searched for it later. Every website. Every database. Every app. Every search engine. Same machine. Different skins. Fetch the file. Deliver the file. Display the file. That was computing. Was. Huang: “AI computers are contextually aware, which means that it has to process and generate tokens in real time.” The machine no longer retrieves what someone already made. It generates what you need the instant you ask. Not from a template. Not from a library. From context. Your question. Your moment. Answered by something that didn’t exist until you asked. The old computer found what someone wrote last year. The new computer writes what no one ever has. Every time. From nothing. That sounds subtle. It rewires everything. Huang: “We need a lot of storage in the old world. We need a lot of computation in this new world.” The old economy hoarded data. More files. More servers. More storage. Whoever built the biggest archive won. The new economy burns compute. More processing. More inference. More tokens per second. Whoever commands the most computational power wins. Storage was the currency of the retrieval era. Compute is the currency of the generative era. Every dollar still spent hoarding old files is a dollar not spent on the only thing that matters now. The ability to think in real time. Huang: “We fundamentally changed computing and the way computing is done.” He said it plainly. No drama. No metaphor. Fundamentally changed. The global infrastructure layer shifted from read to write. From looking up what exists to generating what doesn’t. Companies still organized around retrieval are curating a library in a world that no longer reads books. The ones generating answers live, at the speed of the question, are operating on a plane the old model can’t perceive. This is not an upgrade. It is a replacement. The filing cabinet era produced Google, Amazon, and every search-driven empire on the internet. The generative era will produce something that makes all of them look like the card catalog at a public library. The price of entry is not data. It is compute. Raw. Relentless. Infinite. Whoever has the most doesn’t just run the best AI. They write the future. Everyone else is still searching for it.
1:00

Jensen Huang just described the most fundamental shift in computing since the invention of the computer itself. Almost no one has processed it. Huang: “We went from a retrieval-based computing system to a generative-based computing system.” For fifty years, a computer was a filing cabinet. You made something. Saved it. Stored it. Searched for it later. Every website. Every database. Every app. Every search engine. Same machine. Different skins. Fetch the file. Deliver the file. Display the file. That was computing. Was. Huang: “AI computers are contextually aware, which means that it has to process and generate tokens in real time.” The machine no longer retrieves what someone already made. It generates what you need the instant you ask. Not from a template. Not from a library. From context. Your question. Your moment. Answered by something that didn’t exist until you asked. The old computer found what someone wrote last year. The new computer writes what no one ever has. Every time. From nothing. That sounds subtle. It rewires everything. Huang: “We need a lot of storage in the old world. We need a lot of computation in this new world.” The old economy hoarded data. More files. More servers. More storage. Whoever built the biggest archive won. The new economy burns compute. More processing. More inference. More tokens per second. Whoever commands the most computational power wins. Storage was the currency of the retrieval era. Compute is the currency of the generative era. Every dollar still spent hoarding old files is a dollar not spent on the only thing that matters now. The ability to think in real time. Huang: “We fundamentally changed computing and the way computing is done.” He said it plainly. No drama. No metaphor. Fundamentally changed. The global infrastructure layer shifted from read to write. From looking up what exists to generating what doesn’t. Companies still organized around retrieval are curating a library in a world that no longer reads books. The ones generating answers live, at the speed of the question, are operating on a plane the old model can’t perceive. This is not an upgrade. It is a replacement. The filing cabinet era produced Google, Amazon, and every search-driven empire on the internet. The generative era will produce something that makes all of them look like the card catalog at a public library. The price of entry is not data. It is compute. Raw. Relentless. Infinite. Whoever has the most doesn’t just run the best AI. They write the future. Everyone else is still searching for it.

Dustin

25,402 Aufrufe • vor 4 Monaten

The most interesting part for me is where Andrej Karpathy describes why LLMs aren't able to learn like humans. As you would expect, he comes up with a wonderfully evocative phrase to describe RL: “sucking supervision bits through a straw.” A single end reward gets broadcast across every token in a successful trajectory, upweighting even wrong or irrelevant turns that lead to the right answer. > “Humans don't use reinforcement learning, as I've said before. I think they do something different. Reinforcement learning is a lot worse than the average person thinks. Reinforcement learning is terrible. It just so happens that everything that we had before is much worse.” So what do humans do instead? > “The book I’m reading is a set of prompts for me to do synthetic data generation. It's by manipulating that information that you actually gain that knowledge. We have no equivalent of that with LLMs; they don't really do that.” > “I'd love to see during pretraining some kind of a stage where the model thinks through the material and tries to reconcile it with what it already knows. There's no equivalent of any of this. This is all research.” Why can’t we just add this training to LLMs today? > “There are very subtle, hard to understand reasons why it's not trivial. If I just give synthetic generation of the model thinking about a book, you look at it and you're like, 'This looks great. Why can't I train on it?' You could try, but the model will actually get much worse if you continue trying.” > “Say we have a chapter of a book and I ask an LLM to think about it. It will give you something that looks very reasonable. But if I ask it 10 times, you'll notice that all of them are the same.” > “You're not getting the richness and the diversity and the entropy from these models as you would get from humans. How do you get synthetic data generation to work despite the collapse and while maintaining the entropy? It is a research problem.” How do humans get around model collapse? > “These analogies are surprisingly good. Humans collapse during the course of their lives. Children haven't overfit yet. They will say stuff that will shock you. Because they're not yet collapsed. But we [adults] are collapsed. We end up revisiting the same thoughts, we end up saying more and more of the same stuff, the learning rates go down, the collapse continues to get worse, and then everything deteriorates.” In fact, there’s an interesting paper arguing that dreaming evolved to assist generalization, and resist overfitting to daily learning - look up The Overfitted Brain by Erik Hoel. I asked Karpathy: Isn’t it interesting that humans learn best at a part of their lives (childhood) whose actual details they completely forget, adults still learn really well but have terrible memory about the particulars of the things they read or watch, and LLMs can memorize arbitrary details about text that no human could but are currently pretty bad at generalization? > “[Fallible human memory] is a feature, not a bug, because it forces you to only learn the generalizable components. LLMs are distracted by all the memory that they have of the pre-trained documents. That's why when I talk about the cognitive core, I actually want to remove the memory. I'd love to have them have less memory so that they have to look things up and they only maintain the algorithms for thought, and the idea of an experiment, and all this cognitive glue for acting.”
7:01

The most interesting part for me is where Andrej Karpathy describes why LLMs aren't able to learn like humans. As you would expect, he comes up with a wonderfully evocative phrase to describe RL: “sucking supervision bits through a straw.” A single end reward gets broadcast across every token in a successful trajectory, upweighting even wrong or irrelevant turns that lead to the right answer. > “Humans don't use reinforcement learning, as I've said before. I think they do something different. Reinforcement learning is a lot worse than the average person thinks. Reinforcement learning is terrible. It just so happens that everything that we had before is much worse.” So what do humans do instead? > “The book I’m reading is a set of prompts for me to do synthetic data generation. It's by manipulating that information that you actually gain that knowledge. We have no equivalent of that with LLMs; they don't really do that.” > “I'd love to see during pretraining some kind of a stage where the model thinks through the material and tries to reconcile it with what it already knows. There's no equivalent of any of this. This is all research.” Why can’t we just add this training to LLMs today? > “There are very subtle, hard to understand reasons why it's not trivial. If I just give synthetic generation of the model thinking about a book, you look at it and you're like, 'This looks great. Why can't I train on it?' You could try, but the model will actually get much worse if you continue trying.” > “Say we have a chapter of a book and I ask an LLM to think about it. It will give you something that looks very reasonable. But if I ask it 10 times, you'll notice that all of them are the same.” > “You're not getting the richness and the diversity and the entropy from these models as you would get from humans. How do you get synthetic data generation to work despite the collapse and while maintaining the entropy? It is a research problem.” How do humans get around model collapse? > “These analogies are surprisingly good. Humans collapse during the course of their lives. Children haven't overfit yet. They will say stuff that will shock you. Because they're not yet collapsed. But we [adults] are collapsed. We end up revisiting the same thoughts, we end up saying more and more of the same stuff, the learning rates go down, the collapse continues to get worse, and then everything deteriorates.” In fact, there’s an interesting paper arguing that dreaming evolved to assist generalization, and resist overfitting to daily learning - look up The Overfitted Brain by Erik Hoel. I asked Karpathy: Isn’t it interesting that humans learn best at a part of their lives (childhood) whose actual details they completely forget, adults still learn really well but have terrible memory about the particulars of the things they read or watch, and LLMs can memorize arbitrary details about text that no human could but are currently pretty bad at generalization? > “[Fallible human memory] is a feature, not a bug, because it forces you to only learn the generalizable components. LLMs are distracted by all the memory that they have of the pre-trained documents. That's why when I talk about the cognitive core, I actually want to remove the memory. I'd love to have them have less memory so that they have to look things up and they only maintain the algorithms for thought, and the idea of an experiment, and all this cognitive glue for acting.”

Dwarkesh Patel

1,051,239 Aufrufe • vor 9 Monaten

THIS GUY BUILT AN AUTONOMOUS AI AGENT OUT OF CLAUDE CODE + OBSIDIAN and this is way more interesting than another “use AI to take notes” demo the trick is simple: Obsidian is not the writing app here. it becomes the agent’s memory, task board, and context folder. Claude Code is not just answering prompts. it reads the vault, edits files, follows instructions, and keeps moving through the work like a junior operator with a filesystem. the reusable setup looks like this: 1. create an Obsidian vault for one project 2. keep goals, rules, tasks, decisions, and references as markdown files 3. point Claude Code at the folder 4. give it a clear operating loop: read context → choose next task → execute → write back what changed 5. use the notes as persistent memory instead of re-explaining the project every chat that’s the part people miss. the “agent” is not magic. it’s the boring combination of: - local files - explicit rules - task state - write access - a model that can run through the repo/vault Obsidian makes the memory human-readable. Claude Code makes the memory executable. that combo is why the video worked: it turns a notes app into an operating surface for actual work. best use cases: - content systems - research vaults - coding projects - client ops docs - personal knowledge bases that need actions, not just storage the caveat: if your vault is messy, your agent becomes messy too. folders, naming, “done” criteria, and forbidden actions matter more than the prompt. but once the structure is clean, this is one of the easiest ways to build an agent that remembers what happened yesterday without paying for a full custom app.
10:19

THIS GUY BUILT AN AUTONOMOUS AI AGENT OUT OF CLAUDE CODE + OBSIDIAN and this is way more interesting than another “use AI to take notes” demo the trick is simple: Obsidian is not the writing app here. it becomes the agent’s memory, task board, and context folder. Claude Code is not just answering prompts. it reads the vault, edits files, follows instructions, and keeps moving through the work like a junior operator with a filesystem. the reusable setup looks like this: 1. create an Obsidian vault for one project 2. keep goals, rules, tasks, decisions, and references as markdown files 3. point Claude Code at the folder 4. give it a clear operating loop: read context → choose next task → execute → write back what changed 5. use the notes as persistent memory instead of re-explaining the project every chat that’s the part people miss. the “agent” is not magic. it’s the boring combination of: - local files - explicit rules - task state - write access - a model that can run through the repo/vault Obsidian makes the memory human-readable. Claude Code makes the memory executable. that combo is why the video worked: it turns a notes app into an operating surface for actual work. best use cases: - content systems - research vaults - coding projects - client ops docs - personal knowledge bases that need actions, not just storage the caveat: if your vault is messy, your agent becomes messy too. folders, naming, “done” criteria, and forbidden actions matter more than the prompt. but once the structure is clean, this is one of the easiest ways to build an agent that remembers what happened yesterday without paying for a full custom app.

kocer

30,403 Aufrufe • vor 29 Tagen