WEBVTT 00:00.000 --> 00:08.640 Thank you very much for letting me speak here. 00:08.640 --> 00:13.040 I know this room is probably, I feel like this room is probably full of many activity 00:13.040 --> 00:20.280 pop oriented persons and I'm very thankful for the opportunity to also talk about the relationships 00:20.280 --> 00:23.080 with other protocols here. 00:23.080 --> 00:24.360 This is going to be a lightning talk. 00:24.360 --> 00:28.960 So I am from Vienna and I am a digital, I consider myself a digital human rights activist 00:29.520 --> 00:35.520 and advocacy for activity pop since 2017. 00:35.520 --> 00:39.760 Who have you ever heard of the term SSI before? 00:39.760 --> 00:41.040 Can I see some hands? 00:41.040 --> 00:42.560 Oh, great, great, great. 00:42.560 --> 00:47.480 Who have you thinks to understand what this core idea is about? 00:47.480 --> 00:49.560 Also, I guess, same. 00:49.560 --> 00:55.640 So maybe I, for the rest of you, I say it's a specific way to build a public key infrastructure. 00:55.640 --> 01:03.400 So you have here, this nice little bit in the technical language also called sometimes 01:03.400 --> 01:09.720 a source of common truth, I will come back to specifics of this later, but actually, yeah, 01:09.720 --> 01:15.640 we're talking about a public key infrastructure to manage identities here. 01:15.640 --> 01:24.360 And now I want to say why I am here speaking to you now, I started this effort to bring 01:24.360 --> 01:30.560 public key infrastructure into federated ecosystems like the activity pop ecosystem or the 01:30.560 --> 01:31.560 Fediverse. 01:31.560 --> 01:37.400 I started this actually seven years ago, when a friend of mine, Makusa Badello explained 01:37.400 --> 01:41.120 me the concept of SSI and I was kind of hooked. 01:41.120 --> 01:45.680 So this is a document that's linked here, we'll prove to you that I wrote this with colleagues 01:45.680 --> 01:52.600 in 2019 and submitted it to the first activity pop conference in Prague, 2019. 01:52.600 --> 01:58.880 And sort of the simple suggestion was, hey, we can just add some DIDs here in the actor profile 01:58.880 --> 02:03.840 and just see where this leads us, you know, it maybe it has some benefits for the future. 02:03.840 --> 02:10.800 So what would that offer, that would offer simple ways to verify, make persistence really 02:10.800 --> 02:17.880 long-term persistence of identifying kind of add another dimension to it, clear away some mobility 02:17.880 --> 02:18.880 problems. 02:18.880 --> 02:25.560 For example, if the original instance goes down, you still have a hope of retaining all your 02:25.560 --> 02:31.200 connections and it also helps global discoverability if you want to do that. 02:31.200 --> 02:39.320 So as I said, I was there in 2019 and here you see Christine, here is in Manosporny who 02:39.320 --> 02:45.000 is kind of a chasing LD person, so many W3C people were in the room, I was suggesting this 02:45.000 --> 02:50.480 there and the feeling in the room was, are we still kind of think if you really care about 02:50.480 --> 02:54.760 your identity so much, you just should run your own instance, right? 02:54.760 --> 02:56.600 Then you're safe and good to go. 02:56.600 --> 03:03.120 But also another feeling in the room was okay, but who does not really care about his or her 03:03.120 --> 03:04.120 identity, right? 03:04.120 --> 03:08.560 So there is some, there was some earking feeling at the hands that you show here was 03:08.560 --> 03:14.720 a vote in the room like a room reading of who wants to be open to that thinking that we 03:14.720 --> 03:17.800 could incorporate public keys there. 03:17.800 --> 03:24.720 So first forward, I'm going to skip a little now, so this is around 2020, I saw that Cheg 03:24.720 --> 03:29.440 Grabber did a kind of ecosystem report where she brought these things together, federated 03:29.440 --> 03:36.040 systems and maybe some public key infrastructure that is based on DID's decentralized 03:36.040 --> 03:38.160 identity files. 03:38.160 --> 03:44.040 So now I come to the, what is, for my understanding, really the nice thing of this DID system 03:44.040 --> 03:48.360 and I'm now referencing specifically DID, the PLC, which is the system that's adopted 03:48.360 --> 03:51.440 by ADPoto people. 03:51.440 --> 03:56.600 And I think the crucial thing here is that you create your own account on your own machine 03:56.600 --> 04:02.280 and you just upload the file to this common source of truth. 04:02.280 --> 04:08.600 There is nobody who can really deny that other than the server that says, I deny any kind 04:08.600 --> 04:13.520 of new updates to everyone. 04:13.520 --> 04:19.640 So as I said, you construct this thing on your own machine, sign it and just post it, 04:19.640 --> 04:24.320 and if the server does not accept it, there are ways to prove that the server misbehaves 04:24.320 --> 04:25.320 here. 04:25.320 --> 04:30.320 So what I'm trying to tell you right now is that the only thing that's left to figure 04:30.320 --> 04:33.600 out, the only thing that's left is to figure out is that find a governance model for 04:33.600 --> 04:35.760 this common source of truth. 04:35.760 --> 04:39.880 Yeah, you say the only, it's a big problem. 04:39.920 --> 04:44.680 But the blue sky project actually wants to get rid of this problem as soon as possible. 04:44.680 --> 04:52.600 My feeling is that you want to be sure that this is not in U.S. jurisdiction soon. 04:52.600 --> 04:59.320 So Antioh also saying if this identity server remains to be a stable infrastructure, 04:59.320 --> 05:06.120 it could be beneficial for all the other open projects like our projects here, the Fediverse, 05:06.360 --> 05:12.200 and I'm not the only one saying that this is a quote from really yesterday from Ryan, 05:12.200 --> 05:17.880 from Richard Fed, he says yes, it's a really good way to just start, for example, 05:17.880 --> 05:23.080 having the DAD in the act of profile reference as also known as. 05:23.080 --> 05:27.360 So I think there's a kind of content to be like, well, I'm now trying to, how much time 05:27.360 --> 05:29.360 do I have left? 05:29.440 --> 05:38.560 Okay, what I'm trying to give you now, I think, so this is a community that I've participated 05:38.560 --> 05:44.880 over many years, it was about wireless mesh routing protocols, and there was a big fight 05:44.880 --> 05:50.880 around 2009, which of these protocols is the best, and what we did, we came together like real 05:50.880 --> 05:54.960 people had real differences about, it should be a proactive, no, it should be a reactive one, 05:54.960 --> 05:59.120 and what we did is we established a kind of a movement where we every year meet and do 05:59.600 --> 06:05.760 like a summit to figure out answers in which context is which protocol better, and this is 06:05.760 --> 06:11.280 called the battle mesh movement, I remember of it, they even write scientific reports at the end 06:11.280 --> 06:17.280 of the summit, it's really great. So I think we should do the same here, we should put together 06:17.280 --> 06:22.800 people who are in the DNS based ID word, like activity pop currently is, and other people who are 06:22.800 --> 06:31.840 in a sort of maybe non DNS I call it right now, and I think we can do that if we have, 06:31.840 --> 06:35.920 if we can agree on certain correlations, because then it becomes a coherent research program, 06:37.120 --> 06:40.880 and I think that's my proposal here, maybe we could start with these, like, 06:40.880 --> 06:45.120 we know that community should be in control, I think that's the original story of activity pop, 06:45.840 --> 06:50.400 and I think nobody actually wants to lock people in anywhere, right? That's also one thing, 06:50.480 --> 06:53.840 and this third one is pretty important to my understanding, because it says, 06:54.800 --> 07:00.800 every marketplace, every sort of kind of open space we want to have has a cost attached to it, 07:01.520 --> 07:06.880 there is no free one, if a person says we have to construct this free one, please show them the door, 07:06.880 --> 07:11.440 it's not working, it's an incoherent concept, this is very important, in my understanding. 07:11.440 --> 07:16.560 So, and this is the last one I have, this is a battle of how to quote kind of love this picture, 07:16.560 --> 07:22.000 because it says, yeah, forget about this post truth bullshit, truth is still there, 07:22.000 --> 07:26.240 and love will also never go away, we need to keep talking, that's the point of this picture, 07:26.240 --> 07:32.400 we need to keep talking, we know there is an emotion like, yeah, but we need to keep talking. 07:32.400 --> 07:40.960 So, thank you for your attention, questions, maybe one minute. 07:40.960 --> 07:48.800 Again, we have about one minute for one question, which is the first one I've seen up here, so. 07:51.360 --> 07:56.720 Have you considered did carry, which I understand to be did PLC, but older, 07:57.680 --> 08:01.040 more complicated, more full-featured, and without a network dependency? 08:01.040 --> 08:05.360 I'm a love carry, yeah, there's a carry conference coming up, I've heard. 08:06.160 --> 08:09.920 So, it's, they are very similar, they should learn from each other, adopt each other, 08:09.920 --> 08:16.880 strategies, yeah, a love carry, shout out to the carry people here, and also shout out to Amy Guy, 08:16.880 --> 08:27.120 who is a, I'm here because I read her PhD, and I'm, yeah, so, thank you very much, Paul, thank you, 08:27.120 --> 08:35.840 thank you, it's one of the great things about post damage, we get lots of 08:35.840 --> 08:42.640 crossover between topic areas, and that's really exciting for evolution, I think.