Podcasts about ipfs

In this episode, Peter dives into an important development for Cardano governance: the release of a new decentralised voting tool by the Cardano Foundation. This open-source platform, accessible at voting.cardanofoundation.org, enables DReps (Delegated Representatives), SPOs (Stake Pool Operators), and Constitutional Committee members to vote on-chain using a streamlined interface.Critically, the tool supports multisig wallets and stores immutable voting rationales on IPFS via integrations with Endmaker or custom IPFS providers. The release comes at a crucial time, as the existing community-built voting tool, GovTools, is facing funding challenges. GovTools wasn't included in the latest Intersect budget, leaving its continued development uncertain. A 100k ADA maintenance grant will keep the tool functional for now, but future progress depends on renewed community support.Peter walks through how the Cardano Foundation's tool works, outlining the step-by-step process from inputting your DRep ID to signing and submitting your vote. The new interface simplifies rationale submission, removing the need for GitHub uploads and allowing users to use Endmaker API tokens or even custom storage like Iagon.Crucially, the entire voting tool is open source and can be run locally or on private infrastructure, which ensures the resilience and decentralisation of Cardano governance. If hosted tools like GovTools go offline, users can still vote independently. This tool complements other platforms in the governance ecosystem like Tempo Vote, Governance.space, and the Cardano Forum, but it's one of the few to offer full voting capabilities.Peter applauds the Cardano Foundation for their contribution to the ecosystem's decentralisation and encourages the community to explore this new tool to strengthen participation in on-chain governance.

I, Stewart Alsop, am thrilled to welcome Xathil of Poliebotics to this episode of Crazy Wisdom, for what is actually our second take, this time with a visual surprise involving a fascinating 3D-printed Bauta mask. Xathil is doing some truly groundbreaking work at the intersection of physical reality, cryptography, and AI, which we dive deep into, exploring everything from the philosophical implications of anonymity to the technical wizardry behind his "Truth Beam."Check out this GPT we trained on the conversationTimestamps01:35 Xathil explains the 3D-printed Bauta Mask, its Venetian origins, and its role in enabling truth through anonymity via his project, Poliepals.04:50 The crucial distinction between public identity and "real" identity, and how pseudonyms can foster truth-telling rather than just conceal.10:15 Addressing the serious risks faced by crypto influencers due to public displays of wealth and the broader implications for online identity.15:05 Xathil details the core Poliebotics technology: the "Truth Beam," a projector-camera system for cryptographically timestamping physical reality.18:50 Clarifying the concept of "proof of aliveness"—verifying a person is currently live in a video call—versus the more complex "proof of liveness."21:45 How the speed of light provides a fundamental advantage for Poliebotics in outmaneuvering AI-generated deepfakes.32:10 The concern of an "inversion," where machine learning systems could become dominant over physical reality by using humans as their actuators.45:00 Xathil's ambitious project to use Poliebotics for creating cryptographically verifiable records of biodiversity, beginning with an enhanced Meles trap.Key InsightsAnonymity as a Truth Catalyst: Drawing from Oscar Wilde, the Bauta mask symbolizes how anonymity or pseudonyms can empower individuals to reveal deeper, more authentic truths. This challenges the notion that masks only serve to hide, suggesting they can be tools for genuine self-expression.The Bifurcation of Identity: In our digital age, distinguishing between one's core "real" identity and various public-facing personas is increasingly vital. This separation isn't merely about concealment but offers a space for truthful expression while navigating public life.The Truth Beam: Anchoring Reality: Poliebotics' "Truth Beam" technology employs a projector-camera system to cast cryptographic hashes onto physical scenes, recording them and anchoring them to a blockchain. This aims to create immutable, verifiable records of reality to combat the rise of sophisticated deepfakes.Harnessing Light Speed Against Deepfakes: The fundamental defense Poliebotics offers against AI-generated fakes is the speed of light. Real-world light reflection for capturing projected hashes is virtually instantaneous, whereas an AI must simulate this complex process, a task too slow to keep up with real-time verification.The Specter of Humans as AI Actuators: A significant future concern is the "inversion," where AI systems might utilize humans as unwitting agents to achieve their objectives in the physical world. By manipulating incentives, AIs could effectively direct human actions, raising profound questions about agency.Towards AI Symbiosis: The ideal future isn't a human-AI war or complete technological asceticism, but a cooperative coexistence between nature, humanity, and artificial systems. This involves developing AI responsibly, instilling human values, and creating systems that are non-threatening and beneficial.Contact Information*   Polybotics' GitHub*   Poliepals*   Xathil: Xathil@ProtonMail.com

Rancho Mesa President Dave Garcia sits down with Korben Konrady with IPFS to talk about how the economy affects the insurance industry.Show Notes: IPFS,⁠ ⁠⁠⁠⁠⁠⁠Subscribe to Rancho Mesa's Newsletter⁠⁠⁠⁠⁠⁠Host: ⁠⁠⁠⁠⁠⁠Dave GarciaGuest: Korben KonradyEditor: Jadyn BrandtMusic: "Home" by JHS Pedals, “Breaking News Intro” by nem0production© Copyright 2025. Rancho Mesa Insurance Services, Inc. All rights reserved.

In this week's episode of MARS, hosts Matthew and Rizzle begin by discussing their most recent digital art and collectible purchases.The conversation then shifts to the unique pace of digital interaction enabled by NFTs compared to coins, noting how NFTs facilitate a slower, more deliberate engagement. Next, Rizzle comments on the noticeable scarcity of projects and individuals who have remained active in the space up to this point. Matthew follows by introducing a straightforward framework he's been developing to classify current blockchains, frequently used projects, and active crypto communities. His categorization hinges on whether they existed pre-COVID. Although the resulting list (shared below) is concise, it embodies a persistent ethos and spirit driving the crypto space forward. This list highlights builders, creators, and communities who consistently make the most significant and intentional contributions to the crypto space.Support MARS by minting a free edition of this episode at Pods.Media.Shout-outs & Shots-fired:@zora @solana @luchopoletti @CatOrRaccoon @I____felix____I @CYPHERDUDES @pepenoun @memeexplorers @fx_hash_ @BnoiitC @0xdiid @voxeliving @ripe0x @manifoldxyz @maxosirisart @artbasel @jeffgdavis @ethereumfndn @lukeweaver_eth @tezos @rodeodotclub @JoelKruger @cent @bitcoin @superrare @josiebellini @JOYdotWORLD @opensea @ensdomains @metamask @coinbase @uniswap @niftygateway @samspratt @safe @gnosischain @cryptovoxels @decentraland @TheSandboxGame @somniumspace @IPFS @pinatacloud @base @ethereum @basileus_eth @editionalapp @paypal @axieinfinity @cryptopunksnft s@cryptokitties @poopie @doodles @dwr @farcaster_xyz @steveklbnf @warpcast_ @atbarbaralove @cultcryptoart @baybackner @madebyoona @dragonateyt @dragonatesmomPre-COVID Chains, Projects, & Communities/Mafias active in 2025:****ChainsEthereumBTC & Tezos (only because of art)****ProjectsSRNG (via v1)OSENSIPFSPinataMetaMaskCBWallet (via cipher)UniswapSafe (via gnosis)CVDCL****CommunitiesEarly crypto artist mafia (incl. SR + KO + Josie + JOY)The WIPEditional/Cent mafia0x mafiaCB mafiaCK mafiaPunksRare PepeAxie

What if the future of healthcare lies in our ability to decentralize it? This episode takes us on an insightful journey with Jasmine Smith, the visionary CEO of Rejuve AI. She shares her fascinating transition from health information management to leading a groundbreaking project in decentralized health and wellness. The transformation from Web 2.0 to Web 3.0 is laid bare, with Jasmine revealing how this evolution empowers individuals by taking control away from traditional central entities and addressing challenges like scalability and user experience. We also uncover how technologies such as IPFS and Filecoin are poised to revolutionize sectors like healthcare, particularly in data handling and security.We venture into the intersection of AI, blockchain, and longevity research through Rejuve AI's decentralized platform. This network ambitiously crowdsources health data from users, leveraging wearable devices and health surveys, with future plans for genomic data integration. By personalizing health protocols, Rejuve AI aims to deepen users' understanding of their physiological data, marking a significant stride toward democratizing health information. There's a burgeoning movement toward decentralized science, with comparisons drawn to initiatives like Matt Kaberlein's crowdsource database for rapamycin and VitaDAO's innovative research efforts.As we explore decentralized science further, the episode delves into how it fosters fairness, reduces bias, and accelerates research, especially in the field of aging. VitaDAO's novel approach to funding biotech startups through tokenized intellectual property is highlighted, offering a glimpse into the future of rapid therapy development. The synergy between VitaDAO and Rejuve AI is palpable, with both entities pushing the boundaries of health innovation. Listeners can anticipate the launch of the Rejuve AI app in early 2025, a tool designed to enhance user health and longevity through a freemium model backed by the RJV token. These initiatives are set to transform healthcare into a more collaborative and data-driven industry, promising a healthier future for all.https://www.rejuve.ai/Free sample chapter -Lies I Taught In Medical School :https://www.robertlufkinmd.com/lies/Our sponsors: Complete Metabolic Heart Scan ($100 off with 'LUFKINCT') https://robert-lufkin.mykajabi.com/CMHS Siphox Health, at-home health testing (15% off):https://pathlongevity.com/Prolon & the Fasting Mimicking Diet (20% off ):https://prolonlife.com/Lufkin *** CONNECT***Web: https://robertlufkinmd.com/X: https://x.com/robertlufkinmdYoutube: https://www.youtube.com/robertLufkinmdInstagram: https://www.instagram.com/robertlufkinmd/LinkedIn: https://www.linkedin.com/in/robertlufkinmd/Facebook: https://www.facebook.com/robertlufkinmd Threads: ...

