Podcasts about Assembler

“Vanity of vanities, says the Preacher. All is vanity.” Ecclesiastes 1:2 As a philosopher I have loved the great tradition of human wisdom. For many years I drank from the tributaries. Aristotle taught that the good life is something one lives, not something one acquires. Socrates taught that wisdom begins in humility. These insights nourished me long before I realized they were preparing me to recognize the far greater wisdom God has given in Scripture. The Greek thinkers stood downstream from a fountain they dimly sensed but could not reach. The book of Ecclesiastes speaks from that very source. Qoheleth, קהלת, the Assembler, often called the Preacher, gathers what God has revealed about life in this world. He describes the human condition with a single Hebrew word: hevel, breath, vapor. Not meaninglessness, but ungraspability - and paradox. Life slips through the fingers of those who try to seize it, and understanding reaches its limit in paradox. What cannot be possessed must be received. What we cannot control must become ours by gift. And this is why Ecclesiastes so often speaks the language of generosity. Work is a gift. Food and drink are gifts. Joy is gift. Companionship is gift. Time itself is gift. The Preacher calls us to leave behind the restless striving that characterizes life in the tributaries, and to return instead to the fountain where every good and perfect gift flows from the hand of the Giver. He also tells us something our age urgently needs to hear. There is nothing new under the sun. Our modern confidence in our own progress (central to the evolutionary mythos) is little more than hubris. We imagine ourselves advanced beyond our “primitive” forebears, yet our world repeats the same patterns of confusion and pride. Postmodern deconstruction, gender confusion, DEI initiatives, and cultural relativism are not new. They are ancient errors retold in new vocabulary. Ecclesiastes understood the human heart long before our age attempted to deconstruct it. Near the end of the book the imagery sharpens. “The words of the wise are like goads,” given by one Shepherd to guide us back toward the fountain of wisdom. When the risen Jesus confronted Saul and said, “It is hard for you to kick against the goads,” Paul, deeply trained in Greek language and philosophy, recognized the proverb immediately. The Shepherd's mercy often comes to us as a sharp turn, redirecting us from the dry channels of self-reliance back to the living waters of God Himself. The book ends where all honest searching must end. Fear God. Keep His commandments. Receive His gifts with gratitude. This is the whole duty of man, the culmination not only of the Bible's wisdom literature, but of every sincere philosophical quest. I wandered long among the tributaries, but Scripture led me home to the Fount of every blessing and tuned my heart to sing His grace. Here is a helpful overview of Ecclesiastes. May your listening be as blessed as ours was in the reading. https://www.youtube.com/watch?v=lrsQ1tc-2w

“Vanity of vanities, says the Preacher. All is vanity.” Ecclesiastes 1:2 As a philosopher I have loved the great tradition of human wisdom. For many years I drank from the tributaries. Aristotle taught that the good life is something one lives, not something one acquires. Socrates taught that wisdom begins in humility. These insights nourished me long before I realized they were preparing me to recognize the far greater wisdom God has given in Scripture. The Greek thinkers stood downstream from a fountain they dimly sensed but could not reach. The book of Ecclesiastes speaks from that very source. Qoheleth, קהלת, the Assembler, often called the Preacher, gathers what God has revealed about life in this world. He describes the human condition with a single Hebrew word: hevel, breath, vapor. Not meaninglessness, but ungraspability - and paradox. Life slips through the fingers of those who try to seize it, and understanding reaches its limit in paradox. What cannot be possessed must be received. What we cannot control must become ours by gift. And this is why Ecclesiastes so often speaks the language of generosity. Work is a gift. Food and drink are gifts. Joy is gift. Companionship is gift. Time itself is gift. The Preacher calls us to leave behind the restless striving that characterizes life in the tributaries, and to return instead to the fountain where every good and perfect gift flows from the hand of the Giver. He also tells us something our age urgently needs to hear. There is nothing new under the sun. Our modern confidence in our own progress (central to the evolutionary mythos) is little more than hubris. We imagine ourselves advanced beyond our “primitive” forebears, yet our world repeats the same patterns of confusion and pride. Postmodern deconstruction, gender confusion, DEI initiatives, and cultural relativism are not new. They are ancient errors retold in new vocabulary. Ecclesiastes understood the human heart long before our age attempted to deconstruct it. Near the end of the book the imagery sharpens. “The words of the wise are like goads,” given by one Shepherd to guide us back toward the fountain of wisdom. When the risen Jesus confronted Saul and said, “It is hard for you to kick against the goads,” Paul, deeply trained in Greek language and philosophy, recognized the proverb immediately. The Shepherd's mercy often comes to us as a sharp turn, redirecting us from the dry channels of self-reliance back to the living waters of God Himself. The book ends where all honest searching must end. Fear God. Keep His commandments. Receive His gifts with gratitude. This is the whole duty of man, the culmination not only of the Bible's wisdom literature, but of every sincere philosophical quest. I wandered long among the tributaries, but Scripture led me home to the Fount of every blessing and tuned my heart to sing His grace. Here is a helpful overview of Ecclesiastes. May your listening be as blessed as ours was in the reading. https://www.youtube.com/watch?v=lrsQ1tc-2w

This episode features Karl-Erik Stenfors, a retired IBM systems engineer and since 2015 been teaching Linux, virtualization and z/Assembler at three private universities in France, as well as teaching System Z technologies for two professional education companies. Kark-Erik has been recognized as an IBM Z and Linux One Champion for 2025!!Teaching has been a natural thread throughout his entire career, from installing and introducing new products, to coaching colleagues and customers, to authoring IBM Redbooks (comprehensive guides). In fact, he wrote every Redbook covering new processors during his final ten years at IBM.He also co-authored Introduction to Enterprise Systems written in collaboration with Reg Harbeck, David Boyes and Cameron Seay.Learn more about the book here.His thoughts on the mainframe culture:This is a platform that runs the world. So, that's a very particular culture around how do we run this system that cannot fail, how do you treat things when they go wrong? How to treat things to avoid that the same error doesn't come back. I think culture is a big word, but that's what I like about it. It's still developing every single day, there are new things coming on new languages, new processors, new products. So, it's a world that's very much alive and must keep learning almost every day in this environment.Karl-Erik's teaching Philosophy:I have this philosophy that you should teach only things you know, only things you know how to do, and understand. So that's what I've been doing.Advice to educators:His advice is simple but powerful: don't rush. What matters most is that students truly understand the material. Even if a student asks the same question 20 or 30 times, he says, it's far more important that they ultimately grasp the concepts than it is to push forward too quickly.Listen to the rapid-fire questions to learn the fun things about him like Danish pancakes, herrings and going back to school to study political science!Resources:Visit the IBM Z Educator Hub User Group on the IBM Z and LinuxONE Community to find the latest communications, news and events, as well as collaborate and network. Check out technical lecture's, blogs, events, videos, discussions, and more. Join here .Subscribe to “The z/Education!” Podcast to listen to talks from IBM Z Educators from around the world on their success stories, journeys and their best practices.

“Vanity of vanities, says the Preacher. All is vanity.” Ecclesiastes 1:2 As a philosopher I have loved the great tradition of human wisdom. For many years I drank from the tributaries. Aristotle taught that the good life is something one lives, not something one acquires. Socrates taught that wisdom begins in humility. These insights nourished me long before I realized they were preparing me to recognize the far greater wisdom God has given in Scripture. The Greek thinkers stood downstream from a fountain they dimly sensed but could not reach. The book of Ecclesiastes speaks from that very source. Qoheleth, קהלת, the Assembler, often called the Preacher, gathers what God has revealed about life in this world. He describes the human condition with a single Hebrew word: hevel, breath, vapor. Not meaninglessness, but ungraspability - and paradox. Life slips through the fingers of those who try to seize it, and understanding reaches its limit in paradox. What cannot be possessed must be received. What we cannot control must become ours by gift. And this is why Ecclesiastes so often speaks the language of generosity. Work is a gift. Food and drink are gifts. Joy is gift. Companionship is gift. Time itself is gift. The Preacher calls us to leave behind the restless striving that characterizes life in the tributaries, and to return instead to the fountain where every good and perfect gift flows from the hand of the Giver. He also tells us something our age urgently needs to hear. There is nothing new under the sun. Our modern confidence in our own progress (central to the evolutionary mythos) is little more than hubris. We imagine ourselves advanced beyond our “primitive” forebears, yet our world repeats the same patterns of confusion and pride. Postmodern deconstruction, gender confusion, DEI initiatives, and cultural relativism are not new. They are ancient errors retold in new vocabulary. Ecclesiastes understood the human heart long before our age attempted to deconstruct it. Near the end of the book the imagery sharpens. “The words of the wise are like goads,” given by one Shepherd to guide us back toward the fountain of wisdom. When the risen Jesus confronted Saul and said, “It is hard for you to kick against the goads,” Paul, deeply trained in Greek language and philosophy, recognized the proverb immediately. The Shepherd's mercy often comes to us as a sharp turn, redirecting us from the dry channels of self-reliance back to the living waters of God Himself. The book ends where all honest searching must end. Fear God. Keep His commandments. Receive His gifts with gratitude. This is the whole duty of man, the culmination not only of the Bible's wisdom literature, but of every sincere philosophical quest. I wandered long among the tributaries, but Scripture led me home to the Fount of every blessing and tuned my heart to sing His grace. Here is a helpful overview of Ecclesiastes. May your listening be as blessed as ours was in the reading. https://www.youtube.com/watch?v=lrsQ1tc-2w

“Vanity of vanities, says the Preacher. All is vanity.” Ecclesiastes 1:2 As a philosopher I have loved the great tradition of human wisdom. For many years I drank from the tributaries. Aristotle taught that the good life is something one lives, not something one acquires. Socrates taught that wisdom begins in humility. These insights nourished me long before I realized they were preparing me to recognize the far greater wisdom God has given in Scripture. The Greek thinkers stood downstream from a fountain they dimly sensed but could not reach. The book of Ecclesiastes speaks from that very source. Qoheleth, קהלת, the Assembler, often called the Preacher, gathers what God has revealed about life in this world. He describes the human condition with a single Hebrew word: hevel, breath, vapor. Not meaninglessness, but ungraspability - and paradox. Life slips through the fingers of those who try to seize it, and understanding reaches its limit in paradox. What cannot be possessed must be received. What we cannot control must become ours by gift. And this is why Ecclesiastes so often speaks the language of generosity. Work is a gift. Food and drink are gifts. Joy is gift. Companionship is gift. Time itself is gift. The Preacher calls us to leave behind the restless striving that characterizes life in the tributaries, and to return instead to the fountain where every good and perfect gift flows from the hand of the Giver. He also tells us something our age urgently needs to hear. There is nothing new under the sun. Our modern confidence in our own progress (central to the evolutionary mythos) is little more than hubris. We imagine ourselves advanced beyond our “primitive” forebears, yet our world repeats the same patterns of confusion and pride. Postmodern deconstruction, gender confusion, DEI initiatives, and cultural relativism are not new. They are ancient errors retold in new vocabulary. Ecclesiastes understood the human heart long before our age attempted to deconstruct it. Near the end of the book the imagery sharpens. “The words of the wise are like goads,” given by one Shepherd to guide us back toward the fountain of wisdom. When the risen Jesus confronted Saul and said, “It is hard for you to kick against the goads,” Paul, deeply trained in Greek language and philosophy, recognized the proverb immediately. The Shepherd's mercy often comes to us as a sharp turn, redirecting us from the dry channels of self-reliance back to the living waters of God Himself. The book ends where all honest searching must end. Fear God. Keep His commandments. Receive His gifts with gratitude. This is the whole duty of man, the culmination not only of the Bible's wisdom literature, but of every sincere philosophical quest. I wandered long among the tributaries, but Scripture led me home to the Fount of every blessing and tuned my heart to sing His grace. Here is a helpful overview of Ecclesiastes. May your listening be as blessed as ours was in the reading. https://www.youtube.com/watch?v=lrsQ1tc-2w

“Vanity of vanities, says the Preacher. All is vanity.” Ecclesiastes 1:2 As a philosopher I have loved the great tradition of human wisdom. For many years I drank from the tributaries. Aristotle taught that the good life is something one lives, not something one acquires. Socrates taught that wisdom begins in humility. These insights nourished me long before I realized they were preparing me to recognize the far greater wisdom God has given in Scripture. The Greek thinkers stood downstream from a fountain they dimly sensed but could not reach. The book of Ecclesiastes speaks from that very source. Qoheleth, קהלת, the Assembler, often called the Preacher, gathers what God has revealed about life in this world. He describes the human condition with a single Hebrew word: hevel, breath, vapor. Not meaninglessness, but ungraspability - and paradox. Life slips through the fingers of those who try to seize it, and understanding reaches its limit in paradox. What cannot be possessed must be received. What we cannot control must become ours by gift. And this is why Ecclesiastes so often speaks the language of generosity. Work is a gift. Food and drink are gifts. Joy is gift. Companionship is gift. Time itself is gift. The Preacher calls us to leave behind the restless striving that characterizes life in the tributaries, and to return instead to the fountain where every good and perfect gift flows from the hand of the Giver. He also tells us something our age urgently needs to hear. There is nothing new under the sun. Our modern confidence in our own progress (central to the evolutionary mythos) is little more than hubris. We imagine ourselves advanced beyond our “primitive” forebears, yet our world repeats the same patterns of confusion and pride. Postmodern deconstruction, gender confusion, DEI initiatives, and cultural relativism are not new. They are ancient errors retold in new vocabulary. Ecclesiastes understood the human heart long before our age attempted to deconstruct it. Near the end of the book the imagery sharpens. “The words of the wise are like goads,” given by one Shepherd to guide us back toward the fountain of wisdom. When the risen Jesus confronted Saul and said, “It is hard for you to kick against the goads,” Paul, deeply trained in Greek language and philosophy, recognized the proverb immediately. The Shepherd's mercy often comes to us as a sharp turn, redirecting us from the dry channels of self-reliance back to the living waters of God Himself. The book ends where all honest searching must end. Fear God. Keep His commandments. Receive His gifts with gratitude. This is the whole duty of man, the culmination not only of the Bible's wisdom literature, but of every sincere philosophical quest. I wandered long among the tributaries, but Scripture led me home to the Fount of every blessing and tuned my heart to sing His grace. Here is a helpful overview of Ecclesiastes. May your listening be as blessed as ours was in the reading. https://www.youtube.com/watch?v=lrsQ1tc-2w

“Vanity of vanities, says the Preacher. All is vanity.” Ecclesiastes 1:2 As a philosopher I have loved the great tradition of human wisdom. For many years I drank from the tributaries. Aristotle taught that the good life is something one lives, not something one acquires. Socrates taught that wisdom begins in humility. These insights nourished me long before I realized they were preparing me to recognize the far greater wisdom God has given in Scripture. The Greek thinkers stood downstream from a fountain they dimly sensed but could not reach. The book of Ecclesiastes speaks from that very source. Qoheleth, קהלת, the Assembler, often called the Preacher, gathers what God has revealed about life in this world. He describes the human condition with a single Hebrew word: hevel, breath, vapor. Not meaninglessness, but ungraspability - and paradox. Life slips through the fingers of those who try to seize it, and understanding reaches its limit in paradox. What cannot be possessed must be received. What we cannot control must become ours by gift. And this is why Ecclesiastes so often speaks the language of generosity. Work is a gift. Food and drink are gifts. Joy is gift. Companionship is gift. Time itself is gift. The Preacher calls us to leave behind the restless striving that characterizes life in the tributaries, and to return instead to the fountain where every good and perfect gift flows from the hand of the Giver. He also tells us something our age urgently needs to hear. There is nothing new under the sun. Our modern confidence in our own progress (central to the evolutionary mythos) is little more than hubris. We imagine ourselves advanced beyond our “primitive” forebears, yet our world repeats the same patterns of confusion and pride. Postmodern deconstruction, gender confusion, DEI initiatives, and cultural relativism are not new. They are ancient errors retold in new vocabulary. Ecclesiastes understood the human heart long before our age attempted to deconstruct it. Near the end of the book the imagery sharpens. “The words of the wise are like goads,” given by one Shepherd to guide us back toward the fountain of wisdom. When the risen Jesus confronted Saul and said, “It is hard for you to kick against the goads,” Paul, deeply trained in Greek language and philosophy, recognized the proverb immediately. The Shepherd's mercy often comes to us as a sharp turn, redirecting us from the dry channels of self-reliance back to the living waters of God Himself. The book ends where all honest searching must end. Fear God. Keep His commandments. Receive His gifts with gratitude. This is the whole duty of man, the culmination not only of the Bible's wisdom literature, but of every sincere philosophical quest. I wandered long among the tributaries, but Scripture led me home to the Fount of every blessing and tuned my heart to sing His grace. Here is a helpful overview of Ecclesiastes. May your listening be as blessed as ours was in the reading. https://www.youtube.com/watch?v=lrsQ1tc-2w

“Vanity of vanities, says the Preacher. All is vanity.” Ecclesiastes 1:2 As a philosopher I have loved the great tradition of human wisdom. For many years I drank from the tributaries. Aristotle taught that the good life is something one lives, not something one acquires. Socrates taught that wisdom begins in humility. These insights nourished me long before I realized they were preparing me to recognize the far greater wisdom God has given in Scripture. The Greek thinkers stood downstream from a fountain they dimly sensed but could not reach. The book of Ecclesiastes speaks from that very source. Qoheleth, קהלת, the Assembler, often called the Preacher, gathers what God has revealed about life in this world. He describes the human condition with a single Hebrew word: hevel, breath, vapor. Not meaninglessness, but ungraspability - and paradox. Life slips through the fingers of those who try to seize it, and understanding reaches its limit in paradox. What cannot be possessed must be received. What we cannot control must become ours by gift. And this is why Ecclesiastes so often speaks the language of generosity. Work is a gift. Food and drink are gifts. Joy is gift. Companionship is gift. Time itself is gift. The Preacher calls us to leave behind the restless striving that characterizes life in the tributaries, and to return instead to the fountain where every good and perfect gift flows from the hand of the Giver. He also tells us something our age urgently needs to hear. There is nothing new under the sun. Our modern confidence in our own progress (central to the evolutionary mythos) is little more than hubris. We imagine ourselves advanced beyond our “primitive” forebears, yet our world repeats the same patterns of confusion and pride. Postmodern deconstruction, gender confusion, DEI initiatives, and cultural relativism are not new. They are ancient errors retold in new vocabulary. Ecclesiastes understood the human heart long before our age attempted to deconstruct it. Near the end of the book the imagery sharpens. “The words of the wise are like goads,” given by one Shepherd to guide us back toward the fountain of wisdom. When the risen Jesus confronted Saul and said, “It is hard for you to kick against the goads,” Paul, deeply trained in Greek language and philosophy, recognized the proverb immediately. The Shepherd's mercy often comes to us as a sharp turn, redirecting us from the dry channels of self-reliance back to the living waters of God Himself. The book ends where all honest searching must end. Fear God. Keep His commandments. Receive His gifts with gratitude. This is the whole duty of man, the culmination not only of the Bible's wisdom literature, but of every sincere philosophical quest. I wandered long among the tributaries, but Scripture led me home to the Fount of every blessing and tuned my heart to sing His grace. Here is a helpful overview of Ecclesiastes. May your listening be as blessed as ours was in the reading. https://www.youtube.com/watch?v=lrsQ1tc-2w

“Vanity of vanities, says the Preacher. All is vanity.” Ecclesiastes 1:2 As a philosopher I have loved the great tradition of human wisdom. For many years I drank from the tributaries. Aristotle taught that the good life is something one lives, not something one acquires. Socrates taught that wisdom begins in humility. These insights nourished me long before I realized they were preparing me to recognize the far greater wisdom God has given in Scripture. The Greek thinkers stood downstream from a fountain they dimly sensed but could not reach. The book of Ecclesiastes speaks from that very source. Qoheleth, קהלת, the Assembler, often called the Preacher, gathers what God has revealed about life in this world. He describes the human condition with a single Hebrew word: hevel, breath, vapor. Not meaninglessness, but ungraspability - and paradox. Life slips through the fingers of those who try to seize it, and understanding reaches its limit in paradox. What cannot be possessed must be received. What we cannot control must become ours by gift. And this is why Ecclesiastes so often speaks the language of generosity. Work is a gift. Food and drink are gifts. Joy is gift. Companionship is gift. Time itself is gift. The Preacher calls us to leave behind the restless striving that characterizes life in the tributaries, and to return instead to the fountain where every good and perfect gift flows from the hand of the Giver. He also tells us something our age urgently needs to hear. There is nothing new under the sun. Our modern confidence in our own progress (central to the evolutionary mythos) is little more than hubris. We imagine ourselves advanced beyond our “primitive” forebears, yet our world repeats the same patterns of confusion and pride. Postmodern deconstruction, gender confusion, DEI initiatives, and cultural relativism are not new. They are ancient errors retold in new vocabulary. Ecclesiastes understood the human heart long before our age attempted to deconstruct it. Near the end of the book the imagery sharpens. “The words of the wise are like goads,” given by one Shepherd to guide us back toward the fountain of wisdom. When the risen Jesus confronted Saul and said, “It is hard for you to kick against the goads,” Paul, deeply trained in Greek language and philosophy, recognized the proverb immediately. The Shepherd's mercy often comes to us as a sharp turn, redirecting us from the dry channels of self-reliance back to the living waters of God Himself. The book ends where all honest searching must end. Fear God. Keep His commandments. Receive His gifts with gratitude. This is the whole duty of man, the culmination not only of the Bible's wisdom literature, but of every sincere philosophical quest. I wandered long among the tributaries, but Scripture led me home to the Fount of every blessing and tuned my heart to sing His grace. Here is a helpful overview of Ecclesiastes. May your listening be as blessed as ours was in the reading. https://www.youtube.com/watch?v=lrsQ1tc-2w

