WEBVTT 00:00.000 --> 00:13.000 So, the next topic we will talk about, because we are going to talk about post-Company, 00:13.000 --> 00:14.000 post-Company. 00:14.000 --> 00:17.000 And it is going to be presented by service. 00:17.000 --> 00:18.000 Okay. 00:18.000 --> 00:19.000 Well, thank you. 00:19.000 --> 00:20.000 Thanks for coming. 00:20.000 --> 00:22.000 Thanks for this opportunity. 00:22.000 --> 00:28.000 To give you a talk about post-Company, with the group all using after. 00:28.000 --> 00:33.000 Who knows what the abbreviation post stands for? 00:33.000 --> 00:35.000 Not everyone. 00:35.000 --> 00:40.000 So, that's basically an abbreviation for a publish, one syndicate, everything. 00:40.000 --> 00:46.000 And what that basically means is that when you have a piece of content like a blog article, 00:46.000 --> 00:52.000 you can publish it to other places, to other platforms, or to other, 00:52.000 --> 00:56.000 you can distribute your blog article in an easy way. 00:56.000 --> 01:01.000 Back in the days, when I was still a little bit younger, 01:01.000 --> 01:08.000 that was very easy with all the open APIs we had with Twitter and Facebook, etc. 01:08.000 --> 01:16.000 And today, I used this strategy still, but with the Ripple. 01:16.000 --> 01:20.000 I'm a Ripple developer, so I know how Ripple works. 01:20.000 --> 01:26.000 And I am using Nostor, and Nostor is a pretty new protocol, 01:26.000 --> 01:31.000 which you can compare to activity pop slash 18-proto, 01:31.000 --> 01:34.000 but we all dig into it later. 01:34.000 --> 01:37.000 I will start with the live demo. 01:37.000 --> 01:41.000 So, I hope that everything works, and it will go smoothly. 01:41.000 --> 01:48.000 And then I will go to some technical details and have some time left for questions. 01:48.000 --> 01:55.000 So, let me show what I am going to do. 01:55.000 --> 02:01.000 So, I have my Drupal website here. 02:01.000 --> 02:03.000 This is live. 02:03.000 --> 02:07.000 This is the website I'm retaining. 02:07.000 --> 02:15.000 So, there is a block session here, which has articles, which you can see. 02:15.000 --> 02:22.000 Most of them are supposed to be different here with Nostor. 02:22.000 --> 02:30.000 I have it already, and it is called Hello from Fullstem. 02:30.000 --> 02:33.000 So, this is the article. 02:33.000 --> 02:39.000 It has an image, it has a title, it has a summary, and it has a content field. 02:39.000 --> 02:44.000 So, this article is being published during my live demo. 02:44.000 --> 02:51.000 What I have built, I have built a Drupal module, which is comparable to any plugin. 02:51.000 --> 02:56.000 Everybody can build modules to extend functionality of Drupal. 02:56.000 --> 03:03.000 And that says, okay, I want to broadcast this long form content with Nostor. 03:03.000 --> 03:10.000 So, I check this, and then I can select one of my configured profiles. 03:10.000 --> 03:15.000 So, I am going to select semantics. 03:15.000 --> 03:17.000 That's basically it. 03:17.000 --> 03:25.000 I need to set it on published, and then I will hit save. 03:25.000 --> 03:30.000 Okay, that one's well, because I have a Drupal message here. 03:30.000 --> 03:39.000 I have a response from a relay that says, okay, one message is successfully broadcasted to one of multiple relays. 03:39.000 --> 03:42.000 I don't get into that later on, and this is the idea. 03:42.000 --> 03:57.000 So, when I go back to the edit mode, then it now is fetching some metadata from the relays. 03:57.000 --> 04:01.000 So, that is taking a bit longer. 04:02.000 --> 04:08.000 Let me show, oh wait, I have lost my mouse, yes. 04:13.000 --> 04:19.000 I am going to show you one of the many Nostor clients we have in the Nostor version. 04:19.000 --> 04:27.000 There is one new event, and that is one event is my blog article, I just published. 04:28.000 --> 04:29.000 So, that is this one. 04:29.000 --> 04:34.000 This image is from last year, of course, then we had a main dog. 04:34.000 --> 04:45.000 And there are other clients too, which we can check. 04:45.000 --> 04:52.000 I have a timeout here, that's not good, always the case with. 04:53.000 --> 04:59.000 So, we have the same content here in the different clients. 04:59.000 --> 05:09.000 For that word, let me see if it works, no, okay, that's it. 05:09.000 --> 05:15.000 Okay, let's enter demo here, because it will take too much time. 05:16.000 --> 05:18.000 Okay, cool, yeah. 05:18.000 --> 05:25.000 Well, I'm sure the content has been published, so you can find it in many Nostor clients now. 05:25.000 --> 05:34.000 So, everybody can read the article, especially all my followers on with Nostor. 05:34.000 --> 05:36.000 Okay. 05:36.000 --> 05:39.000 I need to go back there. 05:39.000 --> 05:43.000 The mirror is not working, so, okay. 05:43.000 --> 05:47.000 Yeah, that's me, group of developer. 05:47.000 --> 05:54.000 I'm also the maintainer of the Nostor PHP library, so I write PHP too. 05:54.000 --> 05:59.000 The live demo you just had is, so, okay. 05:59.000 --> 06:03.000 That was a live demo, and I can say something about Nostor. 06:03.000 --> 06:07.000 Nostor is an abbreviation for notes and other stuff transmitted by relays. 06:07.000 --> 06:09.000 It's a protocol. 06:10.000 --> 06:12.000 Yeah, it's a community driven protocol. 06:12.000 --> 06:18.000 Some guy had an idea, shared this idea, and then other people got involved, 06:18.000 --> 06:22.000 and now we are working with a lot of developers on it. 06:22.000 --> 06:27.000 It's just open, it's permissionless, anyone can use it. 06:27.000 --> 06:31.000 You can do whatever you want with it. 06:31.000 --> 06:37.000 Most of the data that is being published with Nostor is public, 06:37.000 --> 06:45.000 and by default stored on relays, but not every relay is storing it forever. 06:45.000 --> 06:53.000 So relays are just really dumb servers, servers, which are handling all the data, 06:53.000 --> 06:56.000 and do whatever they want. 06:56.000 --> 07:02.000 Yeah, as clients are just requesting the data from relays. 07:03.000 --> 07:09.000 And the data we also, also known as events are self-fireable, 07:09.000 --> 07:14.000 and I will show that in a minute. 07:14.000 --> 07:18.000 So there are basically three core pieces of the protocol. 07:18.000 --> 07:22.000 There are keys, like cryptographical keys. 07:22.000 --> 07:29.000 They contain an input, like a public key, and an insect that's a secret key. 07:29.000 --> 07:34.000 And every data is being signed with the secret key. 07:34.000 --> 07:38.000 So every event has a signature. 07:38.000 --> 07:42.000 Well, and the third one is the relays. 07:42.000 --> 07:49.000 I just said a servers that store and relay events to clients. 07:49.000 --> 07:54.000 And this is an example of an officer event. 07:54.000 --> 07:58.000 It has a unique ID, that's on the top. 07:58.000 --> 08:00.000 It has a kind. 08:00.000 --> 08:04.000 And the kind is a number, and it represents a content type. 08:04.000 --> 08:08.000 And within Nostor, we have a lot of numbers. 08:08.000 --> 08:11.000 So we have a lot of different content types. 08:11.000 --> 08:17.000 So we can broadcast very much content types. 08:17.000 --> 08:19.000 And this is a kind one. 08:19.000 --> 08:27.000 And the blog article I just published, that's a long form content type. 08:27.000 --> 08:28.000 And what does that mean? 08:28.000 --> 08:31.000 The difference between those two is, for example, 08:31.000 --> 08:34.000 we have the content field there as well. 08:34.000 --> 08:39.000 The long form content is a markdown for a content field. 08:39.000 --> 08:46.000 And the kind one is just a simply note, which you can compare to a simple tweet. 08:46.000 --> 08:49.000 We used to share on Twitter. 08:49.000 --> 08:52.000 Now, X, I think. 08:52.000 --> 08:58.000 It also has a created ad, that's some timestamp. 08:58.000 --> 09:06.000 And it has some tags or the metadata, which are saying something about this event. 09:06.000 --> 09:12.000 And let me see, this is a note I published this morning. 09:13.000 --> 09:16.000 It has a hashtag, the T tag, false them. 09:16.000 --> 09:18.000 It has a Q tag. 09:18.000 --> 09:28.000 And that Q tag references to another event, which is a long form article I published. 09:28.000 --> 09:30.000 And it has a relay hint as well. 09:30.000 --> 09:35.000 So that event can be found on that relay, for example. 09:35.000 --> 09:39.000 And the last part is the signature. 09:39.000 --> 09:43.000 So this not so event is self-reviable. 09:43.000 --> 09:48.000 Can verify it by yourself, because it has my signature. 09:48.000 --> 09:52.000 And it also might put key. 09:52.000 --> 09:55.000 But the put key is not there, yeah. 09:55.000 --> 09:58.000 Below the kinds. 09:58.000 --> 10:00.000 And it's also location independent. 10:00.000 --> 10:06.000 So it can exist on multiple relays. 10:06.000 --> 10:14.000 Well, let's see, that event, it shows up in this, on other clients, 10:14.000 --> 10:16.000 what I just showed. 10:16.000 --> 10:21.000 That was the JSON format that event. 10:21.000 --> 10:35.000 And this is the format that event in a client with a nice preview of the quoted references other events. 10:35.000 --> 10:47.000 Okay, let's go back. 10:47.000 --> 10:52.000 And if you want to like, yeah, I want to see more of what is possible with Master. 10:52.000 --> 10:59.000 This basically, one requirement that's for pages of this. 10:59.000 --> 11:01.000 I have multiple editions with me. 11:01.000 --> 11:06.000 And I can read how the protocol works. 11:06.000 --> 11:08.000 This is nips 01. 11:08.000 --> 11:11.000 And there are many other nips. 11:11.000 --> 11:14.000 But those are called most implementation possibilities. 11:14.000 --> 11:16.000 Those are not very quiet. 11:16.000 --> 11:24.000 But you can scan the list of what is possible or what nips are there. 11:24.000 --> 11:31.000 For example, for calendar events, for wiki articles as well. 11:31.000 --> 11:37.000 Because there is a big project building a sort over wiki Wikipedia. 11:37.000 --> 11:42.000 It's called Project Alexandria. 11:42.000 --> 11:44.000 And there are many other nips to do. 11:44.000 --> 11:47.000 There's a list with all the kind numbers. 11:47.000 --> 11:52.000 And there is a list with all the tags somewhere below, like here. 11:53.000 --> 11:58.000 As a developer, you're up to use it in a way you would like. 11:58.000 --> 12:05.000 And if there is not a kind number or there is no content type you would like to use. 12:05.000 --> 12:15.000 Just use your own, use your imagination to work out an event structure that works for you for your project. 12:15.000 --> 12:17.000 And you just send it to the relays. 12:17.000 --> 12:20.000 And they will store it for you. 12:20.000 --> 12:25.000 And then you can use it in other clients for all the projects. 12:25.000 --> 12:30.000 So that's basically the short introduction, the like demo. 12:30.000 --> 12:35.000 So the rest of the time is for some questions. 12:35.000 --> 12:37.000 10 minutes. 12:38.000 --> 12:44.000 So are there any questions? 12:44.000 --> 12:45.000 Yes. 12:45.000 --> 12:52.000 What are the main benefits of using Nostar for finishing your computer? 12:52.000 --> 12:57.000 Why do I use Nostar to publish my content? 12:57.000 --> 13:03.000 Well, because I'm very active using Nostar, it's like a protocol. 13:03.000 --> 13:08.000 So it will be useful for social networking. 13:08.000 --> 13:13.000 I never had such a huge fuller base who paired to any other social platform. 13:13.000 --> 13:17.000 So find just basically what I publish on my website. 13:17.000 --> 13:21.000 I would like to bring it to them, to their own clients. 13:21.000 --> 13:27.000 So they can read my blog post in their own clients instead of to visit my website. 13:27.000 --> 13:29.000 This is the classical problem. 13:29.000 --> 13:32.000 We have with the platforms today. 13:32.000 --> 13:35.000 But those platforms are closing down or all-world gardens. 13:35.000 --> 13:40.000 So it's not easy to publish the content to there. 13:40.000 --> 13:45.000 And let it read to someone who's not on the platform. 13:45.000 --> 13:51.000 So that's the main reason for me. 13:52.000 --> 13:53.000 One question. 13:53.000 --> 13:56.000 I really like that the messages are signed in Nostar. 13:56.000 --> 14:01.000 Because as far as I know, activity book doesn't let you sign your messages. 14:01.000 --> 14:06.000 So we're still in line with server for trusting the content of the message. 14:06.000 --> 14:09.000 But Nostar is very widely used. 14:09.000 --> 14:16.000 And your talk says, well, we created what's published in multiple locations. 14:16.000 --> 14:19.000 Could I also write something independent of I. 14:19.000 --> 14:20.000 Nostar, Nostar. 14:20.000 --> 14:22.000 And push it to both. 14:22.000 --> 14:24.000 Is there a client for that? 14:24.000 --> 14:27.000 Or is there a client which goes from Nostar to Nostar to Nostar or the other way around? 14:27.000 --> 14:28.000 Yeah. 14:28.000 --> 14:37.000 So your question is basically, how can I bridge or broadcast the content from Nostar to the Fediverse, etc? 14:37.000 --> 14:45.000 Well, I know there is a bridge that because I follow a lot of people in the Fediverse through my Nostar client through that bridge. 14:45.000 --> 14:49.000 And it works the other way around too. 14:49.000 --> 14:55.000 But I also know that many Fediverse instances are blocking that bridge. 14:55.000 --> 15:08.000 So, yeah, to me, I don't think that's a good thing, but it is possible to follow each other between those different protocols. 15:08.000 --> 15:10.000 So it is possible. 15:10.000 --> 15:25.000 And the funny thing is, when I repost or quotes some content from the Fediverse, often that shows ups in the notifications feed in Nostar as well, of the odds are there. 15:25.000 --> 15:27.000 And then they boost it again. 15:27.000 --> 15:31.000 And then I see a notification in my Nostar client too that they have done that. 15:31.000 --> 15:37.000 Or they just send a reply and then reply gets bridge to my Nostar client. 15:37.000 --> 15:41.000 And interact with people from the Fediverse through that bridge. 15:41.000 --> 15:43.000 That's really cool. 15:43.000 --> 15:45.000 I think. 15:45.000 --> 15:46.000 Yeah? 15:46.000 --> 15:47.000 Yeah. 15:47.000 --> 15:50.000 You leave the Nostar online to the scale at the same time. 15:50.000 --> 15:55.000 Do you have people or do we need that this evening and switch to another examination? 15:55.000 --> 15:59.000 Another way or to another integration with people? 15:59.000 --> 16:03.000 So I didn't fully understand that question. 16:03.000 --> 16:06.000 It was a scaling question about... 16:06.000 --> 16:07.000 The other way or to the other. 16:07.000 --> 16:08.000 The other way or not. 16:08.000 --> 16:10.000 So you have the integration with Lightning. 16:10.000 --> 16:12.000 I mean the same message. 16:12.000 --> 16:13.000 Right? 16:13.000 --> 16:15.000 To the same event. 16:15.000 --> 16:19.000 And you mean Lightning as Bitcoin Lightning? 16:19.000 --> 16:23.000 Well, Bitcoin Lightning is just used for micro payments. 16:23.000 --> 16:24.000 Yeah. 16:24.000 --> 16:25.000 It's an optional. 16:25.000 --> 16:26.000 It's a nip. 16:26.000 --> 16:30.000 But it has nothing to do with a protocol on itself. 16:31.000 --> 16:33.000 We believe that that's going to be the last implementation. 16:33.000 --> 16:36.000 Or we're going to switch to another type of layer too. 16:36.000 --> 16:37.000 No. 16:37.000 --> 16:39.000 It's... 16:39.000 --> 16:40.000 It's... 16:40.000 --> 16:42.000 It's not... 16:42.000 --> 16:44.000 You don't see a button right here there. 16:44.000 --> 16:48.000 Well, there is no button right there because those are two separate things. 16:48.000 --> 16:53.000 Like the Lightning network has nothing to do with Nostar on itself. 16:53.000 --> 16:55.000 Like Nostar does not need. 16:55.000 --> 16:59.000 It's another requirement of using the Bitcoin Lightning network. 16:59.000 --> 17:04.000 That's basically just used for the micro payments. 17:04.000 --> 17:05.000 Okay. 17:05.000 --> 17:06.000 Yeah. 17:06.000 --> 17:08.000 I think like to follow the question. 17:08.000 --> 17:12.000 Do you see a wide integration of Bitcoin or at least thinking about Bitcoin 17:12.000 --> 17:17.000 at the core of Nostar or to the return or the life of the Nostar like... 17:17.000 --> 17:20.000 Well, you're thinking about it really day. 17:20.000 --> 17:22.000 It's something to pay and you don't care. 17:22.000 --> 17:24.000 It's how it came up. 17:24.000 --> 17:25.000 Well, a good question. 17:25.000 --> 17:28.000 The question is, is like... 17:28.000 --> 17:29.000 Are the... 17:29.000 --> 17:35.000 The Nostar control booth is thinking the same way like the Bitcoin Core developers? 17:35.000 --> 17:39.000 Well, the guy who had this idea is a Bitcoiner. 17:39.000 --> 17:41.000 So, from the start, yes. 17:41.000 --> 17:45.000 And many Bitcoiners are using the protocol. 17:45.000 --> 17:49.000 But yeah, I started to use Bitcoin myself in 2020. 17:49.000 --> 17:54.000 But I was very active in a Fediver's because I liked the social networking stuff. 17:54.000 --> 17:56.000 A lot more than just payments. 17:56.000 --> 17:59.000 And I think Bitcoin is just for payments. 17:59.000 --> 18:02.000 And this is something for something else. 18:02.000 --> 18:07.000 This is for building a new kind of internet web. 18:07.000 --> 18:09.000 In some sense, with the same thing, 18:09.000 --> 18:13.000 the people from the Fediver's and the activity pop are doing. 18:13.000 --> 18:20.000 So, I would like to see what you would join forces more. 18:20.000 --> 18:37.000 One question. 18:37.000 --> 18:45.000 So, your question is, if it's possible to send the same message to a message alone? 18:45.000 --> 18:48.000 Well, yeah, it could be. 18:48.000 --> 18:55.000 If I integrate activity pop within, within the Ripple. 18:55.000 --> 18:59.000 It is possible, I think. 18:59.000 --> 19:02.000 That's another plan. 19:02.000 --> 19:03.000 Okay. 19:03.000 --> 19:04.000 One question. 19:04.000 --> 19:06.000 What are the limitations of Lostar? 19:06.000 --> 19:10.000 Can I post a two degree by video? 19:10.000 --> 19:11.000 Okay. 19:11.000 --> 19:12.000 Good question. 19:12.000 --> 19:17.000 Question is, can I post some media like a blob? 19:17.000 --> 19:18.000 Yeah. 19:18.000 --> 19:22.000 Well, if you put some binary data in that content, 19:22.000 --> 19:25.000 field it won't fit, especially when it's not too geeker-bytes. 19:25.000 --> 19:28.000 But there is another protocol being built upon. 19:28.000 --> 19:31.000 The Nostar protocol called Blossom. 19:31.000 --> 19:35.000 And that's basically the blobs of being hashed. 19:35.000 --> 19:39.000 And then can be uploaded to multiple Blossom servers. 19:39.000 --> 19:44.000 And then there is a metadata you can't be being broadcasted to the relay. 19:44.000 --> 19:47.000 So, then clients can fetch that information from the relay. 19:47.000 --> 19:50.000 Where to find that blob. 19:50.000 --> 19:52.000 Yeah, if they want to. 19:52.000 --> 19:58.000 And then they can download the image or the video. 19:58.000 --> 20:05.000 So, it's not taking care of the within the protocol itself. 20:05.000 --> 20:18.000 But it's another implementation as being developed. 20:18.000 --> 20:19.000 Yeah, there is a limit. 20:19.000 --> 20:20.000 There is a limit. 20:20.000 --> 20:24.000 But I don't know it from out of my head. 20:24.000 --> 20:30.000 But there is a limit, especially because the jation is taking some space. 20:30.000 --> 20:36.000 But there are people also working on how to compile it to more binary format. 20:36.000 --> 20:41.000 But then you'll get the down size of it's not easy to read anymore. 20:41.000 --> 20:44.000 But we are aware of that. 20:44.000 --> 20:45.000 Yeah. 20:45.000 --> 20:46.000 Question. 20:46.000 --> 20:52.000 So, if you had a jation file, we showed some of the content of the Blossom message. 20:52.000 --> 21:00.000 And what is the content of the Blossom message? 21:00.000 --> 21:01.000 Yeah. 21:01.000 --> 21:02.000 Yeah. 21:02.000 --> 21:03.000 Well, the website. 21:03.000 --> 21:08.000 The question is why was there a web-circuit link in the event? 21:08.000 --> 21:11.000 The relays are just web-circuit servers. 21:11.000 --> 21:16.000 And the client use a web-circuit client implementation to fetch the data. 21:16.000 --> 21:21.000 So, basically, all the data is being transferred to the web-circuit connections. 21:21.000 --> 21:26.000 But I guess the commands that can be given on that web-circuit are specific to the Blossom. 21:26.000 --> 21:27.000 Yeah. 21:27.000 --> 21:29.000 That's all being given. 21:29.000 --> 21:30.000 That's written here. 21:30.000 --> 21:33.000 That's defined in this NIP-01. 21:33.000 --> 21:36.000 That's basically the protocol. 21:36.000 --> 21:41.000 So, if you have interested, I have multiple with me. 21:41.000 --> 21:44.000 So, I can share it. 21:44.000 --> 21:46.000 I don't know. 21:46.000 --> 21:48.000 How many time is left? 21:49.000 --> 21:50.000 Two minutes. 21:50.000 --> 21:52.000 Okay. 21:52.000 --> 21:54.000 Not a question, yes. 21:54.000 --> 21:57.000 Oh, okay. 21:57.000 --> 21:58.000 Yeah. 22:02.000 --> 22:03.000 Yeah. 22:03.000 --> 22:04.000 I'm around. 22:04.000 --> 22:05.000 So. 22:05.000 --> 22:15.000 Yeah. 22:15.000 --> 22:17.000 Let me go back. 22:17.000 --> 22:18.000 Come on. 22:18.000 --> 22:19.000 I have no work for Poupon. 22:19.000 --> 22:21.000 But I can take you. 22:21.000 --> 22:23.000 Come on, buddy. 22:23.000 --> 22:26.000 I have you, like, business. 22:26.000 --> 22:28.000 The language. 22:28.000 --> 22:30.000 Well, yeah. 22:30.000 --> 22:34.000 Question is, is this a, is a recomply behind this? 22:34.000 --> 22:37.000 I'm, I'm, I'm working for myself. 22:37.000 --> 22:38.000 I'm a solo partner. 22:38.000 --> 22:40.000 I work for small clients. 22:40.000 --> 22:44.000 And also it's just my free and open source side project. 22:44.000 --> 22:52.000 So, for now, there is no business, but we founded a foundation last year. 22:52.000 --> 22:57.000 So, we are trying to find some business, but in a non-profit way. 22:57.000 --> 23:01.000 If that answers your question a bit. 23:01.000 --> 23:02.000 Yeah. 23:02.000 --> 23:03.000 Okay. 23:03.000 --> 23:04.000 Thank you. 23:04.000 --> 23:05.000 Thank you very much. 23:05.000 --> 23:07.000 Thank you. 23:07.000 --> 23:08.000 Thank you very much.