Lex interviews Sam Williams - founder of Arweave. This episode delves into the innovative aspects of Arweave, a protocol designed for permanent data storage and computation within the Web3 ecosystem. The discussion covers a range of topics, from the economic models underpinning Arweave to its potential applications in decentralized finance (DeFi) and beyond. Notable discussion points: The Founding of Arweave and its Mission – Sam Williams' interest in distributed computing and concerns about authoritarianism led him to create Arweave in 2017. Inspired by the Snowden leaks, he saw the need for a blockchain-based permanent storage solution to protect journalism, historical records, and digital assets from censorship. Decentralized vs. Distributed Storage – Williams explained how Arweave differs from alternatives like IPFS and Filecoin. Unlike traditional storage, which requires ongoing payments, Arweave uses a one-time payment model. This storage endowment leverages declining storage costs to ensure long-term data persistence without relying on centralized infrastructure. Arweave's Expansion into Decentralized Compute – Arweave has evolved beyond storage to develop decentralized computing through "Arweave IO." This enables parallelized smart contract execution, making it possible to run AI models, financial automation, and decentralized apps on-chain—aligning with Web3's shift toward autonomous, intelligent systems.MENTIONED IN THE CONVERSATION Topics: Arweave, permanent data storage, Web3, decentralized systems, distributed systems, blockchain, economic models, IPFS, Filecoin, decentralized computing, decentralized finance, compute ABOUT THE FINTECH BLUEPRINT 

Upset over illicit sports streaming websites, Canal+ petitioned a French court to order Google, Cloudflare, Quad9 and Vercara to no longer resolve queries to domains like antenasports.ru. We discuss whether the court's decision to side with Canal+ amounts to "internet censorship" and whether it will have any effect. Check out our accompanying article at royalpalacemedia.comA few precisions/corrections:- Canal+ Groupe has been recently restructured such what we said about Vavendi is not longer up-to-date (the firm remains nonetheless under the control of the Bolloré family).- The acronym for the Inter-planetary File System is "IPFS" but Patrick mistakenly says IFS because interplanetary is arguably one word.- Our website does not have a certificate issued by Cloudflare, but rather Google Trust Services which is one of the five certificate authorities Cloudflare uses to issues SSL certs.

Can decentralization truly revolutionize how we store data? In this episode of The Index, Alex Kehaya talks with Dmitriy Ryajov, Founder and Architect of the Codex Durability Engine at codex.storage, a leader in decentralized storage. Dmitry shares his inspiring journey from traditional software developer to trailblazer in the decentralized tech community. Discover how his early work with Ethereum and IPFS ignited his passion for peer-to-peer systems and open-source contributions.We dive into the complexities of building decentralized storage systems, exploring established players like Filecoin and Arweave alongside emerging solutions like the Shadow Network on Solana. Dmitry tackles these challenges head-on with Codex.For developers, privacy and security are paramount. We discuss data encryption methods, such as symmetric key encryption and data distribution, to safeguard against unauthorized access.Learn how Codex is redefining the landscape of data storage and shaping the future of the internet. This episode is a must-listen for anyone interested in the technical intricacies of decentralized systems.Website: https://codex.storage/Show LinksThe Index X ChannelYouTube

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

What do technologies such as HOME, Noomap, Core Network, Nodesphere, CEPTR, Hylo, Backfeed, Metamaps, Kumu in addition to Web 3.0 and Blockchain projects, such as Ethereum, Bitcoin, NXT and IPFS have in common and how are they related to concepts like Game B, synergistic democracy, co-creation and building the Noosphere? This week's radio hour gives a brief introduction to the Network State in attempt to provide a Birds Eye view of the philosophies and ideologies that drive the technology and infrastructure that being created. What may appear as fringe/ start up might upon deeper examination be uncovered as a master Silicon Valley venture partnered with NGOs linked to the UN etc. Listen weekly as Courtenay broadcasts deeper dives into truth, globally via the WWCR airwaves. Catch the Courtenay Turner Show, LIVE every Monday at 3pm CST. Tune in LIVE via Shortwave Radio on 9.350mHz, or via MP3 stream at: https://bit.ly/CourtenayTurnerShow ▶Episode Resources: ✩ About "The Network State" https://thenetworkstate.com ✩ Balaji Srinivasan's book: "The Network State: How To Start a New Country" https://amzn.to/4fmMhxT ____________________________________________________________________ ▶ GET On-Demand Access for Courtenay's Cognitive Liberty Conference: https://cognitivelibertyconference.com ----------------------------------------- ▶ Follow & Connect with Courtenay:
 https://www.courtenayturner.com ✩ Linktree: https://linktr.ee/courtenayturner ▶ Support my work & Affiliate links:
 ✩Buy Me A Coffee! https://www.buymeacoffee.com/courtzt ✩GiveSendGo: https://www.givesendgo.com/courtenayturnerpodcast ✩Venmo: https://account.venmo.com/u/Courtenay-Turner ✩Cash App: https://cash.app/$CourtzJT ✩ Gold Gate Capital (Secure Your Wealth!) https://bit.ly/COURTZGoldSilver ✩ SatPhone123 (Claim Your Free Satellite Phone!) https://bit.ly/COURTZ123 Promo Code: COURTZ ✩ Richardson Nutritional Center: (B-17!)
 https://rncstore.com/courtz ✩ Relax Far Infrared Saunas: (Warm Up!) https://relaxsaunas.com/COURTZ Discount Code: COURTZ ✩Discover The Magic of MagicDichol: https://iwantmyhealthback.com/COURTZ ✩Defy The Grid With Real Currency.....Goldbacks!: https://bit.ly/Courtenay-Turner-Goldbacks Promo Code: COURTZ ✩Honey Colony "Where The Hive Decides What's Healthy":
https://bit.ly/HoneyColony-COURTZ Promo Code: COURTZ ▶ Follow Courtenay on Social Media: ✩Twitter: 
https://twitter.com/KineticCourtz ✩Substack: https://courtenayturner.substack.com ✩TruthSocial: https://truthsocial.com/@CourtenayTurner ✩Instagram: https://instagram.com/kineticcourtz ✩Telegram: https://t.me/courtenayturnerpodcastcommunity ▶ Listen to &/or watch the podcast here! https://linktr.ee/courtenayturner —————————————————
 ▶ Disclaimer: this is intended to be inspiration & entertainment. We aim to inform, inspire & empower. Guest opinions/ statements are not a reflection of the host or podcast. Please note these are conversational dialogues. All statements and opinions are not necessarily meant to be taken as fact. Please do your own research. Thanks for watching! 
—————————————————
 ©2024 All Rights Reserved Learn more about your ad choices. Visit megaphone.fm/adchoices

