American nonprofit organization that coordinates several Internet address databases
POPULARITY
21 episodes with ICANN
21 episodes with ICANN
14 episodes with ICANN
13 episodes with ICANN
8 episodes with ICANN
18 episodes with ICANN
5 episodes with ICANN
3 episodes with ICANN
4 episodes with ICANN
What to expect in the next round of new top level domain expansion. It's finally happening. ICANN has published its Draft Applicant Guidebook for the next round of new top level domain expansion. Other than adding some deadlines, it's likely to be more or less the final rulebook when applications open starting this time next […] Post link: The new new TLD opportunity – DNW Podcast #538 © DomainNameWire.com 2025. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.
ICANN's Theresa Swinehart discusses brand applications in the upcoming round of top level domains. The next application window for top level domain names opens next year. It's been more than a decade since the last round, and a lot has changed in both the domain name industry and the broader internet landscape. On today's podcast, […] Post link: What's next for dot-brands – DNW Podcast #536 © DomainNameWire.com 2025. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.
Today's guest is Milton L. Mueller, a professor at the Georgia Institute of Technology in the School of Public Policy and the head of an advocacy policy analysis group called the Internet Governance Project. Mueller has long walked the halls and sat in the rooms where internet governance is discussed and debated, and has played a role in shaping global Internet policies and institutions. He's the author of a new book called Declaring Independence in Cyberspace: Internet Self-Governance and the End of US Control of ICANN, which takes us into those rooms, telling the story of how and why the US government gave up its control of ICANN, a key internet governance institution responsible for internet names, numbers, and protocols. That history tells us a lot about where we are today when it comes to the broader geopolitics and governance of technology, and it has implications for the governance fights ahead, including over artificial intelligence.
In the wake of Canada's latest federal election, Jian hosts a timely and incisive roundtable exploring what the results reveal about Iranian-Canadian political identity and influence. With the Liberal Party securing a minority government and traditional voting patterns shifting, this special episode of Roqe asks: How did Iranian-Canadians vote this time, what drove the changes, and what might the new government mean for Canada's approach to the Islamic Republic of Iran? Joining Jian for this in-depth conversation are four sharp and diverse voices: longtime Liberal strategist Maryam Azari from Vancouver; author and activist Mehrdad Loghmani; international law expert and ICANN founder Sadeq Bigdeli; and veteran journalist and Persian Mirror editor-in-chief Dr. Mohammad Tajdolati. From divided loyalties to diaspora awakening, this episode digs into the complexities-and consequences-of a maturing political voice.
En este episodio de Amigos TIC, Rodrigo de la Parra, vicepresidente regional de la ICANN, nos comparte datos clave sobre la organización, su rol en la gestión de dominios en Internet y los lazos que ha construido con distintos países. Además, habla sobre los avances que se han hecho para enfrentar los retos generados por el creciente uso de Internet y la demanda de dominios.Descubre más sobre organización web en este interesante episodio. ¡No te lo pierdas!00:00 Amigos TIC03:41 Rodrigo de la Parra, vicepresidente regional de la ICANN06:47 ¿Qué es ICANN?11:45 Las sedes regionales varían según su dinámica, ¿cómo es en Colombia?16:55 ¿Cómo se puede adquirir un dominio?30:20 ¿Qué nuevos desafíos evidencian?41:01 Ojo al dato, con Santiago Pinzón42:05 ¿Qué tan largos pueden ser los dominios?44:25 ¿Qué libros lee y qué pódcast escucha?
Willkommen beim Podcast von Technologie-Scout Boris Bärmichl!Bereit für eine faszinierende Entdeckungsreise in die Welt der Technologie?
As the internet becomes more integral to economic development, cultural diplomacy, and public governance, there may be strategic value in having custom generic top-level domains (gTLDs). Active participants in the global Internet Governance space, Lance Hinds and Carlton Samuels, are back to discuss ICANN's New gTLD Program: Next Round, which is currently open. The conversation covered, among other things: * the difference between country code top-level domains (ccTLDs) and gTLDs; * the current state of use of ccTLDs in the Caribbean region; * the New gTLD Program and the benefits that could be realised; and * the challenges to Caribbean countries and organisations to apply for new custom gTLDs. The episode, show notes and links to some of the things mentioned during the episode can be found on the ICT Pulse Podcast Page (www.ict-pulse.com/category/podcast/) Enjoyed the episode? Do rate the show and leave us a review! Also, connect with us on: Facebook – https://www.facebook.com/ICTPulse/ Instagram – https://www.instagram.com/ictpulse/ Twitter – https://twitter.com/ICTPulse LinkedIn – https://www.linkedin.com/company/3745954/admin/ Join our mailing list: http://eepurl.com/qnUtj Music credit: The Last Word (Oui Ma Chérie), by Andy Narrell Podcast editing support: Mayra Bonilla Lopez ----------------
If you're in SF: Join us for the Claude Plays Pokemon hackathon this Sunday!If you're not: Fill out the 2025 State of AI Eng survey for $250 in Amazon cards!We are SO excited to share our conversation with Dharmesh Shah, co-founder of HubSpot and creator of Agent.ai.A particularly compelling concept we discussed is the idea of "hybrid teams" - the next evolution in workplace organization where human workers collaborate with AI agents as team members. Just as we previously saw hybrid teams emerge in terms of full-time vs. contract workers, or in-office vs. remote workers, Dharmesh predicts that the next frontier will be teams composed of both human and AI members. This raises interesting questions about team dynamics, trust, and how to effectively delegate tasks between human and AI team members.The discussion of business models in AI reveals an important distinction between Work as a Service (WaaS) and Results as a Service (RaaS), something Dharmesh has written extensively about. While RaaS has gained popularity, particularly in customer support applications where outcomes are easily measurable, Dharmesh argues that this model may be over-indexed. Not all AI applications have clearly definable outcomes or consistent economic value per transaction, making WaaS more appropriate in many cases. This insight is particularly relevant for businesses considering how to monetize AI capabilities.The technical challenges of implementing effective agent systems are also explored, particularly around memory and authentication. Shah emphasizes the importance of cross-agent memory sharing and the need for more granular control over data access. He envisions a future where users can selectively share parts of their data with different agents, similar to how OAuth works but with much finer control. This points to significant opportunities in developing infrastructure for secure and efficient agent-to-agent communication and data sharing.Other highlights from our conversation* The Evolution of AI-Powered Agents – Exploring how AI agents have evolved from simple chatbots to sophisticated multi-agent systems, and the role of MCPs in enabling that.* Hybrid Digital Teams and the Future of Work – How AI agents are becoming teammates rather than just tools, and what this means for business operations and knowledge work.* Memory in AI Agents – The importance of persistent memory in AI systems and how shared memory across agents could enhance collaboration and efficiency.* Business Models for AI Agents – Exploring the shift from software as a service (SaaS) to work as a service (WaaS) and results as a service (RaaS), and what this means for monetization.* The Role of Standards Like MCP – Why MCP has been widely adopted and how it enables agent collaboration, tool use, and discovery.* The Future of AI Code Generation and Software Engineering – How AI-assisted coding is changing the role of software engineers and what skills will matter most in the future.* Domain Investing and Efficient Markets – Dharmesh's approach to domain investing and how inefficiencies in digital asset markets create business opportunities.* The Philosophy of Saying No – Lessons from "Sorry, You Must Pass" and how prioritization leads to greater productivity and focus.Timestamps* 00:00 Introduction and Guest Welcome* 02:29 Dharmesh Shah's Journey into AI* 05:22 Defining AI Agents* 06:45 The Evolution and Future of AI Agents* 13:53 Graph Theory and Knowledge Representation* 20:02 Engineering Practices and Overengineering* 25:57 The Role of Junior Engineers in the AI Era* 28:20 Multi-Agent Systems and MCP Standards* 35:55 LinkedIn's Legal Battles and Data Scraping* 37:32 The Future of AI and Hybrid Teams* 39:19 Building Agent AI: A Professional Network for Agents* 40:43 Challenges and Innovations in Agent AI* 45:02 The Evolution of UI in AI Systems* 01:00:25 Business Models: Work as a Service vs. Results as a Service* 01:09:17 The Future Value of Engineers* 01:09:51 Exploring the Role of Agents* 01:10:28 The Importance of Memory in AI* 01:11:02 Challenges and Opportunities in AI Memory* 01:12:41 Selective Memory and Privacy Concerns* 01:13:27 The Evolution of AI Tools and Platforms* 01:18:23 Domain Names and AI Projects* 01:32:08 Balancing Work and Personal Life* 01:35:52 Final Thoughts and ReflectionsTranscriptAlessio [00:00:04]: Hey everyone, welcome back to the Latent Space podcast. This is Alessio, partner and CTO at Decibel Partners, and I'm joined by my co-host Swyx, founder of Small AI.swyx [00:00:12]: Hello, and today we're super excited to have Dharmesh Shah to join us. I guess your relevant title here is founder of Agent AI.Dharmesh [00:00:20]: Yeah, that's true for this. Yeah, creator of Agent.ai and co-founder of HubSpot.swyx [00:00:25]: Co-founder of HubSpot, which I followed for many years, I think 18 years now, gonna be 19 soon. And you caught, you know, people can catch up on your HubSpot story elsewhere. I should also thank Sean Puri, who I've chatted with back and forth, who's been, I guess, getting me in touch with your people. But also, I think like, just giving us a lot of context, because obviously, My First Million joined you guys, and they've been chatting with you guys a lot. So for the business side, we can talk about that, but I kind of wanted to engage your CTO, agent, engineer side of things. So how did you get agent religion?Dharmesh [00:01:00]: Let's see. So I've been working, I'll take like a half step back, a decade or so ago, even though actually more than that. So even before HubSpot, the company I was contemplating that I had named for was called Ingenisoft. And the idea behind Ingenisoft was a natural language interface to business software. Now realize this is 20 years ago, so that was a hard thing to do. But the actual use case that I had in mind was, you know, we had data sitting in business systems like a CRM or something like that. And my kind of what I thought clever at the time. Oh, what if we used email as the kind of interface to get to business software? And the motivation for using email is that it automatically works when you're offline. So imagine I'm getting on a plane or I'm on a plane. There was no internet on planes back then. It's like, oh, I'm going through business cards from an event I went to. I can just type things into an email just to have them all in the backlog. When it reconnects, it sends those emails to a processor that basically kind of parses effectively the commands and updates the software, sends you the file, whatever it is. And there was a handful of commands. I was a little bit ahead of the times in terms of what was actually possible. And I reattempted this natural language thing with a product called ChatSpot that I did back 20...swyx [00:02:12]: Yeah, this is your first post-ChatGPT project.Dharmesh [00:02:14]: I saw it come out. Yeah. And so I've always been kind of fascinated by this natural language interface to software. Because, you know, as software developers, myself included, we've always said, oh, we build intuitive, easy-to-use applications. And it's not intuitive at all, right? Because what we're doing is... We're taking the mental model that's in our head of what we're trying to accomplish with said piece of software and translating that into a series of touches and swipes and clicks and things like that. And there's nothing natural or intuitive about it. And so natural language interfaces, for the first time, you know, whatever the thought is you have in your head and expressed in whatever language that you normally use to talk to yourself in your head, you can just sort of emit that and have software do something. And I thought that was kind of a breakthrough, which it has been. And it's gone. So that's where I first started getting into the journey. I started because now it actually works, right? So once we got ChatGPT and you can take, even with a few-shot example, convert something into structured, even back in the ChatGP 3.5 days, it did a decent job in a few-shot example, convert something to structured text if you knew what kinds of intents you were going to have. And so that happened. And that ultimately became a HubSpot project. But then agents intrigued me because I'm like, okay, well, that's the next step here. So chat's great. Love Chat UX. But if we want to do something even more meaningful, it felt like the next kind of advancement is not this kind of, I'm chatting with some software in a kind of a synchronous back and forth model, is that software is going to do things for me in kind of a multi-step way to try and accomplish some goals. So, yeah, that's when I first got started. It's like, okay, what would that look like? Yeah. And I've been obsessed ever since, by the way.Alessio [00:03:55]: Which goes back to your first experience with it, which is like you're offline. Yeah. And you want to do a task. You don't need to do it right now. You just want to queue it up for somebody to do it for you. Yes. As you think about agents, like, let's start at the easy question, which is like, how do you define an agent? Maybe. You mean the hardest question in the universe? Is that what you mean?Dharmesh [00:04:12]: You said you have an irritating take. I do have an irritating take. I think, well, some number of people have been irritated, including within my own team. So I have a very broad definition for agents, which is it's AI-powered software that accomplishes a goal. Period. That's it. And what irritates people about it is like, well, that's so broad as to be completely non-useful. And I understand that. I understand the criticism. But in my mind, if you kind of fast forward months, I guess, in AI years, the implementation of it, and we're already starting to see this, and we'll talk about this, different kinds of agents, right? So I think in addition to having a usable definition, and I like yours, by the way, and we should talk more about that, that you just came out with, the classification of agents actually is also useful, which is, is it autonomous or non-autonomous? Does it have a deterministic workflow? Does it have a non-deterministic workflow? Is it working synchronously? Is it working asynchronously? Then you have the different kind of interaction modes. Is it a chat agent, kind of like a customer support agent would be? You're having this kind of back and forth. Is it a workflow agent that just does a discrete number of steps? So there's all these different flavors of agents. So if I were to draw it in a Venn diagram, I would draw a big circle that says, this is agents, and then I have a bunch of circles, some overlapping, because they're not mutually exclusive. And so I think that's what's interesting, and we're seeing development along a bunch of different paths, right? So if you look at the first implementation of agent frameworks, you look at Baby AGI and AutoGBT, I think it was, not Autogen, that's the Microsoft one. They were way ahead of their time because they assumed this level of reasoning and execution and planning capability that just did not exist, right? So it was an interesting thought experiment, which is what it was. Even the guy that, I'm an investor in Yohei's fund that did Baby AGI. It wasn't ready, but it was a sign of what was to come. And so the question then is, when is it ready? And so lots of people talk about the state of the art when it comes to agents. I'm a pragmatist, so I think of the state of the practical. It's like, okay, well, what can I actually build that has commercial value or solves actually some discrete problem with some baseline of repeatability or verifiability?swyx [00:06:22]: There was a lot, and very, very interesting. I'm not irritated by it at all. Okay. As you know, I take a... There's a lot of anthropological view or linguistics view. And in linguistics, you don't want to be prescriptive. You want to be descriptive. Yeah. So you're a goals guy. That's the key word in your thing. And other people have other definitions that might involve like delegated trust or non-deterministic work, LLM in the loop, all that stuff. The other thing I was thinking about, just the comment on Baby AGI, LGBT. Yeah. In that piece that you just read, I was able to go through our backlog and just kind of track the winter of agents and then the summer now. Yeah. And it's... We can tell the whole story as an oral history, just following that thread. And it's really just like, I think, I tried to explain the why now, right? Like I had, there's better models, of course. There's better tool use with like, they're just more reliable. Yep. Better tools with MCP and all that stuff. And I'm sure you have opinions on that too. Business model shift, which you like a lot. I just heard you talk about RAS with MFM guys. Yep. Cost is dropping a lot. Yep. Inference is getting faster. There's more model diversity. Yep. Yep. I think it's a subtle point. It means that like, you have different models with different perspectives. You don't get stuck in the basin of performance of a single model. Sure. You can just get out of it by just switching models. Yep. Multi-agent research and RL fine tuning. So I just wanted to let you respond to like any of that.Dharmesh [00:07:44]: Yeah. A couple of things. Connecting the dots on the kind of the definition side of it. So we'll get the irritation out of the way completely. I have one more, even more irritating leap on the agent definition thing. So here's the way I think about it. By the way, the kind of word agent, I looked it up, like the English dictionary definition. The old school agent, yeah. Is when you have someone or something that does something on your behalf, like a travel agent or a real estate agent acts on your behalf. It's like proxy, which is a nice kind of general definition. So the other direction I'm sort of headed, and it's going to tie back to tool calling and MCP and things like that, is if you, and I'm not a biologist by any stretch of the imagination, but we have these single-celled organisms, right? Like the simplest possible form of what one would call life. But it's still life. It just happens to be single-celled. And then you can combine cells and then cells become specialized over time. And you have much more sophisticated organisms, you know, kind of further down the spectrum. In my mind, at the most fundamental level, you can almost think of having atomic agents. What is the simplest possible thing that's an agent that can still be called an agent? What is the equivalent of a kind of single-celled organism? And the reason I think that's useful is right now we're headed down the road, which I think is very exciting around tool use, right? That says, okay, the LLMs now can be provided a set of tools that it calls to accomplish whatever it needs to accomplish in the kind of furtherance of whatever goal it's trying to get done. And I'm not overly bothered by it, but if you think about it, if you just squint a little bit and say, well, what if everything was an agent? And what if tools were actually just atomic agents? Because then it's turtles all the way down, right? Then it's like, oh, well, all that's really happening with tool use is that we have a network of agents that know about each other through something like an MMCP and can kind of decompose a particular problem and say, oh, I'm going to delegate this to this set of agents. And why do we need to draw this distinction between tools, which are functions most of the time? And an actual agent. And so I'm going to write this irritating LinkedIn post, you know, proposing this. It's like, okay. And I'm not suggesting we should call even functions, you know, call them agents. But there is a certain amount of elegance that happens when you say, oh, we can just reduce it down to one primitive, which is an agent that you can combine in complicated ways to kind of raise the level of abstraction and accomplish higher order goals. Anyway, that's my answer. I'd say that's a success. Thank you for coming to my TED Talk on agent definitions.Alessio [00:09:54]: How do you define the minimum viable agent? Do you already have a definition for, like, where you draw the line between a cell and an atom? Yeah.Dharmesh [00:10:02]: So in my mind, it has to, at some level, use AI in order for it to—otherwise, it's just software. It's like, you know, we don't need another word for that. And so that's probably where I draw the line. So then the question, you know, the counterargument would be, well, if that's true, then lots of tools themselves are actually not agents because they're just doing a database call or a REST API call or whatever it is they're doing. And that does not necessarily qualify them, which is a fair counterargument. And I accept that. It's like a good argument. I still like to think about—because we'll talk about multi-agent systems, because I think—so we've accepted, which I think is true, lots of people have said it, and you've hopefully combined some of those clips of really smart people saying this is the year of agents, and I completely agree, it is the year of agents. But then shortly after that, it's going to be the year of multi-agent systems or multi-agent networks. I think that's where it's going to be headed next year. Yeah.swyx [00:10:54]: Opening eyes already on that. Yeah. My quick philosophical engagement with you on this. I often think about kind of the other spectrum, the other end of the cell spectrum. So single cell is life, multi-cell is life, and you clump a bunch of cells together in a more complex organism, they become organs, like an eye and a liver or whatever. And then obviously we consider ourselves one life form. There's not like a lot of lives within me. I'm just one life. And now, obviously, I don't think people don't really like to anthropomorphize agents and AI. Yeah. But we are extending our consciousness and our brain and our functionality out into machines. I just saw you were a Bee. Yeah. Which is, you know, it's nice. I have a limitless pendant in my pocket.Dharmesh [00:11:37]: I got one of these boys. Yeah.swyx [00:11:39]: I'm testing it all out. You know, got to be early adopters. But like, we want to extend our personal memory into these things so that we can be good at the things that we're good at. And, you know, machines are good at it. Machines are there. So like, my definition of life is kind of like going outside of my own body now. I don't know if you've ever had like reflections on that. Like how yours. How our self is like actually being distributed outside of you. Yeah.Dharmesh [00:12:01]: I don't fancy myself a philosopher. But you went there. So yeah, I did go there. I'm fascinated by kind of graphs and graph theory and networks and have been for a long, long time. And to me, we're sort of all nodes in this kind of larger thing. It just so happens that we're looking at individual kind of life forms as they exist right now. But so the idea is when you put a podcast out there, there's these little kind of nodes you're putting out there of like, you know, conceptual ideas. Once again, you have varying kind of forms of those little nodes that are up there and are connected in varying and sundry ways. And so I just think of myself as being a node in a massive, massive network. And I'm producing more nodes as I put content or ideas. And, you know, you spend some portion of your life collecting dots, experiences, people, and some portion of your life then connecting dots from the ones that you've collected over time. And I found that really interesting things happen and you really can't know in advance how those dots are necessarily going to connect in the future. And that's, yeah. So that's my philosophical take. That's the, yes, exactly. Coming back.Alessio [00:13:04]: Yep. Do you like graph as an agent? Abstraction? That's been one of the hot topics with LandGraph and Pydantic and all that.Dharmesh [00:13:11]: I do. The thing I'm more interested in terms of use of graphs, and there's lots of work happening on that now, is graph data stores as an alternative in terms of knowledge stores and knowledge graphs. Yeah. Because, you know, so I've been in software now 30 plus years, right? So it's not 10,000 hours. It's like 100,000 hours that I've spent doing this stuff. And so I've grew up with, so back in the day, you know, I started on mainframes. There was a product called IMS from IBM, which is basically an index database, what we'd call like a key value store today. Then we've had relational databases, right? We have tables and columns and foreign key relationships. We all know that. We have document databases like MongoDB, which is sort of a nested structure keyed by a specific index. We have vector stores, vector embedding database. And graphs are interesting for a couple of reasons. One is, so it's not classically structured in a relational way. When you say structured database, to most people, they're thinking tables and columns and in relational database and set theory and all that. Graphs still have structure, but it's not the tables and columns structure. And you could wonder, and people have made this case, that they are a better representation of knowledge for LLMs and for AI generally than other things. So that's kind of thing number one conceptually, and that might be true, I think is possibly true. And the other thing that I really like about that in the context of, you know, I've been in the context of data stores for RAG is, you know, RAG, you say, oh, I have a million documents, I'm going to build the vector embeddings, I'm going to come back with the top X based on the semantic match, and that's fine. All that's very, very useful. But the reality is something gets lost in the chunking process and the, okay, well, those tend, you know, like, you don't really get the whole picture, so to speak, and maybe not even the right set of dimensions on the kind of broader picture. And it makes intuitive sense to me that if we did capture it properly in a graph form, that maybe that feeding into a RAG pipeline will actually yield better results for some use cases, I don't know, but yeah.Alessio [00:15:03]: And do you feel like at the core of it, there's this difference between imperative and declarative programs? Because if you think about HubSpot, it's like, you know, people and graph kind of goes hand in hand, you know, but I think maybe the software before was more like primary foreign key based relationship, versus now the models can traverse through the graph more easily.Dharmesh [00:15:22]: Yes. So I like that representation. There's something. It's just conceptually elegant about graphs and just from the representation of it, they're much more discoverable, you can kind of see it, there's observability to it, versus kind of embeddings, which you can't really do much with as a human. You know, once they're in there, you can't pull stuff back out. But yeah, I like that kind of idea of it. And the other thing that's kind of, because I love graphs, I've been long obsessed with PageRank from back in the early days. And, you know, one of the kind of simplest algorithms in terms of coming up, you know, with a phone, everyone's been exposed to PageRank. And the idea is that, and so I had this other idea for a project, not a company, and I have hundreds of these, called NodeRank, is to be able to take the idea of PageRank and apply it to an arbitrary graph that says, okay, I'm going to define what authority looks like and say, okay, well, that's interesting to me, because then if you say, I'm going to take my knowledge store, and maybe this person that contributed some number of chunks to the graph data store has more authority on this particular use case or prompt that's being submitted than this other one that may, or maybe this one was more. popular, or maybe this one has, whatever it is, there should be a way for us to kind of rank nodes in a graph and sort them in some, some useful way. Yeah.swyx [00:16:34]: So I think that's generally useful for, for anything. I think the, the problem, like, so even though at my conferences, GraphRag is super popular and people are getting knowledge, graph religion, and I will say like, it's getting space, getting traction in two areas, conversation memory, and then also just rag in general, like the, the, the document data. Yeah. It's like a source. Most ML practitioners would say that knowledge graph is kind of like a dirty word. The graph database, people get graph religion, everything's a graph, and then they, they go really hard into it and then they get a, they get a graph that is too complex to navigate. Yes. And so like the, the, the simple way to put it is like you at running HubSpot, you know, the power of graphs, the way that Google has pitched them for many years, but I don't suspect that HubSpot itself uses a knowledge graph. No. Yeah.Dharmesh [00:17:26]: So when is it over engineering? Basically? It's a great question. I don't know. So the question now, like in AI land, right, is the, do we necessarily need to understand? So right now, LLMs for, for the most part are somewhat black boxes, right? We sort of understand how the, you know, the algorithm itself works, but we really don't know what's going on in there and, and how things come out. So if a graph data store is able to produce the outcomes we want, it's like, here's a set of queries I want to be able to submit and then it comes out with useful content. Maybe the underlying data store is as opaque as a vector embeddings or something like that, but maybe it's fine. Maybe we don't necessarily need to understand it to get utility out of it. And so maybe if it's messy, that's okay. Um, that's, it's just another form of lossy compression. Uh, it's just lossy in a way that we just don't completely understand in terms of, because it's going to grow organically. Uh, and it's not structured. It's like, ah, we're just gonna throw a bunch of stuff in there. Let the, the equivalent of the embedding algorithm, whatever they called in graph land. Um, so the one with the best results wins. I think so. Yeah.swyx [00:18:26]: Or is this the practical side of me is like, yeah, it's, if it's useful, we don't necessarilyDharmesh [00:18:30]: need to understand it.swyx [00:18:30]: I have, I mean, I'm happy to push back as long as you want. Uh, it's not practical to evaluate like the 10 different options out there because it takes time. It takes people, it takes, you know, resources, right? Set. That's the first thing. Second thing is your evals are typically on small things and some things only work at scale. Yup. Like graphs. Yup.Dharmesh [00:18:46]: Yup. That's, yeah, no, that's fair. And I think this is one of the challenges in terms of implementation of graph databases is that the most common approach that I've seen developers do, I've done it myself, is that, oh, I've got a Postgres database or a MySQL or whatever. I can represent a graph with a very set of tables with a parent child thing or whatever. And that sort of gives me the ability, uh, why would I need anything more than that? And the answer is, well, if you don't need anything more than that, you don't need anything more than that. But there's a high chance that you're sort of missing out on the actual value that, uh, the graph representation gives you. Which is the ability to traverse the graph, uh, efficiently in ways that kind of going through the, uh, traversal in a relational database form, even though structurally you have the data, practically you're not gonna be able to pull it out in, in useful ways. Uh, so you wouldn't like represent a social graph, uh, in, in using that kind of relational table model. It just wouldn't scale. It wouldn't work.swyx [00:19:36]: Uh, yeah. Uh, I think we want to move on to MCP. Yeah. But I just want to, like, just engineering advice. Yeah. Uh, obviously you've, you've, you've run, uh, you've, you've had to do a lot of projects and run a lot of teams. Do you have a general rule for over-engineering or, you know, engineering ahead of time? You know, like, because people, we know premature engineering is the root of all evil. Yep. But also sometimes you just have to. Yep. When do you do it? Yes.Dharmesh [00:19:59]: It's a great question. This is, uh, a question as old as time almost, which is what's the right and wrong levels of abstraction. That's effectively what, uh, we're answering when we're trying to do engineering. I tend to be a pragmatist, right? So here's the thing. Um, lots of times doing something the right way. Yeah. It's like a marginal increased cost in those cases. Just do it the right way. And this is what makes a, uh, a great engineer or a good engineer better than, uh, a not so great one. It's like, okay, all things being equal. If it's going to take you, you know, roughly close to constant time anyway, might as well do it the right way. Like, so do things well, then the question is, okay, well, am I building a framework as the reusable library? To what degree, uh, what am I anticipating in terms of what's going to need to change in this thing? Uh, you know, along what dimension? And then I think like a business person in some ways, like what's the return on calories, right? So, uh, and you look at, um, energy, the expected value of it's like, okay, here are the five possible things that could happen, uh, try to assign probabilities like, okay, well, if there's a 50% chance that we're going to go down this particular path at some day, like, or one of these five things is going to happen and it costs you 10% more to engineer for that. It's basically, it's something that yields a kind of interest compounding value. Um, as you get closer to the time of, of needing that versus having to take on debt, which is when you under engineer it, you're taking on debt. You're going to have to pay off when you do get to that eventuality where something happens. One thing as a pragmatist, uh, so I would rather under engineer something than over engineer it. If I were going to err on the side of something, and here's the reason is that when you under engineer it, uh, yes, you take on tech debt, uh, but the interest rate is relatively known and payoff is very, very possible, right? Which is, oh, I took a shortcut here as a result of which now this thing that should have taken me a week is now going to take me four weeks. Fine. But if that particular thing that you thought might happen, never actually, you never have that use case transpire or just doesn't, it's like, well, you just save yourself time, right? And that has value because you were able to do other things instead of, uh, kind of slightly over-engineering it away, over-engineering it. But there's no perfect answers in art form in terms of, uh, and yeah, we'll, we'll bring kind of this layers of abstraction back on the code generation conversation, which we'll, uh, I think I have later on, butAlessio [00:22:05]: I was going to ask, we can just jump ahead quickly. Yeah. Like, as you think about vibe coding and all that, how does the. Yeah. Percentage of potential usefulness change when I feel like we over-engineering a lot of times it's like the investment in syntax, it's less about the investment in like arc exacting. Yep. Yeah. How does that change your calculus?Dharmesh [00:22:22]: A couple of things, right? One is, um, so, you know, going back to that kind of ROI or a return on calories, kind of calculus or heuristic you think through, it's like, okay, well, what is it going to cost me to put this layer of abstraction above the code that I'm writing now, uh, in anticipating kind of future needs. If the cost of fixing, uh, or doing under engineering right now. Uh, we'll trend towards zero that says, okay, well, I don't have to get it right right now because even if I get it wrong, I'll run the thing for six hours instead of 60 minutes or whatever. It doesn't really matter, right? Like, because that's going to trend towards zero to be able, the ability to refactor a code. Um, and because we're going to not that long from now, we're going to have, you know, large code bases be able to exist, uh, you know, as, as context, uh, for a code generation or a code refactoring, uh, model. So I think it's going to make it, uh, make the case for under engineering, uh, even stronger. Which is why I take on that cost. You just pay the interest when you get there, it's not, um, just go on with your life vibe coded and, uh, come back when you need to. Yeah.Alessio [00:23:18]: Sometimes I feel like there's no decision-making in some things like, uh, today I built a autosave for like our internal notes platform and I literally just ask them cursor. Can you add autosave? Yeah. I don't know if it's over under engineer. Yep. I just vibe coded it. Yep. And I feel like at some point we're going to get to the point where the models kindDharmesh [00:23:36]: of decide where the right line is, but this is where the, like the, in my mind, the danger is, right? So there's two sides to this. One is the cost of kind of development and coding and things like that stuff that, you know, we talk about. But then like in your example, you know, one of the risks that we have is that because adding a feature, uh, like a save or whatever the feature might be to a product as that price tends towards zero, are we going to be less discriminant about what features we add as a result of making more product products more complicated, which has a negative impact on the user and navigate negative impact on the business. Um, and so that's the thing I worry about if it starts to become too easy, are we going to be. Too promiscuous in our, uh, kind of extension, adding product extensions and things like that. It's like, ah, why not add X, Y, Z or whatever back then it was like, oh, we only have so many engineering hours or story points or however you measure things. Uh, that least kept us in check a little bit. Yeah.Alessio [00:24:22]: And then over engineering, you're like, yeah, it's kind of like you're putting that on yourself. Yeah. Like now it's like the models don't understand that if they add too much complexity, it's going to come back to bite them later. Yep. So they just do whatever they want to do. Yeah. And I'm curious where in the workflow that's going to be, where it's like, Hey, this is like the amount of complexity and over-engineering you can do before you got to ask me if we should actually do it versus like do something else.Dharmesh [00:24:45]: So you know, we've already, let's like, we're leaving this, uh, in the code generation world, this kind of compressed, um, cycle time. Right. It's like, okay, we went from auto-complete, uh, in the GitHub co-pilot to like, oh, finish this particular thing and hit tab to a, oh, I sort of know your file or whatever. I can write out a full function to you to now I can like hold a bunch of the context in my head. Uh, so we can do app generation, which we have now with lovable and bolt and repletage. Yeah. Association and other things. So then the question is, okay, well, where does it naturally go from here? So we're going to generate products. Make sense. We might be able to generate platforms as though I want a platform for ERP that does this, whatever. And that includes the API's includes the product and the UI, and all the things that make for a platform. There's no nothing that says we would stop like, okay, can you generate an entire software company someday? Right. Uh, with the platform and the monetization and the go-to-market and the whatever. And you know, that that's interesting to me in terms of, uh, you know, what, when you take it to almost ludicrous levels. of abstract.swyx [00:25:39]: It's like, okay, turn it to 11. You mentioned vibe coding, so I have to, this is a blog post I haven't written, but I'm kind of exploring it. Is the junior engineer dead?Dharmesh [00:25:49]: I don't think so. I think what will happen is that the junior engineer will be able to, if all they're bringing to the table is the fact that they are a junior engineer, then yes, they're likely dead. But hopefully if they can communicate with carbon-based life forms, they can interact with product, if they're willing to talk to customers, they can take their kind of basic understanding of engineering and how kind of software works. I think that has value. So I have a 14-year-old right now who's taking Python programming class, and some people ask me, it's like, why is he learning coding? And my answer is, is because it's not about the syntax, it's not about the coding. What he's learning is like the fundamental thing of like how things work. And there's value in that. I think there's going to be timeless value in systems thinking and abstractions and what that means. And whether functions manifested as math, which he's going to get exposed to regardless, or there are some core primitives to the universe, I think, that the more you understand them, those are what I would kind of think of as like really large dots in your life that will have a higher gravitational pull and value to them that you'll then be able to. So I want him to collect those dots, and he's not resisting. So it's like, okay, while he's still listening to me, I'm going to have him do things that I think will be useful.swyx [00:26:59]: You know, part of one of the pitches that I evaluated for AI engineer is a term. And the term is that maybe the traditional interview path or career path of software engineer goes away, which is because what's the point of lead code? Yeah. And, you know, it actually matters more that you know how to work with AI and to implement the things that you want. Yep.Dharmesh [00:27:16]: That's one of the like interesting things that's happened with generative AI. You know, you go from machine learning and the models and just that underlying form, which is like true engineering, right? Like the actual, what I call real engineering. I don't think of myself as a real engineer, actually. I'm a developer. But now with generative AI. We call it AI and it's obviously got its roots in machine learning, but it just feels like fundamentally different to me. Like you have the vibe. It's like, okay, well, this is just a whole different approach to software development to so many different things. And so I'm wondering now, it's like an AI engineer is like, if you were like to draw the Venn diagram, it's interesting because the cross between like AI things, generative AI and what the tools are capable of, what the models do, and this whole new kind of body of knowledge that we're still building out, it's still very young, intersected with kind of classic engineering, software engineering. Yeah.swyx [00:28:04]: I just described the overlap as it separates out eventually until it's its own thing, but it's starting out as a software. Yeah.Alessio [00:28:11]: That makes sense. So to close the vibe coding loop, the other big hype now is MCPs. Obviously, I would say Cloud Desktop and Cursor are like the two main drivers of MCP usage. I would say my favorite is the Sentry MCP. I can pull in errors and then you can just put the context in Cursor. How do you think about that abstraction layer? Does it feel... Does it feel almost too magical in a way? Do you think it's like you get enough? Because you don't really see how the server itself is then kind of like repackaging theDharmesh [00:28:41]: information for you? I think MCP as a standard is one of the better things that's happened in the world of AI because a standard needed to exist and absent a standard, there was a set of things that just weren't possible. Now, we can argue whether it's the best possible manifestation of a standard or not. Does it do too much? Does it do too little? I get that, but it's just simple enough to both be useful and unobtrusive. It's understandable and adoptable by mere mortals, right? It's not overly complicated. You know, a reasonable engineer can put a stand up an MCP server relatively easily. The thing that has me excited about it is like, so I'm a big believer in multi-agent systems. And so that's going back to our kind of this idea of an atomic agent. So imagine the MCP server, like obviously it calls tools, but the way I think about it, so I'm working on my current passion project is agent.ai. And we'll talk more about that in a little bit. More about the, I think we should, because I think it's interesting not to promote the project at all, but there's some interesting ideas in there. One of which is around, we're going to need a mechanism for, if agents are going to collaborate and be able to delegate, there's going to need to be some form of discovery and we're going to need some standard way. It's like, okay, well, I just need to know what this thing over here is capable of. We're going to need a registry, which Anthropic's working on. I'm sure others will and have been doing directories of, and there's going to be a standard around that too. How do you build out a directory of MCP servers? I think that's going to unlock so many things just because, and we're already starting to see it. So I think MCP or something like it is going to be the next major unlock because it allows systems that don't know about each other, don't need to, it's that kind of decoupling of like Sentry and whatever tools someone else was building. And it's not just about, you know, Cloud Desktop or things like, even on the client side, I think we're going to see very interesting consumers of MCP, MCP clients versus just the chat body kind of things. Like, you know, Cloud Desktop and Cursor and things like that. But yeah, I'm very excited about MCP in that general direction.swyx [00:30:39]: I think the typical cynical developer take, it's like, we have OpenAPI. Yeah. What's the new thing? I don't know if you have a, do you have a quick MCP versus everything else? Yeah.Dharmesh [00:30:49]: So it's, so I like OpenAPI, right? So just a descriptive thing. It's OpenAPI. OpenAPI. Yes, that's what I meant. So it's basically a self-documenting thing. We can do machine-generated, lots of things from that output. It's a structured definition of an API. I get that, love it. But MCPs sort of are kind of use case specific. They're perfect for exactly what we're trying to use them for around LLMs in terms of discovery. It's like, okay, I don't necessarily need to know kind of all this detail. And so right now we have, we'll talk more about like MCP server implementations, but We will? I think, I don't know. Maybe we won't. At least it's in my head. It's like a back processor. But I do think MCP adds value above OpenAPI. It's, yeah, just because it solves this particular thing. And if we had come to the world, which we have, like, it's like, hey, we already have OpenAPI. It's like, if that were good enough for the universe, the universe would have adopted it already. There's a reason why MCP is taking office because marginally adds something that was missing before and doesn't go too far. And so that's why the kind of rate of adoption, you folks have written about this and talked about it. Yeah, why MCP won. Yeah. And it won because the universe decided that this was useful and maybe it gets supplanted by something else. Yeah. And maybe we discover, oh, maybe OpenAPI was good enough the whole time. I doubt that.swyx [00:32:09]: The meta lesson, this is, I mean, he's an investor in DevTools companies. I work in developer experience at DevRel in DevTools companies. Yep. Everyone wants to own the standard. Yeah. I'm sure you guys have tried to launch your own standards. Actually, it's Houseplant known for a standard, you know, obviously inbound marketing. But is there a standard or protocol that you ever tried to push? No.Dharmesh [00:32:30]: And there's a reason for this. Yeah. Is that? And I don't mean, need to mean, speak for the people of HubSpot, but I personally. You kind of do. I'm not smart enough. That's not the, like, I think I have a. You're smart. Not enough for that. I'm much better off understanding the standards that are out there. And I'm more on the composability side. Let's, like, take the pieces of technology that exist out there, combine them in creative, unique ways. And I like to consume standards. I don't like to, and that's not that I don't like to create them. I just don't think I have the, both the raw wattage or the credibility. It's like, okay, well, who the heck is Dharmesh, and why should we adopt a standard he created?swyx [00:33:07]: Yeah, I mean, there are people who don't monetize standards, like OpenTelemetry is a big standard, and LightStep never capitalized on that.Dharmesh [00:33:15]: So, okay, so if I were to do a standard, there's two things that have been in my head in the past. I was one around, a very, very basic one around, I don't even have the domain, I have a domain for everything, for open marketing. Because the issue we had in HubSpot grew up in the marketing space. There we go. There was no standard around data formats and things like that. It doesn't go anywhere. But the other one, and I did not mean to go here, but I'm going to go here. It's called OpenGraph. I know the term was already taken, but it hasn't been used for like 15 years now for its original purpose. But what I think should exist in the world is right now, our information, all of us, nodes are in the social graph at Meta or the professional graph at LinkedIn. Both of which are actually relatively closed in actually very annoying ways. Like very, very closed, right? Especially LinkedIn. Especially LinkedIn. I personally believe that if it's my data, and if I would get utility out of it being open, I should be able to make my data open or publish it in whatever forms that I choose, as long as I have control over it as opt-in. So the idea is around OpenGraph that says, here's a standard, here's a way to publish it. I should be able to go to OpenGraph.org slash Dharmesh dot JSON and get it back. And it's like, here's your stuff, right? And I can choose along the way and people can write to it and I can prove. And there can be an entire system. And if I were to do that, I would do it as a... Like a public benefit, non-profit-y kind of thing, as this is a contribution to society. I wouldn't try to commercialize that. Have you looked at AdProto? What's that? AdProto.swyx [00:34:43]: It's the protocol behind Blue Sky. Okay. My good friend, Dan Abramov, who was the face of React for many, many years, now works there. And he actually did a talk that I can send you, which basically kind of tries to articulate what you just said. But he does, he loves doing these like really great analogies, which I think you'll like. Like, you know, a lot of our data is behind a handle, behind a domain. Yep. So he's like, all right, what if we flip that? What if it was like our handle and then the domain? Yep. So, and that's really like your data should belong to you. Yep. And I should not have to wait 30 days for my Twitter data to export. Yep.Dharmesh [00:35:19]: you should be able to at least be able to automate it or do like, yes, I should be able to plug it into an agentic thing. Yeah. Yes. I think we're... Because so much of our data is... Locked up. I think the trick here isn't that standard. It is getting the normies to care.swyx [00:35:37]: Yeah. Because normies don't care.Dharmesh [00:35:38]: That's true. But building on that, normies don't care. So, you know, privacy is a really hot topic and an easy word to use, but it's not a binary thing. Like there are use cases where, and we make these choices all the time, that I will trade, not all privacy, but I will trade some privacy for some productivity gain or some benefit to me that says, oh, I don't care about that particular data being online if it gives me this in return, or I don't mind sharing this information with this company.Alessio [00:36:02]: If I'm getting, you know, this in return, but that sort of should be my option. I think now with computer use, you can actually automate some of the exports. Yes. Like something we've been doing internally is like everybody exports their LinkedIn connections. Yep. And then internally, we kind of merge them together to see how we can connect our companies to customers or things like that.Dharmesh [00:36:21]: And not to pick on LinkedIn, but since we're talking about it, but they feel strongly enough on the, you know, do not take LinkedIn data that they will block even browser use kind of things or whatever. They go to great, great lengths, even to see patterns of usage. And it says, oh, there's no way you could have, you know, gotten that particular thing or whatever without, and it's, so it's, there's...swyx [00:36:42]: Wasn't there a Supreme Court case that they lost? Yeah.Dharmesh [00:36:45]: So the one they lost was around someone that was scraping public data that was on the public internet. And that particular company had not signed any terms of service or whatever. It's like, oh, I'm just taking data that's on, there was no, and so that's why they won. But now, you know, the question is around, can LinkedIn... I think they can. Like, when you use, as a user, you use LinkedIn, you are signing up for their terms of service. And if they say, well, this kind of use of your LinkedIn account that violates our terms of service, they can shut your account down, right? They can. And they, yeah, so, you know, we don't need to make this a discussion. By the way, I love the company, don't get me wrong. I'm an avid user of the product. You know, I've got... Yeah, I mean, you've got over a million followers on LinkedIn, I think. Yeah, I do. And I've known people there for a long, long time, right? And I have lots of respect. And I understand even where the mindset originally came from of this kind of members-first approach to, you know, a privacy-first. I sort of get that. But sometimes you sort of have to wonder, it's like, okay, well, that was 15, 20 years ago. There's likely some controlled ways to expose some data on some member's behalf and not just completely be a binary. It's like, no, thou shalt not have the data.swyx [00:37:54]: Well, just pay for sales navigator.Alessio [00:37:57]: Before we move to the next layer of instruction, anything else on MCP you mentioned? Let's move back and then I'll tie it back to MCPs.Dharmesh [00:38:05]: So I think the... Open this with agent. Okay, so I'll start with... Here's my kind of running thesis, is that as AI and agents evolve, which they're doing very, very quickly, we're going to look at them more and more. I don't like to anthropomorphize. We'll talk about why this is not that. Less as just like raw tools and more like teammates. They'll still be software. They should self-disclose as being software. I'm totally cool with that. But I think what's going to happen is that in the same way you might collaborate with a team member on Slack or Teams or whatever you use, you can imagine a series of agents that do specific things just like a team member might do, that you can delegate things to. You can collaborate. You can say, hey, can you take a look at this? Can you proofread that? Can you try this? You can... Whatever it happens to be. So I think it is... I will go so far as to say it's inevitable that we're going to have hybrid teams someday. And what I mean by hybrid teams... So back in the day, hybrid teams were, oh, well, you have some full-time employees and some contractors. Then it was like hybrid teams are some people that are in the office and some that are remote. That's the kind of form of hybrid. The next form of hybrid is like the carbon-based life forms and agents and AI and some form of software. So let's say we temporarily stipulate that I'm right about that over some time horizon that eventually we're going to have these kind of digitally hybrid teams. So if that's true, then the question you sort of ask yourself is that then what needs to exist in order for us to get the full value of that new model? It's like, okay, well... You sort of need to... It's like, okay, well, how do I... If I'm building a digital team, like, how do I... Just in the same way, if I'm interviewing for an engineer or a designer or a PM, whatever, it's like, well, that's why we have professional networks, right? It's like, oh, they have a presence on likely LinkedIn. I can go through that semi-structured, structured form, and I can see the experience of whatever, you know, self-disclosed. But, okay, well, agents are going to need that someday. And so I'm like, okay, well, this seems like a thread that's worth pulling on. That says, okay. So I... So agent.ai is out there. And it's LinkedIn for agents. It's LinkedIn for agents. It's a professional network for agents. And the more I pull on that thread, it's like, okay, well, if that's true, like, what happens, right? It's like, oh, well, they have a profile just like anyone else, just like a human would. It's going to be a graph underneath, just like a professional network would be. It's just that... And you can have its, you know, connections and follows, and agents should be able to post. That's maybe how they do release notes. Like, oh, I have this new version. Whatever they decide to post, it should just be able to... Behave as a node on the network of a professional network. As it turns out, the more I think about that and pull on that thread, the more and more things, like, start to make sense to me. So it may be more than just a pure professional network. So my original thought was, okay, well, it's a professional network and agents as they exist out there, which I think there's going to be more and more of, will kind of exist on this network and have the profile. But then, and this is always dangerous, I'm like, okay, I want to see a world where thousands of agents are out there in order for the... Because those digital employees, the digital workers don't exist yet in any meaningful way. And so then I'm like, oh, can I make that easier for, like... And so I have, as one does, it's like, oh, I'll build a low-code platform for building agents. How hard could that be, right? Like, very hard, as it turns out. But it's been fun. So now, agent.ai has 1.3 million users. 3,000 people have actually, you know, built some variation of an agent, sometimes just for their own personal productivity. About 1,000 of which have been published. And the reason this comes back to MCP for me, so imagine that and other networks, since I know agent.ai. So right now, we have an MCP server for agent.ai that exposes all the internally built agents that we have that do, like, super useful things. Like, you know, I have access to a Twitter API that I can subsidize the cost. And I can say, you know, if you're looking to build something for social media, these kinds of things, with a single API key, and it's all completely free right now, I'm funding it. That's a useful way for it to work. And then we have a developer to say, oh, I have this idea. I don't have to worry about open AI. I don't have to worry about, now, you know, this particular model is better. It has access to all the models with one key. And we proxy it kind of behind the scenes. And then expose it. So then we get this kind of community effect, right? That says, oh, well, someone else may have built an agent to do X. Like, I have an agent right now that I built for myself to do domain valuation for website domains because I'm obsessed with domains, right? And, like, there's no efficient market for domains. There's no Zillow for domains right now that tells you, oh, here are what houses in your neighborhood sold for. It's like, well, why doesn't that exist? We should be able to solve that problem. And, yes, you're still guessing. Fine. There should be some simple heuristic. So I built that. It's like, okay, well, let me go look for past transactions. You say, okay, I'm going to type in agent.ai, agent.com, whatever domain. What's it actually worth? I'm looking at buying it. It can go and say, oh, which is what it does. It's like, I'm going to go look at are there any published domain transactions recently that are similar, either use the same word, same top-level domain, whatever it is. And it comes back with an approximate value, and it comes back with its kind of rationale for why it picked the value and comparable transactions. Oh, by the way, this domain sold for published. Okay. So that agent now, let's say, existed on the web, on agent.ai. Then imagine someone else says, oh, you know, I want to build a brand-building agent for startups and entrepreneurs to come up with names for their startup. Like a common problem, every startup is like, ah, I don't know what to call it. And so they type in five random words that kind of define whatever their startup is. And you can do all manner of things, one of which is like, oh, well, I need to find the domain for it. What are possible choices? Now it's like, okay, well, it would be nice to know if there's an aftermarket price for it, if it's listed for sale. Awesome. Then imagine calling this valuation agent. It's like, okay, well, I want to find where the arbitrage is, where the agent valuation tool says this thing is worth $25,000. It's listed on GoDaddy for $5,000. It's close enough. Let's go do that. Right? And that's a kind of composition use case that in my future state. Thousands of agents on the network, all discoverable through something like MCP. And then you as a developer of agents have access to all these kind of Lego building blocks based on what you're trying to solve. Then you blend in orchestration, which is getting better and better with the reasoning models now. Just describe the problem that you have. Now, the next layer that we're all contending with is that how many tools can you actually give an LLM before the LLM breaks? That number used to be like 15 or 20 before you kind of started to vary dramatically. And so that's the thing I'm thinking about now. It's like, okay, if I want to... If I want to expose 1,000 of these agents to a given LLM, obviously I can't give it all 1,000. Is there some intermediate layer that says, based on your prompt, I'm going to make a best guess at which agents might be able to be helpful for this particular thing? Yeah.Alessio [00:44:37]: Yeah, like RAG for tools. Yep. I did build the Latent Space Researcher on agent.ai. Okay. Nice. Yeah, that seems like, you know, then there's going to be a Latent Space Scheduler. And then once I schedule a research, you know, and you build all of these things. By the way, my apologies for the user experience. You realize I'm an engineer. It's pretty good.swyx [00:44:56]: I think it's a normie-friendly thing. Yeah. That's your magic. HubSpot does the same thing.Alessio [00:45:01]: Yeah, just to like quickly run through it. You can basically create all these different steps. And these steps are like, you know, static versus like variable-driven things. How did you decide between this kind of like low-code-ish versus doing, you know, low-code with code backend versus like not exposing that at all? Any fun design decisions? Yeah. And this is, I think...Dharmesh [00:45:22]: I think lots of people are likely sitting in exactly my position right now, coming through the choosing between deterministic. Like if you're like in a business or building, you know, some sort of agentic thing, do you decide to do a deterministic thing? Or do you go non-deterministic and just let the alum handle it, right, with the reasoning models? The original idea and the reason I took the low-code stepwise, a very deterministic approach. A, the reasoning models did not exist at that time. That's thing number one. Thing number two is if you can get... If you know in your head... If you know in your head what the actual steps are to accomplish whatever goal, why would you leave that to chance? There's no upside. There's literally no upside. Just tell me, like, what steps do you need executed? So right now what I'm playing with... So one thing we haven't talked about yet, and people don't talk about UI and agents. Right now, the primary interaction model... Or they don't talk enough about it. I know some people have. But it's like, okay, so we're used to the chatbot back and forth. Fine. I get that. But I think we're going to move to a blend of... Some of those things are going to be synchronous as they are now. But some are going to be... Some are going to be async. It's just going to put it in a queue, just like... And this goes back to my... Man, I talk fast. But I have this... I only have one other speed. It's even faster. So imagine it's like if you're working... So back to my, oh, we're going to have these hybrid digital teams. Like, you would not go to a co-worker and say, I'm going to ask you to do this thing, and then sit there and wait for them to go do it. Like, that's not how the world works. So it's nice to be able to just, like, hand something off to someone. It's like, okay, well, maybe I expect a response in an hour or a day or something like that.Dharmesh [00:46:52]: In terms of when things need to happen. So the UI around agents. So if you look at the output of agent.ai agents right now, they are the simplest possible manifestation of a UI, right? That says, oh, we have inputs of, like, four different types. Like, we've got a dropdown, we've got multi-select, all the things. It's like back in HTML, the original HTML 1.0 days, right? Like, you're the smallest possible set of primitives for a UI. And it just says, okay, because we need to collect some information from the user, and then we go do steps and do things. And generate some output in HTML or markup are the two primary examples. So the thing I've been asking myself, if I keep going down that path. So people ask me, I get requests all the time. It's like, oh, can you make the UI sort of boring? I need to be able to do this, right? And if I keep pulling on that, it's like, okay, well, now I've built an entire UI builder thing. Where does this end? And so I think the right answer, and this is what I'm going to be backcoding once I get done here, is around injecting a code generation UI generation into, the agent.ai flow, right? As a builder, you're like, okay, I'm going to describe the thing that I want, much like you would do in a vibe coding world. But instead of generating the entire app, it's going to generate the UI that exists at some point in either that deterministic flow or something like that. It says, oh, here's the thing I'm trying to do. Go generate the UI for me. And I can go through some iterations. And what I think of it as a, so it's like, I'm going to generate the code, generate the code, tweak it, go through this kind of prompt style, like we do with vibe coding now. And at some point, I'm going to be happy with it. And I'm going to hit save. And that's going to become the action in that particular step. It's like a caching of the generated code that I can then, like incur any inference time costs. It's just the actual code at that point.Alessio [00:48:29]: Yeah, I invested in a company called E2B, which does code sandbox. And they powered the LM arena web arena. So it's basically the, just like you do LMS, like text to text, they do the same for like UI generation. So if you're asking a model, how do you do it? But yeah, I think that's kind of where.Dharmesh [00:48:45]: That's the thing I'm really fascinated by. So the early LLM, you know, we're understandably, but laughably bad at simple arithmetic, right? That's the thing like my wife, Normies would ask us, like, you call this AI, like it can't, my son would be like, it's just stupid. It can't even do like simple arithmetic. And then like we've discovered over time that, and there's a reason for this, right? It's like, it's a large, there's, you know, the word language is in there for a reason in terms of what it's been trained on. It's not meant to do math, but now it's like, okay, well, the fact that it has access to a Python interpreter that I can actually call at runtime, that solves an entire body of problems that it wasn't trained to do. And it's basically a form of delegation. And so the thought that's kind of rattling around in my head is that that's great. So it's, it's like took the arithmetic problem and took it first. Now, like anything that's solvable through a relatively concrete Python program, it's able to do a bunch of things that I couldn't do before. Can we get to the same place with UI? I don't know what the future of UI looks like in a agentic AI world, but maybe let the LLM handle it, but not in the classic sense. Maybe it generates it on the fly, or maybe we go through some iterations and hit cache or something like that. So it's a little bit more predictable. Uh, I don't know, but yeah.Alessio [00:49:48]: And especially when is the human supposed to intervene? So, especially if you're composing them, most of them should not have a UI because then they're just web hooking to somewhere else. I just want to touch back. I don't know if you have more comments on this.swyx [00:50:01]: I was just going to ask when you, you said you got, you're going to go back to code. What
Chapters 00:00 Introduction and Show Branding03:03 Bruce's Journey into Domaining05:54 Outbound Marketing Strategies09:02 Niche Focus in Domaining11:52 Understanding Client Needs14:55 Outbounding Process and Tools17:56 Email and SMS Outreach Techniques21:08 Managing Domain Portfolio24:01 Negotiation Tactics in Sales27:05 Consistency and Discipline in Domaining29:58 Final Thoughts and Industry Insights41:22 The Dream of Trading Domains42:00 AI Tools Revolutionizing Domain Marketing45:32 Building Value with AI and Domain Names50:03 The Power of Outbound Marketing56:05 SEO and AI: A New Era for Domains01:00:14 ICANN Changes and Market Liquidity01:08:01 GoDaddy's Self Brokerage Launch01:15:10 Building User-Centric Features01:20:30 Domain Review and Feedback01:34:45 Insights on Domain Investment Strategies Check out $5 .com Fridays, $1 .xyz Wednesdays, and $5.52 .com transfers for up to $11000 in discounts. Only at https://unstoppabledomains.com
At the APRICOT/APNIC59 meeting held in Petaling Jaya in Malaysia last month, The internet society held it's first PIMF meeting. PIMF, or the Pulse Internet Measurement Forum is a gathering of people interested in Internet measurement in the widest possible sense, from technical information all the way to policy, governance and social questions. ISOC is interested in creating a space for the discussion to take place amongst the community, and bring both technologists and policy specialists into the same room. This time on PING, instead of the usual one-on-one format of podcast we've got 5 interviews from this meeting, and after the next episode from Geoff Huston at APNIC Labs we'll play a second part, with 3 more of the presenters from this session. First up we have Amreesh Phokeer from the Internet Society who manages the PULSE activity in ISOC, and along with Robbie Mitchell set up the meeting. Then we hear from Christoph Visser from IIJ Labs in Tokyo, who presented on his measurements of the "Steam" Game distribution platform used by Valve Software to share games. It's a complex system of application-specific source selection, using multiple Content Distribution Networks (CDN) to scale across the world, and allows Christoph to see into the link quality from a public API. No extra measurements required, for an insight into the gamer community and their experience of the Internet. The third interview is with Anand Raje, from AIORI-IMN, India's Indigenous Internet Measurement System. Anand leads a team which has built out a national measurement system using IoT "orchestration" methods to manage probes and anchors, in a virtual-environment which permits them to run multiple independent measurement systems hosted inside their platform. After this there's an interview with Andre Robachevsky from Global Cyber Alliance (GCA). Andre established the MANRS system, it's platform and nurtured the organisation into being inside ISOC. MANRS has now moved into the care of GCA and Andre moved with it, and discusses how this complements the existing GCA activities. FInally we have a conversation with Champika Wijayatunga from ICANN on the KINDNS project. This is a programme designed to bring MANRS-like industry best practice to the DNS community at large, including authoritative DNS delegates and the intermediate resolver and client supporting stub resolver operators. Champika is interested in reaching into the community to get KINDNS more widely understood and encourage its adoption with over 2,000 entities having completed the assessment process already. Next time we'll here from three more participants in the PIMF session: Doug Madory from Kentik, Beau Gieskins from APNIC Information Products, and Lia Hestina, from the RIPE NCC.
What I learned at ICANN82 in Seattle. The domain name industry gathered in Seattle last week for ICANN's annual community forum. During the show, I caught up on what's happening with two important topics: Adsense for Domains and new top level domains. On today's show I recap what I learned. You will then hear from […] Post link: ICANN82 Recap – DNW Podcast #526 © DomainNameWire.com 2025. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.
In today's episode, Shawn O'Malley (@Shawn_OMalley_) breaks down VeriSign, a company that underpins the functioning of the internet. VeriSign acts like a toll road, collecting fees from anyone using website domains ending in .com or .net, in exchange for managing the global domain registry system and making these domains accessible. VeriSign is a fascinating company with the fifth-highest profit margins in the S&P 500, and its shares have been increasingly snapped up by Berkshire Hathaway of late, which has become its largest shareholder. You'll learn how VeriSign was granted its monopoly, how it supports internet infrastructure, and whether the stock is attractively valued, plus so much more! Prefer to watch? Click here to watch this episode on YouTube. IN THIS EPISODE, YOU'LL LEARN 00:00 - Intro 02:29 - How VeriSign sits at the foundation of the world's internet. 07:22 - Why VeriSign is legally permitted to have a monopoly over the .com & .net website domains. 08:40 - How VeriSign is like a toll road by getting paid by any website ending in .com. 12:29 - What VeriSign does with its ample cash flows. 13:34 - How domain registration works and how VeriSign relies on sites like GoDaddy to drive more domain registrations. 13:44 - Why VeriSign's monopoly likely isn't going anywhere. 32:26 - The biggest risks, from cyberattacks to terrorism, threatening the company's operations. 45:39 - How to think about the company's intrinsic value and how expected returns fluctuate based on your purchase price per share. 51:15 - Whether Shawn adds VeriSign to The Intrinsic Value Portfolio. *Disclaimer: Slight timestamp discrepancies may occur due to podcast platform differences. BOOKS AND RESOURCES Join the exclusive TIP Mastermind Community to engage in meaningful stock investing discussions with Kyle and the other community members. Get smarter about valuing businesses in just a few minutes each week through our newsletter, The Intrinsic Value Newsletter. Check out our discussion of VeriSign in the Q1 2025 Mastermind episode on We Study Billionaires | YouTube Video. Value Investors Club pitch for VRSN. Read the article on Berkshire's acquisitions of VRSN shares. The difference between ICANN and VeriSign, explained. Explore Myths & facts about VeriSign. See here on how to attend the 2025 Berkshire Hathaway shareholder's meeting and meet-ups with The Investor's Podcast Network Check out the books mentioned in the podcast here. Enjoy ad-free episodes when you subscribe to our Premium Feed. NEW TO THE SHOW? Follow our official social media accounts: X (Twitter) | LinkedIn | Instagram | Facebook | TikTok. Browse through all our episodes (complete with transcripts) here. Try Shawn's favorite tool for picking stock winners and managing our portfolios: TIP Finance. Enjoy exclusive perks from our favorite Apps and Services. Learn how to better start, manage, and grow your business with the best business podcasts. SPONSORS Support our free podcast by supporting our sponsors: Netsuite TurboTax Public Airbnb Connect with Shawn: Twitter | LinkedIn | Email HELP US OUT! Help us reach new listeners by leaving us a rating and review on Spotify! It takes less than 30 seconds and really helps our show grow, which allows us to bring on even better guests for you all! Thank you – we really appreciate it! Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://theinvestorspodcastnetwork.supportingcast.fm
Heather Florio is the second-generation owner and CEO of Desert Harvest, a company pioneering sustainable solutions in pelvic and sexual health. Recognized by Authority Magazine as one of the Top 50 Women in Wellness and featured in Forbes as a top woman in business, Heather has spent over 30 years driving innovation in the industry.Under her leadership, Desert Harvest has transformed pelvic healthcare, funding medical research, launching science-backed products, and advocating for those suffering in silence. As a pelvic health specialist and "Sexpert," Heather shares her expertise globally, speaking on panels and at conferences to raise awareness about chronic pelvic health issues.In This Conversation We Discuss:[00:14] Intro[01:09] Developing products that align with brand mission[01:30] Identifying market gaps through personal experience[03:26] Building a business where people find their niche[04:53] Following Ecommerce industry shifts to stay ahead[06:45] Partnering with nonprofits for awareness [08:57] Evolving a brand's online presence over decades[10:35] Selling online before Ecommerce platforms existed[12:00] Struggling with early web design tools [13:59] Navigating regulatory changes in Ecommerce[15:28] Episode sponsors: StoreTester and Intelligems [18:40] Using AI for customer acquisition & targeting[20:18] Optimizing for AI-driven recommendations[21:10] Adapting to AI-driven consumer research[25:41] Building consumer trust through education[27:01] Creating a brand connection that lastsResources:Subscribe to Honest Ecommerce on YoutubeScientifically studied, all-natural supplements and skincare desertharvest.com/Follow Heather Florio linkedin.com/in/heather-florio-468822a4Book a demo today at intelligems.io/Done-for-you conversion rate optimization service storetester.com/If you're enjoying the show, we'd love it if you left Honest Ecommerce a review on Apple Podcasts. It makes a huge impact on the success of the podcast, and we love reading every one of your reviews!
If anyone should be anointed “aunt” or “court jEsther” of the tech industry, it's long time journalist, investor and philanthropist Esther Dyson. When I caught up with Dyson at DLD, she reflected on her 40+ year career in technology and her evolution from tech industry observer to wellness advocate. Her aunt/court jester" role, she explains, is to provide honest feedback to the tech powers-that-be while maintaining independence. In this role, Dyson expresses concern about society's vulnerability to "information diabetes" - addictive content that, like processed food, provides short-term pleasure but long-term harm. She details her work with Wellville, a 10-year project focused on community health and resilience, and explains her upcoming book "Term Limits," which argues for the importance of knowing when to pass the torch rather than trying to live or serve forever. Dyson - who, between 2008 and 2009 lived in Star City outside Moscow, Russia and trained as a backup cosmonaut - also shares her unique insights about Russia's descent into authoritarianism and the privatization of space travel.ESTHER DYSON is an investor, journalist, author, businesswoman, commentator, and philanthropist. She is a leading angel investor focused on health care, open government, digital technology, biotechnology, and outer space. She is chairman of EDventure Holdings and executive founder of Wellville, a ten-year project to show the long-term value, both social and financial, of investing in health. Overall, she is fascinated by new business models, new technologies and new markets (both economically and politically). From October 2008 to March of 2009, she lived in Star City outside Moscow, Russia, training as a backup cosmonaut. Apart from this brief sabbatical, she is an active board member for a variety of startups. She has a BA in economics from Harvard and was founding chairman of ICANN from 1998 to 2000. In addition, she wrote the bestselling, widely translated book Release 2.0: A Design for Living in the Digital Age.Named as one of the "100 most connected men" by GQ magazine, Andrew Keen is amongst the world's best known broadcasters and commentators. In addition to presenting KEEN ON, he is the host of the long-running How To Fix Democracy show. He is also the author of four prescient books about digital technology: CULT OF THE AMATEUR, DIGITAL VERTIGO, THE INTERNET IS NOT THE ANSWER and HOW TO FIX THE FUTURE. Andrew lives in San Francisco, is married to Cassandra Knight, Google's VP of Litigation & Discovery, and has two grown children.Keen On is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit keenon.substack.com/subscribe
Paul Frazee is the CTO of Bluesky. He previously worked on the Beaker browser and the peer-to-peer social media protocol Secure Scuttlebutt. Paul discusses how Bluesky and ATProto got started, scaling up a social media site, what makes ATProto decentralized, lessons ATProto learned from previous peer-to-peer projects, and the challenges of content moderation. Episode transcript available here. My Bluesky profile. -- Related Links Bluesky ATProtocol ATProto for distributed systems engineers Bluesky and the AT Protocol: Usable Decentralized Social Media Decentralized Identifiers (DIDs) ActivityPub Webfinger Beaker web browser Secure Scuttlebutt -- Transcript You can help correct transcripts on GitHub. [00:00:00] Jeremy: Today I am talking to Paul Frazee. He's the current CTO of bluesky, and he previously worked on other decentralized applications like Beaker and Secure Scuttlebutt. [00:00:15] Paul: Thanks for having me. What's bluesky [00:00:16] Jeremy: For people who aren't familiar with bluesky, what is it? [00:00:20] Paul: So bluesky is an open social network, simplest way to put it, designed in particular for high scale. That's kind of one of the big requirements that we had when we were moving into it. and it is really geared towards making sure that the operation of the social network is open amongst multiple different organizations. [00:00:44] So we're one of the operators, but other folks can come in, spin up the software, all the open source software, and essentially have a full node with a full copy of the network active users and have their users join into our network. And they all work functionally as one shared application. [00:01:03] Jeremy: So it, it sounds like it's similar to Twitter but instead of there being one Twitter, there could be any number and there is part of the underlying protocol that allows them to all connect to one another and act as one system. [00:01:21] Paul: That's exactly right. And there's a metaphor we use a lot, which is comparing to the web and search engines, which actually kind of matches really well. Like when you use Bing or Google, you're searching the same web. So on the AT protocol on bluesky, you use bluesky, you use some alternative client or application, all the same, what we're we call it, the atmosphere, all one shared network, [00:01:41] Jeremy: And more than just the, the client. 'cause I think sometimes when people think of a client, they'll think of, I use a web browser. I could use Chrome or Firefox, but ultimately I'm connecting to the same thing. But it's not just people running alternate clients, right? [00:01:57] Paul: Their own full backend to it. That's right. Yeah. Yeah. The anchoring point on that being the fire hose of data that runs the entire thing is open as well. And so you start up your own application, you spin up a service that just pipes into that fire hose and taps into all the activity. History of AT Protocol [00:02:18] Jeremy: Talking about this underlying protocol maybe we could start where this all began so people get some context for where this all came from. [00:02:28] Paul: For sure. All right, so let's wind the clock back here in my brain. We started out 2022, right at the beginning of the year. We were formed as a, essentially a consulting company outside of Twitter with a contract with Twitter. And, uh, our goal was to build a protocol that could run, uh, Twitter, much like the way that we just described, which set us up with a couple of pretty specific requirements. [00:02:55] For one, we had to make sure that it could scale. And so that ended up being a really important first requirement. and we wanted to make sure that there was a strong kind of guarantees that the network doesn't ever get captured by any one operator. The idea was that Twitter would become the first, uh, adopter of the technology. [00:03:19] Other applications, other services would begin to take advantage of it and users would be able to smoothly migrate their accounts in between one or the other at any time. Um, and it's really, really anchored in a particular goal of just deconstructing monopolies. Getting rid of those moats that make it so that there's a kind of a lack of competition, uh, between these things. [00:03:44] And making sure that, if there was some kind of reason that you decided you're just not happy with what direction this service has been going, you move over to another one. You're still in touch with all the folks you were in touch with before. You don't lose your data. You don't lose your, your your follows. Those were the kind of initial requirements that we set out with. The team by and large came from, the decentralized web, movement, which is actually a pretty, large community that's been around since, I wanna say around 2012 is when we first kind of started to form. It got really made more specifically into a community somewhere around 2015 or 16, I wanna say. [00:04:23] When the internet archives started to host conferences for us. And so that gave us kind of a meeting point where all started to meet up there's kind of three schools of thought within that movement. There was the blockchain community, the, federation community, and the peer-to-peer community. [00:04:43] And so blockchain, you don't need to explain that one. You got Federation, which was largely ActivityPub Mastodon. And then peer-to-peer was IPFS, DAT protocol, um, secure scuttlebutt. But, those kinds of BitTorrent style of technologies really they were all kind of inspired by that. [00:05:02] So these three different kind of sub communities we're all working, independently on different ways to attack how to make these open applications. How do you get something that's a high scale web application without one corporation being the only operator? When this team came together in 2022, we largely sourced from the peer-to-peer group of the decentralized community. Scaling limitations of peer-to-peer [00:05:30] Paul: Personally, I've been working in the space and on those kinds of technologies for about 10 years at that stage. And, the other folks that were in there, you know, 5-10 each respectively. So we all had a fair amount of time working on that. And we had really kind of hit some of the limitations of doing things entirely using client devices. We were running into challenges about reliability of connections. Punching holes to the individual device is very hard. Synchronizing keys between the devices is very hard. Maintaining strong availability of the data because people's devices are going off and on, things like that. Even when you're using the kind of BitTorrent style of shared distribution, that becomes a challenge. [00:06:15] But probably the worst challenge was quite simply scale. You need to be able to create aggregations of a lot of behavior even when you're trying to model your application as largely peer wise interactions like messaging. You might need an aggregation of accounts that even exist, how do you do notifications reliably? [00:06:37] Things like that. Really challenging. And what I was starting to say to myself by the end of that kind of pure peer-to-peer stent was that it can't be rocket science to do a comment section. You know, like at some point you just ask yourself like, how, how hard are we willing to work to, to make these ideas work? [00:06:56] But, there were some pretty good pieces of tech that did come out of the peer-to-peer world. A lot of it had to do with what I might call a cryptographic structure. things like Merkel trees and advances within Merkel Trees. Ways to take data sets and reduce them down to hashes so that you can then create nice signatures and have signed data sets at rest at larger scales. [00:07:22] And so our basic thought was, well, all right, we got some pretty good tech out of this, but let's drop that requirement that it all run off of devices. And let's get some servers in there. And instead think of the entire network as a peer-to-peer mesh of servers. That's gonna solve your scale problem. [00:07:38] 'cause you can throw big databases at it. It's gonna solve your availability problems, it's gonna solve your device sync problems. But you get a lot of the same properties of being able to move data sets between services. Much like you could move them between devices in the peer-to-peer network without losing their identifiers because you're doing this in direction of, cryptographic identifiers to the current host. [00:08:02] That's what peer-to-peer is always doing. You're taking like a public key or hash and then you're asking the network, Hey, who has this? Well, if you just move that into the server, you get the same thing, that dynamic resolution of who's your active host. So you're getting that portability that we wanted real bad. [00:08:17] And then you're also getting that kind of in meshing of the different services where each of them is producing these data sets that they can sink from each other. So take peer-to-peer and apply it to the server stack. And that was our kind of initial thought of like, Hey, you know what? This might work. [00:08:31] This might solve the problems that we have. And a lot of the design fell out from that basic mentality. Crytographic identifiers and domain names [00:08:37] Jeremy: When you talk about these cryptographic identifiers, is the idea that anybody could have data about a person, like a message or a comment, and that could be hosted different places, but you would still know which person that originally came from. Is that, is that the goal there? [00:08:57] Paul: That's exactly it. Yeah. Yeah. You wanna create identification that supersedes servers, right? So when you think about like, if I'm using Twitter and I wanna know what your posts are, I go to twitter.com/jeremy, right? I'm asking Twitter and your ID is consequently always bound to Twitter. You're always kind of a second class identifier. [00:09:21] We wanted to boost up the user identifier to be kind of a thing freestanding on its own. I wanna just know what Jeremy's posts are. And then once you get into the technical system it'll be designed to figure out, okay, who knows that, who can answer that for you? And we use cryptographic identifiers internally. [00:09:41] So like all the data sets use these kind of long URLs to identify things. But in the application, the user facing part, we used domain names for people. Which I think gives the picture of how this all operates. It really moves the user accounts up into a free standing first class identifier within the system. [00:10:04] And then consequently, any application, whatever application you're using, it's really about whatever data is getting put into your account. And then that just exchanges between any application that anybody else is using. [00:10:14] Jeremy: So in this case, it sounds like the identifier is some long string that, I'm not sure if it's necessarily human readable or not. You're shaking your head no. [00:10:25] Paul: No. [00:10:26] Jeremy: But if you have that string, you know it's for a specific person. And since it's not really human readable, what you do is you put a layer on top of it which in this case is a domain that somebody can use to look up and find the identifier. [00:10:45] Paul: Yeah, yeah, yeah. So we just use DNS. Put a TXT record in there, map into that long string, or you could do a .well-known file on a web server if that's more convenient for you. And then the ID that's behind that, the non-human readable one, those are called DIDs which is actually a W3C spec. Those then map to a kind of a certificate. What you call a DID document that kind of confirms the binding by declaring what that domain name should be. So you get this bi-directional binding. And then that certificate also includes signing keys and active servers. So you pull down that certificate and that's how the discovery of the active server happens is through the DID system. What's stored on a PDS [00:11:29] Jeremy: So when you refer to an active server what is that server and what is that server storing? [00:11:35] Paul: It's kinda like a web server, but instead of hosting HTML, it's hosting a bunch of JSON records. Every user has their own document store of JSON documents. It's bucketed into collections. Whenever you're looking up somebody on the network you're gonna get access to that repository of data, jump into a collection. [00:11:58] This collection is their post collection. Get the rkey (Record Key), and then you're pulling out JSON at the end of it, which is just a structured piece of stuff saying here's the CreatedAt, here's the text, here's the type, things like that. One way you could look at the whole system is it's a giant, giant database network. Servers can change, signing keys change, but not DID [00:12:18] Jeremy: So if someone's going to look up someone's identifier, let's say they have the user's domain they have to go to some source, right? To find the user's data. You've mentioned, I think before, the idea that this is decentralized and by default I would, I would picture some kind of centralized resource where I send somebody a domain and then they give me back the identifier and the links to the servers. [00:12:46] So, so how does that work in practice where it actually can be decentralized? [00:12:51] Paul: I mentioned that your DID that non-human readable identifier, and that has that certificate attached to it that lists servers and signing keys and things like that. [00:13:00] So you're just gonna look up inside that DID document what that server is your data repository host. And then you contact that guy and say, all right, I'm told you're hosting this thing. Here's the person I'm looking for, hand over the hand over the data. It's really, you know, pretty straightforward. [00:13:18] The way that gets decentralized is by then to the fact that I could swap out that active server that's in my certificate and probably wanna rotate the signing keys 'cause I've just changed the, you know. I don't want to keep using the same signing keys as I was using previously because I just changed the authority. [00:13:36] So that's the migration change, change the hosting server, change out the signing keys. Somebody that's looking for me now, they're gonna load up my document, my DID document. They're gonna say, okay, new server, new keys. Pull down the data. Looks good, right? Matches up with the DID doc. [00:13:50] So that's how you get that level of portability. But when those changes happen, the DID doesn't change, right? The DID document changes. So there's the level of indirection there and that's pretty important because if you don't have a persistent identifier whenever you're trying to change out servers, all those backlinks are gonna break. [00:14:09] That's the kind of stuff that stops you from being able to do clean migrations on things like web-based services. the only real option is to go out and ask everybody to update their data. And when you're talking about like interactions on the social network, like people replying to each other, there's no chance, right? [00:14:25] Every time somebody moves you're gonna go back and modify all those records. You don't even control all the records from the top down 'cause they're hosted all over the web. So it's just, you can't do it. Generally we call this account portability, that you're kinda like phone number portability that you can change your host, but, so that part's portable, but the ID stays the same. [00:14:45] And keeping that ID the same is the real key to making sure that this can happen without breaking the whole system. [00:14:52] Jeremy: And so it, it sounds like there's the decentralized id, then there's the decentralized ID document that's associated with that points you to where the actual location of your, your data, your posts, your pictures and whatnot. but then you also mentioned that they could change servers. [00:15:13] So let's say somebody changes where their data is, is stored, that would change the servers, I guess, in their document. But [00:15:23] then how do all of these systems. Know okay. I need to change all these references to your old server, to these new servers, [00:15:32] Paul: Yeah. Well, the good news is that you only have to, you, you got the public data set of all the user's activity, and then you have like internal caches of where the current server is. You just gotta update those internal caches when you're trying to contact their server. Um, so it's actually a pretty minimal thing to just like update like, oh, they moved, just start talking to update my, my table, my Redis, that's holding onto that kind of temporary information, put it on ttl, that sort of thing. Most communication won't be between servers, it will be from event streams [00:16:01] Paul: And, honestly, in practice, a fair amount of the system for scalability reasons doesn't necessarily work by servers directly contacting each other. It's actually a little bit more like how, I told you before, I'm gonna use this metaphor a lot, the search engines with the web, right? What we do is we actually end up crawling the repositories that are out in the world and funneling them into event streams like a Kafka. And that allows the entire system to act like a data processing pipeline where you're just tapping into these event streams and then pushing those logs into databases that produce these large scale aggregations. [00:16:47] So a lot of the application behavior ends up working off of these event logs. If I reply to somebody, for instance, I don't necessarily, it's not, my server has to like talk to your server and say, Hey, I'm replying to you. What I do is I just publish a reply in my repository that gets shot out into the event logs, and then these aggregators pick up that the reply got created and just update their database with it. [00:17:11] So it's not that our hosting servers are constantly having to send messages with each other, you actually use these aggregators to pull together the picture of what's happening on the network. [00:17:22] Jeremy: Okay, so like you were saying, it's an event stream model where everybody publishes the events the things that they're doing, whether that's making a new post, making a reply, that's all being posted to this event stream. And then everybody who provides, I'm not sure if instances is the right term, but an implementation of the atmosphere protocol (Authenticated Transfer protocol). [00:17:53] They are listening for all those changes and they don't necessarily have to know that you moved servers because they're just listening for the events and you still have the same identifier. [00:18:10] Paul: Generally speaking. Yeah. 'cause like if you're listening to one of these event streams what you end up looking for is just the signature on it and making sure that the signature matches up. Because you're not actually having to talk to their live server. You're just listening to this relay that's doing this aggregation for you. [00:18:27] But I think actually to kind of give a little more clarity to what you're talking about, it might be a good idea to refocus how we're talking about the system here. I mentioned before that our goal was to make a high scale system, right? We need to handle a lot of data. If you're thinking about this in the way that Mastodon does it, the ActivityPub model, that's actually gonna give you the wrong intuition. Designing the protocol to match distributed systems practices (Event sourcing / Stream processing) [00:18:45] Paul: 'cause we chose a dramatically different system. What we did instead was we picked up, essentially the same practices you're gonna use for a data center, a high scale application data center, and said, all right, how do you tend to build these sorts of things? Well, what you're gonna do is you're gonna have, multiple different services running different purposes. [00:19:04] It gets pretty close to a microservices approach. You're gonna have a set of databases, and then you're going to, generally speaking for high scale, you're gonna have some kind of a kafka, some kind of a event log that you are tossing changes about the state of these databases into. And then you have a bunch of secondary systems that are tapping into the event log and processing that into, the large scale, databases like your search index, your, nice postgres of user profiles. [00:19:35] And that makes sure that you can get each of these different systems to perform really well at their particular task, and then you can detach them in their design. for instance, your primary storage can be just a key value store that scales horizontally. And then on the event log, you, you're using a Kafka that's designed to handle. [00:19:58] Particular semantics of making sure that the messages don't get dropped, that they come through at a particular throughput. And then you're using, for us, we're using like ScyllaDB for the big scale indexes that scales horizontally really well. So it's just different kind of profiles for different pieces. [00:20:13] If you read Martin Kleppman's book, data Intensive applications I think it's called or yeah. A lot of it gets captured there. He talks a lot about this kind of thing and it's sometimes called a kappa architecture is one way this is described, event sourcing is a similar term for it as well. [00:20:30] Stream processing. That's pretty standard practices for how you would build a traditional high scale service. so if you take, take this, this kind of microservice architecture and essentially say, okay, now imagine that each of the services that are a part of your data center could be hosted by anybody, not just within our data center, but outside of our data center as well and should be able to all work together. [00:20:57] Basically how the AT Proto is designed. We were talking about the data repository hosts. Those are just the primary data stores that they hold onto the user keys and they hold onto those JSON records. And then we have another service category we call Relay that just crawls those data repositories and sucks that in that fire hose of data we were talking about that event log. App views pull data from relay and produces indexes and threads [00:21:21] Paul: And then we have what we call app views that sit there and tail the index and tail the log, excuse me, and produce indexes off of it, they're listening to those events and then like, making threads like okay, that guy posted, that guy replied, that guy replied. [00:21:37] That's a thread. They assemble it into that form. So when you're running an application, you're talking to the AppView to read the network, and you're talking to the hosts to write to the network, and each of these different pieces sync up together in this open mesh. So we really took a traditional sort of data center model and just turned it inside out where each piece is a part of the protocol and communicate it with each other and therefore anybody can join into that mesh. [00:22:07] Jeremy: And to just make sure I am tracking the data repository is the data about the user. So it has your decentralized identifier, it has your replies, your posts, And then you have a relay, which is, its responsibility, is to somehow find all of those data repositories and collect them as they happen so that it can publish them to some kind of event stream. [00:22:41] And then you have the AppView which it's receiving messages from the relay as they happen, and then it can have its own store and index that for search. It can collect them in a way so that it can present them onto a UI. That's sort of thing that's the user facing part I suppose. [00:23:00] Paul: Yeah, that's exactly it. And again, it's, it's actually quite similar to how the web works. If you combine together the relay and the app view, you got all these different, you know, the web works where you got all these different websites, they're hosting their stuff, and then the search engine is going around, aggregating all that data and turning it into a search experience. [00:23:19] Totally the same model. It's just being applied to, more varieties of data, like structured data, like posts and, and replies, follows, likes, all that kinda stuff. And then instead of producing a search application at the end. I mean, it does that too, but it also produces a, uh, you know, timelines and threads and, um, people's profiles and stuff like that. [00:23:41] So it's actually a pretty bog standard way of doing, that's one of the models that we've seen work for large scale decentralized systems. And so we're just transposing it onto something that kind of is more focused towards social applications [00:23:58] Jeremy: So I think I'm tracking that the data repository itself, since it has your decentralized identifier and because the data is cryptographically signed, you know, it's from a specific user. I think the part that I am still not quite sure about is the relays. I, I understand if you run all the data repositories, you know where they are, so you know how to collect the data from them. [00:24:22] But if someone's running another system outside of your organization, how do they find, your data repositories? Or do they have to connect to your relay? What's the intention for that? Data hosts request relays to pull their data [00:24:35] Paul: That logic runs, again, really similar to how search engines find out about websites. So there is actually a way for, one of these, data hosts to contact Relay and say, Hey, I exist. You know, go ahead and get my stuff. And then it'll be up to the relay to decide like if they want it or not. [00:24:52] Right now, generally we're just like, yeah, you know, we, we want it. But as you can imagine, as the thing matures and gets to higher scale, there might be some trust kind of things to worry about, you know? So that's kind of the naive operation that currently exists. But over time as the network gets bigger and bigger, it'll probably involve some more traditional kind of spiraling behaviors because as more relays come into the system, each of these hosts, they're not gonna know who to talk to. Relays can bootstrap who they know about by talking to other relays [00:25:22] Paul: You're trying to start a new relay. What they're gonna do is they're going to discover all of the different users that exist in the system by looking at what data they have to start with. Probably involve a little bit of a manual feeding in at first, whenever I'm starting up a relay, like, okay, there's bluesky's relay. [00:25:39] Lemme just pull what they know. And then I go from there. And then anytime you discover a new user you don't have, you're like, oh, I wanna look them up. Pull them into the relay too. Right. So there's a, pretty straightforward, discovery process that you'll just have to bake into a relay to, to make sure you're calling as much the network as possible. ActivityPub federation vs AT Proto [00:25:57] Jeremy: And so I don't think we've defined the term federation, but maybe you could explain what that is and if that is what this is. [00:26:07] Paul: We are so unsure. [00:26:10] Jeremy: Okay. [00:26:11] Paul: Yeah. This has jammed is up pretty bad. Um, because I think everybody can, everybody pretty strongly agrees that ActivityPub is federation, right? and ActivityPub kind of models itself pretty similarly to email in a way, like the metaphors they use is that there's inboxes and outboxes and, and every ActivityPub server they're standing up the full vertical stack. [00:26:37] They set up, the primary hosting, the views of the data that's happening there. the interface for the application, all of it, pretty traditional, like close service, but then they're kind of using the perimeter. they're making that permeable by sending, exchanging, essentially mailing records to each other, right? [00:26:54] That's their kind of logic of how that works. And that's pretty much in line with, I think, what most people think of with Federation. Whereas what we're doing isn't like that we've cut, instead of having a bunch of vertical stacks communicating horizontally with each other, we kind of sliced in the other direction. [00:27:09] We sliced horizontally into, this microservices mesh and have all the different, like a total mix and match of different microservices between different operators. Is that federation? I don't know. Right. we tried to invent a term, didn't really work, you know, At the moment, we just kind of don't worry about it that much, see what happens, see what the world sort of has to say to us about it. [00:27:36] and beyond that, I don't know. [00:27:42] Jeremy: I think people probably are thinking of something like, say, a Mastodon instance when you're, when you're talking about everything being included, The webpage where you view the posts, the Postgres database that's keeping the messages. [00:28:00] And that same instance it's responsible for basically everything. [00:28:06] Paul: mm-Hmm [00:28:06] Jeremy: And I believe what you're saying is that the difference with, the authenticated transfer protocol, is that the [00:28:15] Paul: AT Protocol, Yep. [00:28:17] Jeremy: And the difference there is that you've, at the protocol level, you've split it up into the data itself, which can be validated completely separately from other parts of the system. [00:28:31] You could have the JSON files on your hard drive and somebody else can have that same JSON file and they would know that who the user is and that these are real things that user posted. That's like a separate part. And then the relay component that looks for all these different repositories that has people's data, that can also be its own independent thing where its job is just to output events. [00:29:04] And that can exist just by itself. It doesn't need the application part, the, the user facing part, it can just be this event stream on itself. and that's the part where it sounds like you can make decisions on who to, um, collect data from. I guess you have to agree that somebody can connect to you and get the users from your data repositories. [00:29:32] And likewise, other people that run relays, they also have to agree to let you pull the users from theirs. [00:29:38] Paul: Yeah, that's right. Yeah. [00:29:41] Jeremy: And so I think the Mastodon example makes sense. And, but I wonder if the underlying ActivityPub protocol forces you to use it in that way, in like a whole full application that talks to another full application. [00:29:55] Or is it more like that's just how people tend to use it and it's not necessarily a characteristic of the protocol. [00:30:02] Paul: Yeah, that's a good question actually. so, you know, generally what I would say is pretty core to the protocol is the expectations about how the services interact with each other. So the mailbox metaphor that's used in ActivityPub, that design, if I reply to you, I'll update my, local database with what I did, and then I'll send a message over to your server saying, Hey, by the way, add this reply. [00:30:34] I did this. And that's how they find out about things. That's how they find out about activity outside of their network. that's the part that as long as you're doing ActivityPub, I suspect you're gonna see reliably happening. That's that, I can say for sure that's a pretty tight requirement. [00:30:50] That's ActivityPub. If you wanted to split it up the way we're talking about, you could, I don't know, I don't know if you necessarily would want to. Because I don't know. That's actually, I think I'd have to dig into their stack a little bit more to see how meaningful that would be. I do know that there's some talk of introducing a similar kind of an aggregation method into the ActivityPub world which I believe they're also calling a relay and to make things even more complicated. [00:31:23] And NOSTR has a concept of a relay. So these are three different protocols that are using this term. I think you could do essentially what a search engine does on any of these things. You could go crawling around for the data, pull them into a fire hose, and then, tap into that aggregation to produce, bigger views of the network. [00:31:41] So that principle can certainly apply anywhere. AT Protocol, I think it's a little bit, we, we focused in so hard from that on that from the get go, we focus really hard on making sure that this, the data is, signed at rest. That's why it's called the authenticated transfer protocol. And that's a nice advantage to have when you're running a relay like this because it means that you don't have to trust the relay. [00:32:08] Like generally speaking, when I look at results from Google, you know, I'm trusting pretty well that they're accurately reflecting what's on the website, which is fine. You know, there's, that's not actually a huge risk or anything. But whenever you're trying to build entire applications and you're using somebody else's relay, you could really run into things where they say like, oh, you know what Paul tweeted the other day, you know, I hate dogs. [00:32:28] They're like, no, I didn't. That's a lie, right? You just sneak in Little lies like that over a while, it becomes a problem. So having the signatures on the data is pretty important. You know, if you're gonna be trying to get people to cooperate, uh, you gotta manage the trust model. I know that ActivityPub does have mechanisms for signed records. Issuers with ActivityPub identifiers [00:32:44] Paul: I don't know how deep they go if they could fully replace that, that utility. and then Mastodon ActivityPub, they also use a different identifier system that they're actually taking a look at DIDs um, right now, I don't know what's gonna happen there. We're, we're totally on board to, you know, give any kind of insight that we got working on 'em. [00:33:06] But at, at the moment, they use I think it's WebFinger based identifiers they look like emails. So you got host names in there and those identifiers are being used in the data records. So you don't get that continuous identifier. They actually do have to do that hey, I moved update your records sort of thing. [00:33:28] And that causes it to, I mean, it works like decently well, but not as well as it could. They got us to the point where it moves your profile over and you update all the folks that were following you so they can update their follow records, but your posts, they're not coming right, because that's too far into that mesh of interlinking records. [00:33:48] There's just no chance. So that's kind of the upper limit on that, it's a different set of choices and trade-offs. You're always kind of asking like, how important is the migration? Does that work out? Anyway, now I'm just kind of digging into differences between the two here. Issues with an identifier that changes and updating old records [00:34:07] Jeremy: So you were saying that with ActivityPub, all of the instances need to be notified that you've changed your identifier but then all of the messages that they had already received. They don't point to the new identifier somehow. [00:34:24] Paul: Yeah. You run into basically just the practicalities of actual engineering with that is what happens, right? Because if you imagine you got a multimillion user social network. They got all their posts. Maybe the user has like, let's say a thousand posts and 10,000 likes. And that, activity can range back three years. [00:34:48] Let's say they changed their identifier, and now you need to change the identifier of all those records. If you're in a traditional system that's already a tall order, you're going back and rewriting a ton of indexes, Anytime somebody replied to you, they have these links to your posts, they're now, you've gotta update the identifiers on all of those things. [00:35:11] You could end up with a pretty significant explosion of rewrites that would have to occur. Now that's, that's tough. If you're in a centralized model. If you're in a decentralized one, it's pretty much impossible because you're now, when you notify all the other servers like, Hey, this, this changed. How successful are all of them at actually updating that, that those, those pointers, it's a good chance that there's things are gonna fall out of correctness. that's just a reality of it. And if, so, if you've got a, if you've got a mutable identifier, you're in trouble for migrations. So the DID is meant to keep it permanent and that ends up being the anchoring point. If you lose control of your DID well, that's it. Managing signing keys by server, paper key reset [00:35:52] Paul: Your, your account's done. We took some pretty traditional approaches to that, uh, where the signing keys get managed by your hosting server instead of like trying to, this may seem like really obvious, but if you're from the decentralization community, we spend a lot of time with blockchains, like, Hey, how do we have the users hold onto their keys? [00:36:15] You know, and the tooling on that is getting better for what it's worth. We're starting to see a lot better key pair management in like Apple's ecosystem and Google's ecosystem, but it's still in the range of like, nah, people lose their keys, you know? So having the servers manage those is important. [00:36:33] Then we have ways of exporting paper keys so that you could kind of adversarially migrate if you wanted to. That was in the early spec we wanted to make sure that this portability idea works, that you can always migrate your accounts so you can export a paper key that can override. [00:36:48] And that was how we figured that out. Like, okay, yeah, we don't have to have everything getting signed by keys that are on the user's devices. We just need these master backup keys that can say, you know what? I'm done with that host. No matter what they say, I'm overriding what they, what they think. and that's how we squared that one. [00:37:06] Jeremy: So it seems like one of the big differences with account migration is that with ActivityPub, when you move to another instance, you have to actually change your identifier. [00:37:20] And with the AT protocol you're actually not allowed to ever change that identifier. And maybe what you're changing is just you have say, some kind of a lookup, like you were saying, you could use a domain name to look that up, get a reference to your decentralized identifier, but your decentralized identifier it can never change. [00:37:47] Paul: It, it, it can't change. Yeah. And it shouldn't need to, you know what I mean? It's really a total disaster kind of situation if that happens. So, you know that it's designed to make sure that doesn't happen in the applications. We use these domain name handles to, to identify folks. And you can change those anytime you want because that's really just a user facing thing. [00:38:09] You know, then in practice what you see pretty often is that you may, if you change hosts, if you're using, we, we give some domains to folks, you know, 'cause like not everybody has their own domain. A lot of people do actually, to our surprise, people actually kind of enjoy doing that. But, a lot of folks are just using like paul.bsky.social as their handle. [00:38:29] And so if you migrated off of that, you probably lose that. Like your, so your handle's gonna change, but you're not losing the followers and stuff. 'cause the internal system isn't using paul.bsky.social, it's using that DID and that DID stays the same. Benefits of domain names, trust signal [00:38:42] Jeremy: Yeah. I thought that was interesting about using the domain names, because when you like you have a lot of users, everybody's got their own sub-domain. You could have however many millions of users. Does that become, does that become an issue at some point? [00:39:00] Paul: Well, it's a funny thing. I mean like the number of users, like that's not really a problem 'cause you run into the same kind of namespace crowding problem that any service is gonna have, right? Like if you just take the subdomain part of it, like the name Paul, like yeah, only, you only get to have one paul.bsky.social. [00:39:15] so that part of like, in terms of the number of users, that part's fine I guess. Uh, as fine as ever. where gets more interesting, of course is like, really kind of around the usability questions. For one, it's, it's not exactly the prettiest to always have that B sky.social in there. If we, if we thought we, if we had some kind of solution to that, we would use it. [00:39:35] But like the reality is that, you know, now we're, we've committed to the domain name approach and some folks, you know, they kind of like, ah, that's a little bit ugly. And we're like, yeah that's life. I guess the plus side though is that you can actually use like TLD the domain. It's like on pfrazee.com. [00:39:53] that starts to get more fun. it can actually act as a pretty good trust signal in certain scenarios. for instance, well-known domain names like nytimes.com, strong authentication right there, we don't even need a blue check for it. Uh, similarly the .gov, domain name space is tightly regulated. [00:40:14] So you actually get a really strong signal out of that. Senator Wyden is one of our users and so he's, I think it's wyden.senate.gov and same thing, strong, you know, strong identity signal right there. So that's actually a really nice upside. So that's like positives, negatives. [00:40:32] That trust signal only works so far. If somebody were to make pfrazee.net, then that can be a bit confusing. People may not be paying attention to .com vs .net, so it's not, I don't wanna give the impression that, ah, we've solved blue checks. It's a complicated and multifaceted situation, but, it's got some juice. [00:40:54] It's also kinda nice too, 'cause a lot of folks that are doing social, they're, they've got other stuff that they're trying to promote, you know? I'm pretty sure that, uh, nytimes would love it if you went to their website. And so tying it to their online presence so directly like that is a really nice kind of feature of it. [00:41:15] And tells a I think a good story about what we're trying to do with an open internet where, yeah, everybody has their space on the internet where they can do whatever they want on that. And that's, and then thethese social profiles, it's that presence showing up in a shared space. It's all kind of part of the same thing. [00:41:34] And that that feels like a nice kind of thing to be chasing, you know? And it also kind of speaks well to the naming worked out for us. We chose AT Protocol as a name. You know, we back acronymed our way into that one. 'cause it was a @ simple sort of thing. But like, it actually ended up really reflecting the biggest part of it, which is that it's about putting people's identities at the front, you know, and make kind of promoting everybody from a second class identity that's underneath Twitter or Facebook or something like that. [00:42:03] Up into. Nope, you're freestanding. You exist as a person independently. Which is what a lot of it's about. [00:42:12] Jeremy: Yeah, I think just in general, not necessarily just for bluesky, if people had more of an interest in getting their own domain, that would be pretty cool if people could tie more of that to something you basically own, right? [00:42:29] I mean, I guess you're leasing it from ICANN or whatever, but, [00:42:33] yeah, rather than everybody having an @Gmail, Outlook or whatever they could actually have something unique that they control more or less. [00:42:43] Paul: Yeah. And we, we actually have a little experimental service for registering domain names that we haven't integrated into the app yet because we just kind of wanted to test it out and, and kind of see what that appetite is for folks to register domain names way higher than you'd think we did that early on. [00:43:01] You know, it's funny when you're coming from decentralization is like an activist space, right? Like it's a group of people trying to change how this tech works. And sometimes you're trying to parse between what might come off as a fascination of technologists compared to what people actually care about. [00:43:20] And it varies, you know, the domain name thing to a surprising degree, folks really got into that. We saw people picking that up almost straight away. More so than certainly we ever predicted. And I think that's just 'cause I guess it speaks to something that people really get about the internet at this point. [00:43:39] Which is great. We did a couple of other things that are similar and we saw varied levels of adoption on them. We had similar kinds of user facing, opening up of the system with algorithms and with moderation. And those have both been pretty interesting in and of themselves. Custom feed algorithms [00:43:58] Paul: So with algorithms, what we did was we set that up so that anybody can create a new feed algorithm. And this was kind of one of the big things that you run into whenever you use the app. If you wanted to create a new kind of for you feed you can set up a service somewhere that's gonna tap into that fire hose, right? [00:44:18] And then all it needs to do is serve a JSON endpoint. That's just a list of URLs, but like, here's what should be in that feed. And then the bluesky app will pick that up and, and send that, hydrate in the content of the posts and show that to folks. I wanna say this is a bit of a misleading number and I'll explain why but I think there's about 35,000 of these feeds that have been created. [00:44:42] Now, the reason it's little misleading is that, I mean, not significantly, but it's not everybody went, sat down in their IDE and wrote these things. Essentially one of our users created, actually multiple of our users made little platforms for building these feeds, which is awesome. That's the kinda thing you wanna see because we haven't gotten around to it. [00:44:57] Our app still doesn't give you a way to make these things. But they did. And so lots of, you know, there it is. Cool. Like, one, one person made a kind of a combinatorial logic thing that's like visual almost like scratch, it's like, so if it has this hashtag and includes these users, but not those users, and you're kind of arranging these blocks and that constructs the feed and then probably publish it on your profile and then folks can use it, you know? [00:45:18] And um, so that has been I would say fairly successful. Except, we had one group of hackers do put in a real effort to make a replacement for you feed, like magic algorithmic feed kind of thing. And then they kind of kept up going for a while and then ended up giving up on it. Most of what we see are actually kind of weird niche use cases for feeds. [00:45:44] You get straightforward ones, like content oriented ones like a cat feed, politics feed, things like that. It's great, some of those are using ML detection, so like the cat feed is ML detection, so sometimes you get like a beaver in there, but most of the time it's a cat. And then we got some ones that are kind of a funny, like change in the dynamic of freshness. [00:46:05] So, uh, or or selection criteria, things that you wouldn't normally see. Um, but because they can do whatever they want, you know, they try it out. So like the quiet posters ended up being a pretty successful one. And that one just shows people you're following that don't post that often when they do just those folks. [00:46:21] It ended up being, I use that one all the time because yeah, like they get lost in the noise. So it's like a way to keep up with them. Custom moderation and labeling [00:46:29] Paul: The moderation one, that one's a a real interesting situation. What we did there essentially we wanted to make sure that the moderation system was capable of operating across different apps so that they can share their work, so to speak. [00:46:43] And so we created what we call labeling. And labeling is a metadata layer that exists over the network. Doesn't actually live in the normal data repositories. It uses a completely different synchronization because a lot of these labels are getting produced. It's just one of those things where the engineering characteristics of the labels is just too different from the rest of the system. [00:47:02] So we created a separate synchronization for this, and it's really kind of straightforward. It's, here's a URL and here's a string saying something like NSFW or Gore, or you know, whatever. then those get merged onto the records brought down by the client and then the client, you know, based on the user's preferences. [00:47:21] We'll put like warning screens up, hide it, stuff like that. So yeah, these label streams can then, you know, anybody that's running a moderation service can, you know, are publishing these things and so anybody can subscribe to 'em. And you get that kind of collaborative thing we're always trying to do with this. [00:47:34] And we had some users set up moderation services and so then as an end user you find it, it looks like a profile in the app and you subscribe to it and you configure it and off you go. That one has had probably the least amount of adoption throughout all of 'em. It's you know, moderation. [00:47:53] It's a sticky topic as you can imagine, challenging for folks. These moderation services, they do receive reports, you know, like whenever I'm reporting a post, I choose from all my moderation services who I wanna report this to. what has ended up happening more than being used to actually filter out like subjective stuff is more kind of like either algorithmic systems or what you might call informational. [00:48:21] So the algorithmic ones are like, one of the more popular ones is a thing that's looking for, posts from other social networks. Like this screenshot of a Reddit post or a Twitter post or a Facebook post. Because, which you're kinda like, why, you know, but the thing is some folks just get really tired of seeing screenshots from the other networks. [00:48:40] 'cause often it's like, look what this person said. Can you believe it? You know, it's like, ah. Okay, I've had enough. So one of our users aendra made a moderate service that just runs an ML that detects it, labels it, and then folks that are tired of it, they subscribe to it and they're just hide it, you know? [00:48:57] And so it's like a smart filter kind of thing that they're doing. you know, hypothetically you could do that for things like spiders, you know, like you've got arachniphobia, things like that. that's like a pretty straightforward, kind of automated way of doing it. Which takes a lot of the spice, you know, outta out of running moderation. [00:49:15] So that users have been like, yeah, yeah, okay, we can do that. [00:49:20] Those are user facing ways that we tried to surface the. Decentralized principle, right? And make take advantage of how this whole architecture can have this kind of a pluggability into it. Users can self host now [00:49:33] Paul: But then really at the end of the day, kind of the important core part of it is those pieces we were talking about before, the hosting, the relay and the, the applications themselves, having those be swappable in completely. so we tend to think of those as kind of ranges of infrastructure into application and then into particular client side stuff. [00:49:56] So a lot of folks right now, for instance, they're making their own clients to the application and those clients are able to do customizations, add features, things like that, as you might expect, [00:50:05] but most of them are not running their own backend. They're just using our backend. But at any point, it's right there for you. You know, you can go ahead and, and clone that software and start running the backend. If you wanted to run your own relay, you could go ahead and go all the way to that point. [00:50:19] You know, if you wanna do your own hosting, you can go ahead and do that. Um, it's all there. It's really just kind of a how much effort your project really wants to take. That's the kind of systemically important part. That's the part that makes sure that the overall mission of de monopolizing, social media online, that's where that really gets enforced. [00:50:40] Jeremy: And so someone has their own data repository with their own users and their own relay. they can request that your relay collect the information from their own data repositories. And that's, that's how these connections get made. [00:50:58] Paul: Yeah. And, and we have a fair number of those already. Fair number of, we call those the self hosters right? And we got I wanna say 75 self hoster going right now, which is, you know, love to see that be more, but it's, really the folks that if you're running a service, you probably would end up doing that. [00:51:20] But the folks that are just doing it for themselves, it's kind of the, the nerdiest of the nerds over there doing that. 'cause it doesn't end up showing itself in the, in the application at all. Right? It's totally abstracted away. So it, that, that one's really about like, uh, measure your paranoia kind of thing. [00:51:36] Or if you're just proud of the self-hosting or, or curious, you know, that that's kind of where that sits at the moment. AT Protocol beyond bluesky [00:51:42] Jeremy: We haven't really touched on the fact that there's this underlying protocol and everything we've been discussing has been centered around the bluesky social network where you run your own, instance of the relay and the data repositories with the purpose of talking to bluesky, but the protocol itself is also intended to be used for other uses, right? [00:52:06] Paul: Yeah. It's generic. The data types are set up in a way that anybody can build new data types in the system. there's a couple that have already begun, uh, front page, which is kind of a hacker news clone. There's Smoke Signals, which is a events app. There's Blue Cast, which is like a Twitter spaces, clubhouse kind of thing. [00:52:29] Those are the folks that are kind of willing to trudge into the bleeding edge and deal with some of the rough edges there for pretty I think, obvious reasons. A lot of our work gets focused in on making sure that the bluesky app and that use case is working correctly. [00:52:43] But we are starting to round the corner on getting to a full kind of how to make alternative applications state. If you go to the atproto.com, there's a kind of a introductory tutorial where that actually shows that whole stack and how it's done. So it's getting pretty close. There's a couple of still things that we wanna finish up. [00:53:04] jeremy so in a way you can almost think of it as having an eventually consistent data store on the network, You can make a traditional web application with a relational database, and the source of truth can actually be wherever that data repository is stored on the network. [00:53:24] paul Yeah, that's exactly, it is an eventually consistent system. That's exactly right. The source of truth is there, is their data repo. And that relational database that you might be using, I think the best way to think about it is like secondary indexes or computed indexes, right? They, reflect the source of truth. [00:53:43] Paul: This is getting kind of grandiose. I don't tend to poses in these terms, but it is almost like we're trying to have an OS layer at a protocol level. It's like having your own [00:53:54] Network wide database or network-wide file system, you know, these are the kind of facilities you expect out of a platform like an os And so the hope would be that this ends up getting that usage outside of just the initial social, uh, app, like what we're doing here. [00:54:12] If it doesn't end up working out that way, if this ends up, you know, good for the Twitter style use case, the other one's not so much, and that's fine too. You know, that's, that's our initial goal, but we, we wanted to make sure to build it in a way that like, yeah, there's evolve ability to, it keeps, it, keeps it, make sure that you're getting kinda the most utility you can out of it. Peer-to-peer and the difficulty of federated queries [00:54:30] Jeremy: Yeah, I can see some of the parallels to some of the decentralized stuff that I, I suppose people are still working on, but more on the peer-to-peer side, where the idea was that I can have a network host this data. but, and in this case it's a network of maybe larger providers where they could host a bunch of people's data versus just straight peer to peer where everybody has to have a piece of it. [00:54:57] And it seems like your angle there was really the scalability part. [00:55:02] Paul: It was the scalability part. And there's great work happening in peer-to-peer. There's a lot of advances on it that are still happening. I think really the limiter that you run into is running queries against aggregations of data. Because you can get the network, you know, BitTorrent sort of proved that you can do distributed open horizontal scaling of hosting. [00:55:29] You know, that basic idea of, hey, everybody's got a piece and you sync it from all these different places. We know you can do things like that. What nobody's been able to really get into a good place is running, queries across large data sets. In the model like that, there's been some research in what is, what's called federated queries, which is where you're sending a query to multiple different nodes and asking them to fulfill as much of it as they can and then collating the results back. But it didn't work that well. That's still kind of an open question and until that is in a place where it can like reliably work and at very large scales, you're just gonna need a big database somewhere that does give the properties that you need. You need these big indexes. And once we were pretty sure of that requirement, then from there you start asking, all right, what else about the system [00:56:29] Could we make easier if we just apply some more traditional techniques and merge that in with the peer-to-peer ideas? And so key hosting, that's an obvious one. You know, availability, let's just have a server. It's no big deal. But you're trying to, you're trying to make as much of them dumb as possible. [00:56:47] So that they have that easy replaceability. Moderation challenges [00:56:51] Jeremy: Earlier you were talking a a little bit about the moderation tools that people could build themselves. There was some process where people could label posts and then build their own software to determine what a feed should show per a person. [00:57:07] Paul: Mm-Hmm [00:57:07] Jeremy: But, but I think before that layer for the platform itself, there's a base level of moderation that has to happen. [00:57:19] Paul: yeah. [00:57:20] Jeremy: And I wonder if you could speak to, as the app has grown, how that's handled. [00:57:26] Paul: Yeah. the, you gotta take some requirements in moderation pretty seriously to start. And with decentralization. It sometimes that gets a little bit dropped. You need to have systems that can deal with questions about CSAM. So you got those big questions you gotta answer and then you got stuff that's more in the line of like, alright, what makes a good platform? [00:57:54] What kind of guarantees are we trying to give there? So just not legal concerns, but you know, good product experience concerns. That's something we're in the realm of like spam and and abusive behavior and things like that. And then you get into even more fine grain of like what is a person's subjective preference and how can they kind of make their thing better? [00:58:15] And so you get a kind of a telescoping level of concerns from the really big, the legal sort of concerns. And then the really small subjective preference kind of concerns. And that actually that telescoping maps really closely to the design of the system as well. Where the further you get up in the kind of the, in that legal concern territory, you're now in core infrastructure. [00:58:39] And then you go from infrastructure, which is the relay down into the application, which is kind of a platform and then down into the client. And that's where we're having those labelers apply. And each of them, as you kind of move closer to infrastructure, the importance of the decision gets bigger too. [00:58:56] So you're trying to do just legal concerns with the relay right? Stuff that you objectively can, everybody's in agreement like Yeah, yeah, yeah. You know, no bigs don't include that. The reason is that at the relay level, you're anybody that's using your relay, they depend on the decisions you're making, that sort of selection you're doing, any filtering you're doing, they don't get a choice after that. [00:59:19] So you wanna try to keep that focus really on legal concerns and doing that well. so that applications that are downstream of it can, can make their choices. The applications themselves, you know, somebody can run a parallel I guess you could call it like a parallel platform, so we got bluesky doing the microblogging use case, other people can make an application doing the microblogging use case. So there's, there's choice that users can easily switch, easily enough switch between, it's still a big choice. [00:59:50] So we're operating that in many ways. Like any other app nowadays might do it. You've got policies, you know, for what's acceptable on the network. you're still trying to keep that to be as, you know, objective as possible, make it fair, things like that. You want folks to trust your T&S team. Uh, but from the kind of systemic decentralization question, you get to be a little bit more opinionated. [01:00:13] Down all the way into the client with that labeling system where you can, you know, this is individuals turning on and off preferences. You can be as opinionated as you want on that letter. And that's how we have basically approached this. And in a lot of ways, it really just comes down to, in the day to day, you're the moderation, the volume of moderation tasks is huge. [01:00:40] You don't actually have high stakes moderation decisions most of the time. Most of 'em are you know pretty straightforward. Shouldn't have done that. That's gotta go. You get a couple every once in a while that are a little spicier or a policy that's a little spicier. And it probably feels pretty common to end users, but that just speaks to how much moderation challenges how the volume of reports and problems that come through. [01:01:12] And we don't wanna make it so that the system is seized up, trying to decentralize itself. You know, it needs to be able to operate day to day. What you wanna make is, you know, back pressure, you know, uh, checks on that power so that if an application or a platform does really start to go down the wrong direction on moderation, then people can have this credible exit. [01:01:36] This way of saying, you know what, that's a problem. We're moving from here. And somebody else can come in with different policies that better fit people's people's expectations about what should be done at, at these levels. So yeah, it's not about taking away authority, it's about checking authority, you know, kind of a checks and balances mentality. [01:01:56] Jeremy: And high level, 'cause you saying how there's such a high volume of, of things that you know what it is, you'd know you wanna remove it, but there's just so much of it. So is there, do you have automated tools to label these things? Do you have a team of moderators? Do they have to understand all the different languages that are coming through your network? [01:02:20] Yes, yes, yes and yes. Yeah. You use every tool at your disposal to, to stay on top of it. cause you're trying to move as fast as you can, folks. The problems showing up, you know, the slower you are to respond to it, the, the more irritating it is to folks. Likewise, if you make a, a missed call, if somebody misunderstands what's happening, which believe me, is sometimes just figuring out what the heck is going on is hard. [01:02:52] Paul: People's beefs definitely surface up to the moderation misunderstanding or wrong application. Moderators make mistakes so you're trying to maintain a pretty quick turnaround on this stuff. That's tough. And you, especially when to move fast on some really upsetting content that can make its way through, again, illegal stuff, for instance, but more videos, stuff like that, you know, it's a real problem. [01:03:20] So yeah, you're gotta be using some automated systems as well. Clamping down on bot rings and spam. You know, you can imagine that's gotten a lot harder thanks to LLMs just doing text analysis by dumb statistics of what they're talking about that doesn't even work anymore. [01:03:41] 'cause the, the LLMs are capable of producing consistently varied responses while still achieving the same goal of plugging a online betting site of some kind, you know? So we do use kind of dumb heuristic systems for when it works, but boy, that won't work for much longer. [01:04:03] And we've already got cases where it's, oh boy, so the moderation's in a dynamic place to say the least right now with, with LLMs coming in, it was tough before and
Join us for an in-depth conversation in the episode entitled, 'How Will the .Music Domain Change the Music Industry Forever?' with Constantine Roussos who is the Founder & CEO of .MUSIC domain. on the MUBUTV Music Business Insider Podcast. We explore the pivotal role of intellectual property lobbies in influencing ICANN's trademark policies and the launch of the .music domain. Learn about the "Sunrise phase" for trademark holders, the challenges of managing domains for bands with generic names, and the importance of verification to prevent cyber squatting. This episode is a must-watch for anyone intrigued by the merging worlds of tech and music!
Did you know one company has the monopoly on the .com top level domain? How did Verisign become the one DNS registry for .com, and why did some politicians recently challenge the company's practices?See omnystudio.com/listener for privacy information.
DOWNLOAD YOUR COPY OF THE BITCOIN-FOR-BUSINESS QUICK START GUIDE This free, 27-page resource includes:Six ways ANY business can benefit from BitcoinSome of the best Bitcoin-only businesses to partner withKey Bitcoin concepts for people getting startedMike Carson, founder of Spaces Protocol, is revolutionizing digital identity with a decentralized system on Bitcoin that empowers user control. As the owner of Friendster.com, he's planning a reboot to give users ownership of their data. Previously, Carson founded and exited Park.io, co-founded WizeHive, which hit $10 million in revenue and managed three ICANN-accredited registrars. An early Bitcoin advocate, he's been active in the community since 2013, running one of the first Lightning nodes and pioneering real-world Bitcoin transactions.
VeriSign manages the registry for .com domains and sets the prices for these domains. Recent reports indicate that the company raised the annual registration fees for .com domains multiple times. Critics claim that these price increases are excessive and benefit only VeriSign. Concerns arise over the lack of competition in the domain registration market, which allows VeriSign to maintain its pricing power. The U.S. Department of Commerce reviews the agreements between VeriSign and ICANN, the organization that oversees domain names. Additionally, some stakeholders argue for regulatory actions to ensure fair pricing and competition in the domain registration industry.Learn more on this news visit us at: https://greyjournal.net/news/ Hosted on Acast. See acast.com/privacy for more information.
Send us a textWhat if you could find peace and purpose after facing life's toughest challenges? Join us in this episode as we uncover the inspiring journey of Gage, a passionate advocate for autism awareness who transformed his early struggles into a powerful voice for change. Diagnosed with autism at age five, Gage didn't speak until then and found solace in building snack-box towers. His story is a testament to resilience and personal growth, taking us from a young boy in Pennsylvania to a determined advocate in Florida.Gage opens up about confronting trauma and depression, particularly during the pandemic, a time that demanded introspection and healing. With the support of his older brother, who introduced him to meditation and personal growth practices, Gage navigated the challenges, learning patience and self-respect through his experiences at a diner. A pivotal move to Florida marked a new beginning, filled with optimism and the pursuit of his dreams. We explore how these experiences shaped Gage's journey towards becoming a motivational speaker, reigniting his passion through opportunities like the ICANN autism conference and Toastmasters.Dive into the importance of spreading awareness and acceptance within the autism community through platforms like Gage's podcast, Autism Talk. By showcasing uplifting stories of individuals who overcome challenges without adopting a victim mindset, Gage aims to inspire and educate listeners. Be ready to hear heartfelt advice for parents of children with autism and encouraging words for adults diagnosed later in life. This episode is a celebration of potential, collaboration, and the power of sharing impactful stories that uplift and inspire.Support the show
https://bit.ly/4fnDxaKTo the outsider, the internet-related issues that the Internet Corporation for Assigned Names and Numbers (ICANN) is addressing can seem intimidating. But individuals, micro or small businesses, among others, are part of the end-user constituency and are critical players in ICANN's policy development process. In our latest conversation with Albert Daniels, the Senior Manager for Stakeholder Engagement for the Caribbean, we discuss some of the latest developments in the ICANN Space. Some of the areas covered include: * what exactly is ICANN and why it is important; * the Registration Data Request Service and the implications for law enforcement; * the new generic Top-Level Domain (gTLD) Program; and * how Caribbean countries could benefit from this and other upcoming initiatives. The episode, show notes and links to some of the things mentioned during the episode can be found on the ICT Pulse Podcast Page (www.ict-pulse.com/category/podcast/) Enjoyed the episode? Do rate the show and leave us a review! Also, connect with us on: Facebook – https://www.facebook.com/ICTPulse/ Instagram – https://www.instagram.com/ictpulse/ Twitter – https://twitter.com/ICTPulse LinkedIn – https://www.linkedin.com/company/3745954/admin/ Join our mailing list: http://eepurl.com/qnUtj Music credit: The Last Word (Oui Ma Chérie), by Andy Narrell ---------------- Also, Sponsorship Opportunities! The ICT Pulse Podcast is accepting sponsors! Would you like to partner with us to produce an episode of the podcast, or highlight a product or service to our audience? Do get in touch at info@ict-pulse.com with “Podcast Sponsorship” as the subject, or via social media @ictpulse, for more details. _______________
Welcome to another riveting episode of Hearts of Oak, where we delve deep into the stories that shape our world. Today, we're honored to host a distinguished guest, a board-certified obstetrician gynecologist with a background in maternal fetal medicine, whose journey through the medical field has been nothing short of extraordinary. In this episode, our guest shares insights from a career marked by a relentless pursuit of truth, especially in light of the tumultuous events surrounding public health strategies during recent global crises. We'll explore how personal experiences, influenced by historical figures like Dr. Ignaz Semmelweis, have shaped his approach to medicine, emphasizing the importance of standing firm against mainstream narratives when patient safety is at stake. Our discussion will take a critical look at how health policies, driven by a complex web of government, pharmaceutical, and medical organizations, have impacted the most vulnerable among us. We'll tackle the uncomfortable truths about medical ethics, the silence of influential societal groups, and the personal sacrifices made by those who speak out against the status quo. This episode promises to be a beacon of awareness, urging us all to question, to learn, and to remember the importance of integrity in the face of systemic challenges. So, join us as we navigate through the ethical dilemmas of our time, inspired by a physician's commitment to never compromise patient care for profit or popularity. Stay with us as we uncover the layers of this compelling story, right here on Hearts of Oak. Connect with Dr James Thorp Freedom In Truth | Substack Recorded on 17.10.24 *Special thanks to Bosch Fawstin for recording our intro/outro on this podcast. Connect with Hearts of Oak...
In this episode, you'll discover:Here's what is at stake in the upcoming Presidential ElectionWhat Chiropractors need to knowHow to take a stand in your practice and communityLet's Make America Healthy AgainEpisode Highlights00:50 - Introduction of Del Bigtree, host of The High Wire and ICANN president.04:10 - The responsibility of discussing impactful, politicized topics is crucial amid current societal stakes, overcoming fears of neutrality to address issues like censorship and the collusion of major entities.08:05 - A look at the media system and how it is unfairly manipulated by both political parties, lacking equal time for all. 13:35 - How Del became highly rated due to addressing public health concerns leading to involvement in CDC whistleblower story and making the film "VAXXED" with Andrew Wakefield.14:51 - Finding destiny in editing medical film, feeling uniquely qualified for a project, supported by chiropractors.19:36 - The government and media corruption, internet censorship, and a growing societal disconnect.22:45 - What happened with Bobby reached out to Trump after assisination attempt.24:31 - The rigging in Democratic primaries, with criticism of Kamala Harris being selected without election and changes putting candidates in disadvantage in New Hampshire.34:19 - A lack of viable leadership choices, mentions Donald Trump involving Robert Kennedy Jr. and Tulsi Gabbard in efforts to reform government, and expresses concern about potential conflict initiated by Democrats.36:26 - Criticism of Biden-Harris on censorship and vaccine mandates; praise for Trump on free speech.40:39 - Freedom of speech requires open discourse and access to information for informed decision-making.45:05 - Pharma spends five times more than oil and gas on government influence, potentially sidelining alternative health perspectives like chiropractors, who were notably active during COVID-19 when conventional care was less accessible.48:48 - Global governance vs. national sovereignty.50:39 - Focus on policies, not politics; prioritize children's future and encourage open dialogue.53:26 - Listeners are encouraged to find courage, self-reflect, and contribute locally. Resources MentionedWatch Robert F. Kennedy Jr's Step Down Speech at https://www.instagram.com/reel/DAwjmy8v-95/?igsh=MTB2bmFxODc3d3UwMA==For more information on what Dell is working on, visit https://mahaalliance.com/To learn more about the REM CEO Program, please visit: http://www.theremarkablepractice.com/rem-ceoSubscribe to our newest podcast "Build Your Remarkable Practice" here: https://podcasts.apple.com/us/podcast/build-your-remarkable-practice-for-chiropractors/id1734107477 Schedule a Brainstorming call with Dr. PeteDr. Stephen's LinkedInDr. Peter's LinkedInThe Remarkable CEO WebsiteDr. Stephen's Book – The Remarkable Practice: The Definitive Guide to Build a Thriving Chiropractic Business
In this episode of From Startup to Stock Exchange, I chat with Pavani Munjuluri, CEO of CognitiveHealth Technologies, about how AI is changing the game in healthcare. Pavani breaks down how her platform, ICAnn, automates administrative tasks, solves staffing shortages, and helps healthcare providers avoid costly errors. We dive into how AI streamlines workflows, improves efficiency, and ensures providers don't leave money on the table—especially when managing denials and prior authorizations. Pavani also shares her bold vision for how AI will bridge the gap between healthcare providers and payers. If you're interested in the future of healthcare and AI, this episode is a must-listen.
In this episode of Global Risk Community's Risk Management Show, we dive into the world of cybersecurity with David Holtzman, Chief Strategy Officer at Naoris Protocol and former Chief Scientist at IBM. We discussed his bold strategy to fight cyber threats by leveraging aggressive cybersecurity responses. With an illustrious career spanning roles such as designer of the global DNS system for ICANN and White House cybersecurity adviser, David brings invaluable insights into the risks and challenges of both centralized and decentralized systems. He highlights the importance of decentralized technologies and the role they play in enhancing security resilience against growing cyber threats. If you want to be our guest or suggest someone, send your email to info@globalriskconsult.com with the subject line "Guest Suggestion." Join us in exploring cutting-edge solutions and stay ahead in the ever-evolving landscape of cyber security.
Being at the core of the Internet places the DNS under a lot of pressure. New forms of DNS abuse emerge each year, disputes over domain names persist, and all the while, the Internet just keeps getting bigger. Mikhail Anisimov from ICANN talks about the coordinated effort involved in meeting these challenges and shares his views on DNS in Central Asia.As one of the organisations at the core of the Internet that works to coordinate the supply of Internet numbers and domain names, ICANN plays a vital role in helping to support and develop the DNS. Our guest Mikhail has been ICANN's Stakeholder Engagement Senior Manager for Eastern Europe and Central Asia since 2020, so we thought who better to talk to about DNS, DNSSEC, and its ongoing development in Central Asia.Show notes:02:18 - Wikipedia entry on DNS03:30 - You can learn lots about ICANN on their website04:10 – There's a list of all the root DNS servers and their operators on the IANA website. The RIPE NCC operates K-root.05:12 – Statdns has this useful list of DNS related RFCs08:40 – New gTLD program09:10 – FAQ on the next round of the new gTLD15:30 - The 8th Central Asian Internet Governance Forum took place on 21-22 June 2024.15:51 – ICANN's Domain Name Security Threat Information Collection and Reporting (DNSTICR) project16:02 - …and the broader Domain Abuse Activity Reporting (DAAR) project19:07 - Calling Time on DNSSEC by Geoff Huston22:19 – Dan Kaminsky in the Internet Hall of Fame28:00 – ICANN page on DNSSEC33:21 – The next Central Asia Peering and Interconnection Forum, CAPIF 3, takes place in Bishkek, Kyrgyzstan, from 24-25 September 2024.40:42 – Read Chris Buckridge's Fragmentation: Still the Internet's Big Bad here on RIPE Labs. Hosted on Acast. See acast.com/privacy for more information.
Mike Carson is the CEO of Impervious (and Friendster): a Bitcoin-native ZK proof-native protocol which allows for scalable domain registrations on the Bitcoin blockchain. In this episode, he explains how & why he decided to disrupt ICANN.
Featured on Cybersecurity Ventures' list of Cybersecurity Pundits, Alan Wallace's public relations career began with his role as the tour publicist for Chuck Norris' film "Sidekicks.” He then co-founded the first PR, advertising, and online marketing firm for the internet. His background includes Panda Software, ICANN, Microsoft, Trend Micro, and Afilias. Wallace consults under the brand of PressContact, LLC, and represents tech and cybersecurity-focused companies. In this episode, he joins host Scott Schober to discuss public relations for cybersecurity companies.• For more on cybersecurity, visit us at https://cybersecurityventures.com
Those letters at the end of web addresses can mean big bucks — and, for some small countries, a substantial part of the national budget. Zachary Crockett follows the links. SOURCES:Vince Cate, technical contact for the .ai domain in Anguilla.Kim Davies, Vice President of Internet Assigned Numbers Authority Services and President of Public Technical Identifiers at ICANN.Tianyu Fang, contributing editor at Reboot. RESOURCES:"The Two-Decade Fight for Two Letters on the Internet," by Jacob Judah (The New York Times, 2024)."Whose Domain Is It?" by Tianyu Fang (Reboot, 2023)."How a Tiny Pacific Island Became the Global Capital of Cybercrime," by Jacob Judah (MIT Technology Review, 2023)."The Tropical Island With the Hot Domain Name," by Rachel Metz (Bloomberg, 2023)."The Never-ending ccTLD Story," by Peter K. Yu (SSRN, 2003).
Uncover the unforeseen ways foreign policy sways the American electoral tide with us, Marshall Toplansky and Joel Kotkin, as we host a conversation that traverses the global political landscape and its potential shocks to the 2024 elections. With luminaries like former U.S. Ambassador to Italy Ron Spogli and Asia Pacific expert Robert Koepp sharing their insights, this episode is a deep dive into the geopolitical undercurrents—from NATO's strategies to the East Asian power balance. We navigate the complex web of international relations that could very well dictate the next occupant of the White House.Witness a thought-provoking dissection of how America's stance on global democracy, AI, and climate change may just redefine our future. Presidential historian Luke A. Nichter and ex-ICANN innovation lead Ashwin Rangan join our panel to analyze the critical role technology plays in shaping both domestic and global perceptions. The episode doesn't shy away from hard-hitting topics like the decline of democracy and the global economic chess game orchestrated by emerging powers, notably China and India. Their maneuvers on the world stage could be a game-changer in the political arena.Finally, the spotlight turns to the educational forefront with a look at how institutions such as Chapman University are evolving to meet the demands of an ever-changing geopolitical theatre. We ponder America's relationship with Europe and consider the educational strategies needed to arm the next generation with the tools to navigate a world where international policy decisions have profound domestic repercussions. It's a masterclass in connecting the dots between the halls of academia and the complex web of global politics, with an eye firmly on the horizon of the 2024 elections. Join us for an episode that's equal parts enlightening and urgent, as we chart the course for America's role in an increasingly interconnected world.Support Our WorkThe Center for Demographics and Policy focuses on research and analysis of global, national, and regional demographic trends and explores policies that might produce favorable demographic results over time. It involves Chapman students in demographic research under the supervision of the Center's senior staff.Students work with the Center's director and engage in research that will serve them well as they look to develop their careers in business, the social sciences, and the arts. Students also have access to our advisory board, which includes distinguished Chapman faculty and major demographic scholars from across the country and the world.For additional information, please contact Mahnaz Asghari, Associate Director for the Center for Demographics and Policy, at (714) 744-7635 or asghari@chapman.edu.Follow us on LinkedIn:https://www.linkedin.com/company/the-feudal-future-podcast/Tweet thoughts: @joelkotkin, @mtoplansky, #FeudalFuture #BeyondFeudalismLearn more about Joel's book 'The Coming of Neo-Feudalism': https://amzn.to/3a1VV87Sign Up For News & Alerts: http://joelkotkin.com/#subscribeThis show is presented by the Chapman Center for Demographics and Policy, which focuses on research and analysis of global, national and regional demographic trends and explores policies that might produce favorable demographic results over time.
Jeff Neuman fills us in on what happened at the latest ICANN meeting. Jeff Neuman has just about seen it all in the domain business over the past few decades. The former VP of Registry at Neustar currently serves as a lawyer and policy consultant and is the chief legal officer of Dot Hip Hop. […] Post link: This how we do it down in Puerto Rico – DNW Podcast #477 © DomainNameWire.com 2024. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.
On today's show, if you get most of your clients from referrals, is that a good thing? Or is your business at risk of failing? You're about to hear a coaching call with Dwaynia, who's calling in from Alabama in the USA. Dwaynia has a great writing business going. She's working with clients she loves and has a small team to support her. But, Dwaynia literally lies awake at night worried about not having a client generation system in place to bring in predictable new work. Her annual goals are literally pulled out of thin air, and she's not sure how to fix it. Clay and I share a few of our best ideas for building a predictable client referral system, as well as other ways to get clients in the door in a more predictable way. Here we go. This episode was originally aired on January 13, 2022. PS: Get featured in an upcoming Q&A! Just visit http://freelancetofounder.com/ask and submit a question. Support our sponsors so we can keep airing new episodes: Shopify - The global commerce platform. Build your business with Shopify to sell online, offline, and everywhere in between. Book of the Month - Choose from a curated selection of the best new hardcovers and audiobooks every month. LinkedIn Talent Solutions - With access to 900M professionals and real-time data, you can find and hire the right people to grow your business and make it thrive. Porkbun - An amazingly awesome ICANN accredited domain name registrar based out of the Pacific Northwest. Different. Easy. Affordable. HelloFresh - America's #1 Meal Kit now offering 18 Free Meals and Free Breakfast for Life! Dripify - Premium learning platform for entrepreneurs. Get your own on-air coaching call We'd love to feature your business and offer some free on-air advice for growing your business. To see if you're a good fit, click here. Leave us a review on Apple Podcasts: If you enjoy the show, can you do us a favor and leave us an honest rating and review on Apple Podcasts? We'll love you forever. Click here to leave a review. More Recommended Listening: This show is a part of the Podglomerate, a company that produces, distributes, and monetizes podcasts. We encourage you to visit the website and sign up for our newsletter. We suggest you also try other Podglomerate shows about entrepreneurship, business, and creativity, such as Rocketship.fm and Creative Elements. Learn more about your ad choices. Visit megaphone.fm/adchoices
On today's show: how many people does it take to call yourself an agency officially? Is it one, two, or more than that? This question got us thinking a bit about what it actually means to be an agency. Plus, we talk about our ideal team size and answer the question: How many is too many when it comes to your team? It's all on this episode of Freelance to Founder. Here we go. To submit your question, visit FreelanceToFounder.com/ASK, and we'll feature you on an upcoming episode. Listen to our full-length coaching calls: http://freelancetofounder.com Support our sponsors so we can keep airing new episodes: Shopify - The global commerce platform. Build your business with Shopify to sell online, offline, and everywhere in between. Book of the Month - Choose from a curated selection of the best new hardcovers and audiobooks every month. LinkedIn Talent Solutions - With access to 900M professionals and real-time data, you can find and hire the right people to grow your business and make it thrive. Porkbun - An amazingly awesome ICANN accredited domain name registrar based out of the Pacific Northwest. Different. Easy. Affordable. HelloFresh - America's #1 Meal Kit now offering 18 Free Meals and Free Breakfast for Life! Dripify - Premium learning platform for entrepreneurs. SolidGigs - Get more freelance jobs Learn more about your ad choices. Visit megaphone.fm/adchoices
On today's show: Do lead magnets really work? Like, can you actually get new clients by giving away something for free first? Or are they a waste of your time? I'm flying solo today on a coaching call with Garrett—who has questions about using AI to generate lead magnets, how to price his work when he has a unique offering and non-traditional clients, and more. It's all in today's episode of ‘Freelance to Founder.' Thanks for joining. Here we go! This episode was originally aired on August 17, 2023. PS: Get featured in an upcoming Q&A! Just visit http://freelancetofounder.com/ask and submit a question. Support our sponsors so we can keep airing new episodes: Shopify - The global commerce platform. Build your business with Shopify to sell online, offline, and everywhere in between. LinkedIn Talent Solutions - With access to 900M professionals and real-time data, you can find and hire the right people to grow your business and make it thrive. Porkbun - An amazingly awesome ICANN accredited domain name registrar based out of the Pacific Northwest. Different. Easy. Affordable. HelloFresh - America's #1 Meal Kit now offering 18 Free Meals and Free Breakfast for Life! Dripify - Premium learning platform for entrepreneurs. SolidGigs - Get more freelance jobs Get your own on-air coaching call We'd love to feature your business and offer some free on-air advice for growing your business. To see if you're a good fit, click here. Leave us a review on Apple Podcasts: If you enjoy the show, can you do us a favor and leave us an honest rating and review on Apple Podcasts? We'll love you forever. Click here to leave a review. More Recommended Listening: This show is a part of the Podglomerate, a company that produces, distributes, and monetizes podcasts. We encourage you to visit the website and sign up for our newsletter. We suggest you also try other Podglomerate shows about entrepreneurship, business, and creativity, such as Rocketship.fm and Creative Elements. Learn more about your ad choices. Visit megaphone.fm/adchoices
On today's show: you're dead without a vision for your business. That's because without a vision—or a north star—to guide your business, you can very easily end up chasing the wrong things. In today's episode, we chat with Alan, who's ready to grow his family business, but he's not sure where to start when it comes to strategy and processes. If you find it hard knowing where to start, this episode is for you. Here we go. PS: Get featured in an upcoming Q&A! Just visit http://freelancetofounder.com/ask and submit a question. Support our sponsors so we can keep airing new episodes: Shopify - The global commerce platform. Build your business with Shopify to sell online, offline, and everywhere in between. LinkedIn Talent Solutions - With access to 900M professionals and real-time data, you can find and hire the right people to grow your business and make it thrive. Porkbun - An amazingly awesome ICANN accredited domain name registrar based out of the Pacific Northwest. Different. Easy. Affordable. HelloFresh - America's #1 Meal Kit now offering 18 Free Meals and Free Breakfast for Life! Dripify - Premium learning platform for entrepreneurs. SolidGigs - Get more freelance jobs Get your own on-air coaching call We'd love to feature your business and offer some free on-air advice for growing your business. To see if you're a good fit, click here. Leave us a review on Apple Podcasts: If you enjoy the show, can you do us a favor and leave us an honest rating and review on Apple Podcasts? We'll love you forever. Click here to leave a review. More Recommended Listening: This show is a part of the Podglomerate, a company that produces, distributes, and monetizes podcasts. We encourage you to visit the website and sign up for our newsletter. We suggest you also try other Podglomerate shows about entrepreneurship, business, and creativity, such as Rocketship.fm and Creative Elements. Learn more about your ad choices. Visit megaphone.fm/adchoices
On today's Q&A episode, Travis writes in with a problem: a few years ago, he moved from Australia to the U.S. to grow his video business. And while things went well at first, work has really slowed down, and he's wondering: is there something about the U.S. market he's completely missing? Clay and I have never lived “down under,” but we have a few things to consider for anyone looking to break into the US market. It's all on this episode of Freelance to Founder. Here we go… To submit your question, visit FreelanceToFounder.com/ASK, and we'll feature you on an upcoming episode. Listen to our full-length coaching calls: http://freelancetofounder.com Support our sponsors so we can keep airing new episodes: Shopify - The global commerce platform. Build your business with Shopify to sell online, offline, and everywhere in between. LinkedIn Talent Solutions - With access to 900M professionals and real-time data, you can find and hire the right people to grow your business and make it thrive. Porkbun - An amazingly awesome ICANN-accredited domain name registrar based out of the Pacific Northwest. Different. Easy. Affordable. HelloFresh - America's #1 Meal Kit now offers 18 Free Meals and Free Breakfast for Life! Dripify - Premium learning platform for entrepreneurs. SolidGigs - Get more freelance jobs Learn more about your ad choices. Visit megaphone.fm/adchoices
On today's show: should you spread yourself across each of your client's project management tools? Or should you make them join yours? It's a question Taylor's facing as she grows her business. We spoke with Taylor about a year ago, and things are going great. But she works with so many clients now; they each have their preferred project management tool. So, should she keep going from tool to tool? Or make her clients join a single platform that she manages? We'll discuss that and more on today's episode of Freelance to Founder. PS: Get featured in an upcoming Q&A! Just visit http://freelancetofounder.com/ask and submit a question. Support our sponsors so we can keep airing new episodes: Shopify - The global commerce platform. Build your business with Shopify to sell online, offline, and everywhere in between. LinkedIn Talent Solutions - With access to 900M professionals and real-time data, you can find and hire the right people to grow your business and make it thrive. Porkbun - An amazingly awesome ICANN accredited domain name registrar based out of the Pacific Northwest. Different. Easy. Affordable. HelloFresh - America's #1 Meal Kit now offering 18 Free Meals and Free Breakfast for Life! Dripify - Premium learning platform for entrepreneurs. SolidGigs - Get more freelance jobs Get your own on-air coaching call We'd love to feature your business and offer some free on-air advice for growing your business. To see if you're a good fit, click here. Leave us a review on Apple Podcasts: If you enjoy the show, can you do us a favor and leave us an honest rating and review on Apple Podcasts? We'll love you forever. Click here to leave a review. More Recommended Listening: This show is a part of the Podglomerate, a company that produces, distributes, and monetizes podcasts. We encourage you to visit the website and sign up for our newsletter. We suggest you also try other Podglomerate shows about entrepreneurship, business, and creativity, such as Rocketship.fm and Creative Elements. Learn more about your ad choices. Visit megaphone.fm/adchoices
On today's show, we've got the longest Q&A episode we've ever published—coming in at a whopping 50 minutes plus. Why so long? Well, I asked Clay a question that really got him riled up. It has to do with his experience using the software GoHighLevel—which has exploded in popularity lately. But Clay's experience was anything but ideal. You'll see what I mean in this episode of Freelance to Founder. Here we go. This episode was originally aired on October 24, 2023. Mentioned in this episode: Keap CRMs for Freelancers To submit your question, visit FreelanceToFounder.com/ASK, and we'll feature you on an upcoming episode. Listen to our full-length coaching calls: http://freelancetofounder.com Support our sponsors so we can keep airing new episodes: Shopify - The global commerce platform. Build your business with Shopify to sell online, offline, and everywhere in between. LinkedIn Talent Solutions - With access to 900M professionals and real-time data, you can find and hire the right people to grow your business and make it thrive. Porkbun - An amazingly awesome ICANN-accredited domain name registrar based out of the Pacific Northwest. Different. Easy. Affordable. HelloFresh - America's #1 Meal Kit now offers 18 Free Meals and Free Breakfast for Life! Dripify - Premium learning platform for entrepreneurs. SolidGigs - Get more freelance jobs Learn more about your ad choices. Visit megaphone.fm/adchoices
Have you ever felt like you don't know where you're going in your business? It can be debilitating and frustrating. Not only that, but it can leave you spinning your wheels and wishing you knew what to do next to finally get some traction. That's the situation Bernadette finds herself in. Today, she calls in from New Zealand with questions about how to restart her business and build something she can actually get excited about. It's one of the most raw, personal sessions we've had to date, which leads us to some real breakthroughs for Bernadette's business. Stick around for this fun brainstorming session on today's episode of Freelance to Founder. This episode was originally aired on August 10, 2023. PS: Get featured in an upcoming Q&A! Just visit http://freelancetofounder.com/ask and submit a question. Support our sponsors so we can keep airing new episodes: Shopify - The global commerce platform. Build your business with Shopify to sell online, offline, and everywhere in between. LinkedIn Talent Solutions - With access to 900M professionals and real-time data, you can find and hire the right people to grow your business and make it thrive. Porkbun - An amazingly awesome ICANN accredited domain name registrar based out of the Pacific Northwest. Different. Easy. Affordable. Greenlight Financial - The all-in-one money and safety app for families. HelloFresh - America's #1 Meal Kit now offering 18 Free Meals and Free Breakfast for Life! Dripify - Premium learning platform for entrepreneurs. SolidGigs - Get more freelance jobs Get your own on-air coaching call We'd love to feature your business and offer some free on-air advice for growing your business. To see if you're a good fit, click here. Leave us a review on Apple Podcasts: If you enjoy the show, can you do us a favor and leave us an honest rating and review on Apple Podcasts? We'll love you forever. Click here to leave a review. More Recommended Listening: This show is a part of the Podglomerate, a company that produces, distributes, and monetizes podcasts. We encourage you to visit the website and sign up for our newsletter. We suggest you also try other Podglomerate shows about entrepreneurship, business, and creativity, such as Rocketship.fm and Creative Elements. Learn more about your ad choices. Visit megaphone.fm/adchoices
On today's show: if you work with a sub-contractor, something we highly recommend—how much extra should you charge your client? And do they have to sign two different contracts? That's what Kiki asks us in this Q&A episode of Freelance to Founder. Here we go… This episode was originally aired on June 21, 2022. To submit your question, visit FreelanceToFounder.com/ASK, and we'll feature you on an upcoming episode. Listen to our full-length coaching calls: http://freelancetofounder.com Support our sponsors so we can keep airing new episodes: Shopify - The global commerce platform. Build your business with Shopify to sell online, offline, and everywhere in between. LinkedIn Talent Solutions - With access to 900M professionals and real-time data, you can find and hire the right people to grow your business and make it thrive. Porkbun - An amazingly awesome ICANN accredited domain name registrar based out of the Pacific Northwest. Different. Easy. Affordable. Greenlight Financial - The all-in-one money and safety app for families. HelloFresh - America's #1 Meal Kit now offering 18 Free Meals and Free Breakfast for Life! Dripify - Premium learning platform for entrepreneurs. SolidGigs - Get more freelance jobs Learn more about your ad choices. Visit megaphone.fm/adchoices
In today's episode, we learned that working with agencies is a great way to fill your client pipeline regularly. But how does the money work if an agency will “white label” your services? Who gets what? How much? And when? These are the types of questions Nathan asks himself as he grows his business. He's got a few partnerships in the works, but he's unsure how to set up the money side. Naturally, we have a few ideas for him to try. Plus, we talk about how much to charge in your particular market and more. It's all in this episode of ‘Freelance to Founder.' Let's go. Mentioned in this episode: Web Astro - Nathan Mulligan's web design, branding, and content creation company. PS: Get featured in an upcoming Q&A! Just visit http://freelancetofounder.com/ask and submit a question. Support our sponsors so we can keep airing new episodes: Shopify - The global commerce platform. Build your business with Shopify to sell online, offline, and everywhere in between. LinkedIn Talent Solutions - With access to 900M professionals and real-time data, you can find and hire the right people to grow your business and make it thrive. Porkbun - An amazingly awesome ICANN accredited domain name registrar based out of the Pacific Northwest. Different. Easy. Affordable. Greenlight Financial - The all-in-one money and safety app for families. HelloFresh - America's #1 Meal Kit now offering 18 Free Meals and Free Breakfast for Life! Dripify - Premium learning platform for entrepreneurs. SolidGigs - Get more freelance jobs Get your own on-air coaching call We'd love to feature your business and offer some free on-air advice for growing your business. To see if you're a good fit, click here. Leave us a review on Apple Podcasts: If you enjoy the show, can you do us a favor and leave us an honest rating and review on Apple Podcasts? We'll love you forever. Click here to leave a review. More Recommended Listening: This show is a part of the Podglomerate, a company that produces, distributes, and monetizes podcasts. We encourage you to visit the website and sign up for our newsletter. We suggest you also try other Podglomerate shows about entrepreneurship, business, and creativity, such as Rocketship.fm and Creative Elements. Learn more about your ad choices. Visit megaphone.fm/adchoices
In today's Q&A, Rachel Stoneking, from our free Facebook Mastermind Group asked how she could get the passion for her business back. She shares her personal feelings of anxiety and disappointment after losing clients with COVID-19 and getting burned out with everything around it. "How do you overcome these negative feelings and connect back with the passion for your business?" We'll learn a lot from this difficult BUT important question. This episode was originally aired on June 21, 2022. To submit your question, visit FreelanceToFounder.com/ASK, and we'll feature you on an upcoming episode. Listen to our full-length coaching calls: http://freelancetofounder.com Support our sponsors so we can keep airing new episodes: Shopify - The global commerce platform. Build your business with Shopify to sell online, offline, and everywhere in between. LinkedIn Talent Solutions - With access to 900M professionals and real-time data, you can find and hire the right people to grow your business and make it thrive. Porkbun - An amazingly awesome ICANN accredited domain name registrar based out of the Pacific Northwest. Different. Easy. Affordable. Greenlight Financial - The all-in-one money and safety app for families. HelloFresh - America's #1 Meal Kit now offering 18 Free Meals and Free Breakfast for Life! Dripify - Premium learning platform for entrepreneurs. SolidGigs - Get more freelance jobs Learn more about your ad choices. Visit megaphone.fm/adchoices
On today's show: how does working less while making more money sound? Of course, it sounds fantastic! But actually, making it happen is much more complicated. That's where I find today's call-in guest, Diana. She's been freelancing for almost a year and has begun asking herself: what's next? Diana left her corporate job to pursue freedom through freelancing. Now, a year later, she's ready to dial it up and free up time to be with her three boys while still bringing in the revenue her family needs. If you're ready to work less while making more, then stay tuned to this episode of Freelance to Founder. Here we go. PS: Get featured in an upcoming Q&A! Just visit http://freelancetofounder.com/ask and submit a question. Support our sponsors so we can keep airing new episodes: Shopify - The global commerce platform. Build your business with Shopify to sell online, offline, and everywhere in between. LinkedIn Talent Solutions - With access to 900M professionals and real-time data, you can find and hire the right people to grow your business and make it thrive. Porkbun - An amazingly awesome ICANN accredited domain name registrar based out of the Pacific Northwest. Different. Easy. Affordable. Greenlight Financial - The all-in-one money and safety app for families. HelloFresh - America's #1 Meal Kit now offering 18 Free Meals and Free Breakfast for Life! Dripify - Premium learning platform for entrepreneurs. SolidGigs - Get more freelance jobs Get your own on-air coaching call We'd love to feature your business and offer some free on-air advice for growing your business. To see if you're a good fit, click here. Leave us a review on Apple Podcasts: If you enjoy the show, can you do us a favor and leave us an honest rating and review on Apple Podcasts? We'll love you forever. Click here to leave a review. More Recommended Listening: This show is a part of the Podglomerate, a company that produces, distributes, and monetizes podcasts. We encourage you to visit the website and sign up for our newsletter. We suggest you also try other Podglomerate shows about entrepreneurship, business, and creativity, such as Rocketship.fm and Creative Elements. Learn more about your ad choices. Visit megaphone.fm/adchoices
On today's show: how would you like to have clients like Nike, Netflix, Stripe, Twitch, Spotify and more? It's a dream-come-true as a freelancer. And this dream is a reality for motion graphics expert Kate—who's calling into the show today. Kate first talked with us a year ago and, since then, the entertainment industry has been through a lot which leaves Kate wondering where her career is headed and what's next. And we talk about a lot. From Kate's best advice on how to get jobs with big brands like she does TO whether or not you have to hire a team to grow. It's all on this episode of Freelance to Founder. Here we go. PS: Get featured in an upcoming Q&A! Just visit http://freelancetofounder.com/ask and submit a question. Support our sponsors so we can keep airing new episodes: Porkbun - An amazingly awesome ICANN accredited domain name registrar based out of the Pacific Northwest. Different. Easy. Affordable. Dripify - Premium learning platform for entrepreneurs. SolidGigs - Get more freelance jobs Get your own on-air coaching call We'd love to feature your business and offer some free on-air advice for growing your business. To see if you're a good fit, click here. Leave us a review on Apple Podcasts: If you enjoy the show, can you do us a favor and leave us an honest rating and review on Apple Podcasts? We'll love you forever. Click here to leave a review. More Recommended Listening: This show is a part of the Podglomerate, a company that produces, distributes, and monetizes podcasts. We encourage you to visit the website and sign up for our newsletter. We suggest you also try other Podglomerate shows about entrepreneurship, business, and creativity, such as Rocketship.fm and Creative Elements. Learn more about your ad choices. Visit megaphone.fm/adchoices
Dr. Diffie is a pioneer of public-key cryptography and was VP of Information Security and Cryptography at ICANN. He is author of "Privacy on the Line: The Politics of Wiretapping and Encryption". Visit https://www.securityweekly.com/psw for all the latest episodes! Follow us on Twitter: https://www.twitter.com/securityweekly Like us on Facebook: https://www.facebook.com/secweekly Show Notes: https://securityweekly.com/vault-psw-6
How masked domain owners can be unmasked through ICANN's new Registration Data Request Service (RDRS) WhatsApp's addition of Secret Code for extra privacy protection in Chat Lock Iranian hackers exploited default passwords in programmable logic controllers at US water facilities Attempt by Montana to ban TikTok statewide was stalled by a federal judge ruling Over 1 billion Android devices now have RCS messaging enabled EU Cyber Resilience Act will improve security of Internet of Things devices sold in the EU Black Basta ransomware group has netted over $107 million since early 2022 Google's new .meme top-level domain allowing meme-related web properties CISA's Secure by Design initiative echoes security best practices frequently recommended on the podcast France plans to ban use of "foreign" end-to-end encrypted messaging apps like Telegram and require use of French app Olvid instead Concerns raised by industry experts Ivan Ristic and Ryan Hurst about EU's eIDAS 2.0 legislation undermining certificate authority trust Show Notes - https://www.grc.com/sn/SN-951-Notes.pdf Hosts: Steve Gibson and Leo Laporte Download or subscribe to this show at https://twit.tv/shows/security-now. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6. Sponsors: canary.tools/twit - use code: TWIT vanta.com/SECURITYNOW
How masked domain owners can be unmasked through ICANN's new Registration Data Request Service (RDRS) WhatsApp's addition of Secret Code for extra privacy protection in Chat Lock Iranian hackers exploited default passwords in programmable logic controllers at US water facilities Attempt by Montana to ban TikTok statewide was stalled by a federal judge ruling Over 1 billion Android devices now have RCS messaging enabled EU Cyber Resilience Act will improve security of Internet of Things devices sold in the EU Black Basta ransomware group has netted over $107 million since early 2022 Google's new .meme top-level domain allowing meme-related web properties CISA's Secure by Design initiative echoes security best practices frequently recommended on the podcast France plans to ban use of "foreign" end-to-end encrypted messaging apps like Telegram and require use of French app Olvid instead Concerns raised by industry experts Ivan Ristic and Ryan Hurst about EU's eIDAS 2.0 legislation undermining certificate authority trust Show Notes - https://www.grc.com/sn/SN-951-Notes.pdf Hosts: Steve Gibson and Leo Laporte Download or subscribe to this show at https://twit.tv/shows/security-now. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6. Sponsors: canary.tools/twit - use code: TWIT vanta.com/SECURITYNOW
How masked domain owners can be unmasked through ICANN's new Registration Data Request Service (RDRS) WhatsApp's addition of Secret Code for extra privacy protection in Chat Lock Iranian hackers exploited default passwords in programmable logic controllers at US water facilities Attempt by Montana to ban TikTok statewide was stalled by a federal judge ruling Over 1 billion Android devices now have RCS messaging enabled EU Cyber Resilience Act will improve security of Internet of Things devices sold in the EU Black Basta ransomware group has netted over $107 million since early 2022 Google's new .meme top-level domain allowing meme-related web properties CISA's Secure by Design initiative echoes security best practices frequently recommended on the podcast France plans to ban use of "foreign" end-to-end encrypted messaging apps like Telegram and require use of French app Olvid instead Concerns raised by industry experts Ivan Ristic and Ryan Hurst about EU's eIDAS 2.0 legislation undermining certificate authority trust Show Notes - https://www.grc.com/sn/SN-951-Notes.pdf Hosts: Steve Gibson and Leo Laporte Download or subscribe to this show at https://twit.tv/shows/security-now. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6. Sponsors: canary.tools/twit - use code: TWIT vanta.com/SECURITYNOW
How masked domain owners can be unmasked through ICANN's new Registration Data Request Service (RDRS) WhatsApp's addition of Secret Code for extra privacy protection in Chat Lock Iranian hackers exploited default passwords in programmable logic controllers at US water facilities Attempt by Montana to ban TikTok statewide was stalled by a federal judge ruling Over 1 billion Android devices now have RCS messaging enabled EU Cyber Resilience Act will improve security of Internet of Things devices sold in the EU Black Basta ransomware group has netted over $107 million since early 2022 Google's new .meme top-level domain allowing meme-related web properties CISA's Secure by Design initiative echoes security best practices frequently recommended on the podcast France plans to ban use of "foreign" end-to-end encrypted messaging apps like Telegram and require use of French app Olvid instead Concerns raised by industry experts Ivan Ristic and Ryan Hurst about EU's eIDAS 2.0 legislation undermining certificate authority trust Show Notes - https://www.grc.com/sn/SN-951-Notes.pdf Hosts: Steve Gibson and Leo Laporte Download or subscribe to this show at https://twit.tv/shows/security-now. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6. Sponsors: canary.tools/twit - use code: TWIT vanta.com/SECURITYNOW
How masked domain owners can be unmasked through ICANN's new Registration Data Request Service (RDRS) WhatsApp's addition of Secret Code for extra privacy protection in Chat Lock Iranian hackers exploited default passwords in programmable logic controllers at US water facilities Attempt by Montana to ban TikTok statewide was stalled by a federal judge ruling Over 1 billion Android devices now have RCS messaging enabled EU Cyber Resilience Act will improve security of Internet of Things devices sold in the EU Black Basta ransomware group has netted over $107 million since early 2022 Google's new .meme top-level domain allowing meme-related web properties CISA's Secure by Design initiative echoes security best practices frequently recommended on the podcast France plans to ban use of "foreign" end-to-end encrypted messaging apps like Telegram and require use of French app Olvid instead Concerns raised by industry experts Ivan Ristic and Ryan Hurst about EU's eIDAS 2.0 legislation undermining certificate authority trust Show Notes - https://www.grc.com/sn/SN-951-Notes.pdf Hosts: Steve Gibson and Leo Laporte Download or subscribe to this show at https://twit.tv/shows/security-now. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6. Sponsors: canary.tools/twit - use code: TWIT vanta.com/SECURITYNOW
© 2020-2025 Ivy Podcast Discovery LLC