“Vanity of vanities, says the Preacher. All is vanity.” Ecclesiastes 1:2 As a philosopher I have loved the great tradition of human wisdom. For many years I drank from the tributaries. Aristotle taught that the good life is something one lives, not something one acquires. Socrates taught that wisdom begins in humility. These insights nourished me long before I realized they were preparing me to recognize the far greater wisdom God has given in Scripture. The Greek thinkers stood downstream from a fountain they dimly sensed but could not reach. The book of Ecclesiastes speaks from that very source. Qoheleth, קהלת, the Assembler, often called the Preacher, gathers what God has revealed about life in this world. He describes the human condition with a single Hebrew word: hevel, breath, vapor. Not meaninglessness, but ungraspability - and paradox. Life slips through the fingers of those who try to seize it, and understanding reaches its limit in paradox. What cannot be possessed must be received. What we cannot control must become ours by gift. And this is why Ecclesiastes so often speaks the language of generosity. Work is a gift. Food and drink are gifts. Joy is gift. Companionship is gift. Time itself is gift. The Preacher calls us to leave behind the restless striving that characterizes life in the tributaries, and to return instead to the fountain where every good and perfect gift flows from the hand of the Giver. He also tells us something our age urgently needs to hear. There is nothing new under the sun. Our modern confidence in our own progress (central to the evolutionary mythos) is little more than hubris. We imagine ourselves advanced beyond our “primitive” forebears, yet our world repeats the same patterns of confusion and pride. Postmodern deconstruction, gender confusion, DEI initiatives, and cultural relativism are not new. They are ancient errors retold in new vocabulary. Ecclesiastes understood the human heart long before our age attempted to deconstruct it. Near the end of the book the imagery sharpens. “The words of the wise are like goads,” given by one Shepherd to guide us back toward the fountain of wisdom. When the risen Jesus confronted Saul and said, “It is hard for you to kick against the goads,” Paul, deeply trained in Greek language and philosophy, recognized the proverb immediately. The Shepherd's mercy often comes to us as a sharp turn, redirecting us from the dry channels of self-reliance back to the living waters of God Himself. The book ends where all honest searching must end. Fear God. Keep His commandments. Receive His gifts with gratitude. This is the whole duty of man, the culmination not only of the Bible's wisdom literature, but of every sincere philosophical quest. I wandered long among the tributaries, but Scripture led me home to the Fount of every blessing and tuned my heart to sing His grace. Here is a helpful overview of Ecclesiastes. May your listening be as blessed as ours was in the reading. https://www.youtube.com/watch?v=lrsQ1tc-2w

“Vanity of vanities, says the Preacher. All is vanity.” Ecclesiastes 1:2 As a philosopher I have loved the great tradition of human wisdom. For many years I drank from the tributaries. Aristotle taught that the good life is something one lives, not something one acquires. Socrates taught that wisdom begins in humility. These insights nourished me long before I realized they were preparing me to recognize the far greater wisdom God has given in Scripture. The Greek thinkers stood downstream from a fountain they dimly sensed but could not reach. The book of Ecclesiastes speaks from that very source. Qoheleth, קהלת, the Assembler, often called the Preacher, gathers what God has revealed about life in this world. He describes the human condition with a single Hebrew word: hevel, breath, vapor. Not meaninglessness, but ungraspability - and paradox. Life slips through the fingers of those who try to seize it, and understanding reaches its limit in paradox. What cannot be possessed must be received. What we cannot control must become ours by gift. And this is why Ecclesiastes so often speaks the language of generosity. Work is a gift. Food and drink are gifts. Joy is gift. Companionship is gift. Time itself is gift. The Preacher calls us to leave behind the restless striving that characterizes life in the tributaries, and to return instead to the fountain where every good and perfect gift flows from the hand of the Giver. He also tells us something our age urgently needs to hear. There is nothing new under the sun. Our modern confidence in our own progress (central to the evolutionary mythos) is little more than hubris. We imagine ourselves advanced beyond our “primitive” forebears, yet our world repeats the same patterns of confusion and pride. Postmodern deconstruction, gender confusion, DEI initiatives, and cultural relativism are not new. They are ancient errors retold in new vocabulary. Ecclesiastes understood the human heart long before our age attempted to deconstruct it. Near the end of the book the imagery sharpens. “The words of the wise are like goads,” given by one Shepherd to guide us back toward the fountain of wisdom. When the risen Jesus confronted Saul and said, “It is hard for you to kick against the goads,” Paul, deeply trained in Greek language and philosophy, recognized the proverb immediately. The Shepherd's mercy often comes to us as a sharp turn, redirecting us from the dry channels of self-reliance back to the living waters of God Himself. The book ends where all honest searching must end. Fear God. Keep His commandments. Receive His gifts with gratitude. This is the whole duty of man, the culmination not only of the Bible's wisdom literature, but of every sincere philosophical quest. I wandered long among the tributaries, but Scripture led me home to the Fount of every blessing and tuned my heart to sing His grace. Here is a helpful overview of Ecclesiastes. May your listening be as blessed as ours was in the reading. https://www.youtube.com/watch?v=lrsQ1tc-2w

“Vanity of vanities, says the Preacher. All is vanity.” Ecclesiastes 1:2 As a philosopher I have loved the great tradition of human wisdom. For many years I drank from the tributaries. Aristotle taught that the good life is something one lives, not something one acquires. Socrates taught that wisdom begins in humility. These insights nourished me long before I realized they were preparing me to recognize the far greater wisdom God has given in Scripture. The Greek thinkers stood downstream from a fountain they dimly sensed but could not reach. The book of Ecclesiastes speaks from that very source. Qoheleth, קהלת, the Assembler, often called the Preacher, gathers what God has revealed about life in this world. He describes the human condition with a single Hebrew word: hevel, breath, vapor. Not meaninglessness, but ungraspability - and paradox. Life slips through the fingers of those who try to seize it, and understanding reaches its limit in paradox. What cannot be possessed must be received. What we cannot control must become ours by gift. And this is why Ecclesiastes so often speaks the language of generosity. Work is a gift. Food and drink are gifts. Joy is gift. Companionship is gift. Time itself is gift. The Preacher calls us to leave behind the restless striving that characterizes life in the tributaries, and to return instead to the fountain where every good and perfect gift flows from the hand of the Giver. He also tells us something our age urgently needs to hear. There is nothing new under the sun. Our modern confidence in our own progress (central to the evolutionary mythos) is little more than hubris. We imagine ourselves advanced beyond our “primitive” forebears, yet our world repeats the same patterns of confusion and pride. Postmodern deconstruction, gender confusion, DEI initiatives, and cultural relativism are not new. They are ancient errors retold in new vocabulary. Ecclesiastes understood the human heart long before our age attempted to deconstruct it. Near the end of the book the imagery sharpens. “The words of the wise are like goads,” given by one Shepherd to guide us back toward the fountain of wisdom. When the risen Jesus confronted Saul and said, “It is hard for you to kick against the goads,” Paul, deeply trained in Greek language and philosophy, recognized the proverb immediately. The Shepherd's mercy often comes to us as a sharp turn, redirecting us from the dry channels of self-reliance back to the living waters of God Himself. The book ends where all honest searching must end. Fear God. Keep His commandments. Receive His gifts with gratitude. This is the whole duty of man, the culmination not only of the Bible's wisdom literature, but of every sincere philosophical quest. I wandered long among the tributaries, but Scripture led me home to the Fount of every blessing and tuned my heart to sing His grace. Here is a helpful overview of Ecclesiastes. May your listening be as blessed as ours was in the reading. https://www.youtube.com/watch?v=lrsQ1tc-2w

“Vanity of vanities, says the Preacher. All is vanity.” Ecclesiastes 1:2 As a philosopher I have loved the great tradition of human wisdom. For many years I drank from the tributaries. Aristotle taught that the good life is something one lives, not something one acquires. Socrates taught that wisdom begins in humility. These insights nourished me long before I realized they were preparing me to recognize the far greater wisdom God has given in Scripture. The Greek thinkers stood downstream from a fountain they dimly sensed but could not reach. The book of Ecclesiastes speaks from that very source. Qoheleth, קהלת, the Assembler, often called the Preacher, gathers what God has revealed about life in this world. He describes the human condition with a single Hebrew word: hevel, breath, vapor. Not meaninglessness, but ungraspability - and paradox. Life slips through the fingers of those who try to seize it, and understanding reaches its limit in paradox. What cannot be possessed must be received. What we cannot control must become ours by gift. And this is why Ecclesiastes so often speaks the language of generosity. Work is a gift. Food and drink are gifts. Joy is gift. Companionship is gift. Time itself is gift. The Preacher calls us to leave behind the restless striving that characterizes life in the tributaries, and to return instead to the fountain where every good and perfect gift flows from the hand of the Giver. He also tells us something our age urgently needs to hear. There is nothing new under the sun. Our modern confidence in our own progress (central to the evolutionary mythos) is little more than hubris. We imagine ourselves advanced beyond our “primitive” forebears, yet our world repeats the same patterns of confusion and pride. Postmodern deconstruction, gender confusion, DEI initiatives, and cultural relativism are not new. They are ancient errors retold in new vocabulary. Ecclesiastes understood the human heart long before our age attempted to deconstruct it. Near the end of the book the imagery sharpens. “The words of the wise are like goads,” given by one Shepherd to guide us back toward the fountain of wisdom. When the risen Jesus confronted Saul and said, “It is hard for you to kick against the goads,” Paul, deeply trained in Greek language and philosophy, recognized the proverb immediately. The Shepherd's mercy often comes to us as a sharp turn, redirecting us from the dry channels of self-reliance back to the living waters of God Himself. The book ends where all honest searching must end. Fear God. Keep His commandments. Receive His gifts with gratitude. This is the whole duty of man, the culmination not only of the Bible's wisdom literature, but of every sincere philosophical quest. I wandered long among the tributaries, but Scripture led me home to the Fount of every blessing and tuned my heart to sing His grace. Here is a helpful overview of Ecclesiastes. May your listening be as blessed as ours was in the reading. https://www.youtube.com/watch?v=lrsQ1tc-2w

Need drives technology development. A silent force slowing the development of a technology is often a lack of need. In a colony where there is a need for tech that can make computers with local and limited resources, new tech arises, utilizing DNA engineering.A boy takes computers from emulated personality dolls and networks them to make a super computer. Bio engineers make a new kind of vine that aggressively takes over the landscape for kilometers around. They make a computer that runs on little power and grows stronger by the day. If this computer continues to grow, it should become the most powerful computer in a few years.D.N.A. splicers – devices that engineer plants and organisms by directly editing genetic code.Heat pump – refurbished unit that keeps underground living spaces cool by venting heat through a chimney.  Wall spray insulation – hardens to a steel-like layer that keeps heat out of rock shelters.  BritLight panels and lamps – salvaged light sources that provide illumination and support plant growth.  Bio-engineered environment suits – plant-derived protective suits that regulate temperature and air quality.  AR glasses – augmented reality glasses for data display; broken in the story.  Canal link – wearable communication device, likely subdermal or ear-based, for network access.  Holo-screen – projection display used for visualizing 3D simulations in the lab.  Air cleaner – high-grade filtration unit purifying air to ISO class one.  D.N.A. printer – automated bioengineering device for printing modified organisms.  Life simulator / 3D simulation system – allows accelerated evolution and testing of virtual lifeforms.  Computer cabinet – computing unit running the life simulation, subject to wear and decay.  Magique Doll – humanoid robot hosting an emulated human personality (E.P.); powerful AI in synthetic bodies.  Driver pen – hand tool used to unlock or service mechanical and robotic components.  Tablet – portable computing device used to interface with machines and AIs.  Protein computer – second-generation analog computing system grown from synthetic biological materials.  Medusa Net – surviving network infrastructure connecting isolated computing nodes and databases.  Gravimeter – laser-based imaging tool that scans underground masses and visualizes buried objects in 3D.  Assembler/printer cubes – modular manufacturing devices capable of printing mechanical or electronic parts.  Exoskeleton work suits – wearable powered suits designed for labor and mobility in debris or heat.  Lutin transmitter – wireless control system for remote-operating robots.  Babe – Magique Doll AI acting as the neocortex of a networked AI cluster; evolves into an ASI.  Fungi computer – hybrid bio-digital computing system grown from fungus interfaced with electronics.  Sir Anthony Baker's Fungi OS – ancient experimental operating system for fungal signal processing.  Supercomputers – high-capacity computing systems still in use by the colony.  Network nodes – distributed processors that expand computational capacity over time.  Weather armor – heat-resistant outer suit used for surface exploration.  Electric sniffers – sensors that detect air quality and atmospheric conditions.  Robot arms on tracks – automated lab manipulators handling DNA printing and assembly.  Nucleo-stripper – lab device processing genetic material for integration into fungal computing systems.  Sonic manipulator – machine that uses sound waves to manipulate or sterilize biological samples.  Lattice vine – genetically engineered plant that stabilizes the environment and converts rock to soil.  Fungal interface plates – biotechnological hardware allowing fungal networks to communicate electronically.  Relic P.C. – pre-collapse computer reused as an interface for the fungi computer.  Work-site lamp – industrial light source used in underground tunnels.  Thermal transfer cables – salvaged wiring for distributing heat or electrical power in machinery.  Building bots – automated construction robots found in the junkyard.  Shipment drones – delivery robots buried in debris.Many of the characters in this project appear in future episodes.Using storytelling to place you in a time period, this series takes you, year by year, into the future. From 2040 to 2195. If you like emerging tech, eco-tech, futurism, perma-culture, apocalyptic survival scenarios, and disruptive science, sit back and enjoy short stories that showcase my research into how the future may play out. The companion site is https://in20xx.com These are works of fiction. Characters and groups are made-up and influenced by current events but not reporting facts about people or groups in the real world. This project is speculative fiction. These episodes are not about revealing what will be, but they are to excited the listener's wonder about what may come to pass.Copyright © Cy Porter 2025. All rights reserved.