Guest Nolan Lawson Panelist Richard Littauer | Eric Berry | Justin Dorfman Show Notes In this episode of Sustain, Richard, Justin, and Eric revisit an unreleased interview with Nolan Lawson from 2020. They discuss Nolan's experience as a former maintainer of PouchDB, the emotional labor of being an open source maintainer, and the challenges that led him to step away from such high-profile projects. Nolan also shares his thoughts on the impact of reputation-driven development, open source community dynamics, and his journey towards a healthier relationship with open source. The conversation delves into the candid realities of burnout and the personal sacrifices often made by unpaid open source contributors. Nolan highlights his transition to more sustainable open source practices and his new interests including his work on a Mastodon client called Pinafore. Download now to hear more! [00:01:43] Nolan explains his background with PouchDB and shares his fascination with databases and browser technologies. [00:02:58] Richard shares his personal connection to PouchDB, mentioning how he discovered Nolan through his work on the project. [00:03:26] Nolan talks about his blog post form 2017 titled, “What it feels like to be an open source maintainer,” which reflected on the emotional toll and burnout he experienced for maintaining PouchDB. [00:05:33] Justin reflects on the impact of Nolan's blog post, describing it as a “shot heard around the world” in the open source community. [00:06:48] Eric asks why Nolan and other maintainers stay involved in open source despite the challenges. Nolan explains that reputational benefits and personal interest in the technology were initial motivators for staying involved. [00:10:27] Eric asks Nolan how he realized it was time to step away from maintaining PouchDB. Nolan shares that personal life changes helped him reassess his involvement in open source and reflects on advice he received from other maintainers. [00:14:36] Richard emphasizes the personal and emotional investment many maintainers have in their projects and Nolan acknowledges the privilege of being able to work on open source, but also the challenges it poses for maintainers who feel they cannot leave. [00:21:13] Nolan shares stepping away from PouchDB has improved his mental health and personal relationships and he maintains smaller open source projects. [00:24:00] Nolan explains the importance of being personally invested in a project and realizing when it's time to move on and Justin reflects on his own experience of stepping away from maintaining a project after years of involvement. [00:26:00] Eric asks if funding could have made a difference for Nolan's involvement in open source, and Nolan shares that he avoided funding, preferring to keep his work as a “labor of love.” [00:26:52] What is Nolan currently doing? He talks about maintaining a Mastodon client and focusing on personal projects that bring him joy. [00:30:00] Richard discusses the importance of balancing open source work with personal life and the need for a sustainable approach to maintaining projects. [00:30:46] Eric highlights the vulnerability and self-awareness Nolan has shown in discussing his open source journey, thanking him for sharing his experiences. [00:33:13] Find out where you can follow Nolan on the internet. Spotlight [00:33:41] Justin's spotlight is Metabase. [00:34:16] Eric's spotlight is Parametric. [00:35:08] Richard's spotlight is IPFS. [00:35:22] Nolan's spotlight is fake-indexeddb. Links SustainOSS (https://sustainoss.org/) podcast@sustainoss.org (mailto:podcast@sustainoss.org) richard@sustainoss.org (mailto:richard@sustainoss.org) SustainOSS Discourse (https://discourse.sustainoss.org/) SustainOSS Mastodon (https://mastodon.social/tags/sustainoss) Open Collective-SustainOSS (Contribute) (https://opencollective.com/sustainoss) Richard Littauer Socials (https://www.burntfen.com/2023-05-30/socials) Justin Dorfman X (https://twitter.com/jdorfman?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Eric Berry X (https://x.com/coderberry?lang=en) Nolan Lawson Blog (https://nolanlawson.com/) Nolan Lawson Mastodon (https://toot.cafe/@nolan) “What it feels like to be an open source maintainer” (Blog post by Nolan) (https://nolanlawson.com/2017/03/05/what-it-feels-like-to-be-an-open-source-maintainer/) PouchDB (https://pouchdb.com/) Pinafore (https://pinafore.social/) Salesforce (https://www.salesforce.com/) Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal (https://press.stripe.com/working-in-public) Metabase (https://www.metabase.com/) Parametric (https://github.com/ismasan/parametric) IPFS (https://www.ipfs.com/) fake-indexeddb (GitHub) (https://github.com/dumbmatter/fakeIndexedDB) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Nolan Lawson.

Rust meets Linux in a clash of coding cultures. Why some developers are resisting, and where things go from here.Sponsored By:Core Contributor Membership: Take $1 a month of your membership for a lifetime!Tailscale: Tailscale is a programmable networking software that is private and secure by default - get it free on up to 100 devices! 1Password Extended Access Management: 1Password Extended Access Management is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps. Support LINUX UnpluggedLinks:

Synthetix launches the USDx stablecoin. BGD Labs evaluates zkSync Era readiness for Aave V3. And Pinata Cloud releases a Content Attestation Plugin. Read more: https://ethdaily.io/520 Sponsor: Firefly is a one-stop Web3 social aggregator developed by Mask Network. Use one feed to connect with all users across Twitter, Lens, Farcaster, and all Web3 socials. Try it today at firefly.social.

In this episode of Hashing It Out by Cointelegraph, host Owusu Akyaw interviews Pavel Bains, co-founder and CEO of Bluzelle, about decentralized physical infrastructure networks (DePINs). They discuss what DePINs are, why there's growing interest in them, and the role of storage in this ecosystem. Bains explains how Bluzelle is building a decentralized storage network on top of IPFS, offering better security and redundancy than traditional models. They also touch on the use of AI in managing data storage, the importance of incentives in the Web3 space, and the potential interaction between DePINs and DeFi.Timestamps: (00:00) - Introduction to the episode(02:21) - Analysis of the current crypto market, past trends, and prediction of future movements(07:57) - The concept of decentralized physical infrastructure networks(09:54) - Rise of DePINs, the reasons behind the hype(11:16) - Bluzelle's use of IPFs and comparison with traditional storage models(15:55) - The importance of storage in the DePIN ecosystem(17:50) - Challenges in building decentralized storage solutions(19:59) - The role of AI in data storage, potential applications, and limitations of AI in this space(24:10) - The importance of providing incentives in Web3 space(27:30) - The interplay between DeFi and decentralized infrastructure(29:27) - Future of decentralized infrastructureFollow Cointelegraph on Twitter: @CointelegraphFollow the host on Twitter: @ghcryptoguy, or connect with him on LinkedIn: Elisha (GhCryptoGuy)Cointelegraph's website: cointelegraph.comThe views, thoughts, and opinions expressed in this podcast are its participants' alone and do not necessarily reflect or represent the views and opinions of Cointelegraph. This podcast (and any related content) is for entertainment purposes only and does not constitute financial advice, nor should it be taken as such. Everyone must do their own research and make their own decisions. The podcast's participants may or may not own any of the assets mentioned.

With the evolution and the capabilities of AI and the questioning of authenticity during the time of Presidential elections, it is getting increasingly more important that data and files are unable to be corrupted and not controlled by a centralized party. In this episode,  Ian Andrews (CMO, Chainalysis) speaks with renowned cryptocurrency and civil liberties attorney, Marta Belcher (President & Chair, Filecoin Foundation). It's a timely discussion that traverses the innovations and societal impacts of decentralized technologies and how Filecoin and IPFS's decentralized storage solutions are at the forefront of what could be an International shift to securing information. Marta provides exclusive insights into the incredible collaboration with Lockheed Martin deploying IPFS in space and she shares her insights on the recent advances in crypto policy, discussing the importance of the FIT21 bill and the complexities of privacy and content moderation in the digital age. Minute-by-minute episode breakdown 2 | Marta Belcher's journey into Bitcoin, cryptocurrency and civil liberties  4 | Introduction to IPFS and the benefits of decentralized file storage 12 | Understanding the scale of Filecoin and the amount of data and type of data being stored 16 | Filecoin and IPFS technology demonstrated in space with Lockheed Martin 21 | Dealing with decentralized content moderation on web3 platforms  27 | Crypto policy shifts and legal battles unfolding in USA with the FIT21 Bill and the introduction of the Digital Asset Anti-Money Laundering Act  31 | Insights into the debate on privacy vs. anonymity when it relates to cryptocurrency    Related resources Check out more resources provided by Chainalysis that perfectly complement this episode of the Public Key. Website: Filecoin Foundation: On a mission to preserve humanity's most important information Website: Filecoin: Decentralized storage network designed to store humanity's most important information Article: Marta Belcher: Reframing Privacy for the Digital Age Article: Transcript Audio: Elizabeth Warren's New Financial Surveillance Bill Is a Disaster for Privacy and Civil Liberties Report: Chainalysis Money Laundering and Cryptocurrency Report (Available Now) Report: [REPORT PREVIEW] Malign Interference and Crypto: How Crypto Transaction Tracing Can Expose and Disrupt Malign Influence Efforts YouTube: Chainalysis YouTube page Twitter: Chainalysis Twitter: Building trust in blockchain Tik Tok: Building trust in #blockchains among people, businesses, and governments Telegram: Chainalysis on Telegram Speakers on today's episode Ian Andrews * Host * (Chief Marketing Officer, Chainalysis)  Marta Belcher (President & Chair, Filecoin Foundation) This website may contain links to third-party sites that are not under the control of Chainalysis, Inc. or its affiliates (collectively “Chainalysis”). Access to such information does not imply association with, endorsement of, approval of, or recommendation by Chainalysis of the site or its operators, and Chainalysis is not responsible for the products, services, or other content hosted therein. Our podcasts are for informational purposes only, and are not intended to provide legal, tax, financial, or investment advice. Listeners should consult their own advisors before making these types of decisions. Chainalysis has no responsibility or liability for any decision made or any other acts or omissions in connection with your use of this material. Chainalysis does not guarantee or warrant the accuracy, completeness, timeliness, suitability or validity of the information in any particular podcast and will not be responsible for any claim attributable to errors, omissions, or other inaccuracies of any part of such material.  Unless stated otherwise, reference to any specific product or entity does not constitute an endorsement or recommendation by Chainalysis. The views expressed by guests are their own and their appearance on the program does not imply an endorsement of them or any entity they represent. Views and opinions expressed by Chainalysis employees are those of the employees and do not necessarily reflect the views of the company.

In this episode of Shoptalk, David Carothers emphasizes the importance of prospecting in the current busy market, highlighting how neglecting it can lead to a lack of organic opportunities in the pipeline. He argues that prospecting should never be abandoned, even when inbound leads are abundant, to ensure agencies are writing the types of policies they want and can control their direct carriers. Key Points: Importance of prospecting in insurance sales despite busy periods ·       David Carothers thanks sponsors for supporting producers in paradise, highlighting IPFS's leadership. ·       David Carothers argues that agencies should prioritize prospecting new business, even when inbound leads are flowing. ·       He believes that relying solely on inbound leads can lead to a lack of foundation and pipeline in the future. Prioritizing inbound vs outbound leads in insurance agencies ·       David Carothers argues that relying solely on inbound leads can lead to wasted time and effort. ·       He suggests prioritizing prospecting to secure the business agencies want. ·       David Carothers describes offshore fishing trip, including bait fishing techniques. Fishing and the importance of efficient prospecting in the hard market ·       David Carothers shares his fishing experience and its relevance to insurance agencies in the hard market. ·       He emphasizes the importance of prospecting and hitting KPIs in the industry. Connect with: David Carothers LinkedIn Kyle Houck LinkedIn Visit Websites: Killing Commercial Power Producers Podcast The Dirty 130 The Extra 2 Minutes  

This is my conversation with Molly Mackinlay, Head of Engineering, Product, and Research Development at Protocol Labs, and CEO at FilOz.Timestamps:- 00:00:00 intro- 00:01:59 sponsor: Privy- 00:03:15 motivation- 00:09:30 exabytes of network capacity- 00:12:11 edge computing, bringing compute to data- 00:14:26 the history of IPFS, libp2p, IPLD, Filecoin, FVM, L2s and IPC- 00:20:08 designing incentives in Filecoin- 00:25:11 designing the block rewards curve- 00:27:28 progress through time- 00:31:19 learnings from building production systems, - 00:34:15 EVM-compatibility, future-proofing and network upgrades- 00:43:51 sponsor: Optimism- 00:44:56 IPC, L2 scaling on Filecoin- 00:48:55 architecting applications on subnets- 00:54:12 business models on subnets- 00:57:27 the interface between a subnet and the internet- 01:04:41 FilOz as a public goods amplifier- 01:07:10 opening up the Protocol Labs network- 01:12:23 Edge Esmeralda, field building, neurotech, and education- 01:21:04 outroLinks:Molly Mackinlay - https://x.com/momack28Protocol Labs - https://protocol.aiFilecoin - https://filecoin.ioFilOz - https://www.filoz.orgInterPlanetary Consensus - https://www.ipc.space/ Textile Basin - https://basin.textile.io/ web3.storage - https://web3.storage/ Filecoin Virtual Machine - https://fvm.filecoin.io/ Thank you to our sponsors for making this podcast possible:Optimism - https://optimism.io Privy - https://privy.io Into the Bytecode:Twitter - https://twitter.com/sinahab Farcaster - https://warpcast.com/sinahab Other episodes - https://intothebytecode.com Disclaimer: this podcast is for informational purposes only. It is not financial advice nor a recommendation to buy or sell securities. The host and guests may hold positions in the projects discussed.

A bombshell report concerning executive compensation at The HBAR Foundation and the reactions from the Hedera community. I also have an in-depth interview with Grelf on the subject and we see a whole new side to this bald, woodland creature. I give massive community shoutouts to ""the little guys"", plus, other top headlines in the ecosystem. Live

In this episode of the Crazy Wisdom Podcast, host Stewart Alsop welcomes Lachlan Phillips, founder of LiveMind AI, for a compelling conversation about the implications of decentralized AI. They discuss the differences between centralized and decentralized systems, the historical context of centralization, and the potential risks and benefits of distributed computing and storage. Topics also include the challenges of aligning AI with human values, the role of supervised fine-tuning, and the importance of trust and responsibility in AI systems. Tune in to hear how decentralized AI could transform technology and society. Check out LiveMind AI and follow Lachlan on Twitter at @bitcloud for more insights. Check out this GPT we trained on the conversation! Timestamps 00:00 Introduction of Lachlan Phillips and discussion on decentralized AI, comparing it to human brain structure and the World Wide Web. 00:05 Further elaboration on decentralization and centralization in AI and its historical context, including the impact of radio, TV, and the internet. 00:10 Discussion on the natural emergence of centralization from decentralized systems and the problems associated with centralized control. 00:15 Comparison between centralized and decentralized systems, highlighting the voluntary nature of decentralized associations. 00:20 Concerns about large companies controlling powerful AI technology and the need for decentralization to avoid issues similar to those seen with Google and Facebook. 00:25 Discussion on Google's centralization, infrastructure, and potential biases. Introduction to distributed computing and storage concepts. 00:30 Lachlan Phillips shares his views on distributed storage and mentions GunDB and IPFS as examples of decentralized systems. 00:35 Exploration of the relationship between decentralized AI and distributed storage, emphasizing the need for decentralized training of AI models. 00:40 Further discussion on decentralized AI training and the potential for local models to handle specific tasks instead of relying on centralized infrastructures. 00:45 Conversation on the challenges of aligning AI with human values, the role of supervised fine-tuning in AI training, and the involvement of humans in the training process. 00:50 Speculation on the implications of technologies like Neuralink and the importance of decentralizing such powerful tools to prevent misuse. 00:55 Discussion on network structures, democracy, and how decentralized systems can better represent collective human needs and values. Key Insights Decentralization vs. Centralization in AI: Lachlan Phillips highlighted the fundamental differences between decentralized and centralized AI systems. He compared decentralized AI to the structure of the human brain and the World Wide Web, emphasizing collaboration and distributed control. He argued that while centralized AI systems concentrate power and decision-making, decentralized AI systems mimic natural, more organic forms of intelligence, potentially leading to more robust and democratic outcomes. Historical Context and Centralization: The conversation delved into the historical context of centralization, tracing its evolution from the era of radio and television to the internet. Stewart Alsop and Lachlan discussed how centralization has re-emerged in the digital age, particularly with the rise of big tech companies like Google and Facebook. They noted how these companies' control over data and algorithms mirrors past media centralization, raising concerns about power consolidation and its implications for society. Emergent Centralization in Decentralized Systems: Lachlan pointed out that even in decentralized systems, centralization can naturally emerge as a result of voluntary collaboration and association. He explained that the problem lies not in centralization per se, but in the forced maintenance of these centralized structures, which can lead to the consolidation of power and the detachment of centralized entities from the needs and inputs of their users. Risks of Centralized AI Control: A significant part of the discussion focused on the risks associated with a few large companies controlling powerful AI technologies. Stewart expressed concerns about the potential for misuse and bias, drawing parallels to the issues seen with Google and Facebook's control over information. Lachlan concurred, emphasizing the importance of decentralizing AI to prevent similar problems in the AI domain and to ensure broader, more equitable access to these technologies. Distributed Computing and Storage: Lachlan shared his insights into distributed computing and storage, citing projects like GunDB and IPFS as promising examples. He highlighted the need for decentralized infrastructures to support AI, arguing that these models can help sidestep the centralization of control and data. He advocated for pushing as much computation and storage to the client side as possible to maintain user control and privacy. Challenges of AI Alignment and Training: The conversation touched on the difficulties of aligning AI systems with human values, particularly through supervised fine-tuning and RLHF (Reinforcement Learning from Human Feedback). Lachlan criticized current alignment efforts for their top-down approach, suggesting that a more decentralized, bottom-up method that incorporates diverse human inputs and experiences would be more effective and representative. Trust and Responsibility in AI Systems: Trust emerged as a central theme, with both Stewart and Lachlan questioning whether AI systems can or should be trusted more than humans. Lachlan argued that ultimately, humans are responsible for the actions of AI systems and the consequences they produce. He emphasized the need for AI systems that enable individual control and accountability, suggesting that decentralized AI could help achieve this by aligning more closely with human networks and collective decision-making processes.

The interplanetary filesystem, or IPFS, is a peer-to-peer network that uses a distributed and decentralized model. Functionally, IPFS allows users to store and share files without having to rely on a single source of truth for those files. Matt Ober is the Co-Founder & CTO of Pinata. He joins the show to talk about IPFS The post Pinata and the Interplanetary File System with Matt Ober appeared first on Software Engineering Daily.

The interplanetary filesystem, or IPFS, is a peer-to-peer network that uses a distributed and decentralized model. Functionally, IPFS allows users to store and share files without having to rely on a single source of truth for those files. Matt Ober is the Co-Founder & CTO of Pinata. He joins the show to talk about IPFS The post Pinata and the Interplanetary File System with Matt Ober appeared first on Software Engineering Daily.

120 kg American Champion Bobb Matthews returns to KOTL to discuss which division he will compete in after Worlds, his thoughts on the IPFs big 3 (Perk, Jesus, Rondel), who is among the outliers, how he will carve out his legacy, Team USA's ability to sweep, and much more! Hosted by 6 Pack Lapadat

My guests today are 0xTranqui aka Max and Salief Lewis, two of the four co-founders of Lifeworld, the startup that's creating River. River is a blockchain media protocol. In its launch configuration, users can sign in with Privy, register accounts on a smart contract on Optimism, and post references to IPFS-hosted media as calldata to a smart contract on Arbitrum Nova. The team's first-party UI, river.ph, evokes social media collection website are.na. It was great getting to know more about River at such an early stage. I hope you enjoy the show. As always, this show is provided as entertainment and does not constitute legal, financial, or tax advice or any form of endorsement or suggestion. Crypto has risks and you alone are responsible for doing your research and making your own decisions. Links Hosted by @nicholas River

Episode Description:Today's episode features part one of a 3-part detailed discussion on the emerging trends of inscriptions and ordinals in the Bitcoin blockchain, positioning them as exciting new forms of collectibles with real historical significance and potential for value appreciation. James is joined by financial advisors Timothy Collins and Benjamin Honig (Co-Founder & CEO at SatRepublic), who bring their expertise on the subject matter, explaining the technical aspects, comparisons to NFTs on Ethereum, and the intrinsic value of certain Satoshi's due to historical transactions or rarities defined by ordinal theory.The episode covers the potential use cases, like digital art and collectibles with immutable provenance, leveraging the security and permanence of Bitcoin's blockchain, far beyond traditional NFTs stored on more volatile platforms. They delve into how ordinals create a new market for Bitcoin enthusiasts to engage actively with their holdings through creative inscriptions and the anticipation around the Bitcoin halving event that could significantly impact this emerging space. Listeners are guided on how to participate, buy, and potentially create their inscriptions, underscoring the novelty and speculative opportunity ordinals represent in the broader context of cryptocurrency innovations. Episode Summary:00:00 Diving Into the World of NFTs, Inscriptions, and Ordinals00:37 Introducing the Experts: A Deep Dive into Bitcoin's New Frontier02:21 The Historical Significance of Bitcoin Transactions06:54 Exploring the Rarity and Value of Satoshis21:51 The Fascinating World of Inscriptions on Bitcoin26:54 Exploring Recursive Inscriptions and Digital Ownership27:51 Warren Buffett and the Value of Inscribed Picks28:42 Artistic and Practical Uses of Satoshi Inscriptions29:02 The Evolution of NFTs and Blockchain Certifications30:14 The Future of Digital Collectibles and Community Support36:27 Building a Community and the Importance of Early Support44:17 The Potential of Inscriptions Beyond the Crypto Community52:36 Navigating the Marketplace: Buying, Selling, and Holding Rare Sats ------------What do YOU think of the show? Head to JamesAltucherShow.com/listeners and fill out a short survey that will help us better tailor the podcast to our audience!Are you interested in getting direct answers from James about your question on a podcast? Go to JamesAltucherShow.com/AskAltucher and send in your questions to be answered on the air!------------Visit Notepd.com to read our idea lists & sign up to create your own!My new book, Skip the Line, is out! Make sure you get a copy wherever books are sold!Join the You Should Run for President 2.0 Facebook Group, where we discuss why you should run for President.I write about all my podcasts! Check out the full post and learn what I learned at jamesaltuchershow.com------------Thank you so much for listening! If you like this episode, please rate, review, and subscribe to “The James Altucher Show” wherever you get your podcasts: Apple PodcastsiHeart RadioSpotifyFollow me on social media:YouTubeTwitterFacebookLinkedIn

Increase in the number of phishing messages pointing to IPFS and to R2 buckets https://isc.sans.edu/diary/Increase%20in%20the%20number%20of%20phishing%20messages%20pointing%20to%20IPFS%20and%20to%20R2%20buckets/30744 Fortinet New Vulnerabilities https://www.horizon3.ai/attack-research/attack-blogs/fortiwlm-the-almost-story-for-the-forti-forty/ Fortinet Updates https://www.helpnetsecurity.com/2024/03/14/cve-2023-48788-poc/ Arcserve UDP Vulnerability and PoC https://www.tenable.com/security/research/tra-2024-07 Michael Holcomb: Mode Matters: Monitoring PLCs for Detecting Potential ICS/OT Incidents https://www.sans.edu/cyber-research/mode-matters-monitoring-plcs-for-detecting-potential-ics-ot-incidents/

Increase in the number of phishing messages pointing to IPFS and to R2 buckets https://isc.sans.edu/diary/Increase%20in%20the%20number%20of%20phishing%20messages%20pointing%20to%20IPFS%20and%20to%20R2%20buckets/30744 Fortinet New Vulnerabilities https://www.horizon3.ai/attack-research/attack-blogs/fortiwlm-the-almost-story-for-the-forti-forty/ Fortinet Updates https://www.helpnetsecurity.com/2024/03/14/cve-2023-48788-poc/ Arcserve UDP Vulnerability and PoC https://www.tenable.com/security/research/tra-2024-07 Michael Holcomb: Mode Matters: Monitoring PLCs for Detecting Potential ICS/OT Incidents https://www.sans.edu/cyber-research/mode-matters-monitoring-plcs-for-detecting-potential-ics-ot-incidents/

Jason Hudgins is the main developer of the Podcast Guru app and cofounder of Really Bad Apps.In Conversation #104, Jason and I discuss: why he moved to Panama with his family, the soul sucking nature of big corporations, why he loves spending time coding Podcast Guru, how he first found out about the v4v model, the frustrations of advertising and how IPFS/music/video is in the future for his app. Jason is in as a 30% split for this episode so don't forget to boost!Timeline:(0:00) - Intro to Jason(0:30) - Why go to Panama?(5:15) - Why don't American's travel?(7:52) - Jason's previous life ..... meetings(12:42) - Stem Cell Therapy(16:09) - Travel is influenced by where you grew up(19:52) - V4V: An alternative to interruptive ads(25:23) - Micropayments that work(29:10) - Follow the fun music(38:10) - Just not our average percussion(40:55) - History of Really Bad Apps(48:15) - What's next for Podcast Guru(58:25) - Don't blame your app developer(1:07:29) - Podcast app's are Sisyphus's boulder(1:10:35) - Where we spend our time(1:17:20) - V4V: Connect with JasonConnect with Jason:Podcast Guru: https://podcastguru.io/Email: jason@reallybadapps.comConnect with Mere Mortals:Website: https://www.meremortalspodcast.com/Discord: https://discord.gg/jjfq9eGReUTwitter/X: https://twitter.com/meremortalspodInstagram: https://www.instagram.com/meremortalspodcast/TikTok: https://www.tiktok.com/@meremortalspodcastValue 4 Value Support:Boostagram: https://www.meremortalspodcast.com/supportPaypal: https://www.paypal.com/paypalme/meremortalspodcastSupport the show

Chris spends the week in a VR desktop, revealing the glitches, gains, and VR's open-source future.

Mahesh and Connor are joined by Jonathan Victor. Jonathan formerly worked on Filecoin at Protocol Labs, and left to found Ansa Research, a research firm focused on distributed infrastructure covering digital networks that aim to rebuild how internet infrastructure operates. Jonathan talks about how his Palantir background influenced his time at Protocol Labs, why content addressing is a critical component to the future of the web, what the long-term Filecoin roadmap looks like, the protocol's recent investments into retrieval, where Filecoin and other storage protocols fit into the broader ecosystem of enterprise storage, and clears up Filecoin's revenue model. 0:00 Cold Brew Open 0:40 How Jon's background at Palantir led him to Filecoin 4:28 Jon's Decentralized Infrastructure Theses 9:42 How the Various Storage Solutions May Work Together in the Future 13:33 Filecoin's Long-term Roadmap 20:03 Filecoin and Retrieval 24:55 Storage as a Commodity or a Differentiated Offering    29:30 Why Location Matters in Storage  34:04 IPFS and Filecoin's Value Prop 39:33 How Filecoin Cultivated it's robust developer ecosystem 43:42 Filecoin's Revenue Model and Transparency 50:47 Where to find Jon's Work Disclaimer: The hosts and the firms they represent may hold stakes in the companies mentioned in this podcast. None of this is financial advice.

The stories that kept us talking all year, and are only getting hotter! Plus the big flops we're still sore about. Special Guest: Kenji Berthold.

JOIN THE COMMUNITY Logos TwitterDiscordRESOURCES: Edward Snowden X Edward Snowden SubstackJarrad Hope X TIMESTAMPS: 00:00: Intro 01:00: A look back at the last 10 years of surveillance 07:50: Post September 11th Surveillance scheme 09:45: A new era of presumed mass surveillance and the loss of a free internet 14:10: Beyond omnipresent oppression (add subscription card) 15:30: Why should people care about privacy? Privacy is power 19:12: How did your politics evolve over the years? A meta game of politicians25:27: Logos and why the politics of this project matter. Creating political neutrality and just governance. 30:30: Recognizing cyberspace as the fifth domain of conflict. 33:40: Reform or Revolution? 36:39: Why the decentralisation movement is so important. Order via protocol instead of law 41:48: Combining resistance, privacy, and technology 47:35: Logos – Infrastructure for Network States 53:05: Decentralizing access to the internet. Tornado Cash, VPN, TOR, and network blocks 57:30: Catalan Independence Referendum. Decentralized technology, mesh network, IPFS 1:02:20: How economies work and defining private property 1:06:40: Neutrality, Crypto, Central Bank Digital Currencies (CBDC)1:12:20: Encrypted content, private, secure messaging, and metadata 1:16:20: Government forced backdoors into encryption schemes 1:18:50: Ensuring the freedom of future generations

How do you go from sales to consulting? What's the difference? Chase Courtney, a "recovering CPA" and the Director of Technology Sales at Imperial PFS, joins us to discuss how to apply your foundation of knowledge to help sell a particular product. Enjoy the episode! Episode Links: Ellerbrock-Norris: https://www.ellerbrock-norris.com/ Ellerbrock-Norris Wealth Strategies: https://www.ellerbrock-norris-ws.com/ IPFS: https://www.ipfs.com/ LAUNCH: https://getlaunch.io/ Elliot Bassett: https://www.linkedin.com/in/elliot-bassett-aip-cpcu-84499515/ Ryan Brott: https://www.linkedin.com/in/ryan-brott-cepa%C2%AE-77a278a/ Chase Courtney: https://www.linkedin.com/in/chase-courtney-cpa-5a0a2276/ This episode is sponsored by LAUNCH. In the world of insurance, independent agencies fight to survive. Brokers are forced to compete by blocking markets and bid for the lowest price. Worse yet, the industry is fragmented. Agencies find it difficult to collaborate across division on the same client. Millions of dollars in potential revenue are left on the table. And agency owners lie awake at night wondering how to scale. THAT'S WHERE LAUNCH COMES IN. Access the full-revenue potential in your existing book of business. See opportunities other agencies can't. Offer more value. Gain a competitive advantage in a commoditized market. Visit https://getlaunch.io/ to learn more.

How do you go from sales to consulting? What's the difference? Chase Courtney, a "recovering CPA" and the Director of Technology Sales at Imperial PFS, joins us to discuss how to apply your foundation of knowledge to help sell a particular product.Enjoy the episode!Episode Links:Ellerbrock-Norris: https://www.ellerbrock-norris.com/Ellerbrock-Norris Wealth Strategies: https://www.ellerbrock-norris-ws.com/IPFS: https://www.ipfs.com/LAUNCH: https://getlaunch.io/Elliot Bassett: https://www.linkedin.com/in/elliot-bassett-aip-cpcu-84499515/Ryan Brott: https://www.linkedin.com/in/ryan-brott-cepa%C2%AE-77a278a/Chase Courtney: https://www.linkedin.com/in/chase-courtney-cpa-5a0a2276/This episode is sponsored by LAUNCH.In the world of insurance, independent agencies fight to survive. Brokers are forced to compete by blocking markets and bid for the lowest price. Worse yet, the industry is fragmented.Agencies find it difficult to collaborate across division on the same client. Millions of dollars in potential revenue are left on the table. And agency owners lie awake at night wondering how to scale.THAT'S WHERE LAUNCH COMES IN.Access the full-revenue potential in your existing book of business. See opportunities other agencies can't. Offer more value. Gain a competitive advantage in a commoditized market.Visit https://getlaunch.io/ to learn more.

Check out Tailwind at ⁠https://lmg.gg/tailwind⁠ and new subscribers can save 50% on annual plans until November 27th. Get $5 off your Magic Spoon order with code WAN at ⁠https://lmg.gg/magicspoon⁠ Try Notion AI for free at ⁠https://www.Notion.com/wan⁠ Timestamps (Courtesy of NoKi1119) Note timing may be off due to sponsor change: 0:00 Chapters 1:12 Intro 1:38 Topic #1 - Sam Altman is no longer the CEO of OpenAI 14:12 Topic #2 - Epic's Fortnite age restricted certain skins 24:33 Topic #3 - Nothing adds blue bubble messaging on Android 26:50 Topic #4 - Apple announces RCS support 34:16 Topic #5 - Linus ordered Humane's AI Pin 42:07 Merch Messages #1 42:16 Which is better to buy - a used Steam Deck LCD, or OLED? 48:22 BuyMyF-ingGarbage redirects to LTTStore ft. Linus's buying joke, Luke getting a Deck? 50:46 Linus explains merch messages 52:00 LTTStore's new fruit underwear 52:34 Strawberry, eggplant & peach colors variants, men & women styles 54:00 New RGBroken T-shirt, $999 deal 56:25 New RGB knit sweater 56:53 New GPU Christmas ornament 57:32 Black Friday & Cyber Monday sign up list 59:23 Would Linus consider writing a book about LTT after retirement? 1:01:16 Topic #6 - Tesla's clause banned reselling Cybertrucks within its first year 1:07:19 Topic #7 - Amazon to start selling Hyundai cars ft. Troll Linus 1:12:02 Topic #8 - Sony's PlayStation Portal released, sold in two days 1:12:10 Luke witnessed others' bad experiences, Linus mentions reviews 1:15:28 Linus's review was positive, mentions Bluetooth ft. FP Poll 1:18:06 Linus on Sony's decisions & margins, recalls NVIDIA Shield 1:21:54 Luke's personal thoughts, WiFi 5/6/6E, Android 13, lacking bluetooth audio 1:25:40 Linus on the battery life, compared to G Cloud 1:26:08 Topic #9 - Microsoft to follow EU's bill, will allow uninstalling Edge 1:30:43 Topic #10 - X(Twitter) lost major sponsors after Elon Musk's "anti-semitic" tweets 1:37:40 Sponsors 1:42:00 Merch Messages #2 1:54:38 Topic #11 - Google sues DMCA scammers & copyright fraudsters 1:55:51 Topic #12 - Rivian's accidental OTA update breaks infotainment systems 1:58:14 Merch Messages #3 ft. WAN Show After Dark, Luke on Japan's GMT 1:59:28 What does your SO despise that you collect? 2:00:13 Would performance differences add up if you compare PC part SKUs? 2:03:52 Luke's experience with Matsuri 2:06:16 What's some of the visions Linus had for LTT in 2024? 2:10:34 Does Luke believe a P2P solution like IPFS would help with FP's costs? 2:11:53 Why does Linus keep his earrings? Thought of removing them? If Luke fought James, who wins? 2:33:20 Will the Black Friday deals ship in time for Christmas? 2:36:20 What did you enjoy playing the most during the good gaming era? 2:37:52 What video ideas took the least time? Compare to normal videos 2:41:40 With the new Deck, have you considered going back from Ally? 2:42:14 Are you familiar with Wasm? ft. Lagging Luke 2:43:19 Thoughts on doing a Top Gear styled video? 2:44:45 A simple prank that you have done that resulted in laughter? 2:45:48 Any other JRPGs you all enjoy? 2:47:18 Applying right to repair to airplane parts? 2:50:36 A valid argument between Ally & Deck? 2:53:23 Why Linus dislikes Star Trek 2:54:48 Would Luke ever branch off from LMG and make a car related channel? 2:56:48 Does FP use any design principles in CS? 2:58:38 Changes implemented to LMG's IT infrastructure by Dan & Luke? 3:03:40 Most surprising smash hit on LTTStore? 3:04:27 Does Luke have an advice as a C dev to a C dev? 3:06:32 Most surprising smash hit on LTTStore? 3:08:54 Any more pride colored LTTStore merch coming? 3:10:06 ROG reboot CPU fan rubber mounts 3:11:06 Favorite Linus quote? 3:12:14 Topic #13 - Eight Sleep cutting off access to API calls 3:13:05 Any practices or content types on the way out? 3:15:40 Nick mentions the microfiber shirt idea 3:16:45 Outro

"Decentralization will not, absolutely not, be the reason for the average user to use Web3. The average user is not going to use Web3 until it's as easy to use as Web2 and unlocks features that Web2 cannot provide."  This is a powerful quote from this episode's conversation with Ian Andrews (CMO, Chainalysis) and the, Co- Executive Directors of the Web3 Working Group, Amy James and Devon James as they unravel the technical complexities of Decentralized Physical Infrastructure Networks (DePIN) and explain why they believe the next opportunity for wider adoption will not just be adoption in the financial space, but adoption in the technology space. The duo also emphasize the need for open protocols and standards to ensure interoperability and competition in the space, as well as the challenges of building in the Web3 space and the importance of educating policymakers and regulators about the potential for these technologies. Minute-by-minute episode breakdown (2:01) - What is the Web3 Working Group and the need for decentralized physical infrastructure networks (DePins)  (6:08) - Discussing the Open Index Protocol and transitioning from manufacturing to software and Bitcoin (11:20) - Advantages of the protocol and comparison to IPFS and use of BitTorrent and blockchain for indexing content (16:45) - Difficulty in building web3 experiences beyond financial transactions (20:50) - Decentralization won't be the reason for average users to use Web3 (28:02) - Reasons for creating a not-for-profit advocacy group for Web3 and challenges of operating in the US market due to regulations (34:08) - Educating regulators and policymakers on Web3 technology (38:27) - Potential benefits and concerns of traditional finance players entering the crypto space Related resources Check out more resources provided by Chainalysis that perfectly complement this episode of the Public Key. Website:  Web3 Working Group: Advocacy for Decentralized Infrastructure Protocols Youtube: Weekly Youtube Live Show: What Kind of Internet Do You Want?  Podcast: DarkHorse Podcast with Bret Weinstein  Webpage:  Explore DePIN protocols and the decentralized apps that use them Article: What is DePIN? Blog: Risky Business: The Economics Behind Decentralized Storage Networks Blog: OFAC Sanctions Russian National Ekaterina Zhdanova for Using Cryptocurrency to Launder Money on Behalf of Russian Elites and Ransomware Groups Report: The Chainalysis 2023 Geography of Cryptocurrency Report (Available Now) YouTube: Chainalysis YouTube page Twitter: Chainalysis Twitter: BuildCareers at Chainalysising trust in blockchain Tik Tok: Building trust in #blockchains among people, businesses, and governments. Telegram: Chainalysis on Telegram  Speakers on today's episode Ian Andrews * Host * (Chief Marketing Officer, Chainalysis) Amy James (Co- Executive Director, Web3 Working Group) Devon James (Co- Executive Director, Web3 Working Group) This website may contain links to third-party sites that are not under the control of Chainalysis, Inc. or its affiliates (collectively “Chainalysis”). Access to such information does not imply association with, endorsement of, approval of, or recommendation by Chainalysis of the site or its operators, and Chainalysis is not responsible for the products, services, or other content hosted therein. Our podcasts are for informational purposes only, and are not intended to provide legal, tax, financial, or investment advice. Listeners should consult their own advisors before making these types of decisions. Chainalysis has no responsibility or liability for any decision made or any other acts or omissions in connection with your use of this material. Chainalysis does not guarantee or warrant the accuracy, completeness, timeliness, suitability or validity of the information in any particular podcast and will not be responsible for any claim attributable to errors, omissions, or other inaccuracies of any part of such material.  Unless stated otherwise, reference to any specific product or entity does not constitute an endorsement or recommendation by Chainalysis. The views expressed by guests are their own and their appearance on the program does not imply an endorsement of them or any entity they represent. Views and opinions expressed by Chainalysis employees are those of the employees and do not necessarily reflect the views of the company.   

A conversation with Brian Long, co-founder of Triton One.Full show notes: solfate.com/podcast/37Watch this episode on YouTube: youtube.com/watch?v=oVhif85sv_IFollow the @SolfatePod show on Twitter for updates. Thanks for listening frens :)Notes from the showBrian has been in the Solana ecosystem since very early days. Pre-mainnet days. He and his company, Triton One, helped Solana Labs bring up mainnet in March 2020. Even to this day, Brian and Triton continue to be active contributors to the Solana ecosystem. Not only does Triton operate the public mainnet and devnet RPCs nodes for the public, Linus Kendall from Triton is one of the few active contributors of the DAS API and infrastructure that is vital to compressed NFTs on Solana.Triton has also been hard at work on improving the Solana RPC Geyser interfacewith Project Yellowstone. In this umbrella project, the Triton team is focused on several aspects of the Geyser interface to make many improvements. One of those includes Old Faithful, the effort to put the entire Solana history (200TB+ of data) on the IPFS network. This is especially interesting, not only because Solana produces so much data that grows rapidly every day, but also because it this is being not only theorized by engineers at Triton and Firedancer, but is also a collaboration with Protocol Labs (the creators of IPFS and Filecoin). Multiple Layer 1 blockchains working directly together. Find Brian and and Triton onlineFollow Brian Long on twitter - @BrianLongFollow Triton on twitter - @triton_oneVisit the Triton website - https://triton.oneFollow us aroundNickfollow on twitter: @nickfrostyfollow on github: github.com/nickfrostywebsite: https://nick.afJamesfollow on twitter: @jamesrp13follow on github: github.com/jamesrp13

