Podcasts about dids

AGNTCY - Unlock agents at scale with an open Internet of Agents. Visit https://agntcy.org/ and add your support.     What if AI agents needed digital passports to act on your behalf?   In this episode, Ankur Banerjee, Co-Founder and CTO of cheqd.io, reveals how decentralized identity is becoming the foundation of the AI agent economy.    From booking Taylor Swift tickets with an agent to proving you're a real person online, we explore why identity and trust are the hidden infrastructure shaping the future of AI.   Ankur explains how cheqd is building privacy-first tools that let AI agents verify who they are, what they can do, and who they're working for, all without handing over your data to big tech. We dig into the rise of digital credentials, the limits of biometrics, and how protocols like MCP are making the internet safe for autonomous agents.   If you've ever wondered how AI will operate on your behalf in the real world, this conversation offers a glimpse into what's coming next.   Stay Updated: Craig Smith on X: https://x.com/craigss Eye on A.I. on X: https://x.com/EyeOn_AI     (00:00) Why AI Needs Identity (02:16) Ankur's Path to cheqd (05:39) Delegating Tasks to AI Agents (11:26) Identity Lessons from Governments (17:25) Trusting AI with Digital Credentials (23:42) The Problem with Biometrics (30:49) Web Standards for Agent Identity (36:46) MCP and Agent Interoperability (48:47) Bridging Web2 and Web3 Identity (55:18) Why Companies Should Care About Decentralized ID

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

This Christmas, Pastor Shirk preaches on the texts behind some of our favorite Christmas carols.

There's a reason journalist and Bluesky board member Mike Masnick calls the platform “the most interesting experiment going in social media.” Originally launched as a project within Twitter in 2019, Bluesky has since become an independent company intent on making social more like the web. What does that mean, exactly, and why does it matter? Bluesky founder and CEO Jay Graber says social media is stagnating because “we're in this trap where users are locked in and developers are locked out.” It's time to open things up again, she states, like in the innovative early days of the internet. Highlights of this conversation:• Bluesky's origin story • The case for decentralization — and Bluesky• Developer activity and other “wacky experimentation” • Workings of identity online and DIDs (decentralized identifiers)• Bridging AT Protocol and ActivityPub•  Bluesky's exciting cultural momentsMentioned in this episode:Hard Fork podcast episode featuring Jay Graber

In this episode of the Crazy Wisdom podcast, Stewart Alsop speaks with Diego Fernandez, co-creator of QuarkID and the Secretary of Innovation for Buenos Aires. They discuss the future of innovation in Buenos Aires, focusing on how technology can simplify citizen interactions with the government and empower individuals through control over their identity with Web3. The conversation explores the potential of decentralized technologies like blockchain to transform government services and create new opportunities for innovation, especially in Argentina's unique economic landscape. In the episode Stewart forgot the name of something about the innovation of digitizing real world assets in Argentina, see this tweet about the deregulation of warrants so that they can be handled online. And for more on QuarkID, visit www.quarkid.org.Check out this GPT we trained on the conversation!Timestamps00:00 Introduction to the Crazy Wisdom Podcast00:13 Innovation in Buenos Aires: A Vision for the Future01:34 The Role of Technology in Government02:37 Web3 Technologies: Closing the Gap05:29 Argentina's Unique Economic Resilience08:53 Crypto Adoption in Argentina11:25 The Impact of Inflation and Crypto Solutions17:41 Argentina's Potential in the Web3 Era27:40 Crypto Scene in San Francisco28:20 Buenos Aires: A Hub for Crypto Innovation29:04 Aleph's Pop-Up City and Economic Vision31:04 Regulatory Changes and Crypto Opportunities32:09 Decentralization and the Future of Money32:47 The Role of Governments in the Digital Age34:50 The Evolution of Money and Technology38:02 Real-World Crypto Applications: Morphy Token41:09 Decentralized Platforms and Censorship41:57 QuarkID: Revolutionizing Digital Identity45:21 The Future of Digital Identity and Privacy51:22 Conclusion and How to Learn More About QuarkIDKey InsightsInnovation in Buenos Aires: Diego Fernandez emphasizes that the future of innovation in Buenos Aires is centered around making government services seamless and empowering citizens. He envisions a "WiFi-like" government where the state's presence is only noticed when something goes wrong, with a primary focus on streamlining interactions between citizens and government through technology.The Role of Web3 in Identity: Web3 technologies, particularly decentralized identifiers (DIDs) and verifiable credentials, are set to revolutionize how individuals manage their identities. With QuarkID, citizens will have control over their digital identities, securely storing documents and credentials on their own devices. This shifts control from centralized entities like governments or tech giants to individuals.Argentina's Economic Resilience: Fernandez expresses optimism about Argentina's future, calling its citizens "economic Navy Seals" due to their experience in dealing with decades of economic instability. He believes that Argentina's hardships have made its population more entrepreneurial, adaptable, and uniquely positioned to embrace blockchain and Web3 technologies to overcome economic challenges.Web3's Impact on Global Financial Systems: The episode highlights how Web3 technologies are poised to disrupt traditional financial systems by enabling peer-to-peer transactions of value and identity. In Argentina, where economic crises have pushed citizens to adopt cryptocurrencies, the use of decentralized financial tools is not only growing but also fostering innovation in industries like tokenization of real-world assets.The Leapfrogging Potential of Argentina: Fernandez believes that Argentina has the potential to "leapfrog" other nations in developing new financial systems and infrastructure based on decentralized technologies. The country's lack of entrenched financial systems, combined with its thriving blockchain ecosystem, provides an opportunity to build future-proof solutions that could serve as a model for other emerging economies.Blockchain Startups Flourishing in Argentina: Argentina has become a hotspot for blockchain innovation, with notable startups like Decentraland, Ripio, and numerous others being created within the country. Fernandez is bullish on the growth of both centralized and decentralized financial products, as well as advancements in deep tech, especially in cryptography and zero-knowledge proofs.Decentralization and Government's Role: Fernandez draws a parallel between the separation of church and state and the future separation of money from the state. He argues that just as governments no longer control religion, they will eventually lose their control over money as decentralized platforms take hold. This change, driven by technological advancements, could fundamentally reshape governance and public services.

A sit down with Author and Armourer - Dids Hall (Part 2) Firearms Black Spy Podcast Season 15, Episode 00010   This week's Black Spy Podcast is a sit down discussion with Author and Armourer Dids Hall. The discussion ebbs and flows over several topics in two episodes, from the problems he has encountered living in the EU since BREXIT, to the Conservative governments mendacity, Labour's potential and the cost of living crisis in the UK. Dids asks why the UK missed out on recent industrialism as the two discuss lost colonial opportunities, UK militarism, service industries as they question what the future holds. The podcast also discusses firearms and their deployment and utility by police in various countries, plus the lack thereof in the UK as men consider whast unarmed policing actually denotes? The episodes swing into various other topics, providing an interesting, entertaining and eclectic mix. In other words, its another must listen episode of the Black Spy podcast. If you want to continue learning whilst being entertained, please don't forget to subscribe to the Black Spy Podcast for free, so you'll never miss another episode. To contact Firgas Esack of the DAPS Agency go to Linked In To contact Carlton King by utilising any of the following: To donate - Patreon.com/TheBlackSpyPodcast Email: carltonking2003@gmail.com Facebook: The Black Spy Podcast Facebook: Carlton King Author Twitter@Carlton_King Instagram@carltonkingauthor To read Carlton's Autobiography: “Black Ops – The incredible true story of a (Black) British secret agent” Click the link below: https://www.amazon.co.uk/dp/BO1MTV2GDF/ref=cm_sw_r_cp_awdb_WNZ5MT89T9C14CB53651 Carlton is available for speaking events. For this purpose use the contact details above.

A sit down with Author and Armourer - Dids Hall (Part 1) Black Spy Podcast Season 15, Episode 0009 This week's Black Spy Podcast is a sit down discussion with Author and Armourer Dids Hall. The discussion ebbs and flows over several topics in two episodes, from the problems he has encountered living in the EU since BREXIT, to the Conservative governments mendacity, Labour's potential and the cost of living crisis in the UK. Dids asks why the UK missed out on recent industrialism as the two discuss lost colonial opportunities, UK militarism, service industries as they question what the future holds. The podcast also discusses firearms and their deployment and utility by police in various countries, plus the lack thereof in the UK as men consider whast unarmed policing actually denotes? The episodes swing into various other topics, providing an interesting, entertaining and eclectic mix. In other words, its another must listen episode of the Black Spy podcast. If you want to continue learning whilst being entertained, please don't forget to subscribe to the Black Spy Podcast for free, so you'll never miss another episode. To contact Firgas Esack of the DAPS Agency go to Linked In To contact Carlton King by utilising any of the following: To donate - Patreon.com/TheBlackSpyPodcast Email: carltonking2003@gmail.com Facebook: The Black Spy Podcast Facebook: Carlton King Author Twitter@Carlton_King Instagram@carltonkingauthor To read Carlton's Autobiography: “Black Ops – The incredible true story of a (Black) British secret agent” Click the link below: https://www.amazon.co.uk/dp/BO1MTV2GDF/ref=cm_sw_r_cp_awdb_WNZ5MT89T9C14CB53651 Carlton is available for speaking events. For this purpose use the contact details above.

I'm joined by guests Steve Lee, Future Paul, Odell, & Rijndael to go through the list. Housekeeping 00:02:49 Coinkite needs a technical writer Vulnerability Disclosures 00:32:32 SATAn 00:35:45 Mullvad 00:37:28 Federal officials warn of CISA exploitation 00:43:23 Coordinated attacks on Docker Hub via malicious repositories 00:44:11 Cuckoo 1:37:15 Critics fear Signal may be compromised after Katherine Maher appointment Quick fire discussion topics 00:16:16 Ossification 00:18:39 Dev funding Bitcoin • Software Releases & Project Updates 00:48:24 Sparrow Wallet 00:50:04 COLDCARD 00:52:16 Secp256k1 00:57:51 Umbrel 00:58:10 Blockstream Green 00:58:23 BlueWallet 00:58:34 Nunchuk 1:03:58 Theya Inc. Bitcoin wallet 1:06:46 10101 1:06:52 BTCmap-android 1:07:10 Braiins Toolbox Project Spotlight 1:07:18 BBQr-rust 1:08:40 Awning 1:09:47 GroupHug 1:09:54 Hodlboard Privacy Software • Software Releases & Project Updates 1:10:25 Unleashed.Chat Project Spotlight 1:10:40 Emessbee Lightning & L2(+) • Software Releases & Project Updates 1:20:24 LND 1:20:47 Mutiny Node 1:33:39 Breez SDK 1:33:46 Blockstream Green iOS 1:34:29 BoltzExchange boltz-backend 1:35:35 SwissBitcoinPay 1:35:39 LNp2p Bot 1:35:45 Geyser Project Spotlight 1:36:10 clArk 1:36:28 Helm Wallet Nostr • Software Releases & Project Updates 1:40:16 Primal 1:42:50 nos2x 1:43:32 Mostro Project Spotlight 1:43:46 Iris Docs 1:43:53 ROASTr 1:44:09 Magstr 1:44:28 NostrDVM 1:44:49 NosDrive Boosts 1:53:22 Shoutout to top boosters: @apemithrandir, @loke, @jcdenton, @vake, @2ndbreakfast, @bendthefed & @tmakerman Tech Tip of the Day 1:54:58 ASCIImoji News & Noteworthy • Lightning 1:55:38 Ocean launches Lightning payouts • Nostr 1:56:40 NIP-104 2:00:50 LightningTipBot and ln.tips are retiring • Funding 2:06:27 OpenSats receives an additional donation of $21M 2:09:21 OpenSats grants long-term support for Shashwat Vangani 2:09:29 Spiral grant renewals Links & Contacts Website: https://bitcoin.review/Podcast Substack: https://substack.bitcoin.review/ Twitter: https://twitter.com/bitcoinreviewhq NVK Twitter: https://twitter.com/nvk Telegram: https://t.me/BitcoinReviewPod Email: producer@coinkite.com Nostr & LN:⚡nvk@nvk.org (not an email!) Full show notes: https://bitcoin.review/podcast/episode-66

Povod za ovu epizodu i razgovor bio je projekat Lokalac na internetu koji je pokrenula Fondacija Registar nacionalnog internet domena Srbije, a u razgovoru sa Marijanom Borković, Communications menadžerkom u RNIDS-u smo se dotakli još nekih njihovih projekata poput Domen.rs, DIDS konferencije i pričali o potrebi edukacije marketinške publike na temu upotrebe domena, o brendiranju, ali pre svega o projektima koji su namenjeni zajednici, njihovom značaju, kolaboraciji sa drugim brendovima… Jedan drugačiji razgovor o zaista sjajnim projektima i inicijativama koje zaista daju vrednost kako internet zajednici tako i celokupnom društvu. Marijana Borković, Communications Manager @ RNIDS - https://www.linkedin.com/in/marijana-borkovi%C4%87-87579193/ Teme u epizodi: - Uvod i predstavljanje - Marijanin karijerni put od medicine do marketinga i komunikacija - O Fondaciji Registar nacionalnog internet domena Srbije - DIDS: gde sve kreativnost može da se nađe - Domen.rs - Lokalac na internetu Prijavite se na naš YouTube kanal: https://bit.ly/3uWtLES Posetite naš sajt i prijavite se na našu mailing listu - https://www.digitalk.rs Pratite DigiTalk.rs na društvenim mrežama: Facebook: https://www.facebook.com/Digitalk.rs Instagram: https://www.instagram.com/digitalk.rs/ Linkedin: https://www.linkedin.com/company/digitalkrs Veliku zahvalnost dugujemo kompanijama koje su prepoznale kvalitet onoga što radimo i odlučile da nas podrže i daju nam vetar u leđa: Partneri podkasta: - Raiffeisen banka - https://www.raiffeisenbank.rs/ Usluge Raiffeisen banke za stanovništvo koje preporučujemo: https://bit.ly/3UiWNxN Usluge za mala i srednja preduzeća Raiffeisen banke koje preporučujemo: https://bit.ly/3Q41zN7 - Kompanija NIS - https://www.nis.rs/ - Ananas - https://ananas.rs/ - kompanija Idea - https://online.idea.rs/ U Ideinoj online prodavnici unesite promo kod 1000digitalk i očekuje vas 1.000 dinara popusta prilikom vaše online kupovine! Prijatelj podkasta: - BiVits ACTIVA Brain Level Up Booster - https://bivits.com/proizvod/brain-level-up/ Kada želiš da živiš i radiš na višem nivou, uzmi BiVits Brain Level Up za više energije i bolju koncentraciju tokom dana! - Izdavačka kuća Finesa - https://www.finesa.edu.rs/ U ovoj epizodi podelićemo dve knjige "Biografija Bendžamin Franklin: Prvi veliki Amerikanac'' izdavačke kuće Finesa onima koji budu najbrži i najkreativniji sa komentarima, a možete nam slobodno pisati i na info@digitalk.rs i direktno nam uputiti komentar, sugestiju ili primedbu. Takođe, svi oni koji na Finesinom websajtu poruče knjige i unesu promo kod digitalk dobiće 10% popusta na već snižene cene izdanja na sajtu: https://www.finesa.edu.rs/