Katia, Emmanuel et Guillaume discutent Java, Kotlin, Quarkus, Hibernate, Spring Boot 4, intelligence artificielle (modèles Nano Banana, VO3, frameworks agentiques, embedding). On discute les vulnerabilités OWASP pour les LLMs, les personalités de codage des différents modèles, Podman vs Docker, comment moderniser des projets legacy. Mais surtout on a passé du temps sur les présentations de Luc Julia et les différents contre points qui ont fait le buzz sur les réseaux. Enregistré le 12 septembre 2025 Téléchargement de l'épisode LesCastCodeurs-Episode-330.mp3 ou en vidéo sur YouTube. News Langages Dans cette vidéo, José détaille les nouveautés de Java entre Java 21 et 25 https://inside.java/2025/08/31/roadto25-java-language/ Aperçu des nouveautés du JDK 25 : Introduction des nouvelles fonctionnalités du langage Java et des changements à venir [00:02]. Programmation orientée données et Pattern Matching [00:43] : Évolution du “pattern matching” pour la déconstruction des “records” [01:22]. Utilisation des “sealed types” dans les expressions switch pour améliorer la lisibilité et la robustesse du code [01:47]. Introduction des “unnamed patterns” (_) pour indiquer qu'une variable n'est pas utilisée [04:47]. Support des types primitifs dans instanceof et switch (en preview) [14:02]. Conception d'applications Java [00:52] : Simplification de la méthode main [21:31]. Exécution directe des fichiers .java sans compilation explicite [22:46]. Amélioration des mécanismes d'importation [23:41]. Utilisation de la syntaxe Markdown dans la Javadoc [27:46]. Immuabilité et valeurs nulles [01:08] : Problème d'observation de champs final à null pendant la construction d'un objet [28:44]. JEP 513 pour contrôler l'appel à super() et restreindre l'usage de this dans les constructeurs [33:29]. JDK 25 sort le 16 septembre https://openjdk.org/projects/jdk/25/ Scoped Values (JEP 505) - alternative plus efficace aux ThreadLocal pour partager des données immutables entre threads Structured Concurrency (JEP 506) - traiter des groupes de tâches concurrentes comme une seule unité de travail, simplifiant la gestion des threads Compact Object Headers (JEP 519) - Fonctionnalité finale qui réduit de 50% la taille des en-têtes d'objets (de 128 à 64 bits), économisant jusqu'à 22% de mémoire heap Flexible Constructor Bodies (JEP 513) - Relaxation des restrictions sur les constructeurs, permettant du code avant l'appel super() ou this() Module Import Declarations (JEP 511) - Import simplifié permettant d'importer tous les éléments publics d'un module en une seule déclaration Compact Source Files (JEP 512) - Simplification des programmes Java basiques avec des méthodes main d'instance sans classe wrapper obligatoire Primitive Types in Patterns (JEP 455) - Troisième preview étendant le pattern matching et instanceof aux types primitifs dans switch et instanceof Generational Shenandoah (JEP 521) - Le garbage collector Shenandoah passe en mode générationnel pour de meilleures performances JFR Method Timing & Tracing (JEP 520) - Nouvel outillage de profilage pour mesurer le temps d'exécution et tracer les appels de méthodes Key Derivation API (JEP 510) - API finale pour les fonctions de dérivation de clés cryptographiques, remplaçant les implémentations tierces Améliorations du traitement des annotations dans Kotlin 2.2 https://blog.jetbrains.com/idea/2025/09/improved-annotation-handling-in-kotlin-2-2-less-boilerplate-fewer-surprises/ Avant Kotlin 2.2, les annotations sur les paramètres de constructeur n'étaient appliquées qu'au paramètre, pas à la propriété ou au champ Cela causait des bugs subtils avec Spring et JPA où la validation ne fonctionnait qu'à la création d'objet, pas lors des mises à jour La solution précédente nécessitait d'utiliser explicitement @field: pour chaque annotation, créant du code verbeux Kotlin 2.2 introduit un nouveau comportement par défaut qui applique les annotations aux paramètres ET aux propriétés/champs automatiquement Le code devient plus propre sans avoir besoin de syntaxe @field: répétitive Pour l'activer, ajouter -Xannotation-default-target=param-property dans les options du compilateur Gradle IntelliJ IDEA propose un quick-fix pour activer ce comportement à l'échelle du projet Cette amélioration rend l'intégration Kotlin plus fluide avec les frameworks majeurs comme Spring et JPA Le comportement peut être configuré pour garder l'ancien mode ou activer un mode transitoire avec avertissements Cette mise à jour fait partie d'une initiative plus large pour améliorer l'expérience Kotlin + Spring Librairies Sortie de Quarkus 3.26 avec mises à jour d'Hibernate et autres fonctionnalités - https://quarkus.io/blog/quarkus-3-26-released/ mettez à jour vers la 3.26.x car il y a eu une regression vert.x Jalon important vers la version LTS 3.27 prévue fin septembre, basée sur cette version Mise à jour vers Hibernate ORM 7.1, Hibernate Search 8.1 et Hibernate Reactive 3.1 Support des unités de persistance nommées et sources de données dans Hibernate Reactive Démarrage hors ligne et configuration de dialecte pour Hibernate ORM même si la base n'est pas accessible Refonte de la console HQL dans Dev UI avec fonctionnalité Hibernate Assistant intégrée Exposition des capacités Dev UI comme fonctions MCP pour pilotage via outils IA Rafraîchissement automatique des tokens OIDC en cas de réponse 401 des clients REST Extension JFR pour capturer les données runtime (nom app, version, extensions actives) Bump de Gradle vers la version 9.0 par défaut, suppression du support des classes config legacy Guide de démarrage avec Quarkus et A2A Java SDK 0.3.0 (pour faire discuter des agents IA avec la dernière version du protocole A2A) https://quarkus.io/blog/quarkus-a2a-java-0-3-0-alpha-release/ Sortie de l'A2A Java SDK 0.3.0.Alpha1, aligné avec la spécification A2A v0.3.0. Protocole A2A : standard ouvert (Linux Foundation), permet la communication inter-agents IA polyglottes. Version 0.3.0 plus stable, introduit le support gRPC. Mises à jour générales : changements significatifs, expérience utilisateur améliorée (côté client et serveur). Agents serveur A2A : Support gRPC ajouté (en plus de JSON-RPC). HTTP+JSON/REST à venir. Implémentations basées sur Quarkus (alternatives Jakarta existent). Dépendances spécifiques pour chaque transport (ex: a2a-java-sdk-reference-jsonrpc, a2a-java-sdk-reference-grpc). AgentCard : décrit les capacités de l'agent. Doit spécifier le point d'accès primaire et tous les transports supportés (additionalInterfaces). Clients A2A : Dépendance principale : a2a-java-sdk-client. Support gRPC ajouté (en plus de JSON-RPC). HTTP+JSON/REST à venir. Dépendance spécifique pour gRPC : a2a-java-sdk-client-transport-grpc. Création de client : via ClientBuilder. Sélectionne automatiquement le transport selon l'AgentCard et la configuration client. Permet de spécifier les transports supportés par le client (withTransport). Comment générer et éditer des images en Java avec Nano Banana, le “photoshop killer” de Google https://glaforge.dev/posts/2025/09/09/calling-nano-banana-from-java/ Objectif : Intégrer le modèle Nano Banana (Gemini 2.5 Flash Image preview) dans des applications Java. SDK utilisé : GenAI Java SDK de Google. Compatibilité : Supporté par ADK for Java ; pas encore par LangChain4j (limitation de multimodalité de sortie). Capacités de Nano Banana : Créer de nouvelles images. Modifier des images existantes. Assembler plusieurs images. Mise en œuvre Java : Quelle dépendance utiliser Comment s'authentifier Comment configurer le modèle Nature du modèle : Nano Banana est un modèle de chat qui peut retourner du texte et une image (pas simplement juste un modèle générateur d'image) Exemples d'utilisation : Création : Via un simple prompt textuel. Modification : En passant l'image existante (tableau de bytes) et les instructions de modification (prompt). Assemblage : En passant plusieurs images (en bytes) et les instructions d'intégration (prompt). Message clé : Toutes ces fonctionnalités sont accessibles en Java, sans nécessiter Python. Générer des vidéos IA avec le modèle Veo 3, mais en Java ! https://glaforge.dev/posts/2025/09/10/generating-videos-in-java-with-veo3/ Génération de vidéos en Java avec Veo 3 (via le GenAI Java SDK de Google). Veo 3: Annoncé comme GA, prix réduits, support du format 9:16, résolution jusqu'à 1080p. Création de vidéos : À partir d'une invite textuelle (prompt). À partir d'une image existante. Deux versions différentes du modèle : veo-3.0-generate-001 (qualité supérieure, plus coûteux, plus lent). veo-3.0-fast-generate-001 (qualité inférieure, moins coûteux, mais plus rapide). Rod Johnson sur ecrire des aplication agentic en Java plus facilement qu'en python avec Embabel https://medium.com/@springrod/you-can-build-better-ai-agents-in-java-than-python-868eaf008493 Rod the papa de Spring réécrit un exemple CrewAI (Python) qui génère un livre en utilisant Embabel (Java) pour démontrer la supériorité de Java L'application utilise plusieurs agents AI spécialisés : un chercheur, un planificateur de livre et des rédacteurs de chapitres Le processus suit trois étapes : recherche du sujet, création du plan, rédaction parallèle des chapitres puis assemblage CrewAI souffre de plusieurs problèmes : configuration lourde, manque de type safety, utilisation de clés magiques dans les prompts La version Embabel nécessite moins de code Java que l'original Python et moins de fichiers de configuration YAML Embabel apporte la type safety complète, éliminant les erreurs de frappe dans les prompts et améliorant l'outillage IDE La gestion de la concurrence est mieux contrôlée en Java pour éviter les limites de débit des APIs LLM L'intégration avec Spring permet une configuration externe simple des modèles LLM et hyperparamètres Le planificateur Embabel détermine automatiquement l'ordre d'exécution des actions basé sur leurs types requis L'argument principal : l'écosystème JVM offre un meilleur modèle de programmation et accès à la logique métier existante que Python Il y a pas mal de nouveaux framework agentic en Java, notamment le dernier LAngchain4j Agentic Spring lance un serie de blog posts sur les nouveautés de Spring Boot 4 https://spring.io/blog/2025/09/02/road_to_ga_introduction baseline JDK 17 mais rebase sur Jakarta 11 Kotlin 2, Jackson 3 et JUnit 6 Fonctionnalités de résilience principales de Spring : @ConcurrencyLimit, @Retryable, RetryTemplate Versioning d'API dans Spring Améliorations du client de service HTTP L'état des clients HTTP dans Spring Introduction du support Jackson 3 dans Spring Consommateur partagé - les queues Kafka dans Spring Kafka Modularisation de Spring Boot Autorisation progressive dans Spring Security Spring gRPC - un nouveau module Spring Boot Applications null-safe avec Spring Boot 4 OpenTelemetry avec Spring Boot Repos Ahead of Time (Partie 2) Web Faire de la recherche sémantique directement dans le navigateur en local, avec EmbeddingGemma et Transformers.js https://glaforge.dev/posts/2025/09/08/in-browser-semantic-search-with-embeddinggemma/ EmbeddingGemma: Nouveau modèle d'embedding (308M paramètres) de Google DeepMind. Objectif: Permettre la recherche sémantique directement dans le navigateur. Avantages clés de l'IA côté client: Confidentialité: Aucune donnée envoyée à un serveur. Coûts réduits: Pas besoin de serveurs coûteux (GPU), hébergement statique. Faible latence: Traitement instantané sans allers-retours réseau. Fonctionnement hors ligne: Possible après le chargement initial du modèle. Technologie principale: Modèle: EmbeddingGemma (petit, performant, multilingue, support MRL pour réduire la taille des vecteurs). Moteur d'inférence: Transformers.js de HuggingFace (exécute les modèles AI en JavaScript dans le navigateur). Déploiement: Site statique avec Vite/React/Tailwind CSS, déployé sur Firebase Hosting via GitHub Actions. Gestion du modèle: Fichiers du modèle trop lourds pour Git; téléchargés depuis HuggingFace Hub pendant le CI/CD. Fonctionnement de l'app: Charge le modèle, génère des embeddings pour requêtes/documents, calcule la similarité sémantique. Conclusion: Démonstration d'une recherche sémantique privée, économique et sans serveur, soulignant le potentiel de l'IA embarquée dans le navigateur. Data et Intelligence Artificielle Docker lance Cagent, une sorte de framework multi-agent IA utilisant des LLMs externes, des modèles de Docker Model Runner, avec le Docker MCP Tookit. Il propose un format YAML pour décrire les agents d'un système multi-agents. https://github.com/docker/cagent des agents “prompt driven” (pas de code) et une structure pour decrire comment ils sont deployés pas clair comment ils sont appelés a part dans la ligne de commande de cagent fait par david gageot L'owasp décrit l'independance excessive des LLM comme une vulnerabilité https://genai.owasp.org/llmrisk2023-24/llm08-excessive-agency/ L'agence excessive désigne la vulnérabilité qui permet aux systèmes LLM d'effectuer des actions dommageables via des sorties inattendues ou ambiguës. Elle résulte de trois causes principales : fonctionnalités excessives, permissions excessives ou autonomie excessive des agents LLM. Les fonctionnalités excessives incluent l'accès à des plugins qui offrent plus de capacités que nécessaire, comme un plugin de lecture qui peut aussi modifier ou supprimer. Les permissions excessives se manifestent quand un plugin accède aux systèmes avec des droits trop élevés, par exemple un accès en lecture qui inclut aussi l'écriture. L'autonomie excessive survient quand le système effectue des actions critiques sans validation humaine préalable. Un scénario d'attaque typique : un assistant personnel avec accès email peut être manipulé par injection de prompt pour envoyer du spam via la boîte de l'utilisateur. La prévention implique de limiter strictement les plugins aux fonctions minimales nécessaires pour l'opération prévue. Il faut éviter les fonctions ouvertes comme “exécuter une commande shell” au profit d'outils plus granulaires et spécifiques. L'application du principe de moindre privilège est cruciale : chaque plugin doit avoir uniquement les permissions minimales requises. Le contrôle humain dans la boucle reste essentiel pour valider les actions à fort impact avant leur exécution. Lancement du MCP registry, une sorte de méta-annuaire officiel pour référencer les serveurs MCP https://www.marktechpost.com/2025/09/09/mcp-team-launches-the-preview-version-of-the-mcp-registry-a-federated-discovery-layer-for-enterprise-ai/ MCP Registry : Couche de découverte fédérée pour l'IA d'entreprise. Fonctionne comme le DNS pour le contexte de l'IA, permettant la découverte de serveurs MCP publics ou privés. Modèle fédéré : Évite les risques de sécurité et de conformité d'un registre monolithique. Permet des sous-registres privés tout en conservant une source de vérité “upstream”. Avantages entreprises : Découverte interne sécurisée. Gouvernance centralisée des serveurs externes. Réduction de la prolifération des contextes. Support pour les agents IA hybrides (données privées/publiques). Projet open source, actuellement en version preview. Blog post officiel : https://blog.modelcontextprotocol.io/posts/2025-09-08-mcp-registry-preview/ Exploration des internals du transaction log SQL Server https://debezium.io/blog/2025/09/08/sqlserver-tx-log/ C'est un article pour les rugeux qui veulent savoir comment SQLServer marche à l'interieur Debezium utilise actuellement les change tables de SQL Server CDC en polling périodique L'article explore la possibilité de parser directement le transaction log pour améliorer les performances Le transaction log est divisé en Virtual Log Files (VLFs) utilisés de manière circulaire Chaque VLF contient des blocs (512B à 60KB) qui contiennent les records de transactions Chaque record a un Log Sequence Number (LSN) unique pour l'identifier précisément Les données sont stockées dans des pages de 8KB avec header de 96 bytes et offset array Les tables sont organisées en partitions et allocation units pour gérer l'espace disque L'utilitaire DBCC permet d'explorer la structure interne des pages et leur contenu Cette compréhension pose les bases pour parser programmatiquement le transaction log dans un prochain article Outillage Les personalités des codeurs des différents LLMs https://www.sonarsource.com/blog/the-coding-personalities-of-leading-llms-gpt-5-update/ GPT-5 minimal ne détrône pas Claude Sonnet 4 comme leader en performance fonctionnelle malgré ses 75% de réussite GPT-5 génère un code extrêmement verbeux avec 490 000 lignes contre 370 000 pour Claude Sonnet 4 sur les mêmes tâches La complexité cyclomatique et cognitive du code GPT-5 est dramatiquement plus élevée que tous les autres modèles GPT-5 introduit 3,90 problèmes par tâche réussie contre seulement 2,11 pour Claude Sonnet 4 Point fort de GPT-5 : sécurité exceptionnelle avec seulement 0,12 vulnérabilité par 1000 lignes de code Faiblesse majeure : densité très élevée de “code smells” (25,28 par 1000 lignes) nuisant à la maintenabilité GPT-5 produit 12% de problèmes liés à la complexité cognitive, le taux le plus élevé de tous les modèles Tendance aux erreurs logiques fondamentales avec 24% de bugs de type “Control-flow mistake” Réapparition de vulnérabilités classiques comme les failles d'injection et de traversée de chemin Nécessité d'une gouvernance renforcée avec analyse statique obligatoire pour gérer la complexité du code généré Pourquoi j'ai abandonné Docker pour Podman https://codesmash.dev/why-i-ditched-docker-for-podman-and-you-should-too Problème Docker : Le daemon dockerd persistant s'exécute avec des privilèges root, posant des risques de sécurité (nombreuses CVEs citées) et consommant des ressources inutilement. Solution Podman : Sans Daemon : Pas de processus d'arrière-plan persistant. Les conteneurs s'exécutent comme des processus enfants de la commande Podman, sous les privilèges de l'utilisateur. Sécurité Renforcée : Réduction de la surface d'attaque. Une évasion de conteneur compromet un utilisateur non privilégié sur l'hôte, pas le système entier. Mode rootless. Fiabilité Accrue : Pas de point de défaillance unique ; le crash d'un conteneur n'affecte pas les autres. Moins de Ressources : Pas de daemon constamment actif, donc moins de mémoire et de CPU. Fonctionnalités Clés de Podman : Intégration Systemd : Génération automatique de fichiers d'unité systemd pour gérer les conteneurs comme des services Linux standards. Alignement Kubernetes : Support natif des pods et capacité à générer des fichiers Kubernetes YAML directement (podman generate kube), facilitant le développement local pour K8s. Philosophie Unix : Se concentre sur l'exécution des conteneurs, délègue les tâches spécialisées à des outils dédiés (ex: Buildah pour la construction d'images, Skopeo pour leur gestion). Migration Facile : CLI compatible Docker : podman utilise les mêmes commandes que docker (alias docker=podman fonctionne). Les Dockerfiles existants sont directement utilisables. Améliorations incluses : Sécurité par défaut (ports privilégiés en mode rootless), meilleure gestion des permissions de volume, API Docker compatible optionnelle. Option de convertir Docker Compose en Kubernetes YAML. Bénéfices en Production : Sécurité améliorée, utilisation plus propre des ressources. Podman représente une évolution plus sécurisée et mieux alignée avec les pratiques modernes de gestion Linux et de déploiement de conteneurs. Guide Pratique (Exemple FastAPI) : Le Dockerfile ne change pas. podman build et podman run remplacent directement les commandes Docker. Déploiement en production via Systemd. Gestion d'applications multi-services avec les “pods” Podman. Compatibilité Docker Compose via podman-compose ou kompose. Détection améliorée des APIs vulnérables dans les IDEs JetBrains et Qodana - https://blog.jetbrains.com/idea/2025/09/enhanced-vulnerable-api-detection-in-jetbrains-ides-and-qodana/ JetBrains s'associe avec Mend.io pour renforcer la sécurité du code dans leurs outils Le plugin Package Checker bénéficie de nouvelles données enrichies sur les APIs vulnérables Analyse des graphes d'appels pour couvrir plus de méthodes publiques des bibliothèques open-source Support de Java, Kotlin, C#, JavaScript, TypeScript et Python pour la détection de vulnérabilités Activation des inspections via Paramètres > Editor > Inspections en recherchant “Vulnerable API” Surlignage automatique des méthodes vulnérables avec détails des failles au survol Action contextuelle pour naviguer directement vers la déclaration de dépendance problématique Mise à jour automatique vers une version non affectée via Alt+Enter sur la dépendance Fenêtre dédiée “Vulnerable Dependencies” pour voir l'état global des vulnérabilités du projet Méthodologies Le retour de du sondage de Stack Overflow sur l'usage de l'IA dans le code https://medium.com/@amareshadak/stack-overflow-just-exposed-the-ugly-truth-about-ai-coding-tools-b4f7b5992191 84% des développeurs utilisent l'IA quotidiennement, mais 46% ne font pas confiance aux résultats. Seulement 3,1% font “hautement confiance” au code généré. 66% sont frustrés par les solutions IA “presque correctes”. 45% disent que déboguer le code IA prend plus de temps que l'écrire soi-même. Les développeurs seniors (10+ ans) font moins confiance à l'IA (2,6%) que les débutants (6,1%), créant un écart de connaissances dangereux. Les pays occidentaux montrent moins de confiance - Allemagne (22%), UK (23%), USA (28%) - que l'Inde (56%). Les créateurs d'outils IA leur font moins confiance. 77% des développeurs professionnels rejettent la programmation en langage naturel, seuls 12% l'utilisent réellement. Quand l'IA échoue, 75% se tournent vers les humains. 35% des visites Stack Overflow concernent maintenant des problèmes liés à l'IA. 69% rapportent des gains de productivité personnels, mais seulement 17% voient une amélioration de la collaboration d'équipe. Coûts cachés : temps de vérification, explication du code IA aux équipes, refactorisation et charge cognitive constante. Les plateformes humaines dominent encore : Stack Overflow (84%), GitHub (67%), YouTube (61%) pour résoudre les problèmes IA. L'avenir suggère un “développement augmenté” où l'IA devient un outil parmi d'autres, nécessitant transparence et gestion de l'incertitude. Mentorat open source et défis communautaires par les gens de Microcks https://microcks.io/blog/beyond-code-open-source-mentorship/ Microcks souffre du syndrome des “utilisateurs silencieux” qui bénéficient du projet sans contribuer Malgré des milliers de téléchargements et une adoption croissante, l'engagement communautaire reste faible Ce manque d'interaction crée des défis de durabilité et limite l'innovation du projet Les mainteneurs développent dans le vide sans feedback des vrais utilisateurs Contribuer ne nécessite pas de coder : documentation, partage d'expérience, signalement de bugs suffisent Parler du project qu'on aime autour de soi est aussi super utile Microcks a aussi des questions specifiques qu'ils ont posé dans le blog, donc si vous l'utilisez, aller voir Le succès de l'open source dépend de la transformation des utilisateurs en véritables partenaires communautaires c'est un point assez commun je trouve, le ratio parlant / silencieux est tres petit et cela encourage les quelques grandes gueules La modernisation du systemes legacy, c'est pas que de la tech https://blog.scottlogic.com/2025/08/27/holistic-approach-successful-legacy-modernisation.html Un artcile qui prend du recul sur la modernisation de systemes legacy Les projets de modernisation legacy nécessitent une vision holistique au-delà du simple focus technologique Les drivers business diffèrent des projets greenfield : réduction des coûts et mitigation des risques plutôt que génération de revenus L'état actuel est plus complexe à cartographier avec de nombreuses dépendances et risques de rupture Collaboration essentielle entre Architectes, Analystes Business et Designers UX dès la phase de découverte Approche tridimensionnelle obligatoire : Personnes, Processus et Technologie (comme un jeu d'échecs 3D) Le leadership doit créer l'espace nécessaire pour la découverte et la planification plutôt que presser l'équipe Communication en termes business plutôt que techniques vers tous les niveaux de l'organisation Planification préalable essentielle contrairement aux idées reçues sur l'agilité Séquencement optimal souvent non-évident et nécessitant une analyse approfondie des interdépendances Phases projet alignées sur les résultats business permettent l'agilité au sein de chaque phase Sécurité Cyber Attaque su Musée Histoire Naturelle https://www.franceinfo.fr/internet/securite-sur-internet/cyberattaques/le-museum-nati[…]e-d-une-cyberattaque-severe-une-plainte-deposee_7430356.html Compromission massive de packages npm populaires par un malware crypto https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised 18 packages npm très populaires compromis le 8 septembre 2025, incluant chalk, debug, ansi-styles avec plus de 2 milliards de téléchargements hebdomadaires combinés duckdb s'est rajouté à la liste Code malveillant injecté qui intercepte silencieusement l'activité crypto et web3 dans les navigateurs des utilisateurs Le malware manipule les interactions de wallet et redirige les paiements vers des comptes contrôlés par l'attaquant sans signes évidents Injection dans les fonctions critiques comme fetch, XMLHttpRequest et APIs de wallets (window.ethereum, Solana) pour intercepter le trafic Détection et remplacement automatique des adresses crypto sur multiple blockchains (Ethereum, Bitcoin, Solana, Tron, Litecoin, Bitcoin Cash) Les transactions sont modifiées en arrière-plan même si l'interface utilisateur semble correcte et légitime Utilise des adresses “sosies” via correspondance de chaînes pour rendre les échanges moins évidents à détecter Le mainteneur compromis par email de phishing provenant du faux domaine “mailto:support@npmjs.help|support@npmjs.help” enregistré 3 jours avant l'attaque sur une demande de mise a jour de son autheotnfication a deux facteurs après un an Aikido a alerté le mainteneur via Bluesky qui a confirmé la compromission et commencé le nettoyage des packages Attaque sophistiquée opérant à plusieurs niveaux: contenu web, appels API et manipulation des signatures de transactions Les anti-cheats de jeux vidéo : une faille de sécurité majeure ? - https://tferdinand.net/jeux-video-et-si-votre-anti-cheat-etait-la-plus-grosse-faille/ Les anti-cheats modernes s'installent au Ring 0 (noyau système) avec privilèges maximaux Ils obtiennent le même niveau d'accès que les antivirus professionnels mais sans audit ni certification Certains exploitent Secure Boot pour se charger avant le système d'exploitation Risque de supply chain : le groupe APT41 a déjà compromis des jeux comme League of Legends Un attaquant infiltré pourrait désactiver les solutions de sécurité et rester invisible Menace de stabilité : une erreur peut empêcher le démarrage du système (référence CrowdStrike) Conflits possibles entre différents anti-cheats qui se bloquent mutuellement Surveillance en temps réel des données d'utilisation sous prétexte anti-triche Dérive dangereuse selon l'auteur : des entreprises de jeux accèdent au niveau EDR Alternatives limitées : cloud gaming ou sandboxing avec impact sur performances donc faites gaffe aux jeux que vos gamins installent ! Loi, société et organisation Luc Julia au Sénat - Monsieur Phi réagi et publie la vidéo Luc Julia au Sénat : autopsie d'un grand N'IMPORTE QUOI https://www.youtube.com/watch?v=e5kDHL-nnh4 En format podcast de 20 minutes, sorti au même moment et à propos de sa conf à Devoxx https://www.youtube.com/watch?v=Q0gvaIZz1dM Le lab IA - Jérôme Fortias - Et si Luc Julia avait raison https://www.youtube.com/watch?v=KScI5PkCIaE Luc Julia au Senat https://www.youtube.com/watch?v=UjBZaKcTeIY Luc Julia se défend https://www.youtube.com/watch?v=DZmxa7jJ8sI Intelligence artificielle : catastrophe imminente ? - Luc Julia vs Maxime Fournes https://www.youtube.com/watch?v=sCNqGt7yIjo Tech and Co Monsieur Phi vs Luc Julia (put a click) https://www.youtube.com/watch?v=xKeFsOceT44 La tronche en biais https://www.youtube.com/live/zFwLAOgY0Wc Conférences La liste des conférences provenant de Developers Conferences Agenda/List par Aurélie Vache et contributeurs : 12 septembre 2025 : Agile Pays Basque 2025 - Bidart (France) 15 septembre 2025 : Agile Tour Montpellier - Montpellier (France) 18-19 septembre 2025 : API Platform Conference - Lille (France) & Online 22-24 septembre 2025 : Kernel Recipes - Paris (France) 22-27 septembre 2025 : La Mélée Numérique - Toulouse (France) 23 septembre 2025 : OWASP AppSec France 2025 - Paris (France) 23-24 septembre 2025 : AI Engineer Paris - Paris (France) 25 septembre 2025 : Agile Game Toulouse - Toulouse (France) 25-26 septembre 2025 : Paris Web 2025 - Paris (France) 30 septembre 2025-1 octobre 2025 : PyData Paris 2025 - Paris (France) 2 octobre 2025 : Nantes Craft - Nantes (France) 2-3 octobre 2025 : Volcamp - Clermont-Ferrand (France) 3 octobre 2025 : DevFest Perros-Guirec 2025 - Perros-Guirec (France) 6-7 octobre 2025 : Swift Connection 2025 - Paris (France) 6-10 octobre 2025 : Devoxx Belgium - Antwerp (Belgium) 7 octobre 2025 : BSides Mulhouse - Mulhouse (France) 7-8 octobre 2025 : Agile en Seine - Issy-les-Moulineaux (France) 8-10 octobre 2025 : SIG 2025 - Paris (France) & Online 9 octobre 2025 : DevCon #25 : informatique quantique - Paris (France) 9-10 octobre 2025 : Forum PHP 2025 - Marne-la-Vallée (France) 9-10 octobre 2025 : EuroRust 2025 - Paris (France) 16 octobre 2025 : PlatformCon25 Live Day Paris - Paris (France) 16 octobre 2025 : Power 365 - 2025 - Lille (France) 16-17 octobre 2025 : DevFest Nantes - Nantes (France) 17 octobre 2025 : Sylius Con 2025 - Lyon (France) 17 octobre 2025 : ScalaIO 2025 - Paris (France) 17-19 octobre 2025 : OpenInfra Summit Europe - Paris (France) 20 octobre 2025 : Codeurs en Seine - Rouen (France) 23 octobre 2025 : Cloud Nord - Lille (France) 30-31 octobre 2025 : Agile Tour Bordeaux 2025 - Bordeaux (France) 30-31 octobre 2025 : Agile Tour Nantais 2025 - Nantes (France) 30 octobre 2025-2 novembre 2025 : PyConFR 2025 - Lyon (France) 4-7 novembre 2025 : NewCrafts 2025 - Paris (France) 5-6 novembre 2025 : Tech Show Paris - Paris (France) 5-6 novembre 2025 : Red Hat Summit: Connect Paris 2025 - Paris (France) 6 novembre 2025 : dotAI 2025 - Paris (France) 6 novembre 2025 : Agile Tour Aix-Marseille 2025 - Gardanne (France) 7 novembre 2025 : BDX I/O - Bordeaux (France) 12-14 novembre 2025 : Devoxx Morocco - Marrakech (Morocco) 13 novembre 2025 : DevFest Toulouse - Toulouse (France) 15-16 novembre 2025 : Capitole du Libre - Toulouse (France) 19 novembre 2025 : SREday Paris 2025 Q4 - Paris (France) 19-21 novembre 2025 : Agile Grenoble - Grenoble (France) 20 novembre 2025 : OVHcloud Summit - Paris (France) 21 novembre 2025 : DevFest Paris 2025 - Paris (France) 27 novembre 2025 : DevFest Strasbourg 2025 - Strasbourg (France) 28 novembre 2025 : DevFest Lyon - Lyon (France) 1-2 décembre 2025 : Tech Rocks Summit 2025 - Paris (France) 4-5 décembre 2025 : Agile Tour Rennes - Rennes (France) 5 décembre 2025 : DevFest Dijon 2025 - Dijon (France) 9-11 décembre 2025 : APIdays Paris - Paris (France) 9-11 décembre 2025 : Green IO Paris - Paris (France) 10-11 décembre 2025 : Devops REX - Paris (France) 10-11 décembre 2025 : Open Source Experience - Paris (France) 11 décembre 2025 : Normandie.ai 2025 - Rouen (France) 14-17 janvier 2026 : SnowCamp 2026 - Grenoble (France) 2-6 février 2026 : Web Days Convention - Aix-en-Provence (France) 3 février 2026 : Cloud Native Days France 2026 - Paris (France) 12-13 février 2026 : Touraine Tech #26 - Tours (France) 22-24 avril 2026 : Devoxx France 2026 - Paris (France) 23-25 avril 2026 : Devoxx Greece - Athens (Greece) 17 juin 2026 : Devoxx Poland - Krakow (Poland) 4 septembre 2026 : JUG SUmmer Camp 2026 - La Rochelle (France) Nous contacter Pour réagir à cet épisode, venez discuter sur le groupe Google https://groups.google.com/group/lescastcodeurs Contactez-nous via X/twitter https://twitter.com/lescastcodeurs ou Bluesky https://bsky.app/profile/lescastcodeurs.com Faire un crowdcast ou une crowdquestion Soutenez Les Cast Codeurs sur Patreon https://www.patreon.com/LesCastCodeurs Tous les épisodes et toutes les infos sur https://lescastcodeurs.com/