We did Proxmox dirty last week, so we try to explain our thinking. But first, a few things have gone down that you should know about.

In this episode of The Power Producers Podcast, David Carothers interviews Chase Courtney, Director of Technology Sales at Imperial PFS. Chase discusses his role at IPFS and how he is leveraging his experience to help the company appeal to a wider audience. Chase also shares about AndDone, the unified digital premium payment platform from IPFS that allows agencies to create a customized user experience.  Resources Mentioned: Chase Courtney LinkedIn Imperial PFS AndDone David Carothers LinkedIn Kyle Houck LinkedIn Florida Risk Partners The Extra 2 Minutes

In this episode of The Power Producers Podcast, David Carothers interviews Chase Courtney, Director of Technology Sales at Imperial PFS. Chase discusses his role at IPFS and how he is leveraging his experience to help the company appeal to a wider audience. Chase also shares about AndDone, the unified digital premium payment platform from IPFS that allows agencies to create a customized user experience.  Resources Mentioned: Chase Courtney LinkedIn Imperial PFS AndDone David Carothers LinkedIn Kyle Houck LinkedIn Florida Risk Partners The Extra 2 Minutes

Recorded LIVE from IndieTech 2023! In this episode, James talks with Ryan Westerman, President of AndDone, and Chase Courtney, Director of Technology Sales at Imperial PFS. To learn more about AndDone, visit https://anddone.com/ Visit our website to join our email list, get the scoop on our LIVE coaching calls and never miss an episode: https://www.agencyfreedom.com Connect with Agency Freedom Podcast on Facebook at the Agency Freedom Podcast group: https://www.facebook.com/groups/agencyfreedom Email us at podcast@agencyfreedom.com with ideas, questions, complaints or your favorite grilling recipe. Episode Highlights: Chase and Ryan discuss AndDone, a wholly-owned subsidiary and payment solution that exists in the IPFS ecosystem, for the first time on a podcast. (3:59) Ryan explains that AndDone is an API-first enterprise-grade payment solution application that offers a web app for agents to use. It is designed for integration with other solutions such as rate quote buying platforms and AMS systems. (12:34) Chase mentions that IPFS has extensive experience in premium finance services and offers payment processing services to both customers and non-customers while prioritizing providing value and benefits to their customers without any extra charges. (16:30) Ryan discusses the importance of selecting a solution that aligns with your business model and how your team interacts with customers and products. (19:58) Ryan discusses the goal of IPFS which is to provide assistance and offer the most convenient and straightforward payment methods for insurance. (23:38) Key Quotes: “We're in the situation now, where we are replacing Stripe, we are replacing PayPal for our customers. No premium finance involved.” - Chase Courtney “We wake up every day and have IPFS premium volume run through our payment processing. We pass those benefits on to our customers.” - Chase Courtney “We want to give the easiest ways to pay. We want to give the simplest solution for you for the insurance and the options that you need to get that deal closed.” - Ryan Westerman