In this episode of the Defence Connect Spotlight podcast, Stephen Kowal, chief executive officer of Atturra, joins host Liam Garman to unpack how Atturra is building a uniquely sovereign workforce to deliver for Defence – and deliver some top tips for SMEs in the defence industry. The pair commence unpacking the importance of sovereignty given Australia's geographic isolation, and what the Defence Industry Development Strategy (DIDS) means for Australian industrial capability. Kowal then unpacks the workforce constraints facing the defence industry, and what initiatives Atturra employs to get the most from their workforce. The podcast wraps up with some top tips for SMEs navigating this journey, and how Atturra will continue delivering for Defence. Enjoy the podcast, The Defence Connect team

Buckle up folks, we got a long one.  5 hundo eps.  Crazy.  We bring back a blast from the past, our friend, Mercury Stardust.  She regales us with tales of her book tour and crazy tiktok life.  Quizbot grills mercury with the hard hitting questions, and we all wonder if Jon will accidentally deadname his guest? Tune in to find out!  Thanks so much for listening for 500 episodes, here is to 500 more!   Cover art Photo by Dids .: https://www.pexels.com/photo/person-solving-distance-of-points-2714073/

Markus Sabadello has been a pioneer and leader in the field of digital identity for many years and has contributed to cutting-edge technologies that have emerged in this space. He is co-editor of the Decentralized Identifiers specification at W3C and co-chair of the Identifiers and Discovery Working Group at the Decentralized Identity Foundation. Markus is founder of Danube Tech, a consulting and development company that works on DID-related infrastructure and products, including the Universal Resolver, Universal Registrar, and the Godiddy.com platform. About Podcast Episode Read more about the episode by heading to ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://northernblock.io/podcasts/decentralized-identifiers-strengths-weaknesses-opportunities-threats⁠⁠⁠⁠⁠⁠⁠ The full list of topics discussed between Markus and Mathieu in this episode include: [00:47] Comparison of DIDs to Other Verifiable Identifiers: Exploring how DIDs contrast with other types of verifiable identifiers and their benefits over traditional identifiers like email addresses and phone numbers. [11:50] How to trust a DID?: Identifying the technical and governance aspects necessary for trusting DIDs. [15:46] Building Trust Around DID Methods: Discussing the challenges and approaches to building trust in various DID methods, considering technical integrity and governance. [23:34] Multi-Factor Authentication for DIDs: Considering whether incorporating multi-factor authentication concepts into DIDs is a viable framing. [25:34] Governance and Human Trust Inputs in DID Documents:Debating the inclusion of governance or human trust inputs in DID documents and whether these should remain purely technical. [31:13] Placing Claims in DID Documents: Discussing the implications of including claims in DID documents, especially concerning privacy, correlation, and data privacy laws. [39:11] Opportunities for DIDs: Identifying opportunities for DIDs to become easier to use, deploy, and provide value, including DID method discovery. [44:04] Value of DIDs Across Different Protocols: Questioning whether a particular DID method retains the same value across different credential exchange protocols. [52:01] Why the Market Should Focus More on Identifiers: Reflecting on the emphasis on verifiable credentials over identifiers and trust models in the context of ongoing digital identity programs. [58:00] Working Groups and Activities for DIDs: Highlighting current working groups and activities related to DIDs where listeners can contribute and engage. Where to find Markus? LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/markus-sabadello-353a0821/ X: https://twitter.com/peacekeeper Follow Mathieu Glaude X: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/mathieu_glaude⁠⁠⁠ LinkedIn:⁠⁠⁠ ⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/mathieuglaude/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Website:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://northernblock.io/⁠

In this sponsored episode of the Edge of NFT, we explore Root Protocol, a groundbreaking project at the forefront of the Web3 Renaissance. Founder and CEO Dylan Dewdney shares his insights on Root's mission to empower individuals through self-sovereignty and drive the evolution of digital identities. With strong support from key industry players such as Animoca Brands and influential venture capitalists, Root Protocol aims to revolutionize the internet landscape! Support us through our Sponsors! ☕

In today's clearing, we are releasing the mixed energy of other peoples energy in your field. Allow yourself to disconnect from other peoples energy that you may be feeling and not knowing if it's yours or someone elses! Blog: https://vibrationelevation.com/energyclearings Facebook: http://www.Facebook.com/vibrationelevationn Instagram: http://www.instagram.com/vibrationelevationn Podcast https://robinyates.com/podcast Twitter https://twitter.com/@vibeEclearing Spritual Renaissance Youtube: https://www.youtube.com/@spiritualrenaissance Photo by Dids .: https://www.pexels.com/photo/background-of-abstract-painting-with-wavy-fluids-6862231/   For More playlists, please visit the new store at https://vibrationelevation.com/store

Often, there's so much stress around weddings, especially planning a wedding, and we all know that stress is often the biggest contributor to health issues. So, in this solo episode with Bella, she takes you through the things she did and didn't do during her wedding day and the wedding planning process in order to best limit the stress in her life. She chats about mindset, nutrition, expectations, and much more!

Professor James Stevens Curl is the author of the book "Making Dystopia: The Strange Rise and Survival of Architectural Barbarism". He dissects the modernist ideology as a historical phenomenon, which is not independent of the authoritarian social forces that surround it. On the contrary, Stevens Curl demonstrates that modernism became an authoritarian aesthetic ideology from early on, which eventually characterized the whole of Western culture. Where many academics in Western Europe have taken a nihilistic approach to the dystopian urban landscapes that have risen after the Second World War, James Stevens Curl chooses a firm position. As he sees it, modernism is a deeply immoral and a socially destructive project, which should be actively combated. Curl has also written extensively about Victorian architecture. Architecturally, the Victorian era was a rich era, with great building activity and saw the construction of many beautiful churches. In his newest book "English Victorian Churches", Curl explains how the European political currents of the time, British religious policy, and local engagement played a significant role in realizing this rich and beautiful architectural period."

On today's Day Two Cloud we dive into Decentralized Identity, or DID. This W3C standard is a unique identifier, authenticated by cryptographic proofs, that individuals and organizations can generate themselves using systems they trust. A DID can be a person, an object, an organization, a data model, or other subject. We explore DIDs, how they work, and what they can be used for with Dr. Joanne Friedman.

On today's Day Two Cloud we dive into Decentralized Identity, or DID. This W3C standard is a unique identifier, authenticated by cryptographic proofs, that individuals and organizations can generate themselves using systems they trust. A DID can be a person, an object, an organization, a data model, or other subject. We explore DIDs, how they work, and what they can be used for with Dr. Joanne Friedman. The post Day Two Cloud 197: Understanding Decentralized Identity With Dr. Joanne Friedman appeared first on Packet Pushers.

On today's Day Two Cloud we dive into Decentralized Identity, or DID. This W3C standard is a unique identifier, authenticated by cryptographic proofs, that individuals and organizations can generate themselves using systems they trust. A DID can be a person, an object, an organization, a data model, or other subject. We explore DIDs, how they work, and what they can be used for with Dr. Joanne Friedman.

On today's Day Two Cloud we dive into Decentralized Identity, or DID. This W3C standard is a unique identifier, authenticated by cryptographic proofs, that individuals and organizations can generate themselves using systems they trust. A DID can be a person, an object, an organization, a data model, or other subject. We explore DIDs, how they work, and what they can be used for with Dr. Joanne Friedman. The post Day Two Cloud 197: Understanding Decentralized Identity With Dr. Joanne Friedman appeared first on Packet Pushers.

On today's Day Two Cloud we dive into Decentralized Identity, or DID. This W3C standard is a unique identifier, authenticated by cryptographic proofs, that individuals and organizations can generate themselves using systems they trust. A DID can be a person, an object, an organization, a data model, or other subject. We explore DIDs, how they work, and what they can be used for with Dr. Joanne Friedman. The post Day Two Cloud 197: Understanding Decentralized Identity With Dr. Joanne Friedman appeared first on Packet Pushers.

On today's Day Two Cloud we dive into Decentralized Identity, or DID. This W3C standard is a unique identifier, authenticated by cryptographic proofs, that individuals and organizations can generate themselves using systems they trust. A DID can be a person, an object, an organization, a data model, or other subject. We explore DIDs, how they work, and what they can be used for with Dr. Joanne Friedman.

Josiah Didier has been playing professional hockey for nine years, but arguably the biggest honor of his career is his current role as the Captain of the Providence Bruins.  Dids joins the show to break down the excellent regular season that the P-Bruins finished with in 2022-23.  We flash back to Josiah's time as an assistant captain at Denver under now-Bruins head coach Jim Montgomery, winning a conference tournament and playing with current NHL role players.  We discuss one of Dids' favorite moments this year - scoring two of his four goals this season on his 30th birthday against Hartford in April.  Josiah also discusses his upcoming trip to Iceland, some of his favorite golf courses around New England, and a surprising fact about B's prospect Georgii Merkulov's golf game. In Beers, it's two Boston selections!  Jake reviews a jacked-up Mexican lager, "Cerveza Fiesta," from Night Shift Brewing in Boston's Lovejoy Wharf.  Will reviews a recent trip to Notch Brewing in Brighton, where their affinity for Czech, German & Austrian ales is second-to-none in the Boston area.  Our Business segment features a breakdown on Tom Brady's purchase of a stake in the Las Vegas Raiders, and we evaluate teams that are prime to relocate across the sports world. We finish with a recap of the Stanley Cup Playoffs so far, the potential for the Heat to go the distance, if Nikola Jokic is a top-five active NBA player, and where LeBron will end up next year. This episode is brought to you by DraftKings. The DraftKings Sportsbook – Boston's hometown Sportsbook is LIVE right here in Mass! Bet on all your favorite sports from the comfort of your own home. Don't bet with some out-of-town sportsbook, BET LOCAL with DraftKings! Plus, ALL new customers who sign up for DraftKings Sportsbook TODAY using code BBB will receive up to TWO HUNDRED DOLLARS in BONUS bets!Soon you'll be able to bet on money lines, spreads, props, and more with one of America's top-rated Sportsbooks – DraftKings Sportsbook!Download the DraftKings Sportsbook app NOW! Sign up with code BBB to get up to TWO HUNDRED DOLLARS in BONUS bets to use once mobile sports betting hits Massachusetts. Only at DraftKings Sportsbook with code BBB! We're proud to present Manscaped as our partner! What guy wouldn't want The Right Tools for The Job?! Head over to manscaped.com/house, or use the code HOUSE at checkout for 20% off AND free shipping on your order. Thanks for listening! Remember to hit the follow button on Spotify, and leave us a review on Apple Podcasts. Join the conversation on Twitter and Instagram. Check out house-enterprise.com for all of our content. --- Support this podcast: https://podcasters.spotify.com/pod/show/beersbusinessandballs/support

The Networking Magazine - "We think that your story needs to be told". Welcome to this edition of Jabba Jabba, the Networking magazine's podcast show. My next Guest has been writing music since the age of 15 and has amassed a portfolio of over 500 songs. In March 2017, she decided to be a full-time top-line songwriter and producer. DiDs Music Website DiDs Music Editorial Presenter - Sanj Saigal Production - Jibba Jabba Website - www.networkingmagazine.co.uk

Welcome to "Micro-credentials in a Minute," produced by Micro-credential Multiverse. In this episode, micro-credential and digital badge experts Rob Bajor and Allison Fromm (Proofspace.id) discuss how decentralized identifiers (DIDs) enhance security online. They explain that while real-world identifiers like fingerprints and signatures are unique to individuals, online accounts rely on third parties like Google and Amazon for ownership and control. Meanwhile, companies can monitor and use our data while we're forced to remember hundreds of passwords. DIDs, on the other hand, allow us to create the digital equivalent of our unique fingerprint, which is entirely private and belongs only to us. By managing our online identity with a DID, we can regain control of our digital identities and democratize the space. Tune in to learn more about the power of DIDs in enhancing online security.

Markus Sabadello has been a pioneer and leader in the field of digital identity for many years and has contributed to cutting-edge technologies that have emerged in this space. He is co-editor of the Decentralized Identifiers specification at W3C and co-chair of the Identifiers and Discovery Working Group at the Decentralized Identity Foundation. Markus is founder of Danube Tech, a consulting and development company that works on DID-related infrastructure and products, including the Universal Resolver, Universal Registrar, and the Godiddy.com platform. About Podcast Episode Read more about the episode by heading to ⁠⁠https://northernblock.io/decentralized-identifiers-did-methods-did-documents-did-resolution The full list of topics discussed between Markus and I in this podcast conversation include: An overview of Decentralized Identifiers (DIDs) - how DIDs came about, their history and evolution. The core properties of DIDs - what sets them apart from other types of identifiers. DID Methods. As of this post, there are 160+ DID Methods listed in this registry. Are they all decentralized? Why are there so many? What are some popular ones that have been adopted? What things to consider in your selection criteria for the right DID Method(s). When would one use DIDs for abstraction purposes vs vanilla public-key cryptography? DID Documents - what can be stored in them? How are they linked to a DID? What are some examples of things you can store in the authentication and service endpoints. How do you interact with them? Using blockchain vs non-blockchain (e.g., DNS server) implementations for storing DID Documents. What are some key elements to take into consideration when looking at these different options? Do DIDs disrupt or enhance existing certificate business models? The power of DID Resolution - how has it evolved, how does it work? (see video below for a great explainer) Where to find Markus? LinkedIn: https://www.linkedin.com/in/markus-sabadello-353a0821/ Twitter: ⁠⁠⁠⁠https://twitter.com/peacekeeper Follow Mathieu Glaude Twitter: ⁠⁠https://twitter.com/mathieu_glaude  ⁠⁠ LinkedIn:⁠⁠ ⁠⁠⁠⁠https://www.linkedin.com/in/mathieuglaude/⁠⁠ Website:⁠⁠ ⁠⁠⁠⁠https://northernblock.io/

امروز تو دنیای کریپتو چه خبره؟ - راه‌اندازی یک پلتفرم ساخت NFT مبنی بر AI (هوش مصنوعی) به نام Bicasso توسط بایننس - تلاش بایننس برای ورود مجدد به بازار کریپتوی سنگاپور پس از وقفه در معاملات در سال گذشته -راه‌اندازی سرویس "هویت غیر متمرکز (DIDs) " پالیگان - به گفته یک مقام بانک انگلستان، CBDC‌ها فرصت‌هایی را برای شرکت‌های مالی فراهم می‌کنند.