durée : 01:04:58 - Les Nuits de France Culture - par : Mathias Le Gargasson - À Amiens, Edward Bond participe à un atelier de théâtre avec des lycéens. C'est l'occasion pour lui de dire combien il apprécie la simplicité mais aussi l'intelligence, l'intuition et surtout la liberté des jeunes qui contrastent avec notre emprisonnement face aux problèmes du monde. - réalisation : Massimo Bellini - invités : Edward Bond Dramaturge et metteur en scène britannique; Jérôme Hankins Maître de conférences en Études théâtrales à L'université de Picardie Jules Verne (Amiens), traducteur, directeur artistique de l'Outil compagnie (dans la Somme).; Bruno Tackels Essayiste et dramaturge. Agrégé et docteur en philosophie, ancien enseignant d'esthétique et d'histoire du théâtre contemporain.

This episode features Geoffrey Decker, an instructor in Computer Science at the Northern Illinois University (NIU) and a firm believer in quality over quantity when teaching programming. Geoffrey encourages getting students “down and dirty into the programming” — not just teaching theory or showing pictures — so they truly “program and really test their skills.” His goal? Geoffrey wants students to learn so well that “they can teach themselves advanced techniques.” Advice to educators: His message is clear: “No teacher of programming should just be a droner. Don't drone — bring your enthusiasm and a solid, positive attitude to teaching.” This mindset transformed his tough Assembler class into an engaging experience that sparked students' interest to sign up for and continue with advanced Mainframe courses. Don't miss the rapid-fire questions at the end — you won't believe how many vinyl LPs and CDs he owns! If you guess right, let me know!! 

Voici l’essentiel de l’épisode du jeudi 8 mai 2025 pour l’émission La Commission: Léon XIV, Robert Francis Prevost, devient le premier pape américain de l’Histoire. Missionnaire au Pérou pendant vingt ans, artisan discret du Vatican sous François, il incarne une Église proche du peuple et guidée par une modération assumée. On en parle avec Simon Lessard, journaliste spécialisé en affaires religieuses au Verbe médias, et Natalie Roquet, Québécoise qui habite à Rome. Le Québec est le champion des grèves au Canada. En 2023, 91% des arrêts de travail au pays ont touché le Québec. Assembler un immeuble de 20 logements, sur quatre étages, avec ascenseur… en à peine quatre jours et demi : ce n’est plus de la science-fiction, c’est la promesse bien réelle de la construction modulaire. Voir https://www.cogecomedia.com/vie-privee pour notre politique de vie privée

RJJ Software's Software Development Service This episode of The Modern .NET Show is supported, in part, by RJJ Software's Podcasting Services, whether your company is looking to elevate its UK operations or reshape its US strategy, we can provide tailored solutions that exceed expectations. Show Notes "When you program for the NES you deeply need to understand the hardware, right. And that's not a thing; like as a .NET developer you don't really know what a register is, or like or a bus, or like NES has a thing called a PPU"— Jonathan Peppers Welcome friends to The Modern .NET Show; the premier .NET podcast, focusing entirely on the knowledge, tools, and frameworks that all .NET developers should have in their toolbox. We are the go-to podcast for .NET developers worldwide, and I am your host: Jamie "GaProgMan" Taylor. In this episode, Jonathan Peppers joins us to talk about something which is a little out of the ordinary for us here: programming the Nintendo Entertainment System but in C#. We talk about the process behind his (some would say absurd) idea for an AOT transpiler which can convert a subset of C# over to the Assembler required to write and publish a NES game. "So you think about that example, what I described there on the NES side is actually very similar to what's on the IL side, is that in IL, you have a string, right? It goes and looks up in a string table, the contents of the string, and puts it on a stack, and then it calls vram_write, and then it's the runtimes job to actually like make that happen at runtime; or in the case of an AOT compiler it would emit, you know, native machine code that does the same thing."— Jonathan Peppers Along the way, we talk about that Ahead-of-Time compilation is, have a brief intro to what IL is (that's what your C# code is compiled to before running it), and how all of that fits in with .NES—the wonderful name for Jon's AOT NES compiler. Anyway, without further ado, let's sit back, open up a terminal, type in `dotnet new podcast` and we'll dive into the core of Modern .NET. Supporting the Show If you find this episode useful in any way, please consider supporting the show by either leaving a review (check our review page for ways to do that), sharing the episode with a friend or colleague, buying the host a coffee, or considering becoming a Patron of the show. Full Show Notes The full show notes, including links to some of the things we discussed and a full transcription of this episode, can be found at: https://dotnetcore.show/season-7/jonathan-peppers-unleashes-code-chaos-how-dotnet-meets-the-nes/ Links: Native AOT Development System.Reflection.Metadata 8bitworkshop.com neslib BinaryWriter Retron5 Flight68k .NES on GitHub .NES Discord Server Supporting the show: Leave a rating or review Buy the show a coffee Become a patron Getting in Touch: Via the contact page Joining the Discord Remember to rate and review the show on Apple Podcasts, Podchaser, or wherever you find your podcasts, this will help the show's audience grow. Or you can just share the show with a friend. And don't forget to reach out via our Contact page. We're very interested in your opinion of the show, so please get in touch. You can support the show by making a monthly donation on the show's Patreon page at: https://www.patreon.com/TheDotNetCorePodcast. Music created by Mono Memory Music, licensed to RJJ Software for use in The Modern .NET Show

Deuteronomy 20 speaks of laws covering the behaviour of the Israelites in warfare. The priests were to stimulate the courage of the Israelites as they were about to enter into battle. If any man had married recently he would be allowed a year off before joining the army. Similarly anyone would be allowed to partake of their first fruits before enlisting for active army service. Yahweh would fight for His host; however if anyone in the nation was fearful, or doubted their Omnipotent Sovereign's ability to deliver His people then that person was to be sent home so as to not damage the morale of his comrades. For nations other than the seven Canaanitish nations terms of peace were to be offered and if accepted that nation would become a tributary nation. Should terms of peace be rejected then siege would be made, the males of that city would be destroyed and the spoil taken by the Israelites. As for the Canaanitish nations no quarter was to be shown to them, but they were to be totally destroyed. Israel was commanded that during the siege timber could be taken from any tree except fruit trees. Ecclesiastes 12 verses 1-8 instruct us to remember our Creator is the days of our youth. For, says the wise man, the time will come when every desire fails – this he terms the evil day. Those of us who are aging rapidly feel that day encroaching too rapidly. Verses 2 describe the aging process and the declining of the body in a series of graphic and frightening metaphors. Verse 2 speaks of the inability to distinguish light from night and as the bodily heat becomes lost to know what season the aging person is in. Verse 3 tells of the enfeebling of the arms and legs. The same verse tells of the decaying of the teeth and their falling out; and of failing eyesight. Verse 4 is describing the loss of interest in anything external to themselves and the failure to experience stimulation through music and other past delights. Verse 5 describes the anxiety that accompanies aging – everything is an insurmountable trouble. The aged person is resembling a crippled grasshopper dragging itself by its front legs. There is no longer pleasure in anything and the decrepit individual cannot wait for death to come. Verse 6 speaks of the instability of the spine; of the failure of the brain to function; and of the breakdown of the heart. Verse 7 speaks of the end – the body returns to the dust from which it came (Genesis 2:7; 3:17-19). And so, says Solomon, life as an end in itself is entirely meaningless. Verses 9-12 describe the Preacher's exertions to reach wise ways in which there will profit and as assurance of a future. Wise counsel will result in responding to the Almighty and walking in His ways. He will goad us and guide us in the paths of righteousness. God is the Great Shepherd whose Word is firm and His counsel unfailing. And so concludes the Assembler of wise sayings – Koheleth, or the Preacher – in verses 13-14 that the whole, complete, man is the one who reverences God and walks in the way of His commandments. Acts 11 commences with Peter being caused to justify why he baptised Gentiles. We next have a description of the progress of the truth in Antioch in the province of Syria, where believers were first derisively called ‘Christians'. One of these faithful believers is a prophet named Agabus. He prophesies of a great famine that would affect the entire Roman world. The disciples of Antioch start a fund to help Judean believers, who were greatly affected and in dire need. In Acts 12 Herod Antipas kills the Apostle James – the year was AD 44. Seeing how much this delighted the Jews Herod has Peter arrested for execution after Passover. Despite being securely chained between guards the angel of the Lord causes a deep sleep to overcome the guards and releases Peter. Peter proceeds to the house where the ecclesia is gathered to pray for his deliverance. A maid named Rhoda answers the door and runs to tell the disciples that Peter was outside. Rhoda is told that she must be mistaken. The disciples say that it must be Peter's “messenger” (Greek angelos- angel). Peter is admitted to the house and he recounts how he had been delivered. James, the half brother of Jesus. was informed and told Peter to secretly depart to a different location where he cannot be found. Herod kills the guards (verses 20-23). The chapter concludes with an account of Herod's narcissistic claims and his being smitten with dysentery by the angel of God and Herod dying verses 20-23. Nonetheless the Word of God exceedingly prevails.

Been anticipating this Guest mix with Heavy hitter False persona who is one of my favourite musicians atm, after recently releasing a new single with Mall Grab "Crazy" of Fragrance Recordings and playing at the Leeds Warehouse all earlier in February, and he doesn't disappoint with a hard mix in the second hour! ⚡️Like the Show? Click the [Repost] ↻ button so more people can hear it!