Recorded LIVE from IndieTech 2023! In this episode, James talks with Ryan Westerman, President of AndDone, and Chase Courtney, Director of Technology Sales at Imperial PFS. To learn more about AndDone, visit https://anddone.com/ Visit our website to join our email list, get the scoop on our LIVE coaching calls and never miss an episode: https://www.agencyfreedom.com Connect with Agency Freedom Podcast on Facebook at the Agency Freedom Podcast group: https://www.facebook.com/groups/agencyfreedom Email us at podcast@agencyfreedom.com with ideas, questions, complaints or your favorite grilling recipe. Episode Highlights: Chase and Ryan discuss AndDone, a wholly-owned subsidiary and payment solution that exists in the IPFS ecosystem, for the first time on a podcast. (3:59) Ryan explains that AndDone is an API-first enterprise-grade payment solution application that offers a web app for agents to use. It is designed for integration with other solutions such as rate quote buying platforms and AMS systems. (12:34) Chase mentions that IPFS has extensive experience in premium finance services and offers payment processing services to both customers and non-customers while prioritizing providing value and benefits to their customers without any extra charges. (16:30) Ryan discusses the importance of selecting a solution that aligns with your business model and how your team interacts with customers and products. (19:58) Ryan discusses the goal of IPFS which is to provide assistance and offer the most convenient and straightforward payment methods for insurance. (23:38) Key Quotes: “We're in the situation now, where we are replacing Stripe, we are replacing PayPal for our customers. No premium finance involved.” - Chase Courtney “We wake up every day and have IPFS premium volume run through our payment processing. We pass those benefits on to our customers.” - Chase Courtney “We want to give the easiest ways to pay. We want to give the simplest solution for you for the insurance and the options that you need to get that deal closed.” - Ryan Westerman