In this #FinancialFox episode, Steffy speaks with Tim, Founder of IAMX - a token-based self-sovereign identity (SSI) and authentication system, enabling 1Click-Fulfillment transactions that are legally binding on the state/national level. IAMX is the first-ever SSI solution to financially incentivize and reward consumers each time they use their identity online. Here they discuss self-sovereign identity, DIDs (digital identifiers), #ZK zero knowledge Pproofs, mainstream adoption of wallets, why IAMX choose the Cardano blockchain and last but not least how blockchain technology is disrupting the KYC / KYB process for good. Streaming Now :)

This week, I continue my conversation with Jim Nasr, CEO of Acoer about privacy and using distributed ledger technology (DLT). We discuss his work leading The HBAR Foundation's Privacy Market Development Fund and the trends he sees across grant applicants. We also chat about the collapse of FTX and the ripple effect it's had on the crypto space. ---------Thank you to our sponsor, Privado, the developer-friendly privacy platform---------Jim tells us about the types of innovations The HBAR Foundation seeks to fund; why privacy & security usability is an imperative; uses cases for decentralized identifiers (DIDs) and new "DID methods" like PKH. We also discuss FTX's collapse and how to provide real transparency and data regulation in DLT technology. ---------Listen to the episode on Apple Podcasts, Spotify, iHeartRadio, or on your favorite podcast platform.---------Topics Covered:The HBAR Foundation's search for projects to fund that enhance privacy usabilityExciting privacy use cases Jim has seen using Hedera's DLT, including those that enable high-value, privacy-preserving transactions What went wrong with FTX and what we can learn from it's collapse How decentralized identity can enable the next iteration of web privacyThe tech behind MetaMask's Snap software that allows anyone to safely extend capabilities of their wallet Resources Mentioned:Learn about AcoerLearn about The HBAR FoundationRead about The HBAR Foundation's Privacy Market Development Fund Jim Nasr's Info:Follow Jim on LinkedInFollow Jim on TwitterFollow the SPL Show:Follow us on Twitter Follow us on LinkedInCheck out our website Privado.ai Privacy assurance at the speed of product development. Get instant visibility w/ privacy code scans.Shifting Privacy Left Media Where privacy engineers gather, share, & learnBuzzsprout - Launch your podcast Disclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you.Copyright © 2022 - 2024 Principled LLC. All rights reserved.

Decentralized identifiers or “DIDs”. Tune in for an exploration how blockchain and pseudonymization can systematically improve data security and increase users' control over their digital identities. Our tour guide is Phillip Shoemaker, the Executive Director of identity.com, a non-profit that provides tools for developers to help organizations identify individuals without compromising their security or privacy. Through this approach, enterprises can de-couple personal identities from users, providing instead a separate digital identity for the user that is not linked to a phone number, address, Social Security number, or other means of identifying the user whose data is otherwise at risk. Learn what individuals can do to urge governments, regulators, and businesses to arm digital systems with defenses that prevent malicious actors to hack masses of personal data that are then used to steal and misuse identities and assets. As standards are being developed for software, IoT devices, and digital infrastructure, consider the role of DIDs as a best practice to be adopted broadly. If you have ideas for more interviews or stories, please email info@thedataprivacydetective.com.

The CEO and founder of ShareRing, Tim Bos, is the guest on this episode of the DeFi Download with host Piers Ridyard. Some of the subjects covered include how blockchain technology may benefit identity verification, how ShareRing manages the storing of personal information, and what the future holds for digital ID.  ShareRing is a digital identity blockchain system with features that enable its users to utilise their digital ID in the real world.The ShareRing platform does this by providing users with a highly secure Personal Information Vault where they may securely store encrypted personal information. [01:03] The ShareRing experience, viewed from the user's perspective [03:38] How can ShareRing enhance the user experience of possessing a digital identity and utilising it to attend an event? [06:39] How difficult is it for the events industry to ensure that no one under the age of 18 is permitted entrance to an event and to verify an individual's identity? [08:20] How does ShareRing handle user-generated friction, such as the need that tickets be downloaded and shown at the event entrance? [10:17] How might blockchain technology aid in the management of verifiable identities? [12:53] How does eKYC work? [17:21] Does ShareRing intend to handle anti-money laundering from the standpoint of the source of wealth and funds, as well as the regulatory requirements that must be met in order to deposit funds in a financial marketplace?[18:41] How does the process of exchanging data between institutions like banks work?[22:52] How are digital documents stored and managed within the ShareRing Vault? [24:00] Can ShareRing do PEP and sanctions checks? [25:38] From the perspective of having verifiable credentials, a large portion of ShareRing's work is structured in accordance with the W3C's standards for decentralised identifiers (DIDs) [26:38] What hurdles did ShareRing need to overcome in order to design credentials compliant with W3C specifications?[28:28] The process of integrating standards and overcoming the issue of coping with continuously emerging ones [30:10] From a philosophical standpoint, doesn't ShareRing's work contradict the ideals of public ledgers, complete pseudonymity, and the ability to transact without identifying oneself? Why is it important to have an actual identity when you can have things like soulbound tokens (SBTs) and reputation that don't have to relate to a real-world identity? [32:02] Does a soulbound token offer a reference to an on-ledger zero-knowledge proof about a person, or is each soulbound token a unique issuance that depends on what you wish to prove? [33:59] What is ShareRing's primary business growth strategy? [38:41] What is ShareRing's approach to doing business? [39:32] What is the definition of a transaction in the ShareRing ledger? [41:11] How can ShareRing and the institutions with whom it partners ensure that the method of document verification is accurate? [44:12] Hackathons hosted by ShareRingFurther resourcesWebsite: sharering.network Twitter: @ShareRingGlobal, @TheRealTimBos

Sign up for coaching: https://www.melbournestrengthculture.com/coaching-services 0:00 Number 1 in the hearts, number 1 in the charts 0:23 JPS Meet Recap 6:38 Reflecting on Comp Days 8:00 Port Douglas Recap + Phobias 16:00 Dids' Basketball Recap 16:30 What are we watching? 33:06 What supplements do we take? 33:20 Social-media and comparison 42:00 Q&A ➽ Strength Culture's Public Discord: https://discord.gg/qeBqfhPgmf ➽ Elite Supplements: 10% Off Code: CULTURE10 https://www.elitesupps.com.au/ ➽ Instagram: Strength Culture - www.instagram.com/melbournestrengthculture Jamie S - www.instagram.com/j.smith.culture Charlie - www.instagram.com/quantum_lifting Jamie B - www.instagram.com/jamiebouz Didier - www.instagram.com/didiervassou ➽ Online Coaching: https://www.melbournestrengthculture.com/coaching-services ➽ Training Programs and E-books: https://www.melbournestrengthculture.com/store ➽ TikTok: https://www.tiktok.com/@melbournestrengthculture ➽ YouTube: https://www.youtube.com/c/MelbourneStrengthCulture

Photo by Dids on Pexels Latest chillout hour! My weekly shows feature a mix of music new and old, by my favorite producers and myself. I livestream on MixCloud, see my channel for the latest schedule information. If you enjoy, please follow me here for more, and also find me on Mixcloud, Soundcloud, Instagram, and YouTube. Thank you for listening!00:00 - Kota - Bonobo05:30 - Gaia's Garden - Kalya Scintilla13:14 - Looped - Kiasmos19:00 - Grey Light (Christian Löffler Remix) - Christian Löffler, Francesco Tristano24:53 - Origins - Max Cooper27:37 - The Misery (Nu and Pauli vs Acid Remix) - Daniel Bortz33:06 - Something Something - Sync2440:23 - Jetlag Corporation (Remastered) - Aes Dana45:18 - Salta (Edit) - Jacana People49:18 - Sky Trees - Solar Fields52:56 - I Don't Know What To Say (Original Mix) - B. Hayes

Andy Parsons, director of the Content Authenticity Initiative at Adobe gives Doc Searls and Katherine Druckman a lot of confidence that we really can change the Web and the world for the better. If you care about eliminating dis- and mis-information, you want authentic content and clear provenance. Parsons explains on FLOSS Weekly. Hosts: Doc Searls and Katherine Druckman Guest: Andy Parsons Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: IRL Podcast bitwarden.com/twit Compiler - FLOSS

Andy Parsons, director of the Content Authenticity Initiative at Adobe gives Doc Searls and Katherine Druckman a lot of confidence that we really can change the Web and the world for the better. If you care about eliminating dis- and mis-information, you want authentic content and clear provenance. Parsons explains on FLOSS Weekly. Hosts: Doc Searls and Katherine Druckman Guest: Andy Parsons Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: IRL Podcast bitwarden.com/twit Compiler - FLOSS

Andy Parsons, director of the Content Authenticity Initiative at Adobe gives Doc Searls and Katherine Druckman a lot of confidence that we really can change the Web and the world for the better. If you care about eliminating dis- and mis-information, you want authentic content and clear provenance. Parsons explains on FLOSS Weekly. Hosts: Doc Searls and Katherine Druckman Guest: Andy Parsons Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: IRL Podcast bitwarden.com/twit Compiler - FLOSS

Andy Parsons, director of the Content Authenticity Initiative at Adobe gives Doc Searls and Katherine Druckman a lot of confidence that we really can change the Web and the world for the better. If you care about eliminating dis- and mis-information, you want authentic content and clear provenance. Parsons explains on FLOSS Weekly. Hosts: Doc Searls and Katherine Druckman Guest: Andy Parsons Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: IRL Podcast bitwarden.com/twit Compiler - FLOSS

In this month's Investing in Identity series, we tackle recent deals and trends in digital identity that are shaking up the industry. Topics covered include: Thoma Bravo takes identity and access management platform Ping Identity private for $2.8B. BalkanID, an AI-powered privileged access management platform raises a $2.36M seed round extension. Truework, a fintech company that provides income and employment verification, raises $50M in Series C funding. Microsoft Entra Verified ID goes live, enabling direct integration of DIDs with Azure Active Directory.

EPISODE: 69 BLOCK: 743883 PRICE: 4918 sats per dollar TOPICS: decentralized identifiers, credentials, tradeoffs, "web5" proposal, lightning privacy work, unannounced channels, probing, the next week of dispatch is loaded https://citadeldispatch.com/cd69 support the show: https://citadeldispatch.com/contribute twitch: https://twitch.tv/citadeldispatch bitcointv: https://bitcointv.com/video-channels/citadeldispatch/videos podcast: https://www.podpage.com/citadeldispatch telegram: https://t.me/citadeldispatch stream sats to the show: https://www.fountain.fm/ join the chat: https://matrix.to/#/#citadel:bitcoin.kyoto

Dan Lynch and Doc Searls chats with Sam Curren about DIDs and why they're important for today's online identity. Curren has worked extensively on the project ands shares insight with the FLOSS Weekly co-hosts. For more, check out FLOSS Weekly: https://twit.tv/floss/685 Hosts: Doc Searls and Dan Lynch Guest: Sam Curren You can find more about TWiT and subscribe to our podcasts at https://podcasts.twit.tv/

Dan Lynch and Doc Searls chats with Sam Curren about DIDs and why they're important for today's online identity. Curren has worked extensively on the project ands shares insight with the FLOSS Weekly co-hosts. For more, check out FLOSS Weekly: https://twit.tv/floss/685 Hosts: Doc Searls and Dan Lynch Guest: Sam Curren You can find more about TWiT and subscribe to our podcasts at https://podcasts.twit.tv/

Dan Lynch and Doc Searls chats with Sam Curren about DIDs and why they're important for today's online identity. Curren has worked extensively on the project ands shares insight with the FLOSS Weekly co-hosts. For more, check out FLOSS Weekly: https://twit.tv/floss/685 Hosts: Doc Searls and Dan Lynch Guest: Sam Curren You can find more about TWiT and subscribe to our podcasts at https://podcasts.twit.tv/

Sam Curren unpacks for Doc Searls and Dan Lynch why DIDs and DIDcomm are the best approach to identity—and to making people first-class citizens on the Internet. Curren also discusses the origin story of picos and the advantages of nomadic living and hacking. Hosts: Doc Searls and Dan Lynch Guest: Sam Curren Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: kolide.com/floss itpro.tv/twit promo code TWIT30 NetFoundry.io/TWIT

Sam Curren unpacks for Doc Searls and Dan Lynch why DIDs and DIDcomm are the best approach to identity—and to making people first-class citizens on the Internet. Curren also discusses the origin story of picos and the advantages of nomadic living and hacking. Hosts: Doc Searls and Dan Lynch Guest: Sam Curren Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: kolide.com/floss itpro.tv/twit promo code TWIT30 NetFoundry.io/TWIT

Sam Curren unpacks for Doc Searls and Dan Lynch why DIDs and DIDcomm are the best approach to identity—and to making people first-class citizens on the Internet. Curren also discusses the origin story of picos and the advantages of nomadic living and hacking. Hosts: Doc Searls and Dan Lynch Guest: Sam Curren Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: kolide.com/floss itpro.tv/twit promo code TWIT30 NetFoundry.io/TWIT

Sam Curren unpacks for Doc Searls and Dan Lynch why DIDs and DIDcomm are the best approach to identity—and to making people first-class citizens on the Internet. Curren also discusses the origin story of picos and the advantages of nomadic living and hacking. Hosts: Doc Searls and Dan Lynch Guest: Sam Curren Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: kolide.com/floss itpro.tv/twit promo code TWIT30 NetFoundry.io/TWIT

David Chan is a Managing Director within EY's Technology Consulting practice, where he helps entrepreneurs, companies, and government entities solve their most pressing cybersecurity challenges. David has over 16 years of experience in cybersecurity and identity and access management. He is currently focused on security reviews of Web3 and implementing blockchain at large organizations. In this episode… When it comes to cyberspace, digital identity is expanding. To adopt this form of identity, businesses need to adhere to the privacy regulations surrounding its use. So, how can your business implement user-friendly identity and access management programs that maintain privacy and security?  Blockchain encourages user transparency and identity security. With blockchain, users can authenticate their identity without using passwords, ensuring an effortless and secure experience. And, by integrating decentralized identifiers (DIDs) into your business, you can save money on privacy and security while giving users consent over their information and identity. In today's episode of She Said Privacy/He Said Security, Jodi and Justin Daniels sit down with David Chan, Managing Director of EY's Technology Consulting practice, to talk about integrating identity programs into your business. They cover the three types of identity and access management programs, how businesses can adopt DID while adhering to privacy and security, and the benefits of implementing blockchain into your identity programs.