Kacper "prefetcher" Staroń created the PinkSea oekaki BBS on top of the AT Protocol. He also made the online multiplayer game MicroWorks with Noam "noam 2000" Rubin. He's currently studying Computer Science at the Lublin University of Technology. We discuss the appeal of oekaki BBSs, why and how PinkSea was created, web design of the early 2000s, flash animations, and building an application on top of the AT Protocol. Prefetcher Bluesky Github Personal site Microworks (Free multiplayer game) PinkSea and Harbor PinkSea PinkSea Bluesky Account PinkSea repository Harbor image proxy repository Harbor post from bnewbold.net imgproxy (Image proxy used by Bluesky) Early web design Web Design Museum Pixel Art in Web Design Kaliber10000 Eboy Assembler 2advanced epuls.pl (Polish social networking site) Wipeout 3 aesthetic Restorativland (Geocities archive) Flash sites and animations My Flash Archive (Run by prefetcher) dagobah Z0r Juicy Panic - Otarie IOSYS - Marisa Stole the Precious Thing Geocities style web hosts Neocities Nekoweb AT Protocol / Bluesky PDS Relay AppViews PLC directory Decentralized Identifier lexicon Jetstream XRPC ATProto scraping (List of custom PDS and did:web) Tools to view PDS data PDSls atp.tools ATProto browser Posters mentioned vertigris (Artist that promoted PinkSea) Mary (AT Protocol enthusiast) Brian Newbold (Bluesky employee) Oekaki drawing applets Tegaki chickenpaint Group drawing canvas Drawpile Aggie Other links Bringing Geocities back with Kyle Drake (Interview with creator of Neocities) firesky.tv (View all bluesky posts) ATFile (Use PDS as a file store) PinkSky (Instagram clone) front page (Hacker news clone) Smoke Signal (Meetup clone) -- Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today I am talking to Kacper Staroń.  He created an oekaki BBS called PinkSea built on top of the AT protocol, and he's currently studying computer science at the Lublin University of Technology. We are gonna discuss the appeal of oekaki BBS, the web design of the early 2000s, flash animations, and building an application on top of the AT protocol. Kacper, thanks for talking with me today. [00:00:16] Prefetcher: Hello. Thank you for having me on. I'm Kacper Staroń also probably you know me as Prefetcher online. And as Jeremy's mentioned, PinkSea is an oekaki drawing bulletin board. You log in with your Bluesky account and you can draw and post images. It's styled like a mid to late 2000s website to keep it in the spirit. What's an oekaki BBS? [00:00:43] Jeremy: For someone who isn't familiar with oekaki BBSs what is different about them as opposed to say, a photo sharing website? [00:00:53] Prefetcher: The difference is that a photo sharing website you have the image already premade be it a photo or a drawing made in a separate application. And you basically log in and you upload that image. For example on Instagram or pixiv for artists even Flickr. But in the case of an oekaki BBS the thing that sets it apart is that oekaki BBSes already have the drawing tools built in. You cannot upload an already pre-made image with there being some caveats. Some different oekaki boards allow you to upload your already pre-made work. But Pinksea restricts you to a tool called Tegaki. Tegaki being a drawing applet that was built for one of the other BBSes and all of the drawing tools are inside of it. So you draw from within PinkSea and you upload it to the atmosphere. Every image that's on PinkSea is basically drawn right on it by the artists. No one can technically upload any images from elsewhere. How PinkSea got started and grew [00:01:56] Jeremy: You released this to the world. How did people find it and how many people are using it? [00:02:02] Prefetcher: I'll actually begin with how I've made it 'cause it kind of ties into how PinkSea got semi-popular. One day I was just browsing through Bluesky somewhere in the late 2024s. I was really interested in the AT Protocol and while browsing, one of the artists that I follow vertigris posted a post basically saying they'd really want to see something a drawing canvas like Drawpile or Aggie on AT Protocol or something like an oekaki board. And considering that I was really looking forward to make something on the AT Protocol. I'm like, that sounds fun. I used to be a member of some oekaki boards. I don't draw well but it's an activity that I was thinking this sounds like a fun thing to do. I'm absolutely down for it. From like, the initial idea to what I'd say was the first time I was proud to let someone else use it. I think it was like two weeks. I was posting progress on Bluesky and people seemed eager to use it. That kept me motivated. And yeah. Right as I approached the finish I posted about it as a response to vertigris' posts and people seemed to like it. I sent the early version to a bunch of artists. I basically just made a post calling for them. Got really positive feedback, things to fix, and I released it. And thanks to vertigris the post went semi-viral. The launch I got a lot of people which I would also tie to the fact that it was right after one of the user waves that came to Bluesky from other platforms. The website also seemed really popular in Japan. I remember going to sleep, waking up the next day, and I saw like a Japanese post about PinkSea and it had 2000 reposts and 3000 likes and I was just unable to believe it. Within I think the first week we got like 1000 posts overall which to me is just insane. For a week straight I just kept looking at my phone and clicking, refresh, refresh, refresh, just seeing the new posts flow in. There was a bunch of like really insane talented artists just posting their works. And I just could not believe it. PinkSea got I'd say fairly popular as an alternative AppView. People seem to really want oekaki boards back and I saw people going, oh look, it's like one of those 2000s oekaki boards! Oh, that's so cool! I haven't seen them in forever! The art stands out because it's human made [00:04:58] Prefetcher: And it made me so happy every single time seeing it. It's been since November, like four months, give or take. And today alone we got five posts. That doesn't sound seem like a lot but given that every single post is hand drawn it's still insane. People go on there and spend their time to produce their own original artworks. [00:05:26] Jeremy: This is especially relevant now when you have so much image generation stuff and they're making images that look polished but you're kind of like well... did you draw it? [00:05:39] Prefetcher: Yeah. [00:05:40] Jeremy: And when you see people draw with these oekaki boards using the tools that are there I think there's something very human and very nostalgic about oh... This came from you. [00:05:53] Prefetcher: Honestly, yeah. To me seeing even beginner artists 'cause PinkSea has a lot of really, really talented and popular people (and) also beginner artists that do it as a hobby. Ones that haven't been drawing for a long time. And no matter what you look at you just get like that homely feeling that, oh, that's someone that just spent time. That's someone that just wanted to draw for fun. And at least to me, with generative AI like images it really lacks that human aspect to it. You generate an image, you go, oh, that's cool. And it just fades away. But in this case you see people that spent their time drawing it spent their own personal time. And no matter if it's a masterpiece or not it's still incredibly nice to see people just do it for fun. [00:06:54] Jeremy: Yeah. I think whether it's drawing or writing or anything now more than ever people wanna see something that you made yourself right? They wanna know that a human did this. [00:07:09] Prefetcher: Yeah. absolutely. [00:07:11] Jeremy: So it sounds like, in terms of getting the initial users and the ones that are there now, it really all came out of a single Bluesky posts that an existing artist (vertigris) noticed and boosted. And like you said, you were lucky enough to go viral and that carried you all the way to now and then it just keeps going from there, [00:07:36] Prefetcher: Basically if not for vertigris PinkSea (would) just not exist because I honestly did not think about it. My initial idea on making something on ATProto and maybe in the future I'll do something like that would be a platform like StumbleUpon -- Something that would just allow you to go on a website, press a button, and it gets uploaded to your repo and your friends would be able to see oh -- you visited that website and there would be an AppView that would just recommend you sites based on those categories. I really liked that idea and I was dead set on making it but then like I noticed that post (from vertigris) and I'm like, no, that's better. I really wanna make that. And yeah. So right here I want to give a massive shout out to vertigris 'cause they've been incredibly nice to me. They've even contributed the German translation of PinkSea which was just insane to me. And yeah, massive shout out to every single other artist that, Reposted it, liked it, used it because, it's all just snowballed from there and even recently I've had another wave of new users from the PinkSea account. So there are periods where it goes up and it like goes chill -- and then popular again. Old internet and flash [00:08:59] Jeremy: Yeah. And so something that you mentioned is that some people who came across it they mentioned how it was nostalgic or it looked like the old oekaki BBSs from the early internet. And I noticed that that was something that you posted on your own website that you have an interest in that specifically. I wonder what about that part of the internet interests you? [00:09:26] Prefetcher: That is a really good question. Like, to me, even before PinkSea my interests lie in the early internet. I run on Twitter and also on Bluesky now an account called My Flash Archive, which was an archive of very random, like flash animations. And I still do that just not as much anymore 'cause I have a lot of other things to do. I used to on Google just type in Flash and look through the oldest archived random folders just having flash videos. And I would just go over them save all of that or go on like the dagobah or Z0r or swfchan. 'cause the early internet to me, it was really like more explorative. 'cause like now you have, people just concentrated in those big platforms like Twitter, Instagram, Facebook, whatever. And back then at least to me you had more websites that you would just go on, you would find cool stuff. And the designs were like sometimes very minimal, aesthetically pleasing. I'd named here one of my favorite sites, Kaliber10000 which had just fantastic web design. Like, I, I also spend a lot of time on like the web design museum just like looking at old web design and just in awe. My flash archive on Twitter at least got very popular. I kind of abandoned that account, but I think it was sitting at 12,000 followers if not more? And showed that people also yearn for that early internet vibe. And to me it feels really warm. Really different from the internet nowadays. Even with the death of flash you don't really have interactive experiences like it anymore. 'cause flash was supposed to be replaced by HTML5 and JavaScript and whatever but you don't really make interactive experiences that just come packaged in a single file like flash. You need a website and everything. In flash, it just had a single file. It could be shared on multiple sites and just experienced. That kind of propelled my interest. Plus I, I dunno, I just really like the old internet design aesthetics it really warms me (and really close..?) Flash loops [00:12:01] Jeremy: The flash one specifically. Were they animations or games or was there a specific type of a flash project that spoke to you? [00:12:15] Prefetcher: Something we call loops. Basically, it's sometimes animations. 'cause, surprisingly while I like flash games they weren't my main collection. What spoke to me more were loops. Basically someone would take a song, find a gif they liked, and they would just pair it together. Something like YTMND did. At least from loops I found some of my favorite musical artists, some of my favorite songs, a lot of interesting series, be it anime or TV or whatever. And you basically saw people make stuff about their favorite series and they would just share it online. I would go over those. For example, a good website as an example is z0r.de, which is surprisingly still active and updated to this day. And you would see people making loops about members of that community or whatever they like. And you would for example see like 10 posts about the same thing. So you would know someone decided to make 10 loops and just upload them at once. And yeah, to me, loops basically were like, I mean, they weren't always the highest quality or the most unique thing, but you would see someone liked something enough that they decided to make something about it. And I always found that really cool. I would late at night just browse for loops and I'm like, oh, oh, this series, I remember it. I liked it (laughs)! But of course flash games as well. I mean, I used to play a lot when I was younger, but specifically loops, even animations and especially like when someone took like their time to animate something like really in depth. My favorite example is, the music video to a song by the band Juicy Panic called Otari. Someone liked that song enough that they made an entire flash animated music video, which was basically vectorized art of various series like Azumanga Daioh or Neon Genesis Evangelion as well, and other things. And it was so cool, at least to me, like a lot of these loops just basically have an intense, like immense feeling on me (laughs). I just really liked collecting them. [00:14:38] Jeremy: And in that last example, it sounded more like it was a complete music video, not just a brief loop? [00:14:45] Prefetcher: No, it was like a five minute long music video that someone else made. [00:14:48] Jeremy: Five. Oh my gosh. [00:14:49] Prefetcher: Yeah. You would really see people's creativity shine through on just making those weird things that not a lot of people have seen, but you look at it and it's like, wow. It's different than YouTube (Sharable single file, vectorized) [00:15:01] Jeremy: It's interesting because you can technically do and see a lot of these things on, say, YouTube today, but I think it does feel a little different for some reason. [00:15:16] Prefetcher: It really is. Of course I'm not denying on YouTube you see a lot of creative things and whatever. But first and foremost, the fact that Flash is scalable. You don't lose the quality. So be able to open, I don't know, any of the IOSYS flash music videos for like their Touhou songs and the thing would just scale and you would see like in 4K and it's like, wow. And yeah, the fact that on YouTube you have like a central place where you just like put something and it just stays there. Of course not counting reuploads, but with Flash you just had like this one animation file that you would just be able to share everywhere and I don't know, like the aspect of sharing, just like having those massive collections, you would see this flash right here on this website and on that website and also on this website. And also seeing people's personal collections of flash videos and jrandomly online and you would also see this file and this file that you haven't seen it -- it really gives it, it's like explorative to me and that's what I like. You put in the effort to like go over all those websites and you just like find new and new cool stuff. [00:16:32] Jeremy: Yeah, that's a good point too that I hadn't thought about. You can open these files and you have basically the primitives of how it was made and since, like you said, it's vector based, there's no, oh, can you please upload it in 1080 p or 4K? You can make it as big as you want. [00:16:53] Prefetcher: Yeah. Web design differences, pixel art, non-responsive [00:16:55] Jeremy: I think web design as well it was very distinct. Maybe because the tools just weren't there, so a lot of people were building things more from scratch rather than pulling a template or using a framework. A lot of people were just making the design theirs I think rather than putting words on a page and filling into some template. [00:17:21] Prefetcher: Honestly, you raise a good point here that I did not think much about. 'cause like nowadays we have all of this tooling to make web design easier and you have design languages and whatnot. And you see people make really, in my opinion, still pretty websites, very usable websites on top of that. But all of them have like the same vibes to them. All of them have like a unified design language and all of them look very similar. And you kind of lose that creativity that some people had. Of course, you still find pretty websites that were made from scratch. But you don't really get the same vibes that you did get like back then. Like my favorite, for example, trend that used to be back on like the old internet is pixel art in web design. For example, Kaliber10000, or going off the top of my head, you had the Eboy or all the sites and then Poland, for example, ... (polish website) those websites use minimal graphics, like pixel graphics and everything to build really interesting looking websites. They had their own very massive charm to them that, I don't know, I don't see a lot in more modern internet. And it's also because back then you were limited by screen size, so you didn't have to worry about someone being on a Mac with high DPI or on a 32x9 monitor like I am right now. And just having to scale it up. So you would see people go more for images, like UI elements, images instead of just like building everything from scratch and CSS and whatnot. So, yeah, internet design had to accommodate the change. So we couldn't stay how it was forever 'cause technology changed. Design language has changed, but to me it's really lost its charm. Every single website was different, specific, the web design had like this weird form, at least on websites where it was like. I like to call it futuristic minimalism. They looked very modern and also very minimal and sort of dated. And I dunno, I just really like it. I absolutely recommend checking, on the web design museum fantastic website. I love them and the pixel art in web design sub page. Like those websites to me they just look fantastic. [00:19:52] Jeremy: Yeah, and that's a good point you brought up about the screen sizes where now you have to make sure your website looks good on a phone, on a tablet, on any number of monitor sizes. Back then in the late 90s, early 2000s, I think most people were looking at these websites on their 4x3 small CRT monitors. [00:20:20] Prefetcher: My favorite this website is best viewed with an 800 by 600 monitor. It's like ... what? [00:20:28] Jeremy: Exactly. Even if you open your personal site now the design is very reminiscent of those times and it looks really cool but at the same time on a lot of monitors it's a small box in the middle of the monitor, so it's like -- [00:20:49] Prefetcher: I saw that issue, 'cause I was making it on a 1080p monitor and now I have a 32x9 monitor and it does not scale. I've been working on reworking that website, but, also on the topic of my website, I, I wanna shout out a website from the 2000s that still exists today. 'cause, my website was really inspired by a website called Assembler. And Assembler, from what I could gather, was like a net art or like internet design collective. And the website still works to this day. You still had like, all of their projects, including the website that my website was based off of. [00:21:28] Jeremy: Yeah, I mean there, there definitely was an aesthetic to that time. And it's probably, like you said, it's probably people seeing someone else's site in this case, what, what did you call it? Assem? Assembler? [00:21:42] Prefetcher: Assembler. [00:21:42] Jeremy: Yeah. You see someone else's website and then maybe you try to copy some of the design language or you look at the HTML and the CSS and I mean, really at the time, these websites weren't being made with a ton of JavaScript. There weren't the minifiers, so you really could view source and just pull whatever you wanted from there. [00:22:06] Prefetcher: We also had those design studios, design agencies, notably 2advanced which check in now, their website still works, and their website is still in the same aesthetic as it was those 20 so years ago just dictating this futuristic design style that people really like. 'cause a lot of people nowadays also really like this old futurism minimalism for example a lot of people still love the Wipeout 3 aesthetic that was designed by one of my favorite studios overall the designers republic. And yeah, it's just hard for me to explain, but it feels so soulful in a way. [00:22:53] Jeremy: I think there are some trade offs. There's what we were talking about earlier with the flexibility of screen size. But there used to be with a lot of websites that used Flash, there used to be these very elaborate intros where the site is loading and there's these really neat animations. But at the same time, it's sort of like, well, to actually get to the content, it's a bit much, but, everything is a trade off. [00:23:25] Prefetcher: People had flash at their disposal and they just wanted to make, I have the tooling, I'm going to use all of the tooling and all of it. [00:23:33] Jeremy: Yeah. Yeah. but yeah, I definitely get what you're saying where when I went to make my own website I made it very utilitarian and in some ways boring, right? I think we do kind of miss some of what we used to have. [00:23:54] Prefetcher: I mean, in my opinion, utilitarian websites are just as fine. Like in some cases you don't really need a lot of flashy things and a lot of very modern very CPU intensive or whatever animations. Sometimes it is better to go on a website and just like, see, oh, there's the play button and that's it. [00:24:17] Jeremy: Yeah. Well definitely the animations and the intro and all that stuff. I guess more in terms of the aesthetics or the designs. It's tricky because there's definitely people making very cool things now things that weren't even possible back then. But it does feel like maybe the default is I'll pick this existing style sheet or this existing framework and just go with that. [00:24:47] Prefetcher: A lot of modern websites just go for similar aesthetics, similar designs, which they aren't bad, but they are also very just bland. They, they are futuristic, they are very well designed. But when you see the same website. The same -- five websites have the same feel. And this is especially, at least in my opinion, visible with websites built on top of NextJS or other frameworks. And it just feels corporate kind of dead. Like someone just makes a website that they want to sell something to you and not for fun. [00:25:26] Jeremy: With landing pages especially it's like, wow, this looks the same as every other site, but I guess it must work. [00:25:38] Prefetcher: It works. And it really cuts down on development time. You don't need to think much about it. You just already have a lot of well-established design rules that you just follow and you get a cohesive and responsive design system. Designing the PinkSea look and feel [00:25:56] Jeremy: Let's talk about that in connection with PinkSea. What was your thinking when you designed how PinkSea would look and feel? [00:26:06] Prefetcher: Honestly, at first I have to admit I looked at other websites. I looked at Bluesky first and foremost. I looked at, front page. I looked at Smoke Signal, and I thought that I might also build something that's modern and sleek and I sketched it out in an application and I showed it to some friends. One of them suggested I go for more like a 2000 aesthetic. I'm like, yeah, okay. I like that. As the website was built, I just saw more and more of how much I feel this could sit with others. Especially with the fact that it's an oekaki page an oekaki BBS and as you scroll through oekaki has a very distinct style to it. And as you scroll and you see all of those, pixel shaded, all those dithered images, non anti-aliased pens and whatnot. It feels really really cohesive somehow with the design aesthetic. But of course, PinkSea in itself is a modern website. Like if you were to go to my PinkSea repository. It's a modern website built up on top of Vue3, which talks via like XRPC API calls in real time and it's a single page app and whatever. That's kind of the thing I merged the modern way of making sites with a very oldish design language. And I feel, in my opinion, it somehow just really works. And especially it sets PinkSea apart from the other websites. It gives it that really weird aesthetic. You would go on it and you would not be like, oh, this is a modern site that connects with a modern protocol on top of a big decentralized network. This is just someone's weird BBS stuck in the 2000s that they forgot to shut down. (laughs) [00:28:00] Jeremy: Yeah. And I think that's a good reminder too, that when people are intentional about design, the tools we have now are so much better than what we used to have. There's nothing stopping us from making websites that when people go to them they really feel like something's different. I know I did not just land on Instagram. [00:28:27] Prefetcher: Yeah. And making PinkSea taught me that it's really easy to fall into that full string of thought that every site has to look modern. Because I was like, oh yeah, this is a modern protocol, a modern everything, and it has to look the part. It has to look interesting to people and everything. And after talking with a bunch of friends and other people and just going, huh, that's maybe like the 2000s isn't as bad as I thought. And yeah, the website especially it's design people seem to just really like it. Me too. I, I just absolutely love how PinkSea turned out it is really a reminder that you don't need modernness in web design always. And people really appreciate quirky looking pages, so to say, quirky like interesting. [00:29:23] Jeremy: I interviewed the, the creator of Neocities which is like kind of a modern version of GeoCities and yeah, that's really what one of the aspects that I think makes things so interesting to people from that era is, is that it really felt like you're creating your own thing, and not just everything looks the same. The term I think he used is homesteading. You're taking care of your place and it can match your sensibilities, your style, your likes, rather than having to, like you said, try to force everything to be this, this sort of base modern, look. The old spirit of the internet is coming back [00:30:08] Prefetcher: I mean Neocities and by extension also Nekoweb are websites that I often when I don't have much to do -- I like just going through them because you see a bunch of people just make their own places. And you see that even in 2025 when we have those big social media sites. You have platforms where you can get a ton of followers. You can get a ton of attention and everything. People to some extent still want that aspect of self-expression. They want to be able to make something that's uniquely theirs and you see people just make just really amazing websites build insane things on those old Geocities-like platforms using nothing but a code editor. You see them basically just wanting thing to express, oh, that's mine and no one else has it. So to say that's why. Yeah. I feel like to some extent the old school train of thought when it comes to the internet is slowly coming back. Especially with the advent of protocols like ATProto. And you'll experience more websites that just allow people to make their own homes on the internet. Cause in my opinion, one of the biggest problems is that people do not really want to register on a lot of platforms. 'cause you already have this place where you get all of your followers, you have all of your connections, and then you want to move and then you'll lose all of your connections and everything. But with something like ATProto, you can use the social graph of, for example, Bluesky. I want to add followers on PinkSea. So for example, you have an artist that has like 30,000 followers for example, I can just click import my following from Bluesky. And just like that they would already get all of the artists that they follow on Bluesky already added as followers on PinkSea. And for example, someone else joins and they followed that big artist and they instantly followed them on PinkSea as well. I think that we are slowly coming back to the advent of people owning their place online. PinkSea and ATProto (PDS) [00:32:24] Jeremy: Yeah. So let's talk a little bit more about how PinkSea fits into ATProto. For people who aren't super familiar with ATProto, maybe you could talk about how it's split up. You've got the PDS, the relays, the AppView. What are those and how do those fit into what PinkSea is? [00:32:48] Prefetcher: My favorite analogy, ATProto is a massive network, and at least me, when I saw the initial graph I was just very confused. I absolutely did not know what I'm looking at. But let's start with the base building block, something that ATProto wouldn't exist with. And it's the PDS. Think of the PDS as like a filing cabinet. You have a bunch of folders in which you have files, so to say. So you have a filing cabinet with your ID, this is the DID part that sometimes shows up and scares people. It's what we call a decentralized identifier. Basically that identifier is not really tied to the PDS, it just exists somewhere. And the end goal is that every user controls their DID. So for example, if your PDS shuts down, you can always move to somewhere else. Still keep like, for example, that you are prefetcher.miku.place. But in that filing cabinet the PDS going back to it you have your own little zone, your own cabinets, and that has your identifier, it's uniquely yours. Every single application on the AT protocol creates data. They create data and they store the data in a structured format called a record. A record is basically just a bunch of data that explains what that thing is, be it a like, a post on Bluesky an oekaki on PinkSea and an upvote on front page, or even a pixel on place.blue. And all of those records are organized into folders in your cabinet. And that folder is named with something we call a collection id. So for example, a like is, if I remember correctly, it's app.bsky.feed.like, so you see that it belongs to Bluesky. The app.bsky part. it's a feed thing, and the same way, PinkSea, for example, the oekaki and PinkSea uses com.shinolabs.pinksea.oekaki with com.shinolabs being the the collective that I use as a, pen name, so to say. PinkSea being, well, PinkSea and oekaki just being the name. It's an oekaki. If you want to see that there are a lot of tools, for example, PDSls or atp.tools or ATProto browser, if you had to go into one of those and you would type in for example, prefetcher.miku.place, you would see all of your records, the things that, you've created on the AT protocol network. Relay [00:35:19] Prefetcher: So you have a PDS, you have your data, but for example, imagine you have a PDS that you made yourself, you hosted yourself. How will, for example, Bluesky know that you exist? 'cause it won't, it's just a server in the middle of nowhere. That's where we have a relay. A relay is an application that listens to every single server. So every time you create something or you delete something, or for example, you edit a post, you delete an oekaki. You create a new, like -- Your PDS, your filing cabinet generates a record of that. It generates an event, something we call a commit. So, anytime you do something, your PDS goes, Hey, I did that thing. And relays function as big servers that a PDS can connect to. And it's a massive shout box. The PDS goes, Hey, I made this. Then the relay aggregates all of those PDSs into one and creates a massive stream of every single event that's going on the network at once. That's also where the name firehose comes from. 'cause the, the end result, the stream is like a firehose. It just shoots a lot of data directly at anyone who can connect to it. And the thing that makes AT Protocol open and able to be built on is that anyone can just go, I want to connect to jetstream1.west.bluesky.network. They just make a connection to it and boom they just get everything that's happening. You can, for example, see that via firesky.tv. If you go to it, you would open it in your browser. Every single Bluesky post being made in real time right directly in your computer. So you have the PDSs that store data, you have the relay that aggregates every, like, builds a stream of every single event on the network. AppViews [00:37:26] Prefetcher: You just get records. You can't interact with it. You can see that someone made a new record with that name, but to a human, you won't really understand what a cid is or what property something else is. That's why you have what we call AppViews. An AppView, or in full an application view is an application that runs on the AT protocol network. It connects to the relay and it transforms the network into a state that it can be used by people. That's why it's called an application view. 'cause it's a, a specialized view into the whole network. So, for example, PinkSea connects, and then it goes, hey, I want to listen on every single thing that's happening to com.shinolabs.pinksea.oekaki, and it sees all of those, new records coming in and PinkSea understands, oh, I can turn it into this, and then I can take this thing, store it in the database, and then someone can connect with a PinkSea front end. And then it can like, transform those things, those records into something that the front end understands. And then the front end can just display, for example, the timeline, the same way Bluesky, for example -- Bluesky gets every single event, every single new file, new record coming in from the network. And it goes. Okay, so this will translate into one more like on this post. And this post is a reply to that post. So I should chain it together. Oh. And this is a new feed, so I should probably display it to the user if they ask for feeds. And it basically just gets a lot of those disjoint records and it makes sense of them all. The end user has a different API to the Bluesky AppView. And then they can get a more specialized view into Bluesky. PinkSea does not store the original images, the PDS does [00:39:26] Jeremy: And so in that example, the PDSs, they can be hosted by Bluesky the company, or they could be hosted by any person. And so PinkSea itself, when somebody posts a new oekaki, a new image, they're actually telling PinkSea to go create the image in the user's PDS, right? PinkSea is itself not the the source of truth I guess you could say. [00:40:00] Prefetcher: PinkSea in itself. I don't remember which Bluesky team member said it, but I like the analogy that AppViews are like Google. So in Google, when you search something, Google doesn't have those websites. Google just knows that this thing is on that website. In the same vein, PinkSea, when you create a new oekaki, you tell PinkSea, Hey, go to my PDS and create that record for me. And then the person owns the PDS. So for example, let's say that in a year, of course I won't do it, but hypothetically here, I just go rogue and I shut down PinkSea, I delete the database. You still own the things. So for example, if someone else would clone the PinkSea repository and go here, there's PinkSea 2. They can still use all of those images that were already on the network. So, AppViews in a way basically just work as a search engine for the network. PinkSea doesn't store anything. PinkSea just indexes that a user made a thing on that server. And here I can show you how to get to it somehow. Those images aren't stored by PinkSea, but instead, I know that the image itself is stored, for example, on pds.example.com, and of course to reduce the load, we have a proxy. PinkSea asks the proxy to go to pds.example.com and fetch the image, and then it just returns it to the user. [00:41:37] Jeremy: And so what it sounds like then is if someone were to create oekaki on their own PDS completely independently of Pink Sea the fact that they had created that image would be sent to one of the relays, and then PinkSea would receive an event that says oh, this person created a new image then at that point your index could see, oh, somebody created a new image and they didn't even have to go through the PinkSea website or call the PinkSea APIs. Is that right? Sharing PDS records with other applications [00:42:14] Prefetcher: Yep. That is exactly right. For example, someone could now go, Hey, I'm making my own PinkSea-like application. And then they would go, I want to be compatible with PinkSea. So I'm using the same record. Or what we call a lexicon, basically describe how records look like. I forgot to mention that, but every single record has an attached lexicon. And lexicons serve as a blueprint. So a lexicon specifies, oh, this has an image, this has a for example, the tags attached to it, a description of the image. Validate that the record is correct, that you don't get someone just making up random stuff. But yeah, someone could just go, Hey, I'm making another website. Let's call it GreenForest for example. And GreenForest is also an oekaki website, but it uses, for example, chickenpaint instead of tegaki but I want to be able to interoperate with PinkSea. so I'm also gonna use com.shinolabs.pinksea.oekaki the collection, the same record, the same lexicon. And for example, they have their own servers and the servers just create regular oekaki records. So for example, GreenForest gets a new user, they log in, create, draw their beautiful image, and then they click upload it. So GreenForest goes to that person's PDS and tells the PDS, Hey, I want to make a new. com.shinolabs.pinksea.oekaki record. The PDS goes okay, I've done it for you. Let me just inform the relay that I did so, relay gets the notification that someone made that new PinkSea oekaki record. And so the main PinkSea instance, pinksea.art, which is listening in on the relay, gets a notification from the relay going, Hey, there is this new oekaki record. And PinkSea goes, sure, I'll index it. And so PinkSea just gets that GreenForest image directly in itself. And in the same vein, someone at PinkSea could draw something in tegaki -- their own beautiful character. And the same thing would happen with GreenForest. GreenForest would get that PinkSea image, that PinkSea record, and index it locally. So the two platforms, despite being completely different, doing completely different things, they would still be able to share images with each other. Bluesky PDS stores other AppView's data but they could stop at anytime [00:44:38] Jeremy: And these images, since they're stored in the PDS, what that would mean is that anybody building an application on ATProto, they can basically use Bluesky's PDS or the user's PDS as their storage. They could put any number of images in there and they could get into gigabytes of images. And that's the responsibility of the PDS and not yourself to keep track of. [00:45:12] Prefetcher: Yes, that can be the case. Of course, there is a hard limit on how big a single upload can be, which is, if I remember correctly, I don't wanna lie, I think it's 50 megabytes, I don't recall there being a hard cap on how big a single repository can be. I know of some people whose repositories are in the single gigabyte digits but this kind of is a thing scares app developers. 'cause you never know when Bluesky the company -- 'cause most people registering, are registering on Bluesky. We don't really know whether Bluesky, the company will want to keep it for free. Forever allow us to do something like that. You already have projects like, for example, ATFile, which just allow you to upload any arbitrary data just to store it, on their servers and they are paying for you. So we'll never know whether Bluesky will decide, okay, our services are only for Bluesky if you want to use PinkSea you have to deal with it. Or whether they go, okay, if you want to use alternative AppViews you have to pay us in order to host them. So, that also leads me to the fact that decentralization is an important part of AT protocol as Bluesky themselves say that they are a potential adversary. You cannot trust them in the long term. Right now they are benign right now, they're very nice, but, we never know how Bluesky will end up in a year or two. So if you want to be in the full control of your data, you need to sadly host it by yourself. And it's honestly really easy in order to do so. There is a ton of really useful online content blogs and whatever. I think I've set up my PDS in 10 minutes on a break between classes and university. But to a person that's non-technical that doesn't know much I'd say around an hour to two hours The liability and potential abuse from running a PDS [00:47:14] Jeremy: Yeah, I think the scary thing for a lot of people is technical or not, is even if it's easy to set up, you gotta make sure it keeps running. You gotta have backups. And so it could be a lot. [00:47:30] Prefetcher: Yeah. This is to be expected by the fact that you're in control of your data. Keeping it secure the same way, for your personal photos or your documents, for example, your master's diploma or whatever. And it's on you to keep your Bluesky interaction secure. On one hand, it's easier to get someone to do it, and I expect in the future we'll get people that are hosting public PDSes I sometimes thought of doing that for PinkSea, just like allowing people to register by PinkSea. But, doing so as a person, you also have to be constantly on call for abuse. So if someone decides to register via PinkSea and do some illicit activities, you are solely responsible for it. PDS and AppView moderation liability [00:48:17] Jeremy: So if they were to upload content that's illegal, for example, it's hosted on your servers so then it's your problem. [00:48:27] Prefetcher: Yeah, it is my problem. [00:48:29] Jeremy: At least the way that it works now, the majority of the people, their PDS is gonna be hosted by Bluesky. So if they upload content that's breaks the law, then that's the Bluesky company's problem at least currently. [00:48:44] Prefetcher: Yeah. That is something that Bluesky has to deal with. But I do believe that in the future we are going to have, more like independent entities just building infrastructure for ATProto, not even the relay it's just like PDSs for people to be able to join the atmosphere, but not directly via Bluesky. [00:49:06] Jeremy: I'm kind of curious also with the current PDSs, if it's hosted by Bluesky, are they, are they moderating what people upload to their PDSs? [00:49:16] Prefetcher: Good question. Honestly, I don't think they're moderating everything 'cause, it's infeasible for them to, for example, other than moderate Bluesky to also moderate PinkSea and moderate front page and whatnot. So it's the obvious responsibility to moderate itself and to report abuse. I'd say that if someone started uploading illicit material, I do not think, and this is not legal advice, I do not think that they would catch on until some point let's say. [00:49:52] Jeremy: I mean, from what you were describing too, it seems like the AppViews would also, have issues with this because if, let's say someone created a PinkSea record in their PDS directly and the image they put in was not an oekaki image, it's instead something pretty illegal in the country that your AppView is hosted then, Wouldn't that go straight to the PinkSea users viewing the website? [00:50:20] Prefetcher: Yes, sadly, this is something that you have to sign up as you're making an AppView and especially one with images. Sooner or later you are going to get material that you have to moderate and it's entirely on you. That's why, you have to think of moderation while you're working on an AppView. Bluesky has an insanely complicated, at least in my opinion, moderation system, which is composable and everything, which I like. But for smaller AppViews, I think it's too much to build the same level of tooling. So you have to rely more on manual work. Thankfully so far the user base on PinkSea has been nothing but stellar. I didn't have to deal with any law breaking stuff, but I am absolutely ready for one day where I'll have to sadly make some drastic moderation issues. [00:51:18] Jeremy: Yeah. I think to me that's the most terrifying thing about making any application that's open to user content. [00:51:29] Prefetcher: I get it, sadly. I'm no stranger to having issues with people, abusing my websites. Because since 2016, my, first major project was a text board based off of, a text board in a video game called DANGER/U/. It was semi-popular, during the biggest spike in activity in like 2017 and 2016, it had in the tens of thousands of monthly visitors. And sadly, yeah, even though it was only text, I've had to deal with a lot of annoying issues. So to say the worst I think was I remember waking up and people are telling me that DANGER/U/ is down. So I log in the activity logs and someone hit me with two terabytes of traffic in a day. There was a really dedicated person that just hated my website and just either spam me with posts or just with traffic. So, yeah, sadly I have experience with that. I know what to expect that's something that you sadly have to sign up for making a website that allows user content. Pinksea is a single server [00:52:42] Jeremy: To my understanding so far, PinkSea is just a single server. Is that right? [00:52:47] Prefetcher: It is a single server. Yeah. [00:52:48] Jeremy: That's kind of interesting in that, I think a lot of people when they make a project, they worry about scaling and things like that. But, was it a case where you just had a existing VPS and you're like, well hopefully this is, this is good enough? [00:53:03] Prefetcher: I actually ordered a new one even though it's not really powerful, but my train of thought was that I didn't expect it to blow up. I didn't expect it to require more than a single VPS with 8 gigabytes of RAM and whatnot. And so far it's handling it pretty well. I do not expect ever to reach the amounts of traffic that Bluesky does, so I do not really have to worry about insane scalability and whatever. But yeah. I thought of it always as a toy project until the day I released it and realized that it's a bit more than a toy project at this point. To this day, I just kind of think that that website even if it were popular, I would never expect it to have -- And in the best, most amazing case scenario, like a hundred posts a day. I do not have to deal with the amount of traffic that Bluesky does. So one VPS it is. [00:53:59] Jeremy: Yeah, that makes a lot of sense. I mean the application is also mostly reads, right? Most people are coming to see the posts and like you said, you get a few submissions a day, but all the read stuff can probably be cached. Harbor image proxy [00:54:15] Prefetcher: Yeah. The heaviest, thing that PinkSea requires is the image proxy harbor, and that's something that right now only runs on that server. It's in Luxembourg. I think that's where my coprovider hosts it but yeah, that gets the most reads. 'cause in most cases, PinkSea, all it does, all you get is reads from a database, which is just, it's a solved problem. It's really lightweight. But with something like image proxying, you have this whole new problem. 'cause it's a lot of data, and you somehow have to send it -- it's enough for me to just host it locally on that PinkSea server and just direct people to it. But sooner or later, I can always just put it behind something like Bunny CDN or whatnot to have it be worldwide. [00:55:09] Jeremy: So Harbor is something I think you added recently. How did the images work before and what is Harbor doing in its place? [00:55:18] Prefetcher: Before I did what a lot of us currently do and I just freeload atop of Bluesky CDN 'cause Bluesky CDN is just open so far. But it's something that personally irked me. 'cause, I want PinkSea to be completely independent of Bluesky Corporation. I, I wanted to persevere even if Bluesky just decides to randomly, for example, close, the CDN to others or the relay to others or the PLC directory in the worst case scenario. So I wanted to make my own CDN more like proxy. You can't really call it a CDN because it's not worldwide. It's just a single server but let's just say image proxy. So Harbor whenever a person goes to PinkSea, they start loading in all of the images and every single image instead of going to, for example, the PDS or to cdn.bluesky.app. They go to harbor.pinksea.art, you get attached the identifier of the user and what we call a content identifier. Every single, thing uploaded to a PDS has an attached content identifier, which identifies it in a secure way so to say. So Harbor does in reality a really simple set of things. First and foremost, if the user has not seen it, like, not loaded it before first Harbor asks the local cache, do I have this file? If they do, if Harbor does, it just sends the file and it tells the browser, Hey, by the way, please don't ask me about this file for the next day. And in most cases, after one refresh, the user, all of the images load instantly because the web browser just goes, of those files were already sent. And Harbor asked me not to like, ask it more about the same file. So in the case of the image isn't in harbor's local cache, Harbor, first does a lot of those steps to resolve, the users identifier through their PDS, basically resolving that identifier, the DID to a DID document, which is a document basically explaining how that user, what is their, alias, what is their handle and where can we find them, which PDS. So we find the PDS and we then ask the PDS, Hey, send us this file for this user. The PDS sends it or doesn't, in which case we just throw an error and, Harbor just saves it locally and it sends it to the client. It basically just that. But to my knowledge, it's the first non Bluesky image proxy that's deployed for any AppView. Which also caught the attention of Brian Newbold one of the Bluesky employees and made me really happy. DID PLC Lookup [00:58:14] Jeremy: The lookup when you have the user's, DID and you wanna find out where their PDS is that's talking to something called, I think it's the PLC directory? [00:58:25] Prefetcher: Actually there are two different ways. First is PLC directory, PLC originally standed for a placeholder, and then Bluesky realized that it's not a placeholder anymore, and they stealthily changed it to public ledger of credentials. So we have PLC and we have web, the most common version is PLC. The document, the DID document is stored on Bluesky controlled servers under the moniker of PLC directory. They expose a web API that basically just allows you to say, Hey, give me the document for did:plc, whatever. And, the directory goes, have it. And this is the less decentralized version. You can host your own PLC directory and you can basically ask (their) PLC directory to just send you every single document and just you can have your local copy, which some people already do, you kind of sacrifice the fact that you are not in control of the document. It's still on a centralized server, even if you control the keys. 'cause every single DID document also has a key. And that key is used to sign changes to the document. So technically, if you define your own set of keys, you can prevent anyone else from modifying your document, even Bluesky. 'cause every single document is verifiable back and forth. You can see the previous document and its key is used to sign the next document and the chain of trust is visible and no one can just make random changes to your identity, but yeah, it's still on Bluesky to control service and it's a point of contention. Bluesky eventually wants to move it to a nonprofit standards organization, but we have yet to see anything come out of it, sadly. DID WEB lookup The next method is web. And web instead of -- 'cause in did:plc, you have did:plc, and a random string of characters. [01:00:30] Prefetcher: Web relies on domains. So for example, the domain would already like be the sole authority of where the file is. So for example, if I had did:web:example.com, I would parse the DID and I would see it's hosted at example.com. So I go to example.com, I go to /.wellknown/did.json which is the well-known location for the file. And I would have the same DID document as I would have if I used, for example, a PLC DID resolved via the PLC directory. the web method, you are in control of the document entirely. It's on your server under your domain. While it's the more decentralized version, it's just kind of hard for non-technical people to make them. 'cause it relies on a bunch of things. And also the problem is that if you lose your domain, you also lose your identity. [01:01:23] Jeremy: Yeah. So unlike the PLC where it's not really tied to a specific domain, you can change domains. With the web way, you have to always keep the same domain 'cause it's a part of the DID and yeah, like you said, you can't let your renewal lapse or your credit card not work. 'cause then you just lose everything. [01:01:49] Prefetcher: Yeah. You would still be able to change handles, but you would be tied for that domain to forever send your DID otherwise you would just lose it forever. [01:01:57] Jeremy: Yeah, I had mostly only seen the PLC and I wasn't too familiar with the web, form of identification, but yeah that makes sense. [01:02:06] Prefetcher: I think the web if I remember correctly, there is slightly over 300 accounts total on the entire network that use it. Mary who is a person on Bluesky that does a lot of like, ATProto related things, has a GitHub repository that basically gives insight into the network. And on her GitHub repository, you can find the list of every single custom PDS and also how many DID webs there are in existence. And I think it was slightly over 300. [01:02:38] Jeremy: So are you on that list? [01:02:40] Prefetcher: My PDS Yeah. If you were to scroll down. I don't use a web DID 'cause I registered my account before when I was brand new to ATProto, so I didn't know anything. But if you had to scroll down, you would see pds.ata.moe, which is my custom PDS just running. [01:02:55] Jeremy: Cool. [01:02:57] Prefetcher: Yeah. Harbor image proxy can cache any image blob [01:02:58] Jeremy: So something I noticed about harbor, you take the, I believe you take the DID and then you take the CID, the content identifier. I noticed if you take any of those pairs from the ATProto network, like I go find a image somebody posted on Bluesky, I pass that post DID and CID for the image into harbor. Harbor downloads it and caches it. So it's like, does that mean anybody could technically use you as a ATProto CDN? [01:03:38] Prefetcher: Yes, the same way anyone could use like the Bluesky CDN to for example, run PinkSea like I did. cause I do not know if there is a good way to check if a CID of an image or a blob basically. 'cause files on ATProto are called blobs. I do not think there is a nice way to check if that blob is directly tied to a specific record. But that also allows you to make cool, interesting things. Crossposting to Bluesky talks directly to the PDS [01:04:06] Prefetcher: 'cause for example, PinkSea has that, cross post to Bluesky thing. So when you create an image, You already have an option to cross post it to Bluesky, which a lot of people liked. And it was a suggestion from one of the early users of PinkSea. And the way it works is that when we create a PinkSea record, we upload that image, right? And then PinkSea goes, okay, I'm gonna use that same image, the same content identifier, and just create a Bluesky post. So Bluesky and PinkSea all share the same image. I don't upload it twice, I just upload it once. use it in PinkSea and I also use it in Bluesky. And the same way Bluesky its CDN, can just fetch the image. I can also fetch the image from mine, 'cause blobs aren't tied to specific records. They just exist outside of that realm. And you could just query anything. Not even images. You could probably query a video or even a text file. [01:05:04] Jeremy: So when you cross post to Bluesky, you're creating a record directly in the person's PDS, not going through bluesky's API. [01:05:14] Prefetcher: No, I sidestep Bluesky's API completely. And, I basically directly talk to the PDS at all times. I just tell them, Hey, please, for me, create a app.bsky.feed.post record. And you have the image, the text, which also required me to manually parse text into rich text. 'cause like, Bluesky doesn't automatically detect for example, links or tags And you basically get -- like PinkSea creates a record directly with the link to the image. And all of those tags, like the PinkSea tag and whatever, And I completely sidestep. Bluesky's API. If Bluesky, the AppView would cease to exist, PinkSea would still happily create Bluesky crossposts for you. Other applications put metadata into Bluesky posts so they can treat them differently [01:06:02] Jeremy: And since you're creating the records yourself, then you can include additional metadata or fields where you know that this was a PinkSea post, or originally came from PinkSea. [01:06:13] Prefetcher: I could do that. I don't really do that right now 'cause I don't really have much of a reason other than adding a PinkSea hashtag to every single oekaki. But I, noticed, for example, I think it was PinkSky, interesting name, PinkSky, which is like (a) Bluesky Instagram client. Any single time you make a post via PinkSky it uses the Bluesky APIs. It's Bluesky, but it attaches a hidden hashtag like PinkSky underscore some random letters. In its feed building algorithm, it basically detects posts with that hashtag, that specific hashtag, and it builds a PinkSky only timeline. 'cause it's still a Bluesky post, but it has hidden additional metadata that identifies, Hey, it came from PinkSky. [01:07:02] Jeremy: It's pretty interesting how much control you have over what to put in the PDS. So, I'm sure there's a lot of interesting use cases that people are gonna come up with. [01:07:14] Prefetcher: Yeah, of course. You still lose some of the data when you go through the Bluesky API. 'cause of course it stores the record and it's all in formats and whatnot. But you can attach a lot of metadata that can identify posts and build micro networks within Bluesky itself. I see it like that. Bluesky CDN compression [01:07:37] Jeremy: And I think, this might have been a post from you. I think I saw somebody saying that when you view an image from the CDN that the Bluesky CDN specifically, there's some kind of compression going on that that messes with certain types of art. [01:07:55] Prefetcher: It's especially noticeable artists are complaining about it all the time, left and right. Bluesky is very happy with jpeg compression, by default, their CDN, -- like to every single image it applies a really not good amount of jpeg compression which is especially not small. If you compare an image that's uploaded via PinkSea, view an image on PinkSea, and view the same image, which is, it's the same content id. It's the same blob. And you view it on Bluesky, it loses so much fidelity, it loses so much of that aliasing on the pen. You just see everything become really blurry. And on top of that, when you upload an image via Bluesky itself, if I remember correctly, I don't wanna lie here, but they also downscale the image to 1024 pixels by default. So every single image, not only big ones, and artists usually work with really big canvases, they get, downscaled and also additionally they get jpegified. So for example, PinkSea directly uploads PNG files to the PDS. And for example, Harbor gives back the original file. It does no transformations on it, but Bluesky transforms all of them into JPEG compressed images and for photos, it's fine sometimes. 'cause I've also seen people just compare directly, downloaded images of the PDS versus images viewed on Bluesky. But for art it's especially noticible. And people really (do) not like that. [01:09:31] Jeremy: Yeah, that's kind of odd. 'cause if, if I understand correctly, then if you post directly to your PDS and Bluesky pulls it in you'll avoid that, that 1024 resizing. So your images will be higher quality? [01:09:47] Prefetcher: I actually do not know. That's an interesting question. Cause I know that the maybe their CDN also does that 'cause that's what I've heard from others, that on upload the image gets processed and squashed down. So I don't know if doing it via an alternative AppView would change it or would Bluesky just directly reject this post? Because for example, PinkSea, I have built-in which I think I might change in the future -- PinkSea will reject your post if it's bigger than 800x800. 'cause then it'll notice that something is off. This could not have been made with PinkSea. [01:10:26] Jeremy: Yeah, that's a good point I suppose we know at the very least, they have some third party and internal moderation tools that they feed the images through to, so they, they can do some automatic content tagging. But yeah, I, I don't know, like you said, whether, the resizing and all that stuff is at the CDN level [01:10:50] Prefetcher: The jpegification is definitely at the CDN level. 'cause, Bluesky is actually running an open source image proxy. It's called imgproxy. Brian Newbold talked about it a bit on that harbor post. And, yeah, so a lot of the compression, the end user things are done via image proxy, but that, downscaling, I don't know, you'd have to ask someone who's a bit more intimate with Bluesky's internals. [01:11:19] Jeremy: Cool. yeah, I think we've, we've covered a lot. Is there, is there anything else, you wanted to mention or thought we should have talked about? [01:11:26] Prefetcher: Regarding PinkSea I think I've mentioned a ton both the behind the scenes things and, the user things, the design principles. What I'd want to absolutely say, and it will sound cheesy, and, is that I'm eternally grateful to anyone who's actually visited PinkSea. It's definitely grown outta all of my like dreams for the platform, to the point where I'm sitting here just talking about it. I definitely hope that the future will bring us more applications (in) ATProto. I definitely have ideas on how to expand PinkSea, a lot of ideas, a lot of things I want to do, and I'm also a very busy person, so I never get around them. But yeah, think that's it, at least regarding PinkSea. [01:12:15] Jeremy: Cool. Well, if people want to check out PinkSea or see what you're up to, where can they find you? [01:12:22] Prefetcher: So PinkSea is at pinksea.art. That's the website and Bluesky Handle is at pinksea.art and me, well, search prefetcher on Bluesky, you'll probably find me. My tag is at prefetcher.miku.place. all of my socials are probably there. I'm Prefetcher pretty much every single platform except for the platforms that already had someone called Prefetcher. GitHub, github.com/purifetchi because Prefetcher was taken. And, yeah, hit me up. I'm always eager to talk. I don't bite. [01:13:00] Jeremy: Very cool. Well, Kacper thanks. Thanks for taking the time. This was fun. [01:13:04] Prefetcher: Thank you so much, Jeremy, for having me over. It was a pleasure.