Over the past 5 years, Blockcrunch has been a beacon for the Web 3 community. As we evolve, we're thrilled to announce an upcoming rebrand. Stay tuned for details on our renewed commitment to serving our audience even better! But before we embark on this new journey, we're celebrating the legacy of our current show. This week, join us as we host Darryl Wang, Co-Founder of Tangent - the angel collective co-founded by our very own Jason - to discuss: Bull and bear case for the next 12 months Biggest lessons learnt in investing 2 bold predictions for the next crypto cycle Investing in meme coins Host: Jason Choi @mrjasonchoi . Not financial advice. Timestamps: (00:00:00) – Introduction to Tangent  (00:04:10) – Darryl's entry into Web 3 (00:05:51) – Bullish case for next 12 months (00:12:04) – Bearish case for next 12 months (00:15:51) – Consensus ideas that turned out wrong (00:21:06) – Bringing treasury yields onchain via Maker (00:24:40) – Is there need for more chains (00:34:18) – Most hated coin that can do well next cycle (00:38:08) – Wrapping heads around meme coins (00:43:24) – Native yield-generating stablecoin (00:49:31) – Bold prediction for the next cycle Sponsor message: Filecoin is enabling open services for data, built on top of IPFS.   Today, Filecoin focuses primarily on storage as an open service, but looks to build the infrastructure to store, distribute and transform data.   Read the full 30-page report on the future of Filecoin written by Blockcrunch over here: https://bit.ly/41gLdUm More Resources: Guest Darryl Wang's Twitter: https://twitter.com/0xWangarian Tangent's Twitter: https://twitter.com/tangent_xyz Blockcrunch Blockcrunch VIP: https://blockcrunch.substack.com/ Blockcrunch Twitter: https://twitter.com/theBlockcrunch Jason Choi's Twitter: https://twitter.com/mrjasonchoi     Disclaimer: The Blockcrunch Podcast (“Blockcrunch”) is an educational resource intended for informational purposes only. Blockcrunch produces a weekly podcast and newsletter that routinely covers projects in Web 3 and may discuss assets that the host or its guests have financial exposure to. Views held by Blockcrunch's guests are their own. None of Blockcrunch, its registered entity or any of its affiliated personnel are licensed to provide any type of financial advice, and nothing on Blockcrunch's podcast, newsletter, website and social media should be construed as financial advice. Blockcrunch also receives compensation from its sponsor; sponsorship messages do not constitute financial advice or endorsement.   Full disclaimer: https://blockcrunch.substack.com/about  