Daniel Buchner is the Head of Decentralized Identity at Block, the company formerly known as Square. In our talk, Daniel helped me understand the concept of identity, why and how identity can be decentralized, and how having self-sovereignty over your identity can change the relationships and the power dynamics between users and the apps we use today. → TBD: https://tbd.website/ → DIF: https://identity.foundation/ Sponsors → Voltage: https://voltage.cloud?utm_source=kevinrooke&utm_medium=Youtube&utm_campaign=1mo → ZEBEDEE: https://zbd.gg/ At the end of every show, I answer any questions listeners send in over the Lightning Network. To ask a question, send a message, or to support the show, download Fountain from the App Store and load your wallet with a few sats. → Fountain: https://www.fountain.fm/ → More Episodes: https://play.fountain.fm/show/P6XXuSPg6f2rj4ECB0fT → Lightning Address: ⚡kerooke@fountain.fm Links → Twitter: https://twitter.com/kerooke → Books: https://www.kevinrooke.com/book-recommendations → Blog: https://www.kevinrooke.com/blog Timestamps 00:00 - Highlights & Intro 02:34 - Daniel Buchner Intro 08:38 - Taking Control of Your Public Identifiers 13:39 - Securing Decentralized Identifiers 22:59 - Building a Decentralized Identity Network 25:32 - Block's Decentralized Identity Work 36:54 - Privacy for DIDs 45:00 - DIDs vs. Slashtags 49:24 - The Process of Developing Open Standards 56:31 - Applications for Decentralized Identity 1:00:07 - Personal Servers 1:03:00 - How Self-Hosting Changes the Relationships Between Apps and Users 1:12:24 - tbDEX 1:20:06 - The Lightning Round

#53 When you log into an account with Google or Facebook, you're doing an identity verification through a central intermediary. While it may seem convenient to log in with these established accounts, it comes with concerns for privacy. These large intermediaries will gather metadata as you use the account—things like when and how long you used it, where you were located, and other online activity you engaged in during that time. This information is often used to create targeted ads for you. It can be surprising how quickly you start seeing ads for an item you looked up while your activity was being monitored. And ads seem relatively innocent when compared to other possible uses of this metadata, such as interference in elections. Decentralized identifiers (DIDs) provide a different credential-checking method that doesn't rely on that intermediary.How do Decentralized Identifiers (DIDs) Work?

Lifting Workshops: https://www.melbournestrengthculture.com/workshop-seminars We are available for online and in-person coaching: https://www.melbournestrengthculture.com/coaching-services   Timestamps: 0:00 Number 1 in the hearts, number 1 in the charts.1:49 Welcoming back Charles and Dids.4:09 QLD Clout Tour recap.10:35 Tren-Tok.15:16 Jared Powell is a Twitter cowboy.17:50 A thank you to Get Going.21:52 SYD Clout Tour plans.24:11 Kambosos update.29:10 Have you seen Uncut Gems?31:42 How to track “Hectic Eats”?37:32 Favourite sporting moment of all time?39:27 Is ‘line of pull' anything to worry about?44:28 PRI discussion.50:42 Conditioning protocols for powerlifters.58:08 USA manifestation station. TikTok: https://www.tiktok.com/@melbournestrengthculture Instagram: ➽ Strength Culture - www.instagram.com/melbournestrengthculture ➽Jamie S - www.instagram.com/j.smith.culture ➽ Jamie B - www.instagram.com/jamiebouz ➽ Didier - www.instagram.com/didiervassou ➽ Charlie - www.instagram.com/quantum_lifting  

Dylan Dewdney, Co-Founder and Lead Initiator at NFT3.com and Kylin Network, discusses the world of DIDs (decentralized identifiers) and some of the future use cases, along with how Web3 will change the way data is handled. He also talks about the changing relationship between marketers and the data needed to optimize their businesses, and why privacy is often highlighted but becomes compromised in an effort to track results.  We also discuss: How data ownership will impact the ways in which consumers interact with the internet and view their personal privacy The ethics and security considerations for sharing your data in a web3 world The lifetime values of our personal genome data and how much we should or could be paid for sharing it along with ways that large multinational companies can monetize idle data sets Importance of appealing to human emotions in marketing and committing to a particular position or belief. Guest Bio: Dylan Dewdney, Co-Founder and Lead Initiator at NFT3.com and Kylin Network. Dylan is a longtime crypto supporter and enthusiast dating all the way back to 2011. He has consistently been at the forefront of the intersection between society and technology and has appeared alongside such luminaries as Edward Snowden and Gavin Wood.  Dylan is an investor and advisor to a number of crypto projects and has been building in the space since 2017. His most recent interests and pursuits are in the fields of decentralized data monetization and decentralized identity, respectively, as co-founder of Kylin Network and NFT3, respectively.  ---------------------------------------------- About this Show: The Brave Marketer podcast is hosted by Donny Dvorin, VP, Head of Sales at Brave Software - the makers of the privacy-respecting browser with a built-in ads platform that rewards users for their attention with the Basic Attention Token. Brave is at the forefront of a new online privacy frontier and has unique insights into the future of marketing and advertising in a cookieless world.  Music by: Ari Dvorin  

On this episode of DAOn the Rabbit Hole, we're talking with Evin McMullen. Evin is the co-founder of Disco, a company working to bring decentralized identifiers to the web3 party. Evin has long understood the value of data and the role it plays in our daily lives. In the web3 space, we finally have the opportunity to take control of that data and use it in new and exciting ways. Evin explains how all of this data comes together to create our digital identities and reputations, and explains how we can better organize and use the data that we choose to put on-chain.Evin talks about what types of information should and shouldn't be put on-chain, and how a more robust reputation system can help us solve more interesting coordination problems. She also dives deep into decentralized identifiers and the important role they can play in aggregating the many names, accounts, and wallet addresses we use on a daily basis. To continue this conversation and stay up to date on all things DAOn the Rabbit Hole, you can follow Anay on Twitter @anay_sim and RabbitHole @rabbithole_gg. You can follow our guest, Evin McMullen, on Twitter @provenauthority. ⌛ TIMESTAMPS: 0:00 Intro1:02 Evin's Background6:18 Digital Identity and Identifiers12:22 Data and reputation on web215:46 Creating a more robust web3 reputation system17:53 What are decentralized identifiers (DIDs)?   23:44 Verifiable credentials25:49 Use-cases for DIDs29:37 How can we trust DIDs?34:40 Criticisms of DIDs 42:19 What is Disco? 48:00 Disco's long term goals49:52 This or That 