Bonjour à tous!

durée : 01:04:56 - Les Nuits de France Culture - par : Albane Penaranda, Mathias Le Gargasson, Antoine Dhulster - À Amiens, Edward Bond participe à un atelier de théâtre avec des lycéens. C'est l'occasion pour lui de dire combien il apprécie la simplicité mais aussi l'intelligence, l'intuition et surtout la liberté des jeunes qui contrastent avec notre emprisonnement face aux problèmes du monde. - réalisation : Massimo Bellini - invités : Edward Bond Dramaturge et metteur en scène britannique; Jérôme Hankins Maître de conférences en Études théâtrales à L'université de Picardie Jules Verne (Amiens), traducteur, directeur artistique de l'Outil compagnie (dans la Somme).; Bruno Tackels Essayiste et dramaturge. Agrégé et docteur en philosophie, ancien enseignant d'esthétique et d'histoire du théâtre contemporain.

Heute tauchen wir tief in die Transformation von Kernsystemen in der Versicherungsbranche ein. Unsere Gastgeber begrüßen Thorsten Vogel, Partner bei BearingPoint, der uns spannende Einblicke in die Herausforderungen und Erfolge von Modernisierungsprojekten gibt. Wir diskutieren die Notwendigkeit, ältere Systeme schnell zu ersetzen, den Einfluss von Compliance-Problemen und die Bedeutung wettbewerbsfähiger IT-Landschaften. Zudem erfahren wir, wie Standardsoftware und maßgeschneiderte Lösungen die Prozessoptimierung vorantreiben können. Freut Euch auf interessante Ergebnisse aus einer umfassenden Studie mit rund 250 Kernsystem-Implementierungen und nützliche Tipps für eine erfolgreiche Transformation.Schreibt uns gerne eine Nachricht!Folge uns auf unserer LinkedIn Unternehmensseite für weitere spannende Updates.Unsere Website: https://www.insurancemondaypodcast.de/Du möchtest Gast beim Insurance Monday Podcast sein? Schreibe uns unter info@insurancemondaypodcast.de und wir melden uns umgehend bei Dir.Vielen Dank, dass Du unseren Podcast hörst!