Superscrypt is an early-stage web3 company seeded by Temasek, a globally recognized investment powerhouse headquartered in Singapore. Recognizing the immense potential of the decentralized digital landscape, Superscrypt focus exclusively on the next generation of internet technologies.  Today, we have Jacob Ko, Partner at Superscrypt to share with us:  Contrasting investment philosophies between the West and Asia Verticals Superscrypt is excited about Convincing & onboarding non-Web 3 users Singapore vs HongKong's Web 3 scene Host: Jason Choi @mrjasonchoi . Not financial advice. Timestamps: (00:00:00) – Introduction to Superscrypt (00:02:55) – Temasek & Jacob's transition into Web 3 (00:09:42) – Western vs Asian investing focus (00:12:01) – Superscrypt's investment in social & creator economy (00:16:18) – Discussion on blockchain wallets (00:23:21) – Convincing non-Web 3 users (00:30:15) – Handling security in Web 3 (00:33:14) – Singapore vs HongKong's Web 3 scene Sponsor message: Filecoin is enabling open services for data, built on top of IPFS.   Today, Filecoin focuses primarily on storage as an open service, but looks to build the infrastructure to store, distribute and transform data.   Read the full 30-page report on the future of Filecoin written by Blockcrunch over here: https://bit.ly/41gLdUm More Resources: Guest Superscrypt's Twitter:https://twitter.com/superscrypt Jacob Ko's Twitter: https://twitter.com/jacobkxyz   Blockcrunch Blockcrunch VIP: https://blockcrunch.substack.com/ Blockcrunch Twitter: https://twitter.com/theBlockcrunch Jason Choi's Twitter: https://twitter.com/mrjasonchoi     Disclaimer: The Blockcrunch Podcast (“Blockcrunch”) is an educational resource intended for informational purposes only. Blockcrunch produces a weekly podcast and newsletter that routinely covers projects in Web 3 and may discuss assets that the host or its guests have financial exposure to. Views held by Blockcrunch's guests are their own. None of Blockcrunch, its registered entity or any of its affiliated personnel are licensed to provide any type of financial advice, and nothing on Blockcrunch's podcast, newsletter, website and social media should be construed as financial advice. Blockcrunch also receives compensation from its sponsor; sponsorship messages do not constitute financial advice or endorsement.   Full disclaimer: https://blockcrunch.substack.com/about