You've asked for it and now it's here! Join Bob, Brennan, and DJ as they review The Black Hand: Playing the Sabbat.CreditsWRITTEN BY Rachel E. Judd, Khaldoun Khelil, and Saskia LiddickEDITING AND READING: Rachel E. Judd, Khaldoun Khelil, and Saskia LiddickART DIRECTOR: Khaldoun KhelilCOVER ART: Mark KellyINTERIOR ART AND ILLUSTRATION: Mark Kelly, Pexel (Lucas Alves, CottonBro, Dids, Eberhard Grossgasteiger, Kourtney Gunderen, ItzyPhoto, Adrien Olichon, Aleksandar Pasaric, Farzad Sedaghat), and UnSplash (Silvana Amicone, Andrew Amistad, David Bayliss, Volker Braun, BSD, Noah Buscher, James Coleman, Daniele Colucci, Yoal Desurmont, Hiep Duong, Cheng Feng, Samuele Giglio, Matt Hearne, MichaelHeuss, Casey Horner, Maksim Istornin, Jr Korpa, Zane Lee, Ed Leszczynski, Stephany Lorena, Testalize Me, Dima Pechurin, Alexander Popov, Alex Rainer, Jamison Riley, Joshua Rodriguez, Florian Schmetz, Sebastiaan Stam, Nikita Shirokov, Zoriana Stakhni, Diana Vargas, Logan Weaver, Simon Zhu)GRAPHIC DESIGN AND LAYOUT: Khaldoun KhelilPurchase it here: The Black Hand: Playing the SabbatSupport the show (https://www.patreon.com/25yearsofvampirethemasquerade)

Today in the lab we talk about what it is to be an empath. We dive into our own stress and then have some laughs at a canceled Hitler sitcom and Hugh Jackman being built. Full episode with video on YouTube!!! https://linktr.ee/TactLabThis is TACT Lab, a podcast where nothing is off limits. Join four guys as they talk about the greatest accomplishments and problems in life. Hosted by Tyler, Alex, Chris, and Thomas. Check us out on all social media by searching TACT Lab or click the link above. New episodes every Wednesday. Help Support us at our Patreon. Like, follow, comment and let us know how we are doing!

Stepan Gershuni is working towards making it easier for DAOs to onboard talent through Professional ID credentials. There is an oversupply of talent looking to join DAOs and Stepan is trying to help them manage their excess talent pools and onboard people faster. About Episode During this conversation, we discuss: Where are the opportunities to apply SSI principles and frameworks towards DAOs? How do you decentralize hiring, education, and the coordination of work. Are .eth good or bad identifiers? Are .eth names and decentralized identifiers (DIDs) mutually exclusive? How can the decentralized discovery of professional skills happen? And more! About Guest Stepan Gershuni is the Lead Product Manager at Affinidi, Founder of Credentia and Deep Skills. Twitter: https://twitter.com/sgershuni LinkedIn: https://www.linkedin.com/in/sgershuni/ Follow Mathieu Glaude Twitter: https://twitter.com/mathieu_glaude LinkedIn: https://www.linkedin.com/in/mathieuglaude/

DMK promised 1K gave 0, DIds says 5K! Whose money is it? Dr. Swamy breaks down the pros and cons of freebies and how they affect the country in the long run.

DIDs or Digital Identities enable us to take our personal information onto a decentralised network where we can choose exactly what we want to share and who to share it with. Microsoft is one of the leaders in this field with their Identity Overlay Network, brining this technology to the public.Feel free to get in touch via any of my social media which can all be found here:https://linktr.ee/BlockchainAndBeyond   

  The Black Spy Podcast Season 2, episode 0005 Hollywood shooting death, how could it happen? Should the British Police be Armed? - A conversion with author, armourer and firearms instructor, Dids Hall. This week's Black Spy Podcast brings you a thought provoking discussion with Did's Hall, author, armourer and firearms instructor. Did's and Carlton discuss firearms in society, including: The questionable shooting death of a Hollywood producer by a world famous actor. Do the movies get firearms use correct. Carlton asks Did's which actor, in his option, portrays the most realistic use of firearms in a movie. Should all British police be routinely armed? Should civilians have the right to bare arms? Can police be fully professional if they don't routinely carry firearms. Does being unarmed mean that British police, must police by consent, whereas the routinely armed police of other countries don't? Are unarmed police forced to be more violent? The historical reason why British police are unarmed. Listeners will note that Dids and Carlton are not in total agreement on these issues, which makes for riveting and entertaining listening. In short, this is another Black Spy episode that goes way beyond simple concepts. This episode is a fine example of the Black Spy Podcast's tendency go deeper, in order to educate. This episode will be released on Monday 15th of November 2021 To donate to The Black Spy go to: Patreon.com/TheBlackSpyPodcast To contact Carlton: Email: carltonking2003@gmail. Facebook: The Black Spy Podcast Facebook: Carlton King Author Twitter: @Carlton_King Instagram: @carltonkingauthor To know more about Carlton's unique journey into the secret services read his autobiography: “Black Ops – The incredible true story of a British secret agent” CLICK: https://www.amazon.co.uk/dp/BO1MTV2GDF/ref=cm_sw_r_cp_awdb_WNZ5MT89T9C14CB53651 Carlton is also available for speaking events, to book him, use the contacts above.  

There have been numerous studies and interviews with people throughout the many stages of life to discover what we regret the most. Let's discuss what we can be doing RIGHT NOW to create a life full of meaning and purpose. A life on the path to Master Happiness. Join us as we discuss how to AVOID REGRET with the power of BACON! B - Beckon Happiness, pull it is and spread it around. A - Adventures, risks, and chances! Take them while you can! C - Cherish Your Family and Friends. You are not promised a tomorrow with them. O - Occupation Switch? Maybe it's time to go for that promotion or find a new, more fulfilling job N - Nourishing your Body and Mind gives you the most life and the most out of life! Don't fill your past with would haves, could haves, and should haves! Fill it with DIDs and DONEs, & tons of FUN! www.MasterHappiness.com/live #SalesCoach #PublicSpeaking #Keynote #Career #Relationships #MasterHappiness #Jalove #Bacon #WRLR #BaconBits #MartyJalove #WhatsYourBACON #Fear #Courage #regrets

In this episode we talk about our kinda shady pasts and some suspicious things we saw in school growing up. See behind the scenes on Instagram:instagram.com/natelovesjeninstagram.com/coreyphoebus If you're enjoying this podcast and would like to donate a little bit to help us keep this podcast going, feel free to go to buymeacoffee.com/natelovesjen to share the love.

Murray Legg and his team of cryptographers at PhotoChromic are building biometrically managed self sovereign digital identity NFTs on the blockchains. Check out today's podcast to learn more about the technology, it's application, and the progress being made in the realm of DIDs. View links mentioned in the podcast and check out more information in the description on Youtube: https://youtu.be/Xkjh7FsA5MI

We use our identity each day, and often more times than we realize. We use our identity to shop online, submit tax returns and even logon for a day's work. Each of these require a separate identity and the need to remember passwords, and a separate registration process. What if we could merge these and have a shared ID instead of having different credentials? The good news is that blockchain has enabled a new way to solve this problem through constructs like verifiable credentials (VCs) and the ability to orchestrate identity verification across the network. In this episode, David Chan, Ernst & Young LLP, speaks with Ankur Patel, Microsoft – Identity Products Lead and Rob Foster, Ernst & Young LLP, about how DIDs (decentralized identities) can improve the user experience and streamline identity management processes.

My guest today is Donald E. Bullers, the founder of Tuum Technology. Tuum Technology is Tuum Technologies is the world's leading Elastos software company. Tuum enables a global network of entrepreneurs, developers, academics, industry experts, and users to access the decentralized internet. Through their network, they empower teams with the necessary resources to build revolutionary applications and launch decentralized platforms. Elastos is the largest Web3 provider of open source solutions, employing not only blockchain technology, but a peer-to-peer network for communication, decentralized data storage services, and a decentralized ID system. With Elastos, Tuum aims to revolutionize the internet. Tuum is fully decentralized and serverless, all communication runs through Elastos Peer-to-Peer Network(Carrier). Prior to Tuum, Donald's career consisted of 10+ years of positive leadership in the field of technology that spans from a digital marketing agency to Vice President to Founder of a global software development company. With interest in data rights and personal cloud computing, he advances teams developing software for an entirely decentralized internet using Elastos Web 3.0 technology. You will find my conversation with Donald to be eye-opening and thought-provoking. In our discussion, we cover Tuum Technology, Elastos, the future of digital identities, building infrastructure for Web3.0, and much more. Donald explains what makes Elastos unique and how Tuum is building tools to empower people to become sovereign individuals. Donald dives deep into the suite of products Tuum is building to provide the infrastructure layer needed to bring Web3.0 to the mainstream. We also discuss the importance of digital identities (DID) and how identity is the killer app to unlock the true potential of crypto and Web3.0. Donald goes on to discuss real-world examples of how DIDs are being used and how they can be integrated into society. One of the most important topics discussed during my conversation with Donald was how Web3.0 tech will fundamentally disrupt the Web2.0 tech-stack leading to reorganization of value creation and society more broadly. Towards the end of our conversation, we discuss how the content one consumes influences their thoughts and actions. We finish our conversation by urging listeners to consciously curate the content they consume. Please enjoy my conversation with Donald Bullers. -- Kava connects the world's largest cryptocurrencies, ecosystems and financial applications on DeFi's most trusted, scalable and secure earning platform. Built to scale on the largest decentralized PoS network, Kava lets you mint stablecoins, lend, borrow, earn and swap safely and efficiently across the world's biggest crypto assets with a simple and intuitive user experience and the full confidence of institutional-grade security and quality . To learn more visit https://untoldstories.link/kava -- Ledn provides financial products to help you unlock the power of digital assets. With a secure and easy-to-use platform, it's the simplest way to earn interest, borrow, and trade your BTC and USDC. For maximum accountability, Ledn offers Proof of Reserves attestations to give you peace of mind while you make the most of your Bitcoin. Untold Stories listeners can receive $50 in free BTC when you create a new loan. More info at https://untoldstories.link/LEDN -- This podcast is powered by Blockworks. For exclusive content and events that provide insights into the crypto and blockchain space, visit them at https://blockworks.co

Sunday September 12, 2021. "A Church of 'Dids' and 'Didn'ts'" a sermon on Matthew 25:31-46 from Reverend Robert O. Browning.

Sunday September 12, 2021. "A Church of 'Dids' and 'Didn'ts'" a sermon on Matthew 25:31-46 from Reverend Robert O. Browning.

Bajie links in with musician and Newcastle fan T_dids and tested his memory on his football love.

About Nader DabitNader Dabit is a web and mobile developer, author, and Developer Relations Engineer building the decentralized future at Edge and Node. Previously, he worked as a Developer Advocate at AWS Mobile working with projects like AWS AppSync and AWS Amplify. He is also the author and editor of React Native in Action and OpenGraphQL.Nader Dabit Twitter: @dabit3Edge and Node Twitter: @edgeandnodeGraph protocol Twitter: @graphprotocolEdge and Node: edgeandnode.com Everest: everest.link YouTube: YouTube.com/naderdabitWhat is Web3? The Decentralized Internet of the Future ExplainedWatch this episode on YouTube: https://youtu.be/pSv_cCQyCPQ This episode is sponsored by CBT Nuggets and Fauna. TranscriptJeremy: Hi everyone. I'm Jeremy Daly and this is Serverless Chats. Today I am joined again by Nader Dabit. Hey Nader, thanks for joining me.Nader: Hey Jeremy. Thanks for having me.Jeremy: You are now a developer relations engineer at Edge & Node. I would love it if you could tell the listeners a little bit about yourself. I think a lot of people probably know you already, but a little bit about your background and then what Edge & Node is.Nader: Yeah, totally. My name is Nader Dabit like you mentioned, and I've been a developer for about, I guess, nine or ten years now. A lot of people might know me from my work with AWS, where I worked with the Amplify team with the front end web and mobile team, doing a lot of full stack stuff there as well as serverless. I've been working as a developer relations person, developer advocate, actually, leading the front end web and mobile team at AWS for a little over three years I was there. I was a manager for the last year and I became really, really interested in serverless while I was there. It led to me writing a book, which is Full Stack Serverless. It also just led me down the rabbit hole of managed services and philosophy and all this stuff.It's been really, really cool to learn about everything in the space. Edge & Node is my next step, I would say, in doing work and what I consider maybe a serverless area, but it's an area that a lot of people might not associate with the traditional, I would say definition of serverless or the types of companies they often associate with serverless. But Edge & Node is a company that was spun off from a team that created a decentralized API protocol, which is called the Graph protocol. And the Graph protocol started being built in 2017. It was officially launched in a decentralized way at the end of 2020. Now we are currently finalizing that migration from a hosted service to a decentralized service actually this month.A lot of really exciting things going on. We'll talk a lot about that and what all that means. But Edge & Node itself, we do support the Graph protocol, that's part of what we do, but we also build out decentralized applications ourselves. We have a couple of applications that we're building as engineers. We're also doing a lot of work within the Web3 ecosystem, which is known as the decentralized web ecosystem by investing in different people and companies and supporting different things and spreading awareness around some of the things that are going on here because it does have a lot to do with maybe the work that people are doing in the Web2 space, which would be the traditional webspace, the space that I was in before.Jeremy: Right, right. Here I am. I follow you on Twitter. Love the videos that you do on your YouTube channel. You're like a shining example of what a really good developer relations dev advocate is. You just produce so much content, things like that, and you're doing all this stuff on serverless and I'm loving it. And then all of a sudden, I see you post this thing saying, hey, I'm leaving AWS Amplify. And you mentioned something about blockchain and I'm like, okay, wait a minute. What is this that Nader is now doing? Explain to me this, or maybe explain to me and hopefully the audience as well. What is the blockchain have to do with this decentralized applications or decentralized, I guess Web3?Nader: Web3 as defined by definition, what you might see if you do some research, would be what a lot of people are talking about as the next evolution of the web as we know it. In a lot of these articles and stuff that people are trying to formalize ideas and stuff, the original web was the read-only web where we were not creators, the only creators were maybe the developers themselves. Early on, I might've gone and read a website and been able to only interact with the website by reading information. The current version that we're currently experiencing might be considered as Web2 where everyone's a creator. All of the interfaces, all of the applications that we interact with are built specifically for input. I can actually create a comment, I can upload a video, I can share stuff, and I can write to the web. And I can read.And then the next evolution, a lot of people are categorizing, yes, is Web3. It's like taking a lot of the great things that we have today and maybe improving upon those. A lot of people and everyone kind of, this is just a really, a very old discussion around some of the trade-offs that we currently make in today's web around our data, around advertising, around the way a lot of business models are created for monetization. Essentially, they all come down to the manipulation of user data and different tricks and ways to steal people's data and use that essentially to create targeted advertising. Not only does this lead to a lot of times a negative experience. I just saw a tweet yesterday that resonated a lot with me that said, "YouTube is no longer a video platform, it's now an ad platform with videos in between." And that's the way I feel about YouTube. My kids ...Jeremy: Totally.Nader: ... I have kids that use YouTube and it's interesting to watch them because they know exactly what to do when the ads come up and exactly how to time it because they're used to, ads are just part of their experience. That's just what they're used to. And it's not just YouTube, it's every site that's out there, that's a social site, Instagram, LinkedIn. I think that that's not the original vision that people had, right, for the web. I don't think this was part of it. There have been a lot of people proposing solutions, but the core fundamental problem is how these applications are engineered, but also how the applications are paid for. How do these companies pay for developers to build. It's a really complex problem that, the simplest solution is just sell ads or maybe create something like a developer platform where you're charging a weekly or monthly or yearly or something like that.I would say a lot of the ideas around Web3 are aiming to solve this exact problem. In order to do that you have to rethink how we build applications. You have to rethink how we store data. You have to rethink about how we think about identity as well, because again, how do you build an application that deals with user data without making it public in some way? Right? How do we deal with that? A lot of those problems are the things that people are thinking about and building ways to address those in this decentralized Web3 world. It became really fascinating to me when I started looking into it because I'm very passionate about what I'm doing. I really enjoy being a developer and going out and helping other people, but I always felt there was something missing because I'm sitting here and I love AWS still.In fact, I would 100% go back and work there or any of these big companies, right? Because you can't really look at a company as, in my opinion, a black or white, good or bad thing, there's companies are doing good things and bad things at the same time. For instance, at AWS, I would meet a developer, teach them something at a workshop, a year later they would contact me and be like, hey, I got my first job or I created a business, or I landed my first client. So you're actually helping improve people's lives, at the same time you're reading these articles about Amazon in the news with some of the negative stuff going on. The way that I look at it is, I can't sit there and say any company is good or bad, but I felt a lot of the applications that people were building were also, at the end goal when you hear some of these VC discussions or people raising money, a lot of the end goal for some of the people I was working with were just selling advertising.And I'm like, is this really what we're here to do? It doesn't feel fulfilling anymore when you start seeing that over and over and over. I think the really thing that fascinated me was that people are actually building applications that are monetized in a different way. And then I started diving into the infrastructure that enabled this and realized that there was a lot of similarities between serverless and how developers would deploy and build applications in this way. And it was the entry point to my rabbit hole.Jeremy: I talked to you about this and I've been reading some of the stuff that you've been putting out and trying to educate myself on some of this. It seems very much so that show Silicon Valley on HBO, right? This decentralized web and things like that, but there's kind of, and totally correct me if I'm wrong here, but I feel there's two sides of this. You've got one side that is the blockchain, that I think some people are familiar with in the, I guess in the context of cryptocurrency, right? This is a very popular use of the blockchain because you have that redundancy and you have the agreement amongst multiple places, it's decentralized. And so you have that security there around that. But there's other uses for the blockchain as well.Especially things like banking and real estate and some of those other use cases that I'd like to talk about. And then there's another side of it that is this decentralized piece. Is the decentralized piece of it like building apps? How is that related to the blockchain or are those two separate things?Nader: Yeah, absolutely. I'm a big fan of Silicon Valley. Working in tech, it's almost like every single episode resonates with you if you've been in here long enough because you've been in one of those situations. The blockchain is part of the discussion. Crypto is part of the discussion, and those things never really interested me, to be honest. I was a speculator in crypto from 2015 until now. It's been fun, but I never really looked at crypto in any other way other than that. Blockchain had a really negative, I would say, association in my mind for a long time, I just never really saw any good things that people were doing with it. I just didn't do any research, maybe didn't understand what was going on.When I started diving into it originally what really got me interested is the Graph protocol, which is one of the things that we work on at Edge & Node. I started actually understanding, why does this thing exist? Why is it there? That led me to understanding why it was there and the fact that 90% of dApps, decentralized apps in the Ethereum ecosystem are using it. And billions of queries, companies with billions of dollars in transactions are all using this stuff. I'm like, okay, this whole world exists, but why does it exist? I guess to give you an example, I guess we can talk about the Graph protocol. And there are a lot of other web, I would say Web3 or decentralized infrastructure protocols that are out there that are similar, but they all are doing similar things in the sense of how they're actually built and how they allow participation and stuff like that.When you think of something like AWS, you think of, AWS has all of these different services. I want to build an app, I need storage. I need some type of authentication layer, maybe with Cognito, and then maybe I need someplace to execute some business logic. So maybe I'll spin up some serverless functions or create an EC2 instance, whatever. You have all these building blocks. Essentially what a lot of these decentralized protocols like the Graph are doing, are building out the same types of web infrastructure, but doing so in a decentralized way. Why does that even matter? Why is that important? Well, for instance, when you live, let's say for example in another country, I don't know, in South America and outside the United States, or even in the United States in the future, you never know. Let's say that you have some application and you've said something rude about maybe the president or something like that.Let's say that for whatever reason, somebody hacks the server that you're dealing with or whatever, at the end of the day, there is a single point of failure, right? You have your data that's controlled by the cloud provider or the government can come in and they can have control over that. The idea around some of, pretty much all of the decentralized protocols is that they are built and distributed in a way that there is no single point of failure, but there's also no single point of control. That's important when you're living in areas that have to even worry about stuff like that. So maybe we don't have to worry about that as much here, but in other countries, they might.Building something like a server is not a big deal, right? With AWS, but how would you build a server and make it available for anyone in the world to basically deploy and do so in a decentralized way? I think that's the problem that a lot of these protocols are trying to solve. For the Graph in particular, if you want to build an application using data that's stored on a blockchain. There's a lot of applications out there that are basically using the blockchain for mainly, right now it's for financial, transactional reasons because a lot of the transactions actually cost a lot of money. For instance, Uniswap is one of these applications. If you want to basically query data from a blockchain, it's not as easy as querying data from a traditional server or database.For us we are used to using something like DynamoDB, or some type of SQL database, that's very optimized for queries. But on the blockchain, you're basically having these blocks that add up every time. You create a transaction, you save it. And then someone comes behind them and they save another transaction. Over time you build up this data that's aggregated over time. But let's say you want to hit that database with the, quote-unquote, database with a query and you want to retrieve data over time, or you want to have some type of filtering mechanism. You can't do that. You can't just query blockchains the way you can from a regular database. Similar to how a database basically indexes data and stores it and makes it efficient for retrieval, the Graph protocol basically does that, but for blockchain data.Anyone that wants to build an application, one of these decentralized apps on top of blockchain data has a couple of options. They can either build their own indexing server and deploy it to somewhere like AWS. That takes away the whole idea of decentralization because then you have a single point of failure again. You can query data directly from the blockchain, from your client application, which takes a very long time. Both of those are not, I would say the most optimal way to build. But also if you're building your own indexing server, every time you want to come up with a new idea also, you have to think about the resources and time that go into it. Basically, I want to come up with a new idea and test it out, I have to basically build a server index, all this data, create APIs around it. It's time-intensive.What the Graph protocol allows you to do is, as a developer you can basically define a subgraph using YAML, similar to something like cloud formation or a very condensed version of that maybe more Serverless Framework where you're defining, I want to query data from this data source, and I want to save these entities and you deploy that to the network. And that subgraph will basically then go and look into that blockchain. And will look for all the transactions that have happened, and it will go ahead and save those and make those available for public retrieval. And also, again, one of the things that you might think of is, all of this data is public. All of the data that's on the blockchain is public.Jeremy: Right. Right. All right. Let me see if I could repeat what you said and you tell me if I'm right about this. Because this was one of those things where blockchain ... you're right. To me, it had a negative connotation. Why would you use the blockchain, unless you were building your own cryptocurrency? Right. That just seemed like that's what it was for. Then when AWS comes out with QLDB or they announced that or whatever it was. I'm like, okay, so this is interesting, but why would you use it, again, unless you're building your own cryptocurrency or something because that's the only thing I could think of you would use the blockchain for.But as you said, with these blockchains now, you have highly sensitive transactions that can be public, but a real estate transaction, for example, is something really interesting, where like, we still live in a world where if Bank of America or one of these other giant banks, JPMorgan Chase or something like that gets hacked, they could wipe out financial data. Right? And I know that's backed up in multiple regions and so forth, but this is the thing where if you're doing some transaction, that you want to make sure that transaction lives forever and isn't manipulated, then the blockchain is a good place to do that. But like you said, it's expensive to write there. But it's even harder to read off the blockchain because it's that ledger, right? It's just information coming in and coming in.So event storming or if you were doing event sourcing or something that, it's that idea. The idea with these indexers are these basically separate apps that run, and again, I'm assuming that these protocols, their software, and things that you don't have to build this yourself, essentially you can just deploy these things. Right? But this will read off of the blockchain and do that aggregation for you and then make that. Basically, it caches the blockchain. Right? And makes that available to you. And that you could deploy that to multiple indexers if you wanted to. Right? And then you would have access to that data across multiple providers.Nader: Right. No single point of failure. That's exactly right. You basically deploy a very concise configuration file that defines how you want your data stored and made available. And then it goes, and it just starts at the very beginning and it queries all those blocks or reads all those blocks, saves the data in a database, and then it keeps up with additional new updates. If someone writes a new transaction after that, it also saves that and makes it available for efficient retrieval. This is just for blockchain data. This is the data layer for, but it's not just a blockchain data in the future. You can also query from IPFS, which is a file storage layer, somewhat S3. You can query from other chains other than Ethereum, which is kind of like the main chamber.In the future really what we're hoping to have is a complete API on top of all public data. Anybody that wants to have some data set available can basically deploy a subgraph and index it and then anyone can then essentially query for it. It's like when you think of public data, we're not really used to thinking of data in this way. And also I think a good thing to talk about in a moment is the types of apps that you can build because you wouldn't want to store private messages on a blockchain or something like that. Right? The types of apps that people are building right now at least are not 100% in line with everything. You can't do everything I would say right now in Web3 that you can do in Web2.There are only certain types of applications, but those applications that are successful seem to be wildly successful and have a lot of people interested in them and using them. That's the general idea, is like you have this way to basically deploy APIs and the technology that we use to query is GraphQL. That was one of the reasons that I became interested as well. Right now the main data sources are blockchains like Ethereum, but in the future, we would like to make that available to other data sources as well.Jeremy: Right. You mentioned earlier too because there are apps obviously being built on this that you said are successful. And the problem though, I think right now, because I remember I speculated a little bit with Bitcoin and I bought a whole bunch of Ripple, so I'm still hanging on to it. Ripple XPR whatever, let's go. Anyways, but it was expensive to make a transaction. Right? Reading off of the blockchain itself, I think just connecting generally doesn't cost money, but if you're, and I know there's some costs with indexers and that's how that works. But in terms of the real cost, it's writing to the blockchain. I remember moving some Bitcoin at one point, I think cost me $30 to make one transaction, to move something like that.I can see if you're writing a $300,000 real estate transaction, or maybe some really large wire transfer or something that you want to record, something that makes sense where you could charge a fee of $30 or $40 in order to do that. I can't see you doing that for ... certainly not for web streaming or click tracking or something like that. That wouldn't make sense. But even for smaller things there might be writing more to it, $30 or whatever that would be ... seems quite expensive. What's the hope around that?Nader: That was one of the biggest challenges and that was one of the reasons that when I first, I would say maybe even considered this as a technology back in the day, that I would be considering as something that would possibly be usable for the types of applications I'm used to seeing. It just was like a no-brainer, like, no. I think right now, and that's one of the things that attracted me right now to some of the things that are happening, is a lot of those solutions are finally coming to fruition for fixing those sorts of things. There's two things that are happening right now that solve that problem. One of them is, they are merging in a couple of updates to the base layer, layer one, which would be considered something like Ethereum or Bitcoin. But Ethereum is the main one that a lot of the financial stuff that I see is happening.Basically, there are two different updates that are happening, I think the main one that will make this fee transactional price go down a little bit is sharding. Sharding is basically going to increase the number of, I believe nodes that are basically able to process the transactions by some number. Basically, that will reduce the cost somewhat, but I don't think it's ever going to get it down to a usable level. Instead what the solutions seem to be right now and one of the solutions that seems to actually be working, people are using it in production really recently, this really just started happening in the last couple of months, is these layer 2 solutions. There are a couple of different layer 2 solutions that are basically layers that run on top of the layer one, which would be something like Ethereum.And they treat Ethereum as the settlement layer. It's almost like when you interact with the bank and you're running your debit card. You're probably not talking to the bank directly and they are doing that. Instead, you have something like Visa who has this layer 2 on top of the banks that are managing thousands of transactions per second. And then they take all of those transactions and they settle those in an underlying layer. There's a couple different layer 2s that seem to be really working well right now in the Ethereum ecosystem. One of those is Arbitrum and then the other is I think Matic, but I think they have a different name now. Both of those seem to be working and they bring the cost of a transaction down to a fraction of a penny.You have, instead of paying $20 or $30 for a transaction, you're now paying almost nothing. But now that's still not cheap enough to probably treat a blockchain as a traditional database, a high throughput database, but it does open the door for a lot of other types of applications. The applications that you see building on layer one where the transactions really are $5 to $20 or $30 or typically higher value transactions. Things like governance, things like financial transactions, you've heard of NFTs. And that might make sense because if someone's going to spend a thousand bucks or 500 bucks, whatever ...Jeremy: NFTs don't make sense to me.Nader: They're not my thing either, the way they're being, I would say, talked about today especially, but I think in the future, the idea behind NFTs is interesting, but yeah, I'm in the same boat as you. But still to those people, if you're paying a thousand dollars for something then that 5 or 10 or 20 bucks might make sense, but it's not going to make sense if I just want to go to an e-commerce store and pay $5 for something. Right? I think that these layer 2s are starting to unlock those potential opportunities where people can start building these true financial applications that allow these transactions to happen at the same cost or actually a lot cheaper maybe than what you're paying for a credit card transaction, or even what those vendors, right? If you're running a store, you're paying percentages to those companies.The idea around decentralization comes back to this discussion of getting rid of the middleman, and a lot of times that means getting rid of the inefficiencies. If you can offload this business logic to some type of computer, then you've basically abstracted away a lot of inefficiencies. How many billions of dollars are spent every year by banks flying their people around the world and private jets and these skyscrapers and stuff. Now, where does that money come from? It comes from the consumer and them basically taking fees. They're taking money here and there. Right? That's the idea behind technology in general. They're like whenever something new and groundbreaking comes in, it's often unforeseen, but then you look back five years later and you're like, this is a no-brainer. Right?For instance Blockbuster and Netflix, there's a million of them. I don't have to go into that. I feel this is what that is for maybe the financial institutions and how we think about finance, especially in a global world. I think this was maybe even accelerated by COVID and stuff. If you want to build an application today, imagine limiting yourself to developers in your city. Unless you're maybe in San Francisco or New York, where that might still work. If I'm here in Mississippi and I want to build an application, I'm not going to just look for developers in a 30-mile radius. That is just insane. And I don't use that word mildly, it's just wild to think about that. You wouldn't do that.Instead, you want to look in your nation, but really you might want to look around the world because you now have things like Slack and Discord and all these asynchronous ways of doing work. And you might be able to find the best developer in the world for 25% or 50% of what you would typically find locally and an easy way to pay them might just be to just send them some crypto. Right? You don't have to go find out all their banking information and do all the wiring and all this other stuff. You just open your wallet, you send them the money and that's it. It's a done deal. But that's just one thing to think about. To me when I think about building apps in Web2 versus Web3, I don't think you're going to see the Facebook or Instagram use case anytime in the next year or two. I think the killer app for right now, it's going to be financial and e-commerce stuff.But I do think in maybe five years you will see someone crack that application for, something like a social media app where we're basically building something that we use today, but maybe in a better way. And that will be done using some off-chain storage solution. You're not going to be writing all these transactions again to a blockchain. You're going to have maybe a protocol like Graph that allows you to have a distributed database that is managed by one of these networks that you can write to. I think the ideas that we're talking about now are the things that really excite me anyway.Jeremy: Let's go back to GraphQL for a second, though. If you were going to build an app on top of this, and again, that's super exciting getting those transaction fees down, because I do feel every time you try to move money between banks or it's the $3 fee, if you go to a foreign ATM and you take money out of an ATM, they charge you. Everybody wants to take a cut somewhere along, and there's probably reasons for it, but also corporate jets cost money. So that makes sense as well. But in terms of the GraphQL protocol here, so if I wanted to build an application on top of it, and maybe my application doesn't write to the blockchain, it just reads from it, with one of these indexers, because maybe I'm summing up some financial transactions or something, or I've got an app we can look things up or whatever, I'm building something.I'm querying using the GraphQL, this makes sense. I have to use one of these indexers that's aggregating that data for me. But what if I did want to write to the blockchain, can I use GraphQL to do a mutation and actually write something to the blockchain? Or do I have to write to it directly?Nader: Yeah, that's actually a really, really good question. And that's one of the things that we are currently working on with the Graph. Right now if you want to write a transaction, you typically are going to be using one of these JSON RPC wallets and using some type of client library that interacts with the wallet and signs the transaction with the private key. And then that sends the transaction to the blockchain directly. And you're talking to the blockchain and you're just using something like the Graph to query. But I think what would be ideal and what we think would be ideal, is if someone could use a single technology, a single language, and a single abstraction to do everything, not only with reading and writing but also with subscriptions for real-time updates.That's where we think the whole idea for this will ultimately be, and that's what we're working on now. Right now you can only query. And if you want to write a transaction, you basically are still going to be using something like ethers.js or Web3 or one of these other libraries that allows you to sign a transaction using your wallet. But in the future and in fact, we're already building this right now as having an end-to-end GraphQL library that allows you to write transactions as well as read. That way someone just learns a single API and it's a lot easier. It would also make it easier for developers that are coming from a traditional web background to come in because there's a little bit of learning curve for understanding how to create one of these signed providers and write the transaction. It's not that much code, but it is a new way of thinking about things.Jeremy: Well I think both of us coming from the serverless space, we know that new way of thinking about things certainly can throw a wrench in the system when a new developer is trying to pick that stuff up.Nader: Yeah.Jeremy: All right. So that's the blockchain side of things with the data piece of it. I think people could wrap their head around that. I think it makes a lot of sense. But I'm still, the decentralized, the other things that you talked about. You mentioned an S3, something that's sort of an S3 type protocol that you can use. And what are some of the other ones? I think I've written some of them down here. Acash was one, Filecoin, Livepeer. These are all different protocols or services that are hosted by the indexers, or is this a different thing than the indexers? How does that work? And then how would you use that to save data, maybe save some blob, a blob storage or something like that?Nader: Let's talk about the tokenomics idea around how crypto fits into this and how it actually powers a protocol like this. And then we'll talk about some of those other protocols. How do people actually build all this stuff and do it for, are they getting paid for it? Is it free? How does that work and how does this network actually stay up? Because everything costs money, developers' time costs money, and so on and so forth. For something like the Graph, basically during the building phase of this protocol, basically, there was white papers and there was blog posts, and there was people in Discords talking about the ideas that were here. They basically had this idea to build this protocol. And this is a very typical life cycle, I would say.You have someone that comes up with an idea, they document some of it, they start building it. And the people that start building it are going to be basically part of essentially the founding team you could think of, in the sense of they're going to be having equity. Because at the end of the day, to actually launch one of these decentralized protocols, the way that crypto comes into it, there's typically some type of a token offering. The tokens need to be for a network like this, some type of utility token to keep the network running in the future. You're not just going to create some crypto and that's it like, right? I think that's the whole idea that I thought was going on when in reality, these tokens are typically used for powering the protocol.But let's say early on you have let's say 20 developers and they all build 5% of the system, whatever percentage that you want to talk about, whatever. Let's say you have these people helping out and then you actually build the thing and you want to go ahead and launch it and you have something that's working. A lot of times what people will do is they'll basically have a token offering, where they'll basically say, okay, let's go ahead and we're going to mint X number of tokens, and we're going to put these on the market and we're going to also pay these people that helped build this system, X number of tokens, and that's going to be their payment. And then they can go and sell those or keep those or trade those or whatever they would like to do.And then you have the tokens that are then put on the public market essentially. Once you've launched the protocol, you have to have tokens to basically continue to power the protocol and fund it. There are different people that interact with the protocol in different ways. You have the indexers themselves, which are basically software engineers that are deploying whatever infrastructure to something like AWS or GCP. These people are still using these cloud providers or they're maybe doing it at their house, whatever. All you basically need is a server and you want to basically run this indexer node, which is software that is open source, and you run this node. Basically, you can go ahead and say, okay, I want to start being an indexer and I want to be one of the different nodes on the network.To do that you basically buy some GRT, Graph Token, and in our case you stake it, meaning you are putting this money up to basically affirm that you are an indexer on the protocol and you are going to be accepting subgraph developers to deploy their subgraphs to your indexer. You stake that money and then when people use the API, they're basically paying money just like they might pay money to somewhere like API gateway or AppSync. Instead, they're paying money for their subgraph and that money is paid in GRT and it's distributed to the people in the ecosystem. Like me as a developer, I'm deploying the subgraph, and then if I have a million people using it, then I make some money. That's one way to use tokens in the system.Another way is basically to, as an outside person looking in, I can say, this indexer is really, really good. They know what they're doing. They're a very strong engineer. I'm going to basically put some money into their indexer and I'm basically backing them as an indexer. And then I will also share the money that comes in from the query fees. And then there are also people that are subgraph developers, which is the stuff that I've been working with mainly, where I can basically come up with a new API. I can be like, it'd be cool if I took data from this blockchain and this file system and merged it together, and I made this really cool API that people can use to build their apps with. I can deploy that. And basically, people can signal to this subgraph using tokens. And when people do that, they can say that they believe that this is a good subgraph to use.And then when people use that, I can also make money in that way. Basically, people are using tokens to be part of the system itself, but also to use that. If I'm a front end application like Uniswap and I want to basically use the Graph, I can basically say, okay, I'm going to put a thousand dollars in GRT tokens and I'm going to be using this API endpoint, which is a subgraph. And then all of the money that I have put up as someone that's using this, is going to be taken as the people start using it. Let's say I have a million queries and each query is one, 1000th of a cent, then after those million queries are up, I've spent $100 or something like that. Kind of similar to how you might pay AWS, you're now paying, you know, subgraph developers and indexers.Jeremy: Right. Okay. That makes sense. So then that's the payment method of that. So then these other protocols that get built on top of it, the Acash and Filecoin and Livepeer. So those ...Nader: They're all operating in a very similar fashion.Jeremy: Okay. All right. And so it's ...Nader: They have some type of node software that's run and people can basically run this node on some server somewhere and make it available as part of the network. And then they can use the tokens to participate. There's Filecoin for file storage. There's also IPFS, which is actually more of, it's a completely free service, but it's also not something that's as reliable as something like S3 or Filecoin. And then you have, like you mentioned, I believe Acash, which is a way to execute arbitrary code, business logic, and stuff like that. You have Ceramic Network, which is something that you can use for authentication. You have Livepeer which is something you use for live streaming. So you have all these ideas, these decentralized services fitting in these different niches.Jeremy: Right, right. Okay. So then now you've got a bunch of people. Now you mentioned this idea of, you could say, this is a good indexer. What about bad indexers? Right?Nader: That's a really good question.Jeremy: Yeah. You're relying on people to take data off of a public blockchain, and then you're relying on them to process it correctly and give you back good data. I'm assuming they could manipulate that data if they wanted to. I don't know why, but let's say they did. Is there a way to guarantee that you're getting the correct data?Nader: Yeah. That's a whole part of how the system works. There's this whole idea and this whole, really, really deep rabbit hole of crypto-economics and how these protocols are structured to incentivize and also disincentivize. In our protocol, basically, you have this idea of slashing and this is also a fairly known and used thing in the ecosystem and in the space. It's this idea of slashing. Basically, you incentivize people to go out and find people that are serving incorrect data. And if that person finds someone that's serving incorrect data, then the person that's serving the incorrect data is, quote-unquote, slashed. And that basically means that they're not only not going to receive the money from the queries that they were serving, but they also might lose the money that they put up to be a part of the network.I mentioned you have to actually put up money to deploy an indexer to the network, that money could also be at risk. You're very, very, very much so financially disincentivized to do that. And there's actually, again, incentives in the network for people to go and find those people. It's all-around incentives, game theory, and things like that.Jeremy: Which makes a ton of sense. That's good to know. You mentioned, you threw out the number, five years from now, somebody might build the killer app or whatever, they'll figure out some of these things. Where are we with this though? Because this sounds really early, right? There's still things that need to be figured out. Again, it's public data on the blockchain. How do you see this evolving? When do you think Web3 will be more accessible to the masses?Nader: Today people are actually building really, really interesting applications that are fitting the current technology stack, what are the things that you can build? People are already building those. But when you think about the current state of the web, where you have something like Twitter, or Facebook or Instagram, where I would say, especially maybe something like Facebook, that's extremely, extremely complex with a lot of UI interaction, a lot of private data, messages and stuff. I think to build something like that, yeah, it's going to be a couple of years. And then you might not even see certain types of applications being built. I don't think there is going to be this thing where there is no longer these types of applications. There are only these new types. I think it's more of a new type of application that people are going to be building, and it's not going to be a winner takes all just like in all tech in my opinion.I wouldn't say all but in many areas of tech where you're thinking of something as a zero-sum game where I don't think this is. But I do think that the most interesting stuff is around how Web3 essentially enables native payments and how people are going to use these native payments in interesting ways that maybe we haven't thought of yet. One of the ways that you're starting to see people doing, and a lot of venture capitalists are now investing in a lot of these companies, if you look at a lot of the companies coming out of YC and a lot of the new companies that these traditional venture capitalists are investing in, are a lot of TOMS crypto companies.When you think about the financial incentives, the things that we talked about early on, let's say you want to have the next version of YouTube and you don't want to have ads. How would that even work? Right? You still need to enable payments. But there's a couple of things that could happen there. Well, first of all, if you're building an application in the way that I've talked about, where you basically have these native payments or these native tokens that can be part of the whole process now, instead of waiting 10 years to do an IPO for an application that has been around for those 10 years and then paying back all his investors and all of those people that had been basically pulling money out their pockets to take part in.What if someone that has a really interesting idea and maybe they have a really good track record, they come out with a new application and they're basically saying, okay, if you want to own a piece of this, we're going to basically create a token and you can have ownership in it. You might see people doing these ICO's, initial coin offerings, or whatever, where basically they're offering portions of the company to anyone that wants to own it and then incentivizing people to basically use those, to govern how the application is built in the future. Let's say I own 1% of this company and a proposal is put up to do something new. I can basically say, I can use that portion of my ownership to vote on things. And then people that are speculating can say, this company is doing interesting things. I'm going to buy into it, therefore driving the price up or down.Kind of like the same way that you see the traditional stock market there, but without all of the regulation and friction that comes with that. I think that's interesting and you're already seeing companies doing that. You're not seeing the majority of companies doing that or anything like that, but you are starting to see those types of things happening. And that brings around the discussion of regulations. Is ... can you even do something like that in the United States? Well, maybe, maybe not. Does that mean people are going to start building these companies elsewhere? That's an interesting discussion as well. Right now if you want to build an application this way, you need to have some type of utility that these tokens are there for. You can't just do them purely on speculation, at least right now. But I think it's going to be interesting for sure, to watch.Jeremy: Right. And I think too that, I'm just thinking if you're a bank, right? And you maybe have a bunch of private transactions that you want to keep private. Because again, I don't even know how, I don't know how we get to private transactions on the blockchain. I could see you wanting to have some transactions that were public blockchain and some that were private and maybe a hybrid approach would make sense for some companies.Nader: I think the idea that we haven't really talked about at all is identity and how identity works compared to how we're used to identity. The way that we're used to identity working is, we basically go to a new website and we're like, this looks awesome. Let me try it out. And they're like, oh wait, we need your name, your email address, your phone number, and possibly your credit card and all this other stuff. We do that over and over and over, and over time we've now given our personal information to 500 people. And then you start getting these emails, your data has been breached, every week you get one of these emails, if you're someone like me, I don't know. Maybe I'm just signing up for too much stuff. Maybe not every week, but maybe every month or two. But you're giving out your personal data.But we're used to identity as being tied to our own physical name and address and things like that. But what if identity was something that was more abstract? And I think that that's the way that you typically see identity managed in Web3. When you're dealing with authentication mechanisms, one of the most interesting things that I think that is part of this whole discussion is this idea of a single sign-on mechanism, that you own your identity and you can transfer it across all the applications and no one else is in control of it. When you use something like an Ethereum wallet, like MetaMask, for example, it's an extension you can just download and put crypto in and basically make payments on the web with. When you create a wallet, you're given a wallet address. And the wallet address is basically created using public key cryptography, where basically you start with this private key, your public key is derived from the private key, and then your address is dropped from the public key.And when you send a transaction, you basically sign the transaction with your private key and you send your public key along with the transaction, and the person that receives that can decode the transaction with the public key to verify that that's who signed the transaction. Using this public key cryptography that only you can basically sign with your own address and your own password, it's all stored on the blockchain or in some decentralized manner. Actually in this case stored on the blockchain or it depends on how you use it really, I guess. But anyway, the whole idea here is that you completely own your identity. If you never decide to associate that identity with your name and your phone number, then who knows who's sending these transactions and who knows what's going on, because why would you need to associate your own name and phone number with all of these types of things, in these situations where you're making payments and stuff like that. Right?What is the idea of a user profile anyway, and why do you actually need it? Well, you might need it on certain applications. You might need it or want it on social network, or maybe not, or you might come up with a pseudonym, because maybe you don't want to associate yourself with whatever. You might want to in other cases, but that's completely up to you and you can have multiple wallet addresses. You might have a public wallet address that you associate your name with that you are using on social media. You might have a private wallet address that you're never associating with your name, that you're using for financial transactions. It's completely up to you, but no one can change that information. One of the applications that I recently built was called Decentralized Identity. I built it and release it a few days ago.And it's an implementation of this and it's using some of these Web3 technologies. One of them is IDX. One of them is Ceramic, which is a decentralized protocol similar to the Graph but for identity. And then it's using something called DIDs, which are decentralized identifiers, which are a way to have a completely unique ID based off of your address. And then you own the control over that. You can basically go in and make updates to that profile. And then any application across the web that you choose to use can then access that information. You're only dealing with it stored in one place. You have full control over it, at any time you can go in and delete that. You can go in and change it. No one has control over it except for you.The idea of identity is a mind-bending thing in this space because I think we're so used to just handing everybody our real names and our real phone numbers and all of our personal information and just having our fingers crossed, that we're just not used to anything else.Jeremy: It's all super interesting. You mentioned earlier about, would it be legal in the United States? I'm thinking of all these recent ransomware attacks and I think they were able to trace back some Bitcoin transaction, they were actually able to trace it back to the individual group that accepted the payment. It opens up a whole can of worms. I love this idea of being anonymous and not being tracked, but then it's also like, what could bad actors do with anonymous financial transactions and things like that? So ...Nader: There kind of has been anonymous transactional layer for a long time. Cash brought in, you can't really do a lot of illegal stuff these days without cash. So should we get rid of cash? I think with any technology ...Jeremy: No, but I mean, there's a limit though, right? You can't withdraw more than $10,000 worth of cash without the FBI being flagged and you can't deposit more, you know what I mean?Nader: You can't take a million dollars worth of Bitcoin that you've gotten from ransomware and turn it into cash either.Jeremy: That's also true. Right.Nader: Because it's all tracked on the blockchain, that's probably how they caught those people. Right? They somehow had their personal information tied to a transaction, because if you follow these transactions long enough, you're going to find some origination point. I agree though. There's definitely trade-offs with everything. I don't think I'm ever the type to argue that. There's good things and there's bad things. I think you have to look at the whole picture and decide for yourself, what you think. I'm the type that's like, let's lay out all of the ideas and let the market decide.Jeremy: Right. Yeah. I totally agree with that. All this stuff is fascinating, there is way too much more for me to learn at this point. I think my brain is filled at this point. Anything else about Edge & Node? Any cool things you're working on there or anything you want people to know?Nader: We're working on a couple of different projects. I can't really talk about some of them because they're not released yet, but we are working on a new version of something called Everest, and Everest is already out. If you want to check it out, it's at everest.link. It's basically a repository of a bunch of different applications that have already been built in the Web3 ecosystem. It also ties in a lot of the stuff that we talked about, like identity and stuff like that. You can basically sign in with your Ethereum wallet. You can basically interact with different applications and stuff, but you can also just see the types of stuff people are building. It's categorized into games, financial apps. If you've listened to this and you're like, this sounds cool, but are people actually building stuff? This is a place to see hundreds of apps that people have are already built and that are out there and successful.Jeremy: Awesome. All right. Well, listen, Nader, this was awesome. Thank you so much for sharing this with me. I know I learned a ton. I hope the listeners learned a ton. If people want to learn more about this or just follow you and keep up with what you're doing, what's the best way to do that?Nader: I would say check out Twitter, we're on Twitter @dabit3 for me, @edgeandnode for Edge & Node, and of course @graphprotocol for Graph protocol.Jeremy: Okay. And then edgeandnode.com. Your YouTube channel is just youtube.com/naderdabit, N-A-D-E-R D-A-B-I-T. And then you had an article on Web3 and I'll put it in the show notes.Nader: Yeah. Put it in the show notes. For freeCodeCamp, it's called what is Web3. And it's really a condensed version of a lot of the stuff we talked about. Maybe go into a little bit more depth around native payments and how people might build companies in the way that we've talked about here.Jeremy: Awesome. All right. Well, I will get all that stuff into the show notes. Thanks again, Nader.Nader: Thanks for having me. It was good to talk.

Dids joined the boys to chat Bucks after his former teammate & coach had his last game at the helm of Collingwood on Monday.

In this episode, Raj Hegde sits down with Dr. Carsten Stöcker, Founder & CEO of Spherity to understand how #decentralized identity is transforming the end-to-end supply chain lifecycle. Tune in to this episode to explore the increasingly important role of provenance in helping build a better world and learn about the intersection of exciting concepts such as non-fungible tokens (NFTs) and decentralized identifiers (DIDs).

In this episode, Raj Hegde sits down with Dr. Carsten Stöcker, Founder & CEO of Spherity to understand how #decentralized identity is transforming the end-to-end supply chain lifecycle. Tune in to this episode to explore the increasingly important role of provenance in helping build a better world and learn about the intersection of exciting concepts such as non-fungible tokens (NFTs) and decentralized identifiers (DIDs).

Transitioning gender has its ups and downs and can impact our mental health and wellbeing. It is the way we conduct ourselves in those times that gives us the experience and confidence to move forward. Trust in yourself, believe in you, and smile because you are fabulous. HOT AIR BALLOON Some days, I feel like a hot air balloon, Some days, I am holding the rope. Some days, I feel like soaring up high, Some days, well, I just don't. On the days when I dream of floating proud, I could fill the world with hope. On the days when I feel tied to the ground, It's all I can do to cope. Days afloat are when I am found, Anxiety and fear elopes. On the days when my fears abound, I cling on, best I can, to slippery slopes. Some days I look to the clouds in the sky, Some days my head just falls, and I cry. Some days I wonder if I really belong, Some days I fear I may not be strong. Some days I feel like yes, yes, yes, Some days I retreat with no. The days when fear outweighs hope, Are days when strong winds blow. It is in those winds that I really know, How well I truly cope. Because its not the fear of holding the rope, The fear is letting go. (c) Jay Rose Ana Woman Volume 2 Photo by Aleksandar Pasaric from Pexels Hot Air Balloon Photo by Dids from Pexels

Finding a Jiminy Cricket to sit on your shoulder. Photo by Dids from Pexels.

A collection of avant-garde experiments in texture. Photo by Dids from Pexels

World Worst and Longest Songs: from the mind of DIDs. #Dissociative Identity Disorder. We love the harp, the mouth harp, the harmonica, bur more we love the feeling and inspiration given to me by Norika. BTW, Wally-Wally song in it's finest at the END History. We hope you enjoy some of Wally-Wally and the Life's Song for no worry. I hope you enjoy the best-my-worst can get. God Bless!

We have a special guest this week, the Chief Executive of Anti-Copying in Design (ACID) - a membership organization that exists to support designers in their design and intellectual property. If you’ve ever been copied, worried about copying someone else or had any questions, they can help!    EPISODE RECAP   Can you start by sharing about yourself and how you got involved in this area? (1:40) What was your background when you started this organization? (3:20) How do I as a jeweller protect my designs? (5:16) In what case would you register a design? (6:42) What counts as copying? (11:03) What is copyright? (12:45) The whole process is a lot easier with a contract (16:22) What is a trademark and do I need one? (17:12) Does this work the same in other countries? Does it protect your designs in other countries? (20:45) If you’re selling at a craft fair, is there any guidance on protecting yourself? (24:15) What do we do if we think our designs have been copied? (28:24) With a commission piece, who owns the design? (34:07) Tell us a bit more about ACID (36:51)   RESOURCES ACID Website ACID Facebook ACID Instagram Dids Macdonald Twitter Jewellery Business Bootcamp     Find Jewellers Academy on Instagram and Facebook! 

Michael Shea is the Managing Director of the Dingle Group and the Chair of Sovrin Foundation’s SSI in IoT Working Group. In this podcast we discussed the white paper he authored on Self Sovereign Identity and IoT. To explain the opportunities SSI can provide to IoT, Michael introduces us to three profiles: Jamie (machine to person), Bob (machine to machine) and Bessie the cow (digital twin).   What is blockchain? Blockchain is a decentralised database, which is cryptographically secured and immutable. The decentralised part means that it operates in a wider ecosystem than traditional ones, that sits within corporate firewalls, which gives it greater resiliency and redundancy. The cryptographic component along with the different proof of work, resolve the double spend problem and bring a level of assurance that transactions have not been modified.   An introduction to Self-Sovereign Identify (SSI), Decentralised Identifiers (DID) and verifiable credentials. Self-sovereign identity is an identity model, where an entity is in control of its own identity and information related to it. SSI as a concept started to take shape in 2016 with Christopher Allen’s 10 principles of self-sovereign identity. In December 2020 the Sovrin Foundation released its 12 principles of self-sovereign identity, which fundamentally is about an entity’s ability to control the information about themselves. Decentralised identifiers (DIDs) is a pointer to the identify information known as a DID document that helps to create the trust layers within SSI. A verifiable credential is a cryptographic bundle that is created by an issuer of a credential such as the DVLA for a driver’s license. That credential includes attributes stating that the driver is legally entitled to drive a vehicle and it may contain other pieces of information such as your address and other details. A cryptographic bundle is signed using the public private key of the issuer in this case the DVLA which is then returned to the holder of the driver’s license. That holder can then use that credential to a verifier to indicate his/her authorisation to drive a vehicle.   Internet of Things (IoT) Machine to Person Machine to person is where a device is interacting with an individual. The machine can be attached or worn by a person and is measuring some aspect of the person's personal or physical environment and transmitting this data directly or indirectly to a connected device. For example, a person with diabetes would have a sensor that is attached to their body reading their glucose level and communicating the data to an app on a smartphone or a separate physical device.   Machine to machine Machine to machine is the communication between an IoT device and a computer, smartphone or device. Using the above analogy, the machine is the device or the smartphone speaking up to a central repository for transmitting that information to an endocrinologist on behalf of the patient.   Digital twins A digital twin is a virtual digital representation of a physical object. That can be a person, an animal, or a thing. The most common use of digital twins is in an industrial setting. For example, a jet engine has hundreds of sensors embedded inside it, streaming data off to the aircraft engine manufacturers and creating a whole digital profile of itself.   Risks associated with IoT On the 21st of October 2016, multiple major DDoS attacks happened which took down numerous high-profile websites such as Netflix, Twitter, GitHub, Airbnb and others. This denial of service attack, known as the Mirai botnet attack, was a result of the Mirai malware installed on a large number of IoT devices. Such attacks illustrated the risks associated with poor security on IoT devices. As the number of IoT devices continue to grow every year, Michael believes that IoT and security is going to continue being very much like oil and water.

You finally hear from the side of people who live with people who are mentally challenge or mentally disabled. It's not any Sunshine and Roses. It' usually never the loved ones but those that have the disability that are the cause of life despair. You here how Norika wanted to give up. Sometimes I think she should have. - Clem

We have the feeling...a reason in the beginning...caught in the vortex in my mind...how can I dance for you...just sign a little tune...I'll tap a story out you see...I'll make myself in the merry way...play upon the world and stage...keeping you entertained without a care...please come down the rabbit hole and join the merry wonder of the river flowing from my soul...illuminating all around and keeping light the life a clown will be in a misery of time...and you can't keep it all you see...the time is fragile on your knee...don't quake the passing bye away...keep a chin up for you can...see a little river and among the scene...drown the worries on the tidal flow...the edge is near and reaching out...it might take a bit to shout..but all you need is love in the kind... You can only turn around three times before you start to realize the path you pick will always be the same...insanity is like a cloth that wrapps you warm and keeps you taunt from life that runs around without a head...and now you have to listen in..this won't be like anything....even I cant see the road beyond the turn....Beyond Our Comprehension.

The Government has been forced into a U-turn on plans to return Leaving Cert students and reopen special schools next week. From Monday all students, including children with special needs will have to rely on remote learning. What do you make of this decision? Clare hears from listeners Photo by Dids from Pexels Listen and subscribe to Lunchtime Live on Apple Podcasts, Google Podcasts and Spotify.      Download, listen and subscribe on the Newstalk App.    You can also listen to Newstalk live on newstalk.com or on Alexa, by adding the Newstalk skill and asking: 'Alexa, play Newstalk'.

In this, the fifth episode of Designed for Life, the podcast brought to you by The Design and Technology Association in partnership with The Edge Foundation, we talk with Dids Macdonald OBE Co-founder and Chief Executive of ACID (Anti-copying in Design). At the time of recording, Dids was also Master of The Furniture Makers Company, the City of London livery company and charity for the furniture industry. We were joined in the conversation by Anne Sampson, who was the outgoing Educational Events and Campaigns Manager. Designers are notoriously bad at protecting their intellectual property, while some are very aware that a good idea is easily stolen and copied, many get so wrapped up in the iterative process of bringing a design from concept to market that they completely ignore or are ignorant of simple actions that they can take to protect their design from being illegally copied. As a young designer herself, Dids was outraged by the audacity shown by some who openly copied and replicated her work and the work of colleagues. Instead of moaning about it, she decided to take action and Co-founded ACID, which has been working for the last 25 years to help to protect design intellectual property. In this episode, Dids talks us through the relatively simple steps that all designers should take to protect their work. We talk through how this could (and perhaps should) be taught as part of a D&T secondary or even primary education (it is taught to all primary aged pupils in China). Dids also takes us behind the scenes at one of the City's newest livery companies. What is a livery company? How does this work with and for the furniture industry, and what can we do within education to encourage more students to consider furniture design as a worthy option? A wide-ranging and engaging conversation that lifts the lid on design theft and how to protect against it. 

In this episode of the Benton Byte, P-Dids is away and we talk to her and her special friend. We discuss the random topics of how Strudel and P-Dids are officially friends, poor life choices, reminiscing on favorite Benton Byte episodes and more. Email us at bentonbytepodcast@gmail.com Strudel's knitting blog: www.serenitybyjen.com

On today's episode we're covering a topic that I know bothers a lot of you - how can you protect your designs from being copied. Dids MacDonald OBE has dedicated the last 20 years of her career in helping designers to protect their design ideas. Discover in this episode: What the myths are around protecting your design ideas. How you can make sure that your design ideas are covered. The difference between registered and unregistered design rights. What a trademark is and why you might need one. What to do if you think someone has copied your designs. If you're interested in finding out more about how ACID can help your business go to acid.uk.com Our trade show: www.makeitbritishlive.com

Hoy tengo de invitado a un gran amigo, con quien fuimos socios en Mondome en 2014.Comenzó su trabajo en el mundo de la tecnología en Altavista, uno de los primeros buscadores en la web allá por la década de los 90s, siendo el 1er webmaster del buscador.Como tecnólogo construyó una de las primeras plataformas de criptomonedas NeuClear, 9 años antes de Bitcoin. Antes de empezar uPort trabajaba llevando Bitcoin a consumidores y negocios en Africa con Kipochi.Estoy hablando de Pelle Braendgaard, co-fundador de uPort y actualmente está trabajando en un proyecto secreto relacionado con la identidad.En la conversación hablamosdel impacto de la "regla de Viaje" de la GAFI en los exchanges de criptomonedas que se viene.Como fué su experiencia como CTO de uPortCuáles son los proyectos gubernamentales en los que se está utilizando uPort.Cómo han evolucionado los estándares de identidad y que están desarrollando actualmente.¿Qué es un DIDs y un Verifiable Credentials?¿Cómo ve la evolución de Ethereum en los últimos años?Los riesgos de MakerDAOOpcionalidad.Su nuevo proyecto con Andres Jungue...y muchas cosas másPuedes conectar con Pelle directamente via Twitter si lo buscas como @pelleb (https://twitter.com/PelleB).Si te gusta este podcast, déjanos tus comentarios en twitter o compártelos a aquellos que les pueda interesar. Recuerda que además puedes ver los videos tutoriales en YouTube y puedes visitarnos en btcenespanol.com o seguirnos en twitter, instagram o facebook como @btcenespanolEspero que la disfrutes!

TelecomsXChange (TCXC) platform enables modern communication providers to buy and sell voice, SMS and virtual numbers (DIDs) securely and transparently using intuitive UI or programmatically using API. What’s new? From today you’ll notice new API endpoints for buyers and sellers and new UI features in TCXC portal, find below brief summary of what’s new. When… Continue reading Release Notes: New APIs, DID Features & More.. The post Release Notes: New APIs, DID Features & More.. appeared first on TelecomsXChange Blog.

Happy New Year! Today we want to discuss ways to prepare yourself and plan ahead for an amazing 2020! --- Support this podcast: https://anchor.fm/didstalk/support

It is that time of year again! With Christmas around the corner we wanted to chat about all of our favorite Christmas past times and memories. Let us know what yours are @DidsTalk on Instagram! --- Support this podcast: https://anchor.fm/didstalk/support

Tis' the Holiday Season and with that comes nothing but ads ads ads. Today we discuss our thoughts on the way media portrays consumerism and the things we can do to make sure we don't fall victim to spending all this money on things we will just end up throwing out next month. --- Support this podcast: https://anchor.fm/didstalk/support

We finally did it. We tied the knot after almost 5 years of being a long distance couple. We have learned so much about each other having been long distance and we have met so many other couples along the way, some who have succeeded, some who have not. Distance is such a difficult thing to maneuver in a relationship and we want to take today to discuss our experience and what helped us through! --- Support this podcast: https://anchor.fm/didstalk/support

If you may or may not know, we are a long distance couple. Karen was from Canada and moved to the USA where I (Eric) was. Today we want to have a little fun and quiz each other on each others countries, as well as discuss our favorite things about each country and how they are alike and different in many ways! --- Support this podcast: https://anchor.fm/didstalk/support

We have always been advocates for mental health and wellness, and we also feel it can be a difficult thing to discuss in the workplace. In this episode we dive into how we can help anyone, within the workplace or out, and what we can do within the workplace as either an employee or employer to help those who may be in need. Hotlines that can help: National Suicide Prevention Lifeline- 1-800-273-TALK (8255) Substance Abuse and Mental Health Services Administration - 1-800-662-HELP (4357) --- Support this podcast: https://anchor.fm/didstalk/support

There has been much anticipation for the release of Death Stranding and for good reason. The game is a hit! What we really discovered while playing the game is just how much effort was put into the little details. There is seemingly a game within a game and today we discuss our thoughts on Death Stranding itself and how it can influence the future of video games as a whole! --- Support this podcast: https://anchor.fm/didstalk/support

Where to even begin. Microtransactions have taken on many forms during the evolution of video gaming. From DLC, to Loot Boxes we dive into the psychology behind the draw of microtransactions and how they can be utilized by game designers in a positive light! --- Support this podcast: https://anchor.fm/didstalk/support

Welcome to Dids Talk. This show is hosted by Karen 'GamerGirlDelux' and Eric 'DidsLive'. We have been a Long Distance Couple for 5 years and just this summer tied the knot! On this podcast we want to chat about all things gaming, mental health, long-distance relationships, or really anything that comes to our minds. There are going to be many laughs and great insights to come so stay tuned and be sure to subscribe! --- Support this podcast: https://anchor.fm/didstalk/support

In this episode Sam meets Eric Didier, co-founder of Urban Misfit Ventures, photographer and filmmaker. They chat about how he started his business, LinkedIn content creation, streaming on Twitch, his father getting cancer, his fiancee in Canada, going to school for graphic design and film, and negative internet comments.

We cover juicing spiders, turtlenecks, time traveling, the DIDs, and whether Miles would be a jailhouse snitch. Join us as we recap Law & Order SVU season 9 episode 1, "Alternate," with our friend Delaney Harris-Finch!Subscribe today via Apple Podcasts, Google Play, Overcast, or Stitcher.

Background: Knowledge of how CFTR mutations other than F508del translate into the basic defect in cystic fibrosis (CF) is scarce due to the low incidence of homozygous index cases.Methods: 17 individuals who are homozygous for deletions, missense, stop or splice site mutations in the CFTR gene were investigated for clinical symptoms of CF and assessed in CFTR function by sweat test, nasal potential difference and intestinal current measurement.Results: CFTR activity in sweat gland, upper airways and distal intestine was normal for homozygous carriers of G314E or L997F and in the range of F508del homozygotes for homozygous carriers of E92K, W1098L, R553X, R1162X, CFTRdele2(ins186) or CFTRdele2,3(21 kb). Homozygotes for M1101K, 1898+3 A-G or 3849+10 kb C-T were not consistent CF or non-CF in the three bioassays. 14 individuals exhibited some chloride conductance in the airways and/or in the intestine which was identified by the differential response to cAMP and DIDS as being caused by CFTR or at least two other chloride conductances.Discussion: CFTR mutations may lead to unusual electrophysiological or clinical manifestations. In vivo and ex vivo functional assessment of CFTR function and in-depth clinical examination of the index cases are indicated to classify yet uncharacterised CFTR mutations as either disease-causing lesions, risk factors, modifiers or neutral variants.

Double-barrelled ion-sensitive micro-electrodes were used to measure the changes of the intracellular activities of Cl-, K+, and Na+ (aiCl, aiK, aiNa) in neurones of isolated rat sympathetic ganglia during the action of gamma-aminobutyric acid (GABA). The membrane potential of some of the neurones was manually 'voltage clamped' by passing current through the reference barrel of the ion-sensitive micro-electrode. This enabled us to convert the normal depolarizing action of GABA into a hyperpolarization. A GABA-induced membrane depolarization was accompanied by a decrease of aiCl, aiK and no change in aiNa, whereas a GABA-induced membrane hyperpolarization resulted in an increase of aiCl, aiK and also no change in aiNa. GABA did not change the free intracellular Ca2+ concentration, as measured with a Ca2+-sensitive micro-electrode, whereas such an effect was seen during the action of carbachol. pH-sensitive electrodes, on the other hand, revealed a small GABA-induced extracellular acidification. The inward pumping of Cl- following the normal, depolarizing action of GABA required the presence of extracellular K+ as well as Na+, whereas CO2/HCO3--free solutions did not influence the uptake process. Furosemide, but not DIDS, blocked the inward pumping of Cl-. In conclusion, our data show that only changes in intracellular activities of K+ and Cl- are associated with the action of GABA. Furthermore, they indicate that a K+/Cl- co-transport, and not a Cl-/HCO3- counter-transport, may be involved in the homoeostatic mechanism which operates to restore the normal transmembrane Cl- distribution after the action of GABA.