About Bill Hinshaw and Cobol Cowboys: Experienced Founder and CEO with a demonstrated history of working in the information technology industry. Proven expertise in systems architect, development, integration and support of mainframe software for banking and state government. Experienced in starting companies for software design, development, support and deliverables. Highly skilled in COBOL, CICS, DB2, VSAM, MQ, Assembler and related mainframe and server products. Expert witness in matters related to systems integration vs. database interfaces. Testified at State of New Jersey Senate Hearings on Unemployment Claims. AI advisory role for debugging & documenting COBOL programs. Strong business professional — attended Indiana University-Purdue University at Indianapolis, Indiana. Appointed Director of Data Processing by Governor of Indiana to implement mainframe computer services. Founded and headquartered in North Texas, Cobol Cowboys provides professionals for legacy COBOL systems and other programming environments. Our name, Cobol Cowboys, was inspired by the movie “Space Cowboys” in which experienced (some retired) astronauts were called back into service to solve a current day problem in outer space. After researching many published articles (both positive and negative) on the future life of COBOL, we came away with renewed confidence in its continued life in the coming years. Since COBOL is still the programming foundation and under-structure used today in most USA and International companies, we founded Cobol Cowboys in North Texas to provide professionals for legacy COBOL Systems and non-COBOL systems. This renewed confidence in COBOL is supported by IBM's strategies to keep COBOL robust and evergreen as a viable programming language today and years to come. These strategies are evidenced by IBM's continued enhancements which allow COBOL and Java to run together on mainframes and to take advantage of the latest industry-driven database products (such as DB2 and SQL). Furthermore, COBOL has been enhanced to develop “object oriented” code in addition to its time-proven legacy code still in use today. These and other programming enhancements offered by IBM keep COBOL a state-of-the-art programming solution. We offer experienced COBOL (and other software) professionals in various vertical markets; including banking, government, insurance, health care, manufacturing, warehousing, transportation and others.

Before founding DH Property Holdings, Dov was the Executive Vice President of Acquisitions of Asset Management at Extell Development Company. During his 13+ years at Extell, Dov negotiated and supervised the acquisitions of over $20 billion of New York real estate. Dov was directly responsible for sourcing some of the most notable transactions over the last 10 years, including The Ring Portfolio, One 57, Nordstrom Tower, and One Manhattan Square. We discuss: Stories from Dov's career assembling iconic NYC sites Pivoting to Class B Industrial How to Negotiate in RE We'd appreciate you filling out our audience survey, so we can continuously work on providing relevant content to our listeners.  https://www.thefortpod.com/survey Topics (00:00:00) - Intro (00:01:56) - Dov's early career  (00:05:02) - Land assemblage and zoning in NYC (00:13:12) - Tenant risks (00:16:06) - Assembling Central Park Tower site (00:27:21) - Assembling 1 Manhattan Square site (00:32:45) - The Ring portfolio (00:48:19) - Hiring Japanese actors to finalize a deal (00:56:42) - Venturing into Class B Industrial (01:13:58) - How would outsiders perform in NYC trying to assemble land? (01:15:00) - The power of negotiation Links DH Property Holdings More on Dov Hertz Dov in The Real Deal Dov in Crain's New York Business Dov's Real Estate Investment Blog Support our Sponsors Relay Human Cloud: https://bit.ly/3sjQcaY Fort: https://bit.ly/FortCompanies Follow Fort on LinkedIn: https://www.linkedin.com/company/fort-companies/ Chris on Social Media: X: https://bit.ly/3BYIjcH LinkedIn: https://bit.ly/45gIkFd   Watch The Fort on YouTube: https://bit.ly/3oynxNX Visit our website: https://bit.ly/43SOvys Leave a review on Apple: https://bit.ly/45crFD0 Leave a review on Spotify: https://bit.ly/3Krl9jO  The FORT is produced by Johnny Podcasts

"Bboy Techno with Davy Wreck aims to create a captivating energizing sonic journey, fusing diverse electronic genres to make bodies move and spirits groove. Each episode will showcase my genre-bending sound of Dance Music, drawing inspiration from my rich background in Breakdancing, Producing, & Design. " Tracklist "Mizzo - Bringing 88 back Sofie superflying jackson - Doshys boomin kotti vibes Sellrude - That's movement Data theft - Data loss RHR - Na capture DAWL - System check Parasit - Elektrotechnik Yarnit - Ibs Davy Wreck - Shoot for the stars (unreleased) Dj naughty - Your Man (Dj Swisha bootleg) Assembler code - Architects XO-5 - Technologic Davy Wreck - Million dollar break DJ Godfather - Decifer the code K_Schreiber - Zanzibar Davy Wreck - Rave at 8 Club cab - Space case Sketchy - Hit em with the low cut"

Welcome back Kacey and welcome in Matt. Matt served in the Navy. So naturally we have lot of questions about the food he ate and the best part about being in the Navy. We also ask him what his reaction was when he found out when he was deploying and to where he was deploying. Then he talks to us about his journey on his road to hope. 

Ein Leitspruch für die Frontend-Welt: Make simple things simple and complex things possibleDie Frontend-Entwicklung hat in den letzten Jahren einen ziemlich großen Wandel erlebt. Es fing alles ganz simpel an: CSS und JavaScript wurden einfach via script-tag inkludiert. Danach kamen Performance-Optimierung durch Minification, mehr JavaScript- und CSS Features (zB Browser-APIs) wurden in die Browser implementiert und die Standards kamen nicht hinterher, doch wir Entwickler*innen wollten wir diese schon in Produktion nutzen (aka Polyfills und Transpilieren). Und auch die Web-Apps wurden immer mehr “Desktop-Like”, was einen Effekt auf die Frontends von heute hat, zB. React, Vue und Co. Und wo sind wir heute? Frameworks wie HTMX, die mit Einfachheit werben, erleben einen neuen Hype.Doch ist das alles neu oder nur “alter Wein in neuen Schläuchen”? Erkaufen wir uns durch diesen großen Tooling-Stack wirklich Einfachheit oder schließen wir uns durch die Komplexität doch nicht in eine "proprietäre API” ein, die es sehr schwer macht, das Framework zu wechseln? Und zu guter letzt: Ist die Komplexität gerechtfertigt?Zu diesem Thema sprechen wir mit Golo Roden. Golo ist Frontend-Experte und spezialisiert auf native Webtechnologien. Mit ihm behandeln wir Themen wie die Probleme von aktuellen UI-Frameworks und woher diese Probleme eigentlich kommen, wie er zu einfacheren Konzepten wie HTMX steht, über mögliche Lösungsansätze für die Probleme, Standards wie Web Components und welche Rolle TypeScript in dem ganzen Mix einnimmt.Bonus: Warum Monkey Island das richtige Spiel für dich und deine Kinder ist.**** Diese Episode wird von der HANDELSBLATT MEDIA GROUP gesponsert.Wirtschaft ist nicht immer einfach. Deswegen lautet die Mission der HANDELSBLATT MEDIA GROUP: „Wir möchten Menschen befähigen, die Wirtschaft zu verstehen.“ Mit ihren Kernprodukten, dem Handelsblatt und der WirtschaftsWoche, sowie 160.000 Abonnements, 15 Millionen Besuchern und 3 Milliarden Anfragen in einem Monat leisten sie einen wichtigen Beitrag zur Orientierung und Meinungsbildung in den Bereichen Wirtschaft und Politik und machen damit einen ausgezeichneten Job.Wenn du Teil dieser Mission sein möchtest, schau auf https://engineeringkiosk.dev/handelsblatt vorbei und werde ein Teil der HANDELSBLATT MEDIA GROUP.********Das schnelle Feedback zur Episode:

"...Happy birthday dear ThursdAIiiiiiiii, happy birthday to youuuuuu

 If we understand Mozart then we can get a broader understanding of the divine. And we skip the morality about sexuality and profanity. Mozart was such rascal and genius to the same time.Mozart was obsessed with sex and cracked, dirty, profane jokes, without even thinking of the consequences of his bad behavior…Even he did openly sex in public toilets… There is no ending of his misconducts...  With 4 years he started to compose, with 7 years he had composed already a complete concert…Mozart composed also dirty songs, for instance: Leck mir den Arsch Fein recht schön saber. (I refuse to translate)Can you do such thing?And he never had corrected any note that he composed.Mozart could write entire concerts out of his mind, without correcting anything.Amadeus Mozart was a channel of the Lord…How does such thing work out…?If we are totally relaxed and open mind, only then the Lord can choose us as a channel.What I described in a previous blog, within an instance of a second, I got so deep insights and great solution when I was under the shower.I had designed the hardware for the satellite navigation system already and the software was missing and I was running out of time… Within 3/2 hours I wrote down the complete program in Assembler (microprocessor language) just so. For that task I would normally need 6 weeks… For sure, I had to correct this program, because I am not a genius… At this time, I had also an awesome sexual life, that made me so relaxed… I lived for 10 years in an Ashram and watched the absurdity of a perverse system…To create so many rules to live in chastity (abstinence…) a religious life…So, more rules so more the rules were broken, at the end who cared/cares in an ashram, monastery for rules? The Guru/Abbot looks that his disciples keep the rules and he/she is breaking the rules/morality by him/herself.Morality is for the others, never for yourself. (Oscar Wild)When I was attending a worship of God in an African church, then Jesus was coming.Did we chase purity? We were dancing and singing the praise of the Lord like crazy.The priest was yelling and even rolling on the ground when he broke out in anger…Such madness and divine…The church was filled with so much spirituality, that Jesus had to come.And that should happen in every church or temple.A religious system that is obsessed with absurd rules will never connect to the Lord/divine, even more it will prevent love and spirituality...And we can watch the religious fanaticism, that kills/killed so many people…For what are the Religions good for? My video: Can we understand God? https://youtu.be/uu_pFdsjhkQMy audio: https://divinesuccess.net/wp-content/uploads/2021/Podcast1/Can.we.understand.God.mp3

The Definition of Done This episode of The Modern .NET Show is supported, in part, by "The Definition of Done and Other Tall Tales". The Definition of Done and Other Tall Tales now available on Amazon. Get your hands on this literary masterpiece either as a beautiful physical book or conveniently for your kindle. Don't miss out on this unique intersection of tech and text. Show Notes Welcome to The Modern .NET Show! Formerly known as The .NET Core Podcast, we are the go-to podcast for all .NET developers worldwide and I am your host Jamie "GaProgMan" Taylor. In this episode, I spoke with Scott Hunter about the dynamic world of .NET, open-source, and a bunch of the related technologies that Microsoft have released. Things like DevContainers: "Yeah. So I would tell people that listen to this: please check out dev containers. I waited way too long to check them out. I knew they existed for a long time and just was too busy and never actually dug deep into it. And now that I have, it's a really cool feature" - Scott Hunter. Along the way, we touch on the fact that .NET is not just open-source but actively accepts contributions from the wider development community - something unheard of in the .NET Framework days. As an example, .NET Seven had over 1,000 contributions from the developer community - not counting the changes that Microsoft's engineers made to it. We also touch on some advice that Scott has for participating in open-source communities, along with some hints as to how Microsoft helps to lead the community around their open-source projects. There's some great advice here, from someone who works in enterprise-lead open-source everyday. Supporting the Show If you find this episode useful in any way, please consider supporting the show by either leaving a review (check our review page for ways to do that), sharing the episode with a friend or colleague, buying the host a coffee, or considering becoming a Patron of the show. Full Show Notes The full show notes, including links to some of the things we discussed and a full transcription of this episode, can be found at: https://dotnetcore.show/season-6/navigating-the-netverse-from-assembler-to-open-source-marvel-with-scott-hunter/ Useful Links Wildcat dot.net Azure Developer CLI aka "azd" Dapr Code Spaces dev containers nvm .NET reliable web app pattern Fedora Silverblue .NET Blog The Modern .NET Show Code of Conduct HomeBridge Shared Source Initiative JSON.net JSON.net on NuGet.org Episode 72 - Emulating a Video Game System in .NET with Ryujinx Microsoft Graph Performance Improvements in .NET 8 Graal Supporting the show: Leave a rating or review Buy the show a coffee Become a patron Getting in touch: via the contact page joining the Discord Music created by Mono Memory Music, licensed to RJJ Software for use in The Modern .NET Show Remember to rate and review the show on Apple Podcasts, Podchaser, or wherever you find your podcasts, this will help the show's audience grow. Or you can just share the show with a friend. And don't forget to reach out via our Contact page. We're very interested in your opinion of the show, so please get in touch. You can support the show by making a monthly donation on the show's Patreon page at: https://www.patreon.com/TheDotNetCorePodcast.

Quelle chance extraordinaire d'avoir une enfance banale où nous avons pu grandir en toute sécurité au sein d'une famille aimante! Malheureusement, beaucoup d'enfants n'ont pas pu avoir droit à ce même privilège. Non seulement ils subissent des manques, mais ils doivent composer avec la violence et les abus de toute sorte. Pour survivre à des traumatismes profonds vécus très tôt dans leur vie, ces enfants développent de puissants mécanismes de défense. Même si les menaces elles-mêmes en viennent à disparaître, ces mécanismes, eux, vont demeurer. Ces mécanismes prennent différentes formes et engendrent une variété de conséquences dans la vie d'adulte. Il demeure très difficile de déconstruire par la suite ce qui a pu être aidant à notre survie. Voilà l'origine des troubles de personnalité selon Jacques Debigaré, professeur en psychologie à l'Université de Trois-Rivières. Dans cet épisode, j'aborde son ouvrage de référence qui s'avère extrêmement riche en informations concernant les 10 troubles de personnalité du DSM. Nous allons explorer ensemble l'origine des troubles au moment de l'enfance ainsi que les pistes d'intervention en psychothérapie afin de réassembler les morceaux de ces enfances brisées. Ordre du jour 0m23: Introduction 13m24: Présentation du livre 17m10: Explication générale sur les troubles 23m15: Différentes approches thérapeutiques 35m46: Introduction aux 10 troubles 49m30: Schizoïde 53m21: Schizotypique 57m13: Dépendant 1h02m44: Évitant (en lien aussi avec la personnalité passive-agressive) 1h05m38: Obsessionnel (en lien aussi avec la personnalité type A) 1h09m02: Paranoïaque 1h12m36: Personnalité limite (Borderline) 1h17m13: Antisocial 1h22m51: Histrionique 1h28m15: Narcissique  1h32m26: Réflexion personnelle Pour encore plus de détails, consulte la page web de l'épisode

Un nuevo 808 en el que descubrimos las últimas creaciones de Fort Romeau, Dusky o Karen Juhl entre muchas otras. Ponemos en marcha el Generador de Ideas para entender por qué es necesaria la despolitización del cambio climático y Criminal Crisis está presentando proyecto. La Lista I: apaull - Tight Dope (Dina Summer Remix) [Furnace Room Records] Nightmares On Wax - Whodunit [WARP] Eartheater - Crushing [Chemical X] Anagrams - Birds on Clifton [Balmat] Altinbas - Radiance [Observer Station] Al Habla: Criminal Crisis. La Lista II: frankydrama - Everybody Dance! [Criminal Crisiis] Rupert Clervaux & Dania III [OOH-sounds] Fort Romeau - Blue [Romantic Gestures] EMJIE - Owner of a Lovely Heart [True Romance] Sega Bodega & Safety trance - Arena! Nutritious - I Love Mitsubishis [Paper Recordings] Guy Gerber - Rainchecks In Montreal (Roy Rosenfeld Remix) [RUMORS] La Lista III: Blake Reyes - The Dreamer [Axis Records] Lupe - The Invocation (Alinka Remix) [Pets] Jasper Tygner x DJ BORING - So Unknown Karen Juhl - Whole World In My Hands [inklingroom] Dusky - Free Your Mind [17 Steps] Seb Wildblood - 366 (ft. laraaji) [All My Thoughts] Generador de Ideas: Por la despolitización del cambio climático, con Emilio Chuvieco. La Lista IV: Luke Hess - E. Grand Blvd. [TS series] Dave NA - Planet Eli [Typeless] Casual Treatment - Miles Away [EarToGround] Mundo D - Outta Space [Espacio Cielo] Phil Berg - Sinara [SK_eleven] Assembler code & Jensen Interceptor - Not a Test Powel - First Swim Of The Year [Seven Villas Music]