Recently, we have a few asset managers, including some of the largest in the world like Blackrock apply to create Bitcoin spot ETFs in the United States. This sparked a lot of speculation about whether this could herald institutional adoption of crypto and kickstart a bull market. Today, we have Ram Ahluwalia, CEO of Lumida and previous Head of Crypto & Digital Assets at Cross River, a crypto-friendly bank to share with us: Implications of BTC ETF on markets Odds of SEC approval Reasons for previous rejections And more! Host: Jason Choi @mrjasonchoi . Not financial advice.   Timestamps: (00:00:00) – Introduction to BTC ETFs (00:03:10) – Importance of Spot BTC ETF (00:06:52) – SEC's reason for rejecting BTC ETFs (00:13:57) – SEC's stance on Crypto (00:17:30) – Why BlackRock is applying for BTC ETF now (00:21:38) – Larry Fink's agenda  (00:28:38) – Need for clearer guidance (00:32:44) – Likelihood of ETF approval (00:35:11) – Past applications vs Now Sponsor message: Filecoin is enabling open services for data, built on top of IPFS.   Today, Filecoin focuses primarily on storage as an open service, but looks to build the infrastructure to store, distribute and transform data.   Read the full 30-page report on the future of Filecoin written by Blockcrunch over here: https://bit.ly/41gLdUm More Resources: Guest Ram Ahluwalia's Twitter: https://twitter.com/ramahluwalia Blockcrunch Blockcrunch VIP: https://blockcrunch.substack.com/ Blockcrunch Twitter: https://twitter.com/theBlockcrunch Jason Choi's Twitter: https://twitter.com/mrjasonchoi     Disclaimer: The Blockcrunch Podcast (“Blockcrunch”) is an educational resource intended for informational purposes only. Blockcrunch produces a weekly podcast and newsletter that routinely covers projects in Web 3 and may discuss assets that the host or its guests have financial exposure to. Views held by Blockcrunch's guests are their own. None of Blockcrunch, its registered entity or any of its affiliated personnel are licensed to provide any type of financial advice, and nothing on Blockcrunch's podcast, newsletter, website and social media should be construed as financial advice. Blockcrunch also receives compensation from its sponsor; sponsorship messages do not constitute financial advice or endorsement.   Full disclaimer: https://blockcrunch.substack.com/about  

Arkham Intelligence is a blockchain data analytics platform that recently started a huge debate on Twitter due to its Intel-to-Earn model, which pays users to deanonymize blockchain wallets. There are also discussions on whether Arkham collects off-chain data on its users, and whether Arkham is actually a government project used to spy on crypto users. Today, we have Miguel Morel, CEO of Arkham on the show where we asked him: Info that will be allowed on Arkham's marketplace Will Arkham work with government agencies Does Arkham collect non-public data of users Host: Jason Choi @mrjasonchoi . Not financial advice. Timestamps: (00:00:00) – Introduction to Arkham Intelligence (00:02:47) – What is Arkham (00:06:42) – Arkham users and use-cases (00:11:17) – Is Arkham working with government agencies (00:24:33) – Issues surround Arkham's referral system (00:30:09) – The controversial Intro-to-Earn system (00:45:07) – Data quality and accuracy (00:50:29) – Privacy blockchains (00:37:09) – Value accrual across layers Sponsor message: Filecoin is enabling open services for data, built on top of IPFS.   Today, Filecoin focuses primarily on storage as an open service, but looks to build the infrastructure to store, distribute and transform data.   Read the full 30-page report on the future of Filecoin written by Blockcrunch over here: https://bit.ly/41gLdUm More Resources: Tweet that claims Arkham Intel Referral System exposed 100s of private emails: https://twitter.com/nftherder/status/1680065466738376704?s=46&t=FkUP6WZfEjMkbcsVeZ1C1w Guest Miguel Morel's Twitter: https://twitter.com/RealMiguelMorel Arkham Intelligence's Twitter: https://twitter.com/ArkhamIntel   Blockcrunch Blockcrunch VIP: https://blockcrunch.substack.com/ Blockcrunch Twitter: https://twitter.com/theBlockcrunch Jason Choi's Twitter: https://twitter.com/mrjasonchoi     Disclaimer: The Blockcrunch Podcast (“Blockcrunch”) is an educational resource intended for informational purposes only. Blockcrunch produces a weekly podcast and newsletter that routinely covers projects in Web 3 and may discuss assets that the host or its guests have financial exposure to. Views held by Blockcrunch's guests are their own. None of Blockcrunch, its registered entity or any of its affiliated personnel are licensed to provide any type of financial advice, and nothing on Blockcrunch's podcast, newsletter, website and social media should be construed as financial advice. Blockcrunch also receives compensation from its sponsor; sponsorship messages do not constitute financial advice or endorsement.   Full disclaimer: https://blockcrunch.substack.com/about  

Maven11 is one of the foremost crypto-venture funds renowned for its early trend detection and deep focus on the infrastructural layer of the crypto space.   In this episode, we dive into the secular trends that crypto investors should be aware of, particularly the Modular Blockchain thesis. Watch this episode to keep up with the next wave of blockchain evolution and its potential to shape the future of the crypto landscape   Chief Investment Officer Balder Bomans and Mathijs, Associate Partner of Maven11 shares with us: What exactly is the Modular Blockchain thesis Which layer accrues the most value in Modular Blockchains 4 interesting verticals other than Modular Blockchains   Host: Jason Choi @mrjasonchoi . Not financial advice.     Timestamps: (00:00:00) – Introduction to Maven11 (00:03:38) – How Maven11 came about (00:08:19) – Maven11's secret to forming theses (00:12:48) – Real-world Assets, Credit & Privacy (00:16:15) – Modular Blockchains thesis (00:20:25) – Data Availability (00:25:02) – Future of Roll-Ups (00:31:15) – Roll-Ups-as-a-Service (00:37:09) – Value accrual across layers Sponsor message: Filecoin is enabling open services for data, built on top of IPFS.   Today, Filecoin focuses primarily on storage as an open service, but looks to build the infrastructure to store, distribute and transform data.   Read the full 30-page report on the future of Filecoin written by Blockcrunch over here: https://bit.ly/41gLdUm More Resources: Guest Maven11's Twitter: https://twitter.com/gizatechxyz Maven11's Substack: https://maven11.substack.com Balder's Twitter: https://twitter.com/BalderBomans Mathijs's Twitter: https://twitter.com/MathijsvEsch   Blockcrunch Blockcrunch VIP: https://blockcrunch.substack.com/ Blockcrunch Twitter: https://twitter.com/theBlockcrunch Jason Choi's Twitter: https://twitter.com/mrjasonchoi     Disclaimer: The Blockcrunch Podcast (“Blockcrunch”) is an educational resource intended for informational purposes only. Blockcrunch produces a weekly podcast and newsletter that routinely covers projects in Web 3 and may discuss assets that the host or its guests have financial exposure to. Views held by Blockcrunch's guests are their own. None of Blockcrunch, its registered entity or any of its affiliated personnel are licensed to provide any type of financial advice, and nothing on Blockcrunch's podcast, newsletter, website and social media should be construed as financial advice. Blockcrunch also receives compensation from its sponsor; sponsorship messages do not constitute financial advice or endorsement.   Full disclaimer: https://blockcrunch.substack.com/about  

Podcasting 2.0 June 16th 2023 Episode 137: "Wonk Factor" Adam & Dave discuss the week's developments on podcastindex.org - Of course we discuss the Damus nostr issue as it relates (or doesn't) to V4V and plenty of namespace talk, IPFS experiments and we swith the wallet for our featured artist! ShowNotes We are LIT, soon on fountain! Apple’s threat to delist Damus impacts the V4V community Guidelines can change Apple is a shitcoin PWA's (most apps already have web versions) V4V is about support, not convenience V4V will work in many ways Parcast and Gimlet Layoffs Reflect a Bigger Spotify Podcast Pivot - Bloomberg DistroKid faces potential class-action lawsuit over how it handles takedown requests – Music Business Worldwide ISO-Bot Archive Page Bitcoin 2024 and BA Presentation Live stream Livestream value block business with timeSplits! IPFS test - with loop around in SF Longy - The Underclass on LN Beats - 9 secs Announcing Durin: a New Mobile App for the IPFS Network Update Frequency Form MKUltra chat Transcript Search What is Value4Value? - Read all about it at Value4Value.info V4V Stats Last Modified 06/16/2023 14:59:11 by Freedom Controller

IPFS Phishing and the need for correctly set HTTP security headers https://isc.sans.edu/diary/IPFS%20phishing%20and%20the%20need%20for%20correctly%20set%20HTTP%20security%20headers/29638 Exploiting CVE-2023-23397: Microsoft Outlook Elevation of Privilege Vulnerability https://www.mdsec.co.uk/2023/03/exploiting-cve-2023-23397-microsoft-outlook-elevation-of-privilege-vulnerability/ CVE-2023-23415 ICMP RCE https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-23415 Chromium Certificate Proposals https://www.chromium.org/Home/chromium-security/root-ca-policy/moving-forward-together/

IPFS Phishing and the need for correctly set HTTP security headers https://isc.sans.edu/diary/IPFS%20phishing%20and%20the%20need%20for%20correctly%20set%20HTTP%20security%20headers/29638 Exploiting CVE-2023-23397: Microsoft Outlook Elevation of Privilege Vulnerability https://www.mdsec.co.uk/2023/03/exploiting-cve-2023-23397-microsoft-outlook-elevation-of-privilege-vulnerability/ CVE-2023-23415 ICMP RCE https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-23415 Chromium Certificate Proposals https://www.chromium.org/Home/chromium-security/root-ca-policy/moving-forward-together/