WEBVTT 00:00:05.839 --> 00:00:09.259 The Bitcoin Street Journal. Bitcoin Market Update. 00:00:10.039 --> 00:00:13.859 Episode 24. Week 23. Welcome to The Bitcoin Street 00:00:13.859 --> 00:00:16.679 Journal, your daily source for live market updates, 00:00:17.280 --> 00:00:19.660 technical analysis, and breaking news regarding 00:00:19.660 --> 00:00:22.500 Bitcoin. Stay up to date with the latest Bitcoin 00:00:22.500 --> 00:00:26.059 trends, market capitalization and supply, as 00:00:26.059 --> 00:00:28.800 well as financial and economic news by subscribing 00:00:28.800 --> 00:00:32.020 to our podcast. Join us on the journey through 00:00:32.020 --> 00:00:34.979 the world of Bitcoin. and its impact on our daily 00:00:34.979 --> 00:00:38.539 lives. In today's episode, we'll cover the basics 00:00:38.539 --> 00:00:41.380 of the Noster Protocol, including how to create 00:00:41.380 --> 00:00:44.079 an account, use clients to access the protocol, 00:00:44.700 --> 00:00:48.200 follow friends, and browse content. We'll also 00:00:48.200 --> 00:00:51.240 discuss the use of NIPs and relays, and offer 00:00:51.240 --> 00:00:53.780 tips on using specific clients like Coracle and 00:00:53.780 --> 00:00:56.880 Damus. Finally, we'll talk about how to contribute 00:00:56.880 --> 00:01:06.379 to the success of Noster. Have you ever wanted 00:01:06.379 --> 00:01:09.099 a truly global and sensor -resistant social network? 00:01:09.500 --> 00:01:12.000 Well, that's where Noster comes in. Noster is 00:01:12.000 --> 00:01:14.340 a simple and open protocol that enables just 00:01:14.340 --> 00:01:17.060 that. It's a decentralized social network created 00:01:17.060 --> 00:01:20.000 to empower users and allow them to connect directly 00:01:20.000 --> 00:01:22.859 without relying on a central authority. So how 00:01:22.859 --> 00:01:25.140 can you get started on Noster? It's simple. Create 00:01:25.140 --> 00:01:27.420 an account and join thousands of others who are 00:01:27.420 --> 00:01:29.760 already on the network. Once you're in, you'll 00:01:29.760 --> 00:01:31.859 be able to see what makes the protocol so special. 00:01:32.189 --> 00:01:34.629 The Noster protocol is based on flexible event 00:01:34.629 --> 00:01:37.590 objects that use standard elliptic curve cryptography 00:01:37.590 --> 00:01:41.450 for keys and signing. By relying only on WebSockets 00:01:41.450 --> 00:01:44.170 connections from clients to relays, it promotes 00:01:44.170 --> 00:01:46.590 software diversity and makes it easy to write 00:01:46.590 --> 00:01:49.510 clients and relays. One of the essential features 00:01:49.510 --> 00:01:52.209 that make Noster unique is that it is resilient. 00:01:52.769 --> 00:01:55.109 Noster doesn't rely on a small number of trusted 00:01:55.109 --> 00:01:58.140 servers for moving or storing data. This means 00:01:58.140 --> 00:02:00.900 that the protocol is very resilient to censorship 00:02:00.900 --> 00:02:03.700 or any other kind of interference. Users can 00:02:03.700 --> 00:02:05.920 connect and publish to an arbitrary number of 00:02:05.920 --> 00:02:08.319 relays that they can change over time. Another 00:02:08.319 --> 00:02:10.759 key aspect of Noster is that it's verifiable. 00:02:11.240 --> 00:02:14.139 Every Noster account is based on public key cryptography. 00:02:14.560 --> 00:02:16.560 This feature makes it easy to verify that the 00:02:16.560 --> 00:02:18.919 messages were actually sent by the user in question. 00:02:19.319 --> 00:02:21.819 But why do we need Noster? Our current social 00:02:21.819 --> 00:02:24.639 media systems are fundamentally broken. They 00:02:24.639 --> 00:02:27.180 rely on using users' attention to sell ads and 00:02:27.180 --> 00:02:30.319 bizarre techniques to keep people addicted. These 00:02:30.319 --> 00:02:32.560 systems also decide what content to show you 00:02:32.560 --> 00:02:34.819 based on a secret algorithm that you can't inspect 00:02:34.819 --> 00:02:38.379 or change. And unfortunately, they also have 00:02:38.379 --> 00:02:41.219 complete control over who can participate and 00:02:41.219 --> 00:02:44.340 who is censored. The good news is that there 00:02:44.340 --> 00:02:46.360 are resources out there to help you learn more 00:02:46.360 --> 00:02:49.460 about Nostr and how you can use it. There are 00:02:49.460 --> 00:02:52.500 different clients, apps you can use for the web, 00:02:52.699 --> 00:02:56.139 iOS, Android or desktop, whatever suits your 00:02:56.139 --> 00:02:58.759 needs best. There are also contributions you 00:02:58.759 --> 00:03:01.419 can make to help develop the Nostr protocol or 00:03:01.419 --> 00:03:04.719 relay implementation. So are you ready to become 00:03:04.719 --> 00:03:07.580 part of this exciting decentralized social network 00:03:07.580 --> 00:03:10.819 revolution? Check out the recommended external 00:03:10.819 --> 00:03:14.319 content and micro tools that can help you navigate 00:03:14.319 --> 00:03:18.039 and use Nostr. The possibilities are endless 00:03:18.039 --> 00:03:27.870 and the benefits are significant. Today we're 00:03:27.870 --> 00:03:29.750 talking about how to get started with Nostr, 00:03:29.909 --> 00:03:31.770 and I'm here to guide you through the process. 00:03:32.349 --> 00:03:34.430 When you create a Nostr account, it's based on 00:03:34.430 --> 00:03:37.229 a public -private key pair. Your public key is 00:03:37.229 --> 00:03:39.490 basically your username, and your private key 00:03:39.490 --> 00:03:42.389 acts as your password. But with one major difference. 00:03:42.729 --> 00:03:45.530 If you lose your private key, it can't be reset. 00:03:46.050 --> 00:03:48.389 So be sure to store it in a safe place, like 00:03:48.389 --> 00:03:51.770 a password manager. Now, Nostr itself is just 00:03:51.770 --> 00:03:54.610 a protocol. a set of rules for passing messages 00:03:54.610 --> 00:03:57.009 around on the internet. To access this protocol, 00:03:57.370 --> 00:03:59.949 you'll need a client. Clients can be web -based, 00:04:00.150 --> 00:04:02.689 desktop -based, or even on your mobile device. 00:04:03.169 --> 00:04:05.550 They help you fetch data from relays, as well 00:04:05.550 --> 00:04:07.629 as generate new data and share it with others. 00:04:08.189 --> 00:04:10.530 The only form of data that exists in Noster is 00:04:10.530 --> 00:04:13.189 the event, which must contain a signature to 00:04:13.189 --> 00:04:15.870 prove who created it. To construct this signature, 00:04:16.129 --> 00:04:18.660 the client will need your private key. For native 00:04:18.660 --> 00:04:20.720 apps, you can paste your private key into the 00:04:20.720 --> 00:04:23.519 app itself. While for web apps, we recommend 00:04:23.519 --> 00:04:26.000 using a browser extension that can handle Nostr 00:04:26.000 --> 00:04:29.220 related functionality. Ready to try Nostr for 00:04:29.220 --> 00:04:31.839 yourself? Check out some of our recommended clients 00:04:31.839 --> 00:04:35.240 like Coracle for the web, Damus for iOS, Gossip 00:04:35.240 --> 00:04:38.660 for desktop, and Nostros for Android. And if 00:04:38.660 --> 00:04:40.139 you're looking to connect with others in the 00:04:40.139 --> 00:04:42.480 Nostr community, you can use Nostr directory 00:04:42.480 --> 00:04:44.459 to find Twitter people that are already connected 00:04:44.459 --> 00:04:47.680 to Nostr. Alternatively, you can start following 00:04:47.680 --> 00:04:50.660 a few prominent Noster keys to get started. Finally, 00:04:51.040 --> 00:04:53.000 remember that you can use your public -private 00:04:53.000 --> 00:04:55.939 key pair on any Noster client, although not all 00:04:55.939 --> 00:04:58.139 clients support all protocol features in the 00:04:58.139 --> 00:05:00.639 same way. So be sure to check out our Client 00:05:00.639 --> 00:05:02.920 Comparison Guide to find the best client for 00:05:02.920 --> 00:05:12.519 your needs. Hey there! Today we're going to talk 00:05:12.519 --> 00:05:15.360 about a fascinating topic. the Noster Protocol. 00:05:15.839 --> 00:05:17.980 If you're curious about how it works and why 00:05:17.980 --> 00:05:20.720 it's essential, keep on reading. First things 00:05:20.720 --> 00:05:23.459 first, let's talk about what Noster is. In short, 00:05:23.600 --> 00:05:26.920 it has two main components, clients and relays. 00:05:27.399 --> 00:05:30.240 Each user runs a client and anyone can run a 00:05:30.240 --> 00:05:33.160 relay. The Noster Protocol aims to make it easier 00:05:33.160 --> 00:05:36.180 for users to share their data securely. But how 00:05:36.180 --> 00:05:38.860 exactly does it work? Every user has a public 00:05:38.860 --> 00:05:41.620 key that identifies them and every post is signed. 00:05:42.000 --> 00:05:44.519 That means that every client validates these 00:05:44.519 --> 00:05:47.000 signatures. It's important to ensure that all 00:05:47.000 --> 00:05:49.379 data is authenticated before it's sent across 00:05:49.379 --> 00:05:52.160 the network, and Noster takes this very seriously. 00:05:52.680 --> 00:05:55.459 Here's how it works in practice. Noster clients 00:05:55.459 --> 00:05:58.480 fetch data from relays of their choice and publish 00:05:58.480 --> 00:06:00.939 data to relays of their choice. It's important 00:06:00.939 --> 00:06:03.120 to note that relays don't talk to each other. 00:06:03.579 --> 00:06:06.620 They only communicate directly with users. That's 00:06:06.620 --> 00:06:09.160 Noster's way of ensuring that no unauthorized 00:06:09.160 --> 00:06:12.100 parties can access your data. For example, if 00:06:12.100 --> 00:06:14.500 you want to follow someone, all you have to do 00:06:14.500 --> 00:06:17.259 is instruct your client to query the relays it 00:06:17.259 --> 00:06:19.879 knows for posts from that public key. It's as 00:06:19.879 --> 00:06:23.160 simple as that. In summary, the NOSTER protocol 00:06:23.160 --> 00:06:26.079 is designed to make data sharing more secure 00:06:26.079 --> 00:06:29.399 and easier for users. By using public keys and 00:06:29.399 --> 00:06:32.319 validating all data signatures, NOSTER ensures 00:06:32.319 --> 00:06:34.680 that all data is legitimate before it's sent 00:06:34.680 --> 00:06:44.470 across the network. Hey there! Today we're going 00:06:44.470 --> 00:06:46.930 to dive into the fascinating world of NOSTER 00:06:46.930 --> 00:06:50.149 events. Events, as you might already know, are 00:06:50.149 --> 00:06:52.790 the atomic unit of the NOSTER protocol. This 00:06:52.790 --> 00:06:54.970 means that they're the only object type on the 00:06:54.970 --> 00:06:58.189 network. But what exactly is an event and what 00:06:58.189 --> 00:07:00.569 types are there? Well, let's answer these questions 00:07:00.569 --> 00:07:03.829 one by one. An event is a text note that is intended 00:07:03.829 --> 00:07:06.110 to be used in Twitter -like feeds, replies, and 00:07:06.110 --> 00:07:09.009 comments. Each event also has a specific kind 00:07:09.009 --> 00:07:11.819 number that determines its type. For instance, 00:07:12.120 --> 00:07:14.779 Kind 0 is a metadata event that users can use 00:07:14.779 --> 00:07:17.300 to give details about themselves, such as their 00:07:17.300 --> 00:07:20.339 name and profile picture. Meanwhile, relays might 00:07:20.339 --> 00:07:22.860 delete older versions of Kind 0 events and keep 00:07:22.860 --> 00:07:25.839 only the latest one. On the other hand, Kind 00:07:25.839 --> 00:07:28.279 1 events are the most commonly used and are just 00:07:28.279 --> 00:07:30.500 plain text notes designed to be read by others. 00:07:31.120 --> 00:07:32.980 They are also the type of events you would probably 00:07:32.980 --> 00:07:35.519 use when building a basic social networking app 00:07:35.519 --> 00:07:38.480 on the Nostr protocol. Now I know what you might 00:07:38.480 --> 00:07:41.139 be thinking. If there are only two kinds of events 00:07:41.139 --> 00:07:43.660 you need to build a social networking app, then 00:07:43.660 --> 00:07:46.180 why are there other types? Well, other types 00:07:46.180 --> 00:07:48.220 of events were invented to provide additional 00:07:48.220 --> 00:07:50.759 functionalities that clients needed. You'll find 00:07:50.759 --> 00:07:53.800 all the details on those in the NIPs. It's essential 00:07:53.800 --> 00:07:56.819 to understand that for each new use case, a sub 00:07:56.819 --> 00:07:59.000 -protocol must be thought of and proposed as 00:07:59.000 --> 00:08:02.649 an NIP. This ensures maximum interoperability 00:08:02.649 --> 00:08:05.470 with existing and future clients that might be 00:08:05.470 --> 00:08:07.949 interested in implementing that particular functionality. 00:08:08.470 --> 00:08:11.490 Plus, it makes sure everything is backward compatible 00:08:11.490 --> 00:08:13.829 and has nice fallbacks for anything that exists 00:08:13.829 --> 00:08:16.990 and doesn't want to change. Moving on, each event 00:08:16.990 --> 00:08:19.870 also has a created underscore at property. This 00:08:19.870 --> 00:08:22.209 is a Unix timestamp set by the event creator. 00:08:22.889 --> 00:08:24.750 Normally it's set to the time it was created, 00:08:24.810 --> 00:08:27.500 but there are no checks made against that. Finally, 00:08:27.800 --> 00:08:30.240 tags are another essential aspect of NOSTER events. 00:08:30.800 --> 00:08:32.899 They can vary depending on the kind of event, 00:08:33.299 --> 00:08:36.120 but some of the common tags include P, which 00:08:36.120 --> 00:08:39.600 is used to mention a public key, and E, which 00:08:39.600 --> 00:08:41.639 refers to another event. Well, that's a quick 00:08:41.639 --> 00:08:44.200 overview of NOSTER events and their types. Stay 00:08:44.200 --> 00:08:55.299 tuned for more exciting tech talk. You might 00:08:55.299 --> 00:08:57.120 be wondering what they are and why you should 00:08:57.120 --> 00:09:00.200 care about them. Well, aside from the first NIP, 00:09:00.419 --> 00:09:03.100 NIP -01, which describes the basic protocol, 00:09:03.500 --> 00:09:07.220 all NIPs are optional. But what is an NIP anyway? 00:09:07.740 --> 00:09:10.720 A NIP stands for Noster Implementation Possibilities. 00:09:11.259 --> 00:09:14.080 Its purpose is to promote interoperability. Instead 00:09:14.080 --> 00:09:16.779 of each developer coming up with their own solutions 00:09:16.779 --> 00:09:19.399 to common problems and implementing it in their 00:09:19.399 --> 00:09:22.340 own app only, it's better for everyone to implement 00:09:22.340 --> 00:09:24.440 solutions that are compatible with each other. 00:09:25.840 --> 00:09:28.779 NIIPs exist to coordinate this process. Think 00:09:28.779 --> 00:09:31.399 of it this way. A new idea might look great on 00:09:31.399 --> 00:09:34.019 one developer's app, but it will be much better 00:09:34.019 --> 00:09:36.500 if lots of other apps implement the same standard 00:09:36.500 --> 00:09:39.299 and they can interoperate nicely. This is why 00:09:39.299 --> 00:09:43.080 you should care about NIPS. Noster is decentralized 00:09:43.080 --> 00:09:45.879 and not owned by a centralized service like Twitter. 00:09:46.399 --> 00:09:48.460 This means that the direction of the protocol 00:09:48.460 --> 00:09:51.539 is up to all of us. We can suggest and advocate 00:09:51.539 --> 00:09:54.379 for changes and offer feedback on ideas suggested 00:09:54.379 --> 00:09:57.759 by others. Being an active part of the community 00:09:57.759 --> 00:09:59.919 gives you a say in the direction of the network. 00:10:00.820 --> 00:10:03.759 Curious where you can find NIPs? Check out the 00:10:03.759 --> 00:10:06.240 NosterNIPs repository. It's as simple as that. 00:10:06.720 --> 00:10:09.519 So start exploring the NIPs today and see how 00:10:09.519 --> 00:10:19.080 you can contribute to the Noster community. When 00:10:19.080 --> 00:10:21.580 it comes to using the Noster Protocol, clients 00:10:21.580 --> 00:10:24.580 are your way in. Think of it as the app you use 00:10:24.580 --> 00:10:27.460 to access and interact with the protocol, similar 00:10:27.460 --> 00:10:30.120 to how you might use Twitter's iOS app or web 00:10:30.120 --> 00:10:33.340 app to view tweets. The flexibility and simplicity 00:10:33.340 --> 00:10:36.600 of the Noster Protocol means that different clients 00:10:36.600 --> 00:10:39.340 can approach it in different ways. Some clients 00:10:39.340 --> 00:10:41.879 try to mirror Twitter's experience, while others 00:10:41.879 --> 00:10:45.019 focus on the importance of relays, or use algorithms 00:10:45.019 --> 00:10:48.200 to ensure censorship resistance without overwhelming 00:10:48.200 --> 00:10:51.100 users. If you want to try out different clients, 00:10:51.519 --> 00:10:53.940 you can switch them or sign into as many as you'd 00:10:53.940 --> 00:10:56.320 like, as long as they're pulling data from the 00:10:56.320 --> 00:10:59.820 same relays. However, it's generally best not 00:10:59.820 --> 00:11:02.759 to enter your private key into any client. While 00:11:02.759 --> 00:11:04.700 most clients do try to keep your key secure, 00:11:05.320 --> 00:11:07.679 there's always the potential for bugs or breaches 00:11:07.679 --> 00:11:10.620 that could compromise your identity. If you're 00:11:10.620 --> 00:11:12.950 looking for some client recommendations, there 00:11:12.950 --> 00:11:15.350 are plenty to choose from. Some of our favorites 00:11:15.350 --> 00:11:18.789 include Snort for web, Nose for iOS, and Nostros 00:11:18.789 --> 00:11:21.750 for Android. Each client has its strengths and 00:11:21.750 --> 00:11:24.250 unique features, so explore and find the one 00:11:24.250 --> 00:11:26.870 that works best for you. And for a more in -depth 00:11:26.870 --> 00:11:28.429 look, be sure to check out the guides provided 00:11:28.429 --> 00:11:37.659 for each client. Today, we are going to walk 00:11:37.659 --> 00:11:39.700 you through getting started with Nostr on two 00:11:39.700 --> 00:11:42.240 different clients, Coracle on the web and Damus 00:11:42.240 --> 00:11:45.620 on iOS. First up, let's dive into Coracle. To 00:11:45.620 --> 00:11:50.399 get started with Coracle, open up https://coracle 00:11:50.399 --> 00:11:53.220 .social in your browser. You'll be prompted to 00:11:53.220 --> 00:11:56.320 either log in or sign up. If you already have 00:11:56.320 --> 00:11:59.100 a private key, then select log in and paste it 00:11:59.100 --> 00:12:02.559 in. If not, select sign up and Coracle will generate 00:12:02.559 --> 00:12:05.039 a new key pair for you. Once you've got your 00:12:05.039 --> 00:12:07.000 key pair, you'll want to start following some 00:12:07.000 --> 00:12:10.139 people. If you click on the search option, you'll 00:12:10.139 --> 00:12:12.879 see a list of people that you can follow. Alternatively, 00:12:13.440 --> 00:12:16.500 you can click on the Advanced tab to paste profiles, 00:12:16.879 --> 00:12:19.840 endpubs, or other identifiers. From there, you 00:12:19.840 --> 00:12:21.960 can browse through your feed and click on any 00:12:21.960 --> 00:12:24.419 note to see replies and its parent. Now let's 00:12:24.419 --> 00:12:27.000 talk about Damus on iOS. First, head over to 00:12:27.000 --> 00:12:29.179 the iOS app store and download the Damus app. 00:12:29.580 --> 00:12:31.740 When you open it, you'll have the option to either 00:12:31.740 --> 00:12:34.340 create a new account, or log in with a private 00:12:34.340 --> 00:12:36.620 key that you've already generated. If you don't 00:12:36.620 --> 00:12:39.480 have a private key yet, then select Create Account. 00:12:40.279 --> 00:12:42.580 Pick a username and optionally add some other 00:12:42.580 --> 00:12:45.179 profile details. Damus will generate keys for 00:12:45.179 --> 00:12:47.600 you at this stage and your public key will be 00:12:47.600 --> 00:12:50.480 your account ID. Once done, click Create and 00:12:50.480 --> 00:12:52.590 you're good to go. However, before you start 00:12:52.590 --> 00:12:54.789 using Daymas, you'll need to save your private 00:12:54.789 --> 00:12:57.409 key somewhere very safe. Navigate to Settings 00:12:57.409 --> 00:12:59.669 by clicking your profile image at the top left 00:12:59.669 --> 00:13:02.289 of the screen and then Settings. From there, 00:13:02.570 --> 00:13:04.970 you'll find your public account ID, your public 00:13:04.970 --> 00:13:07.809 key, and your secret account login key, your 00:13:07.809 --> 00:13:10.909 private key. Copy both of these values and store 00:13:10.909 --> 00:13:13.309 them somewhere super safe, like one password 00:13:13.309 --> 00:13:15.909 or a different password manager. Remember, if 00:13:15.909 --> 00:13:18.070 you don't save this value, you won't be able 00:13:18.070 --> 00:13:20.950 to recover your account. Lastly, if you already 00:13:20.950 --> 00:13:23.429 have a private key, select login and enter in 00:13:23.429 --> 00:13:25.889 your private key when prompted. Remember that 00:13:25.889 --> 00:13:27.929 Damus doesn't store your private key on their 00:13:27.929 --> 00:13:37.409 servers in any way. If you're looking to use 00:13:37.409 --> 00:13:39.809 Gossip on your desktop, we've got a step -by 00:13:39.809 --> 00:13:42.190 -step guide for you. The first thing you should 00:13:42.190 --> 00:13:44.950 do is download either the Gossip Linux binary 00:13:44.950 --> 00:13:47.509 or the Windows installable from the releases 00:13:47.509 --> 00:13:50.950 section. Once you open the app, go to You and 00:13:50.950 --> 00:13:53.429 generate a key pair. However, if you already 00:13:53.429 --> 00:13:56.370 have a private key, you can import it. It's important 00:13:56.370 --> 00:13:58.649 to get this done so your keys are set up, but 00:13:58.649 --> 00:14:01.009 you're not following anyone yet, so your feeds 00:14:01.009 --> 00:14:03.789 section will be empty. To start following people, 00:14:03.850 --> 00:14:06.289 head to the People section and click Follow Someone 00:14:06.289 --> 00:14:09.309 New. From there, you can type in a DNS ID like 00:14:09.309 --> 00:14:13.289 fiatjoff .com or jacketcache .app. If you have 00:14:13.289 --> 00:14:16.289 a specific NPUB1 or hex key, you can specify 00:14:16.289 --> 00:14:19.379 a relay manually. Keep in mind that Gossip follows 00:14:19.379 --> 00:14:21.960 specific people at specific relays and doesn't 00:14:21.960 --> 00:14:24.899 have a global list of relays. After you're done 00:14:24.899 --> 00:14:27.320 following someone new, you may have to restart 00:14:27.320 --> 00:14:30.360 Gossip so that your feed shows up. After restarting, 00:14:30.360 --> 00:14:33.639 head to the People tab and click on Refresh Metadata. 00:14:34.259 --> 00:14:36.500 This will update the profiles of the people you're 00:14:36.500 --> 00:14:39.100 following and show their pictures, making the 00:14:39.100 --> 00:14:41.860 experience more enjoyable. You may notice that 00:14:41.860 --> 00:14:44.279 Gossip won't let you write anything until you've 00:14:44.279 --> 00:14:46.500 chosen a set of relays to write your posts on. 00:14:46.840 --> 00:14:50.639 To get started, go to Relays and then Configure. 00:14:51.019 --> 00:14:53.220 Pick a few relays where you want to publish your 00:14:53.220 --> 00:14:56.360 posts and you're good to go. You can even manually 00:14:56.360 --> 00:14:59.700 type in relay addresses if you want. Once everything 00:14:59.700 --> 00:15:03.500 is set up, browsing the feed is easy. The Feed 00:15:03.500 --> 00:15:06.279 tab shows all the notes from the people you're 00:15:06.279 --> 00:15:09.759 following and only them. You can click on the 00:15:09.759 --> 00:15:12.100 notes and read replies as long as there's enough 00:15:12.100 --> 00:15:15.370 relay information to fetch them. The inbox section 00:15:15.370 --> 00:15:18.070 shows your mentions and notes. To publish your 00:15:18.070 --> 00:15:20.669 own notes, type in the text box above the feed 00:15:20.669 --> 00:15:23.450 and add a subject. You can also mention people 00:15:23.450 --> 00:15:25.549 by searching for them in the little text box 00:15:25.549 --> 00:15:29.490 below. Any content like NP of one or note one 00:15:29.490 --> 00:15:32.230 pasted in the text box should be automatically 00:15:32.230 --> 00:15:35.149 picked and parsed into a real mention and given 00:15:35.149 --> 00:15:37.690 a different color. Now, if you prefer to use 00:15:37.690 --> 00:15:40.649 Nostros on your Android device, here's what you 00:15:40.649 --> 00:15:43.669 need to do. Open the app. and generate a private 00:15:43.669 --> 00:15:45.870 key if you don't have one. You'll be prompted 00:15:45.870 --> 00:15:48.250 to create a sequence of words, which you should 00:15:48.250 --> 00:15:50.909 write down if you're serious about this. If not, 00:15:50.929 --> 00:15:53.549 you can just move forward. In the next screen, 00:15:53.649 --> 00:15:56.129 you'll be asked to type the words again. If you 00:15:56.129 --> 00:15:59.269 noted them down, type them in. Otherwise, there's 00:15:59.269 --> 00:16:02.190 a skip button you can click. To follow someone, 00:16:02.230 --> 00:16:04.830 head to the contacts screen and paste their public 00:16:04.830 --> 00:16:08.669 key. You can also type a NIP05 address. After 00:16:08.669 --> 00:16:10.850 that, you can see their profile information. 00:16:11.210 --> 00:16:13.730 Your feed tab will show the people you're following. 00:16:14.250 --> 00:16:16.909 To find other people, take a look at those with 00:16:16.909 --> 00:16:19.090 whom they're interacting. You'll see colored 00:16:19.090 --> 00:16:21.450 bars that represent the relays where each note 00:16:21.450 --> 00:16:24.889 was found. That's it for our guides. Now you're 00:16:24.889 --> 00:16:34.450 ready to use Gossip and Nostros. Have you ever 00:16:34.450 --> 00:16:36.509 heard of relays? Well, these are like the backend 00:16:36.509 --> 00:16:39.559 servers for Nostr. They enable Nostr clients 00:16:39.559 --> 00:16:42.159 to send messages where they may or may not be 00:16:42.159 --> 00:16:44.360 stored and then broadcast to other connected 00:16:44.360 --> 00:16:47.179 clients. It's essential to note that since Nostr 00:16:47.179 --> 00:16:50.000 is decentralized and relies on relays to store 00:16:50.000 --> 00:16:53.200 and retrieve data, if you experience slow performance, 00:16:53.700 --> 00:16:55.799 it's possible that the relays you're using are 00:16:55.799 --> 00:16:58.460 at fault. So it's worth adding more relays to 00:16:58.460 --> 00:17:00.840 your client. You're probably wondering where 00:17:00.840 --> 00:17:03.740 you can find a list of relays. No worries, we've 00:17:03.740 --> 00:17:06.059 got you covered. The best resource we've found 00:17:06.059 --> 00:17:08.180 for browsing and assessing the speed of known 00:17:08.180 --> 00:17:11.220 relays is the Nostr .Watch site. Now let's talk 00:17:11.220 --> 00:17:13.559 about what happens if all the relays you use 00:17:13.559 --> 00:17:16.480 stop working. If all relays you've used in the 00:17:16.480 --> 00:17:19.519 past go offline, your posts will be unretrievable. 00:17:20.200 --> 00:17:22.220 One reason why Nostr allows users to connect 00:17:22.220 --> 00:17:24.779 with many relays is to guarantee some degree 00:17:24.779 --> 00:17:27.700 of backup. However, if you're very interested 00:17:27.700 --> 00:17:30.039 in being uncensorable, you can run your relay. 00:17:30.269 --> 00:17:32.690 For most people, this may seem daunting, but 00:17:32.690 --> 00:17:34.410 for those who want to ensure that their speech 00:17:34.410 --> 00:17:37.130 is entirely unsensorable, then running your relay 00:17:37.130 --> 00:17:39.650 is recommended. You may be wondering how someone 00:17:39.650 --> 00:17:42.210 can access you in a personal or obscure relay. 00:17:42.809 --> 00:17:44.589 If you want to hint where you're publishing to 00:17:44.589 --> 00:17:46.849 people that might be interested, you can use 00:17:46.849 --> 00:17:51.470 the NIP19N profile code or the NIP05 relays field. 00:17:52.089 --> 00:17:54.109 You can also publish a list of the relays you 00:17:54.109 --> 00:17:57.539 use to multiple other relays you don't use. Finally, 00:17:57.579 --> 00:17:59.660 you might be asking yourself whether any public 00:17:59.660 --> 00:18:02.880 relays exist in the ecosystem. Well, the Nostr 00:18:02.880 --> 00:18:05.480 .Watch website keeps a very comprehensive list 00:18:05.480 --> 00:18:08.039 that has lots of valuable information about each 00:18:08.039 --> 00:18:11.359 relay, not only their address. So, there you 00:18:11.359 --> 00:18:21.480 have it, relays and how they work. Hey there! 00:18:21.779 --> 00:18:23.960 Today we're talking about relay implementations 00:18:23.960 --> 00:18:27.029 for the Nostr Relay Spec. This list includes 00:18:27.029 --> 00:18:30.049 all known implementations and is helpful if you're 00:18:30.049 --> 00:18:32.509 thinking of running a relay yourself. To start, 00:18:32.549 --> 00:18:35.690 let's discuss what relays are. So far, they're 00:18:35.690 --> 00:18:37.950 application agnostic. This means you can either 00:18:37.950 --> 00:18:40.529 run your own relay or use any or all of the public 00:18:40.529 --> 00:18:43.769 instances. Now, on to the most used relays in 00:18:43.769 --> 00:18:48.309 the wild. First up, we have Nostrars Relay. It's 00:18:48.309 --> 00:18:50.869 a minimalistic optimized relay written in Rust 00:18:50.869 --> 00:18:53.900 that uses Sklite. Next, we have Nostream. a NOSTA 00:18:53.900 --> 00:18:55.900 relay written in TypeScript that's optimized 00:18:55.900 --> 00:18:58.420 for load balancing and fault tolerance, and backed 00:18:58.420 --> 00:19:01.559 by PostgreSQL and Redis. Another great one is 00:19:01.559 --> 00:19:04.859 me, Untether at NOSTA Relay, which is written 00:19:04.859 --> 00:19:07.319 in Clojure, very strict and performant, and uses 00:19:07.319 --> 00:19:10.180 Sqlite. And finally, Stirfree is a relay written 00:19:10.180 --> 00:19:13.440 in C++, which is very performant and uses LMDB 00:19:13.440 --> 00:19:16.000 for data storage. It also comes with a built 00:19:16.000 --> 00:19:18.420 -in set reconciliation mechanism for syncing. 00:19:18.819 --> 00:19:20.900 Now, let's move on to the other implementations. 00:19:21.299 --> 00:19:23.890 First is Relayer Basic. which is a simple reference 00:19:23.890 --> 00:19:26.609 relay backed by Postgres. It's written as a demo 00:19:26.609 --> 00:19:28.769 on top of the Relayer Go framework for building 00:19:28.769 --> 00:19:32.329 custom relays. Next is Inoster, a relay written 00:19:32.329 --> 00:19:35.650 in C hash. Then we have Soster, which is a Noster 00:19:35.650 --> 00:19:38.630 relay designed for a single writer pub key. There's 00:19:38.630 --> 00:19:41.390 also the Minds Noster relay, a relay for Minds, 00:19:41.609 --> 00:19:44.130 an open source social network. Another one is 00:19:44.130 --> 00:19:46.750 Noster underscore relay, a Noster relay written 00:19:46.750 --> 00:19:49.609 in Python and backed by skew light. If you're 00:19:49.609 --> 00:19:51.970 using LnBits, you can launch LnBits Relay in 00:19:51.970 --> 00:19:54.589 your own server with just one click or two. Wrapper 00:19:54.589 --> 00:19:57.289 over Nostr underscore relay. And last but not 00:19:57.289 --> 00:19:59.730 least, we have Nostr Poster Relay. It's written 00:19:59.730 --> 00:20:02.569 in Kotlin and supports both Skulite and PostgresQL. 00:20:03.269 --> 00:20:05.930 And if you like metrics, Nostr is a Nostr relay 00:20:05.930 --> 00:20:08.210 implemented in Kotlin with support for Postgres 00:20:08.210 --> 00:20:10.970 and Metrix. So there you have it, a comprehensive 00:20:10.970 --> 00:20:17.240 list of the Nostr relay implementations. So you're 00:20:17.240 --> 00:20:19.019 interested in contributing to the success of 00:20:19.019 --> 00:20:22.319 Noster? Fantastic. There are plenty of ways you 00:20:22.319 --> 00:20:24.839 can get involved and help promote decentralization 00:20:24.839 --> 00:20:27.940 and ultra interoperability. One way to contribute 00:20:27.940 --> 00:20:30.460 is by working on your favorite client. Try to 00:20:30.460 --> 00:20:32.339 come up with approaches that are both fun and 00:20:32.339 --> 00:20:34.720 useful while keeping the principles of Noster 00:20:34.720 --> 00:20:37.599 in mind. If you have new ideas that don't fit 00:20:37.599 --> 00:20:40.220 in an existing app, you can even start a new 00:20:40.220 --> 00:20:43.500 client all on your own. Check out bouncer .com 00:20:43.500 --> 00:20:45.920 for things that might interest you. You may come 00:20:45.920 --> 00:20:47.859 across some bounties that you could contribute 00:20:47.859 --> 00:20:50.720 to. Of course, you could always simply use Noster 00:20:50.720 --> 00:20:52.920 and tell others about it. Let them know what 00:20:52.920 --> 00:20:55.160 you like about it and what you think can be improved. 00:20:56.019 --> 00:20:58.259 Don't forget to give feedback to client authors. 00:20:58.900 --> 00:21:02.019 However, when you do so, be patient. If you're 00:21:02.019 --> 00:21:04.140 feeling generous, you can donate money to people 00:21:04.140 --> 00:21:06.680 doing things you think are good. Another way 00:21:06.680 --> 00:21:09.259 to contribute is by writing explainers and curated 00:21:09.259 --> 00:21:12.400 resources for Noster. Put them online so that 00:21:12.400 --> 00:21:14.599 others can learn from them. If you want to get 00:21:14.599 --> 00:21:16.799 even more involved, check how your skills can 00:21:16.799 --> 00:21:19.039 help Nostr software or the mission of spreading 00:21:19.039 --> 00:21:21.559 the Nostr world. You can partner with others 00:21:21.559 --> 00:21:23.519 who may be searching for that type of assistance. 00:21:24.359 --> 00:21:27.400 Or if you have a real life example of how Nostr 00:21:27.400 --> 00:21:30.299 has helped you and you think others might be 00:21:30.299 --> 00:21:33.339 interested in building on it, bring it up. You 00:21:33.339 --> 00:21:35.700 never know who else you might inspire. Finally, 00:21:35.779 --> 00:21:37.980 if all else fails, annoy your favorite content 00:21:37.980 --> 00:21:40.410 creators, people banned from social media. or 00:21:40.410 --> 00:21:42.369 other personalities you follow until they check 00:21:42.369 --> 00:21:44.650 out Nostr for themselves. Who knows, they might 00:21:44.650 --> 00:21:54.069 thank you for it later. In today's episode, we 00:21:54.069 --> 00:21:56.849 talked about the Nostr protocol and how it enables 00:21:56.849 --> 00:21:59.650 an open and censorship resistant social media 00:21:59.650 --> 00:22:02.869 experience, as well as the importance of clients, 00:22:03.250 --> 00:22:06.960 relays, and NIPs. We also discussed different 00:22:06.960 --> 00:22:10.299 ways to access and interact with Noster, including 00:22:10.299 --> 00:22:13.039 recommended clients such as Coracle and Damus. 00:22:13.539 --> 00:22:15.839 Finally, we touched on the importance of contributing 00:22:15.839 --> 00:22:18.640 to Noster's success. Thanks for listening to 00:22:18.640 --> 00:22:20.960 today's episode. I'll see you guys at the next 00:22:20.960 --> 00:22:22.440 one and don't forget to subscribe.