Dave Cole remembers his first encounter with the TSO TEST command, back during the mid-1970s. “I said to myself, I can do better,” he recalls, concluding, “I did better.” Four decades later, ColeSoft z/XDC is the benchmark of assembler tools, relied on by IBM Z developers worldwide for analyzing code. z/XDC continues to evolve -- and it's helping train the next generation of IBM Z talent. “It's exciting to get younger people coming around,” Dave says. “We can generate some real excitement once we get somebody who's committed to that direction.” Listen and hear where z/XDC is headed next … Antarctica, perhaps?To learn more about ColeSoft and z/XDC, visit their website.  Join the ISV Ecosystem User Group on the IBM Z and LinuxONE Community for more  updates on how ISVs and partners are innovating the IBM Z platform: blogs, events, videos, discussions, and more.  Join here.And don't forget IBM Z Day, coming on October 18. Join this one-say online event to learn the very latest about innovation from IBM Z, spanning AI, hybrid cloud, quantum-safe security, and more. Register here.Subscribe to z/Action! Each month we meet some of the world's most innovative companies as they share how they're expanding horizons and driving success with IBM Z.

What the kingdom of God looks like; Loving God; Existence of Moses; Ecclesiastes; Sacrifice of fools; Taking oaths; Pagan gods; Clinging to delusions; Vanity; Corban of the Pharisees; Shepherds; Getting out of the world systems; Well-read apostles; Idiotes; Bearing witness; Being diligent; Mt 22:17-21; Gurus?; Ecclesiastes 6:1; Charity; Snares and traps; Living in darkness; Prov 1:10; Identifying the spirit of God; Nimrod; Increasing vanity; Having life more abundant; Your need for repentance; Seeing your part in trauma; Networking; Legal charity; Your goal; Hearing the cries of others; Law of nature; Right to choose; Sparing "the rod"; Minister's job; Free assemblies; Seeking the Holy Spirit; Q and A; Knowing who you are?; Saving yourself?; Witness testimony; Being hurt by Gregory's teachings?; Value of fiat money?; Notes; Redeemability; Bank loans; Defrauding bankers; Being friends with the unrighteous mammon; Going back into bondage; Avoiding the light; Mark of the beast; Seeking the Kingdom; Learning to help one another; Pretend salvation; Coming together; Q: Unrighteous Mammon?; Following the still-small voice; Meditation; "I don't know" prayer; Knowing yourself; Waiting upon the Lord; Gregory history; Bible about law and government; Kingdom in the moment; Seeking the kingdom so nobody has to take the world's benefits; His Holy Church; Early Church; "Other" witnesses; Christian checklist; Follow God's leading; Congregating; Serpent lies; "Assembler"; Voluntary society; Not-so-early Church; Fasting and prayer; Declining empires; Instructions for Christ's ministers; Seven men throughout the kingdom; "Tables"; Credit unions; Crossing the Red Sea; "Rhomaios"; Fitting the puzzle; Acts 19; Tax burdens for shipping; Trust; Fractional reserve banking; Non-participators; Invest in one another; 1 Cor 12:13; 'Why the Network"; Mt 5:46; First fruits; Joining the journey; Lk 6:32; 1 Cor 1:12; Don't be a foolish virgin.

Today, we meet with Mark Wallace. Mark wrote his first computer program in 1965, and has written a lot of them since, using languages ranging from Assembler to SQL. His interest in zero defect software led him to study software engineering methods such as Structured Design and Object-Oriented Design, and ways to adopt them using Computer-Aided Software Engineering (CASE) tools. In recent years, he has taught robotics to middle and high school students, and served as a judge in the World Robot Olympics and First Lego League competitions. He is now retired in Boynton Beach, but volunteers to teach computer programming to high school students through a Microsoft-sponsored charity. We met Mark recently while we were all judging student robot presentations and we were quite impressed. We know you will be too and we hope you stay tuned after for the takeaway. Link for the Microsoft program mentioned in the podcast: https://www.microsoft.com/en-us/teals/about --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app Support this podcast: https://anchor.fm/shawna-christenson2/support

Array Cast - February 17, 2023 Show NotesThanks to Bob Therriault and Adám Brudzewsky for gathering these links:[01] 00:01:20 APLSeeds '23 https://www.dyalog.com/apl-seeds-user-meetings/aplseeds23.htm[02] 00:02:26 KXCon https://kx.com/events/kx-con-2023/[03] 00:04:30 plrank.com https://plrank.com/[04] 00:05:30 Michael Higginson ArrayCast Episode https://www.arraycast.com/episodes/episode46-michael-higginson Iverson Centenary https://britishaplassociation.org/iverson-centenary-december-2020/[05] 00:06:30 Lower Canada College https://www.lcc.ca/ IBM 2741 https://en.wikipedia.org/wiki/IBM_2741 Anderson Jacobson serial modem https://en.wikipedia.org/wiki/Anderson_Jacobson Gilman and Rose - An Interactive Approach https://apl.wiki/Books#APL_―_An_Interactive_Approach Leap Year https://en.wikipedia.org/wiki/Gregorian_calendar#Accuracy APL implementation Leap Year https://tryapl.org/?clear&q=≠%E2%8C%BF0%3D4000%20400%20100%204∘.%7C1600%201700%201800%201900%202000%202100%202200%202300%204000&run[06] 00:13:53 Larry Breed https://apl.wiki/Larry_Breed Scientific Time Sharing Corporation https://en.wikipedia.org/wiki/Scientific_Time_Sharing_Corporation STSC promotional video https://www.youtube.com/watch?v=mjgkhK-nXmk 666 BOX https://www.jsoftware.com/papers/APLQA.htm#666box[07] 00:17:20 University of Toronto https://www.utoronto.ca/ Arthur Whitney https://aplwiki.com/wiki/Arthur_Whitney I.P. Sharp and Associates https://apl.wiki/I.P._Sharp_Associates[08] 00:18:23 360 Assembler https://en.wikipedia.org/wiki/IBM_System/360_architecture#Instruction_formats Eric Iverson https://aplwiki.com/wiki/Eric_Iverson[09] 00:22:40 IESO https://www.ieso.ca/[10] 00:22:50 Smart Meters https://en.wikipedia.org/wiki/Smart_meter[11] 00:23:30 Kdb+ https://code.kx.com/q/learn/brief-introduction/[12] 00:24:30 First Derivatives https://fdtechnologies.com/ KX https://kx.com/ KX Sensors https://kx.com/solutions/energy-utilities/[13] 00:27:52 George Hotz https://en.wikipedia.org/wiki/George_Hotz[14] 00:36:56 ⎕ec https://abrudz.github.io/SAX2/SAX61.pdf#page=790[15] 00:41:20 APL Programming Language https://en.wikipedia.org/wiki/APL_(programming_language) Blackberry RIM https://en.wikipedia.org/wiki/BlackBerry_Limited Rise and Fall of Blackberry https://www.businessinsider.com/blackberry-smartphone-rise-fall-mobile-failure-innovate-2019-11[16] 00:45:45 Ken Iverson https://en.wikipedia.org/wiki/Kenneth_E._Iverson Guy Steele https://en.wikipedia.org/wiki/Guy_L._Steele_Jr.[17] 00:55:12 Nick Psaris ArrayCast Episode https://www.arraycast.com/episodes/episode42-nick-psaris-q[18] 00:56:23 Right Parenthesis ) https://apl.wiki/System_command Quad ⎕ https://apl.wiki/Quad_name[19] 00:57:16 APL2 https://aplwiki.com/wiki/APL2 Axiom System https://dl.acm.org/doi/pdf/10.1145/800136.804446 Trenchard More https://en.wikipedia.org/wiki/Trenchard_More Jim Brown https://aplwiki.com/wiki/Jim_Brown[20] 00:59:28 SHARP APL https://aplwiki.com/wiki/SHARP_APL Roger Moore https://en.wikipedia.org/wiki/Roger_Moore_(computer_scientist) Richard Lathwell https://en.wikipedia.org/wiki/Richard_H._Lathwell[21] 01:04:15 Array Models https://apl.wiki/Array_model[22] 01:04:50 Strand Notation https://apl.wiki/Strand_notation[23] 01:06:05 J Programming Language https://www.jsoftware.com/indexno.html[24] 01:18:02 q Programming Language https://kx.com/academy/ Type of https://apl.wiki/Type[25] 01:21:13 Haskell Programming Language https://www.haskell.org/[26] 01:24:30 ⎕ML Migration Level https://apl.wiki/Migration_level[27] 01:25:50 Oxide and Friends https://oxide.computer/podcasts/oxide-and-friends Java Pubhouse https://www.javapubhouse.com/episodes[28] 01:27:26 British APL Meetings https://britishaplassociation.org/[29] 01:35:06 contact AT ArrayCast DOT COM

resent (v.) c. 1600, "feel pain or distress" (a sense now obsolete); 1620s, "take (something) ill, consider as an injury or affront; be in some degree angry or provoked at," from French ressentir "feel pain, regret," from Old French resentir "feel again, feel in turn" (13c.) sentient (adj.) 1630s, "capable of feeling, having the power of or characterized by the exercise of sense-perception," from Latin sentientem (nominative sentiens) "feeling," present participle of sentire "to feel" 1. Sentience: the capacity to feel, perceive, or experience subjectively. 2. Sentiency: the state of being aware of one's surroundings and of having a conscious experience. 3. Sentimentalism: the tendency to rely too heavily on emotions when making decisions or forming opinions. 4. Sentimentality: the excessive display of emotion, especially in an overly sentimental manner. 5. Sentiment: a general feeling or opinion about something, based on emotion rather than reason. 6. Sentimentalize: to make something overly sentimental or to cause something to be viewed sentimentally. 7. Sentimentality: an excessive or mawkish display of emotion. 8. Sentimentalize: to cause something to become overly sentimental. 9. Sentimentalism: an excessive attachment to or reliance on emotion. 10. Sensibility: the capacity to perceive or feel things. resemble (v.) "be like, have likeness or similarity to," mid-14c., from Old French resembler "be like" (12c., Modern French ressemble), from re-, here perhaps an intensive prefix, + sembler "to appear, to seem, be like," from Latin simulare "to make like, imitate, copy, represent," from stem of similis "like, resembling, of the same kind" 1. Semblance - a superficial resemblance or outward appearance 2. Assembler - one who assembles or puts together reservation (n.) late 14c., "act of reserving or keeping back," from Old French reservation (14c.) and directly from Late Latin reservationem (nominative reservatio), noun of action from past-participle stem of Latin reservare "keep back, save up; retain, preserve," from re- "back" + servare "to keep, save, preserve, protect" 1. Servile - adj. excessively submissive; slavish 2. Service - n. an act of helpful activity; assistance 3. Servitude - n. the state of being a slave; forced labor 4. Serve - v. to be of use; to be of service 5. Servitor - n. a servant; one who is subservient 6. Servitude - n. the condition of being a slave; forced labor 7. Servitorial - adj. of or relating to a servitude; subjugated 8. Servilely - adv. in a slavish manner; submissively 9. Servitorially - adv. in a servitorial manner; submissively --- Support this podcast: https://anchor.fm/liam-connerly/support

In this episode, Jutta Eckstein, an independent coach, consultant and trainer, based in Germany, shares Her origin story of starting as a product engineer, with an interest in software developmentStarted as a trained teacher and when the need for teachers dropped, went on to study product engineering and studying Pascal - and completely falling in love with software developmentAlso getting trained as pollution control commissioner, when she could move from street protests to actually working to keep pollution under controlHer early experience with Pascal and Assembler, and Smalltalk being her all time favoriteBeing part of the professional communities such as OOPSLA, and getting an orientation on the techniques and practices that got crystallized as Agile practicesHer transition from an engineer to a coach : discovering her strength based on a trigger by her project managerMoving into areas of architecture and design and becoming a team coachThe difference between a consultant and coach rolesStudying business coaching and change management, to get a formal understanding and foundationHow that enabled developing connections with people across various industriesMy task is not to create the right mindset, my task is coming with the right mindset myselfThe importance of listening, coming with experience, and working with expertsStarting with a retrospectiveStarting with a few questions: clients having prior experience with changeWhy do you think it will be successful this timeWhat hinders you from starting nowIf she discovered anything surprising in these initial explorations… her response of a pattern she sees.. In the next episodeJutta Eckstein works as an independent coach, consultant, and trainer. She has helped many teams and organizations worldwide to make an Agile transition. She has a unique experience in applying Agile processes within medium-sized to large distributed mission-critical projects. Jutta has recently pair-written with John Buck a book entitled Company-wide Agility with Beyond Budgeting, Open Space & Sociocracy (dubbed BOSSA nova). Besides that, she has published her experience in her books Agile Software Development in the Large, Agile Software Development with Distributed Teams, Retrospectives for Organizational Change, and together with Johanna Rothman Diving for Hidden Treasures: Uncovering the Cost of Delay in your Project Portfolio.Jutta is a member of the Agile Alliance (having served the board of directors from 2003-2007) and a member of the program committee of many different American, Asian, and European conferences, where she has also presented her work. She holds a M.A. in Business Coaching & Change Management, a Dipl.Eng. (MSc.) in Product-Engineering, a B.A. in Education, and is trained as pollution control commissioner on ecological environmentalism.links: @JuttaEckstein | https://www.linkedin.com/in/juttaeckstein/ | https://www.jeckstein.com/| https://www.agilebossanova.org | https://jeckstein.com/sustainability

In this episode, I had the pleasure of talking with Doug Bierer about his history in computing, a history which if you're a computing hardware or programming nerd, you're going to love. Doug shares how he got in to computing with the TRS-80 and Commodore 64. How he taught himself to program in Assembler during shifts when he had some quiet time, and how music was what lead him to programming. We both recount our time in computing back in the 90's and what it was like to work with Microsoft Windows and UNIX/Linux.Some key takeaways are: Throwing hardware at the problem doesn't fix it. Bad code upon bad code just makes more bad code. Automating code creation doesn't necessarily result in good code. Less is more. A GiveawayFor a chance to win a copy of Doug's new Book, PHP 8 Programming Tips, Tricks, and Best Practices, leave your thoughts, your feedback on the episode. Doug and I will give one copy of the book to the person that, in our opinion, leaves the most interesting feedback. You can comment at https://www.freethegeek.fm/48, or on Twitter. Make sure you tag the show (@freeingthegeek).Links PHP 8 Programming Tips, Tricks, and Best Practices (Doug's NEW Book) Unlikely Source (Doug's Company) The TRS-80 The Commodore 64 DR DOS The Motorola 6809 Peek and Poke Unixware Novell U.S. Antitrust law GitHub Copilot Potsdam State University of New York Guests: Doug Bierer (@bierer_doug).Hosted By: Matthew Setter.Thanks for tuning in to Free the Geek. If you'd like to be a guest on the podcast or know someone who'd make a great guest, email me: matthew[at]matthewsetter.com. This podcast is produced by Matthew Setter for the Web Dev With Matt "network".SupportIf you want to support the show, you can always buy me a coffee. I'd greatly appreciate your financial support. ★ Support this podcast ★

La Font Matrix, un concept simple et appliquable pour catégoriser et assembler des polices d'écriture... Source du concept : https://www.youtube.com/watch?v=731-k8xSyqE

@LeoPiccioli Cada éxito está compuesto por un montón de fracasos previos. Los medios no nos cuentan todas las veces que fracasaron los fundadores. Me gusta el fracaso porque es una señal de que lo intentaste. De chiquito me encantaba la computación. Programaba en BASIC y en Assembler, y también leía mucha ciencia ficción. En la UBA milité en política en TNT («Tontos pero No Tanto»), un partido en joda que fue creado para no ganar. Axel era excelente orador y, al menos por entonces, honesto. Él y yo nos graduamos el mismo día. Tengo foto con él, los dos «enhuevados». Está mal valuar a una empresa por sus ventas, pero lo hacemos todos. La valuación por ventas es cómoda porque suele usarse cuando la competencia cotiza en bolsa. En septiembre de 2016 me fui de Staples. Estuve 18 años en la misma compañía. Cuanto más tiempo estás en un laburo más difícil es irte. Lo que aprendí es que cada 3 o 4 años tenés que cambiar de laburo. No digo cambiar de empresa eh, sino de responsabilidades. LinkedIn es de las redes sociales más viejas que conocemos, es del 2004. Hasta que la compró Microsoft era buena, después se volvió mala. Ahora está volviendo a tener contenido de calidad. Tener una empresa tiene un desafío de decisiones que no me encanta. Por ejemplo: echar gente. En las empresas hay que poner la misión por encima de las personas. @LeoPiccioli dándole un consejo al Leo de hace 10 años: "Relajate, disfrutá del camino." https://twitter.com/ETPA_Spaces/status/1564011774994677761

Jacques Bergeon talks guitar assembly, crazy stories from his youth, and a possible upcoming album??

Hoy hablamos de un interesantísimo proyecto de formación en programación creado por CRISTIAN FONDEVILA y KASIA ADAMOWICZ . Se llama ASSEMBLER INSTITUTE OF TECHNOLOGY y podéis encontrar toda su información a través del siguiente enlace: https://go.assemblerinstitute.com/keB En un mundo cada vez más tecnológico éste área es un campo con muchísimo futuro tanto por las posibilidades en el ámbito laboral como por las necesidades que tendremos en el día a día. Quiero dar las gracias a todo el equipo de Assembler Institute por su accesibilidad y disposición para grabar éste podcast y especialmente a Cristian por someterse a mi tortura.

Un ancien policier détourne un jeu organisé par McDonald's et vole des millions de dollars. Son nom : Jerome Jacobson. Découvrez sa True Story. Qui n'a jamais triché pour gagner au Monopoly ? Parmi les techniques, voici une : portez-vous volontaire en début de partie pour être banquier. A chaque fois que la banque vous doit de l'argent, piochez un ou deux billets supplémentaires. Comme la technique de Jerome Jacobson pour gagner des millions à un jeu organisé par McDonald's aux Etats-Unis. Un jeu Monopoly justement, pour lequel chaque client reçoit une vignette à son passage en caisse. Le but ? Assembler des cartes propriétés pour gagner un jeu vidéo ou de l'argent. Il est aussi possible d'obtenir une carte gain instantané qui donne droit à un Big Mac ou… 1 million de dollars. Ecoutez la suite de cette histoire incroyable dans ce podcast. Pour découvrir d'autres récits passionnants, cliquez ci-dessous : Oprah Winfrey, du ghetto au sommet L'affaire du col Dyatlov, le cold case russe devenu un mythe Casanova, le séducteur aux multiples visages Learn more about your ad choices. Visit megaphone.fm/adchoices

Sarah Jérôme, artiste plasticienne, est l'invitée du 9ème épisode de Femmes artistes / Artistes femmes le podcast.  Avec elle, nous avons parlé de son parcours de femme et d'artiste, du fil rouge qui inspire son travail, du cœur de son quotidien, et de sa « grotte » basée à Montreuil dans laquelle elle concocte des œuvres et assemble des matières : la peinture à l'huile et le papier calque, la cire et la céramique, le tissu sur papier… Son œuvre, à la fois sombre et candide, abstraite et figurative, prend tout son sens au regard de sa narration. En quête d'une reconciliation de âmes et des matières, les couleurs de Sarah Jérôme se superposent, en couches, et laissent apparaître des images dont l'harmonie semble sourdre du chaos. Cet épisode est une ode à nos ambivalences... Artistes qui inspirent son travail : Les symbolistes, Louise Bourgeois, Marlène Dumas, Pina Bausch, Berlinde De Bruyckere, Guiseppe Penone, Patti Smith, Katharina Ziemke Références littéraires Une femme de Anne Delbée (biographie de Camille Claudel) ; La femme qui tremble de Siri Hustvedt ; Le mur invisible de Marlen Haushofer ; Poupées de Éleonore Pourriat Expositions à venir : Duo Show avec Gael Davrinche (qui aura lieu début juin à la Chaufferie de l'Antiquaille à Lyon) et exposition We love witches à la galerie Sabine Vazieux à Paris, décalée en décembre 2021 Oeuvre décrite en intro de l'épisode :  Solace (2018) Technique mixte sur papier calque 180 x 137,5 cm Le site internet de Sarah Jérôme : www.sarahjerome.com et sa page Instagram @sarahsaje.jerome Les galeries avec lesquelles elle travaille  Galerie Vachet-Delmas, Galerie Sabine Vazieux, Doppelgaenger, Galerie Da-End  Suivez-moi sur la page instagram du podcast @artistesfemmeslepodcast et sur mon fil twitter @adakafel. Femmes artistes / Artistes femmes est un podcast entièrement indépendant créé et produit par Ada Kafel. Ada Kafel est artiste peintre et maman d'un petit garçon. On peut voir son travail sur son site internet https://www.adakafel.com/ ou sa page instagram @a_felka. Musique d'introduction : Leonie Pernet, Butterfly feat. Malik Djoudi Musique de fin : Ruppert Pupkin "Dans ma peau, On ne tue jamais par amour". Un film tourné en confinement de Bruno Merle et Ruppert Pupkin. 

Meet Seth. He's an assembler. With his certificate in Airframe & Powerplant, his path led to a position as an Assembler. His favorite tool? A profilometer. Listen and learn about his path as Seth talks shop. FOLLOW ON INSTAGRAM // FACEBOOK