WEBVTT 00:00:14.900 --> 00:00:17.379 Welcome to the Bitcoin Street Journal, Bitcoin 00:00:17.379 --> 00:00:19.620 Market Update podcast, your daily source for 00:00:19.620 --> 00:00:22.359 live updates on the Bitcoin market. Join us as 00:00:22.359 --> 00:00:24.800 we delve into current Bitcoin technical analysis, 00:00:25.399 --> 00:00:29.579 track Bitcoin, BTC prices, explore market capitalization 00:00:29.579 --> 00:00:32.840 trends, and analyze market supply. Stay ahead 00:00:32.840 --> 00:00:34.899 of the curve with our comprehensive coverage 00:00:34.899 --> 00:00:38.060 of the ever evolving world of Bitcoin. In today's 00:00:38.060 --> 00:00:40.679 episode, we'll cover the topics of creating a 00:00:40.679 --> 00:00:43.020 censorship -resistant social network, without 00:00:43.020 --> 00:00:45.719 relying on central servers, the issues faced 00:00:45.719 --> 00:00:49.159 by Mastodon and SSB's complicated protocol, how 00:00:49.159 --> 00:00:51.560 Noster uses clients and relays for censorship 00:00:51.560 --> 00:00:54.399 resistance, the unique features that set Noster 00:00:54.399 --> 00:00:57.079 apart from other social networks, and the process 00:00:57.079 --> 00:00:59.560 of finding people to follow in a Noster social 00:00:59.560 --> 00:01:03.399 network. Hey there, let me tell you about Noster. 00:01:03.679 --> 00:01:06.120 notes and other stuff transmitted by relays. 00:01:06.480 --> 00:01:09.200 It's a super cool open protocol that aims to 00:01:09.200 --> 00:01:11.900 create a global social network that is resistant 00:01:11.900 --> 00:01:14.840 to censorship once and for all. And the best 00:01:14.840 --> 00:01:17.099 part? It doesn't rely on any trusted central 00:01:17.099 --> 00:01:19.680 server making it resilient and secure. So how 00:01:19.680 --> 00:01:22.319 does it work? Well, it's all based on cryptographic 00:01:22.319 --> 00:01:24.859 keys and signatures making it tamper -proof. 00:01:25.359 --> 00:01:27.060 You and everyone else who wants to be part of 00:01:27.060 --> 00:01:30.000 Nostr runs a client which can be a native client 00:01:30.000 --> 00:01:32.930 or a web client. When you want to publish something, 00:01:33.129 --> 00:01:35.650 you simply write a post, sign it with your key, 00:01:35.709 --> 00:01:38.290 and send it to multiple relays. These relays 00:01:38.290 --> 00:01:40.930 are servers hosted by someone else or even yourself. 00:01:41.549 --> 00:01:43.109 Now, when you want to get updates from other 00:01:43.109 --> 00:01:45.430 people, you ask multiple relays if they know 00:01:45.430 --> 00:01:47.790 anything about these other people. The cool thing 00:01:47.790 --> 00:01:50.390 is that anyone can run a relay, and they're super 00:01:50.390 --> 00:01:52.810 simple and dumb. They accept posts from some 00:01:52.810 --> 00:01:55.590 people and forward them to others. And the best 00:01:55.590 --> 00:01:58.290 part is that you don't have to trust these relays. 00:01:58.790 --> 00:02:02.090 The client side verifies the signatures. ensuring 00:02:02.090 --> 00:02:04.450 that your messages aren't tampered with. Now, 00:02:04.450 --> 00:02:06.569 if you're eager to start using Noster, there 00:02:06.569 --> 00:02:09.009 are a few handy resources you should check out. 00:02:09.610 --> 00:02:11.870 First, you'll find a Telegram group where you 00:02:11.870 --> 00:02:14.189 can join and get involved in the ongoing work. 00:02:14.610 --> 00:02:16.389 It's a great place to connect with others who 00:02:16.389 --> 00:02:18.789 are passionate about this project. If you're 00:02:18.789 --> 00:02:20.830 wondering about the features of the Noster client, 00:02:21.449 --> 00:02:23.469 we have a nifty comparison chart to help you 00:02:23.469 --> 00:02:26.110 out. It highlights the different functionalities 00:02:26.110 --> 00:02:29.069 of the native and web clients, making it easier 00:02:29.069 --> 00:02:31.150 for you to choose the one that suits your needs. 00:02:31.689 --> 00:02:33.689 And to give you a taste of the awesomeness built 00:02:33.689 --> 00:02:36.650 on Nostr, there's a handy list of projects that 00:02:36.650 --> 00:02:38.469 have been developed using this open protocol. 00:02:39.250 --> 00:02:41.530 It's amazing to see the innovation and creativity 00:02:41.530 --> 00:02:44.409 that has sprung from this community. So why is 00:02:44.409 --> 00:02:47.030 Nostr needed anyway? Well, let's talk about the 00:02:47.030 --> 00:02:49.590 problems with Twitter. First and foremost, Twitter 00:02:49.590 --> 00:02:52.659 bombards us with ads. It can get pretty annoying 00:02:52.659 --> 00:02:54.259 when you're trying to scroll through your feed 00:02:54.259 --> 00:02:57.300 and all you see are sponsored posts. Noster, 00:02:57.340 --> 00:02:59.419 on the other hand, focuses on providing a clean 00:02:59.419 --> 00:03:02.719 and uninterrupted user experience. Another issue 00:03:02.719 --> 00:03:04.560 with Twitter is its strange techniques to keep 00:03:04.560 --> 00:03:07.560 us addicted. The constant notifications, the 00:03:07.560 --> 00:03:10.000 algorithmic timeline, and the never -ending scroll, 00:03:10.180 --> 00:03:13.159 all designed to keep us hooked. Noster takes 00:03:13.159 --> 00:03:15.300 a different approach, putting control back into 00:03:15.300 --> 00:03:17.740 the hands of the users. And let's not forget 00:03:17.740 --> 00:03:20.060 about Twitter's lackluster historical feed from 00:03:20.060 --> 00:03:22.930 people you follow. It doesn't show you a complete 00:03:22.930 --> 00:03:25.889 and chronological timeline of their posts, making 00:03:25.889 --> 00:03:28.610 it hard to catch up on what you've missed. With 00:03:28.610 --> 00:03:30.710 Noster, you can rest assured that you'll get 00:03:30.710 --> 00:03:33.590 an actual historical feed, making it easier to 00:03:33.590 --> 00:03:36.110 stay up to date with the people you follow. Now, 00:03:36.169 --> 00:03:38.150 one of the most frustrating aspects of Twitter 00:03:38.150 --> 00:03:41.909 is its penchant for banning people. It's disheartening 00:03:41.909 --> 00:03:44.250 to see individuals being silenced for expressing 00:03:44.250 --> 00:03:47.280 their thoughts and opinions. Noster stands against 00:03:47.280 --> 00:03:49.919 such censorship, providing a platform where freedom 00:03:49.919 --> 00:03:52.800 of speech is respected. To make matters worse, 00:03:53.080 --> 00:03:55.319 Twitter sometimes resorts to shadow banning, 00:03:55.620 --> 00:03:57.520 which means suppressing the reach of certain 00:03:57.520 --> 00:03:59.960 users without their knowledge. It's a sneaky 00:03:59.960 --> 00:04:02.699 tactic that Noster avoids completely, ensuring 00:04:02.699 --> 00:04:05.360 that every user's voice is heard loud and clear. 00:04:06.159 --> 00:04:08.419 Lastly, let's not forget about the never -ending 00:04:08.419 --> 00:04:11.060 deluge of spam on Twitter. Whether it's bots 00:04:11.060 --> 00:04:13.560 promoting questionable content or endless self 00:04:13.560 --> 00:04:16.240 -promotion, it can be a cesspool of unwanted 00:04:16.240 --> 00:04:19.420 noise. Noster takes spam seriously and aims to 00:04:19.420 --> 00:04:21.600 provide a clean and spam -free environment for 00:04:21.600 --> 00:04:24.680 users to connect and share ideas. So there you 00:04:24.680 --> 00:04:27.459 have it. A quick rundown of Noster, the open 00:04:27.459 --> 00:04:29.759 protocol that aims to revolutionize the way we 00:04:29.759 --> 00:04:32.209 experience social networking. If you're tired 00:04:32.209 --> 00:04:34.449 of the issues plaguing traditional platforms 00:04:34.449 --> 00:04:37.430 like Twitter, Nostr might just be the fresh breath 00:04:37.430 --> 00:04:40.649 of air you've been looking for. Get involved, 00:04:41.170 --> 00:04:44.069 join the conversation, and be part of the movement 00:04:44.069 --> 00:04:46.930 towards a censorship -resistant global social 00:04:46.930 --> 00:04:50.569 network. So today, let's talk about some of the 00:04:50.569 --> 00:04:52.569 problems with Mastodon and similar programs. 00:04:53.250 --> 00:04:55.819 Now, when it comes to these platforms, One of 00:04:55.819 --> 00:04:58.620 the main issues is that user identities are attached 00:04:58.620 --> 00:05:00.980 to domain names controlled by third parties. 00:05:01.720 --> 00:05:03.759 This means that you are dependent on another 00:05:03.759 --> 00:05:06.879 entity to maintain your online presence. And 00:05:06.879 --> 00:05:09.540 as we all know, server owners have the power 00:05:09.540 --> 00:05:12.680 to ban users, just like Twitter does. So even 00:05:12.680 --> 00:05:15.540 on these alternative platforms, you're not completely 00:05:15.540 --> 00:05:17.879 free from the possibility of being blocked or 00:05:17.879 --> 00:05:21.000 silenced by someone in control. In addition to 00:05:21.000 --> 00:05:23.740 that, server owners also have the ability to 00:05:23.740 --> 00:05:26.639 block other servers. This creates a fragmented 00:05:26.639 --> 00:05:29.079 environment where communication and interaction 00:05:29.079 --> 00:05:31.639 can be severely limited. And if you're someone 00:05:31.639 --> 00:05:34.060 who values the freedom to migrate between different 00:05:34.060 --> 00:05:36.579 servers, well, that's where the problems arise. 00:05:37.160 --> 00:05:39.800 Migration between servers is not a seamless process 00:05:39.800 --> 00:05:42.420 and can only be accomplished if the servers cooperate. 00:05:43.060 --> 00:05:45.279 This means that if servers are in an adversarial 00:05:45.279 --> 00:05:47.500 environment, all of your followers can be lost. 00:05:47.899 --> 00:05:49.939 It's like starting from scratch every time you 00:05:49.939 --> 00:05:52.660 switch servers. And that's definitely not ideal. 00:05:53.270 --> 00:05:56.009 Moreover, there are no clear incentives for people 00:05:56.009 --> 00:05:59.430 to run servers. As a result, the task often falls 00:05:59.430 --> 00:06:01.610 into the hands of enthusiasts or individuals 00:06:01.610 --> 00:06:03.949 who simply want their name attached to a cool 00:06:03.949 --> 00:06:07.009 domain. Now the issue with this is that users 00:06:07.009 --> 00:06:09.910 then become subject to the despotism of a single 00:06:09.910 --> 00:06:12.610 person. In some cases, this can be even worse 00:06:12.610 --> 00:06:15.029 than what you experience on platforms like Twitter, 00:06:15.610 --> 00:06:17.649 where at least there are some rules and regulations 00:06:17.649 --> 00:06:21.170 in place. And to make matters worse, users can't 00:06:21.170 --> 00:06:23.529 easily migrate out of these situations because 00:06:23.529 --> 00:06:26.550 of the lack of server interoperability. Furthermore, 00:06:26.769 --> 00:06:29.329 since servers tend to be run amateurishly, they 00:06:29.329 --> 00:06:32.129 are often abandoned after a while. This is effectively 00:06:32.129 --> 00:06:34.110 the same as banning everybody because once a 00:06:34.110 --> 00:06:36.850 server goes offline, all of the users lose their 00:06:36.850 --> 00:06:39.810 access. So it's not a sustainable solution in 00:06:39.810 --> 00:06:42.970 the long run. Now let's talk about the data aspect. 00:06:43.870 --> 00:06:45.870 Having a ton of servers can be problematic when 00:06:45.870 --> 00:06:48.500 it comes to updates. If every server needs to 00:06:48.500 --> 00:06:50.879 push and save updates to multiple other servers, 00:06:51.399 --> 00:06:54.060 it becomes a cumbersome process. And when you 00:06:54.060 --> 00:06:56.459 factor in the large number of servers that exist, 00:06:57.040 --> 00:06:59.420 it means that more data has to be passed to more 00:06:59.420 --> 00:07:02.259 places more often. This creates a strain on the 00:07:02.259 --> 00:07:05.180 entire system and can lead to inefficiencies. 00:07:05.860 --> 00:07:07.800 To illustrate this point further, let's look 00:07:07.800 --> 00:07:11.470 at the specific example of video sharing. Activity 00:07:11.470 --> 00:07:13.910 Pub enthusiasts realized that transmitting videos 00:07:13.910 --> 00:07:16.089 from server to server the same way text notes 00:07:16.089 --> 00:07:18.449 are transmitted would be completely impossible. 00:07:18.990 --> 00:07:21.170 So they decided to keep the videos hosted only 00:07:21.170 --> 00:07:23.370 on the instance where they were originally posted. 00:07:23.949 --> 00:07:26.290 This is similar to the Nostra approach, where 00:07:26.290 --> 00:07:29.009 content remains centralized. While this may solve 00:07:29.009 --> 00:07:31.689 the problem of video transmission, it also limits 00:07:31.689 --> 00:07:33.829 the decentralized nature of these platforms. 00:07:34.329 --> 00:07:36.470 Now let's move on to discussing the issues with 00:07:36.470 --> 00:07:39.649 secure scuttlebutt, SSB. While there aren't as 00:07:39.649 --> 00:07:42.149 many problems with SSB compared to other alternatives, 00:07:42.589 --> 00:07:44.790 there are still some key concerns. One of the 00:07:44.790 --> 00:07:46.870 primary issues is that the protocol is quite 00:07:46.870 --> 00:07:49.470 complicated. It wasn't initially designed to 00:07:49.470 --> 00:07:52.490 be an open protocol, but rather grew organically 00:07:52.490 --> 00:07:54.850 from a quick solution to a specific problem. 00:07:55.509 --> 00:07:58.490 As a result, it has some strange and unnecessary 00:07:58.490 --> 00:08:01.389 quirks, like signing a JSON string that strictly 00:08:01.389 --> 00:08:06.439 follows the rules of ECMA 262 6th edition. This 00:08:06.439 --> 00:08:08.660 complexity can create challenges for adoption 00:08:08.660 --> 00:08:12.500 and usage. Another aspect of SSB that some users 00:08:12.500 --> 00:08:15.019 find unnecessary is the insistence on having 00:08:15.019 --> 00:08:18.439 a chain of updates from a single user. This adds 00:08:18.439 --> 00:08:21.199 bloat and rigidity to the platform because each 00:08:21.199 --> 00:08:23.540 server and user must store the entire chain of 00:08:23.540 --> 00:08:26.959 posts to ensure the validity of new ones. While 00:08:26.959 --> 00:08:29.240 there may be reasons for this approach, it can 00:08:29.240 --> 00:08:31.779 feel burdensome for users who simply want a more 00:08:31.779 --> 00:08:34.730 streamlined experience. Despite these concerns, 00:08:35.169 --> 00:08:38.330 SSB does have some advantages, particularly in 00:08:38.330 --> 00:08:41.250 its peer -to -peer syncing capabilities. However, 00:08:41.450 --> 00:08:44.330 it may be worth considering using SSB as a basis 00:08:44.330 --> 00:08:47.070 and adapting it to the client relay server model. 00:08:47.549 --> 00:08:50.450 By doing so, we can leverage the benefits of 00:08:50.450 --> 00:08:53.129 an established standard while still aligning 00:08:53.129 --> 00:08:55.929 with the desired characteristics of a decentralized 00:08:55.929 --> 00:08:59.409 platform. Lastly, let's briefly touch on the 00:08:59.409 --> 00:09:01.789 challenges that arise when everyone is expected 00:09:01.789 --> 00:09:04.330 to run their own server. While this approach 00:09:04.330 --> 00:09:06.850 can provide a high level of control and autonomy, 00:09:07.590 --> 00:09:10.690 it also presents its own set of issues. For one, 00:09:11.090 --> 00:09:13.769 it requires everybody to have the technical expertise 00:09:13.769 --> 00:09:16.190 and resources to set up and maintain their own 00:09:16.190 --> 00:09:19.389 server. Additionally, even if individuals have 00:09:19.389 --> 00:09:22.169 their own servers, censorship can still occur 00:09:22.169 --> 00:09:25.669 if domain names are censored or blocked. In conclusion, 00:09:25.929 --> 00:09:28.710 while alternatives like Mastodon and SSB offer 00:09:28.710 --> 00:09:31.649 promising avenues for decentralization and freedom 00:09:31.649 --> 00:09:34.289 from corporate control, they also come with their 00:09:34.289 --> 00:09:37.470 own set of challenges. From the dependence on 00:09:37.470 --> 00:09:40.669 third -party domain names to server owner censorship 00:09:40.669 --> 00:09:43.009 and the lack of incentives for server maintenance, 00:09:43.830 --> 00:09:46.529 there are various obstacles to overcome. Finding 00:09:46.529 --> 00:09:49.129 a sustainable solution that addresses these issues 00:09:49.129 --> 00:09:51.850 while still preserving the benefits of a decentralized 00:09:51.850 --> 00:09:55.299 platform remains a complex task. Nonetheless, 00:09:55.779 --> 00:09:57.740 the ongoing exploration and development in this 00:09:57.740 --> 00:10:00.519 field hold promise for a more open and inclusive 00:10:00.519 --> 00:10:04.799 digital landscape. So how does Nostr work? Well, 00:10:04.899 --> 00:10:07.220 it's made up of two core components, clients 00:10:07.220 --> 00:10:10.620 and relays. Every user runs a client and anyone 00:10:10.620 --> 00:10:13.559 can run a relay. Each user is identified by a 00:10:13.559 --> 00:10:16.519 public key and every post in Nostr is signed. 00:10:17.019 --> 00:10:20.269 To ensure the authenticity of the posts, Every 00:10:20.269 --> 00:10:23.250 client validates these signatures. Now let's 00:10:23.250 --> 00:10:26.210 dive into how clients and relays interact within 00:10:26.210 --> 00:10:29.070 the Noster network. Clients fetch data from the 00:10:29.070 --> 00:10:31.669 relays they choose, and they also have the ability 00:10:31.669 --> 00:10:34.350 to publish data to other relays of their choice. 00:10:35.529 --> 00:10:37.570 It's important to note here that a relay doesn't 00:10:37.570 --> 00:10:40.809 communicate directly with another relay. It only 00:10:40.809 --> 00:10:44.009 interacts directly with users. For example, let's 00:10:44.009 --> 00:10:46.950 say you want to follow someone's posts on Noster. 00:10:47.470 --> 00:10:49.870 All you have to do is instruct your client to 00:10:49.870 --> 00:10:52.509 query the relays you know for posts from that 00:10:52.509 --> 00:10:55.289 specific public key. This allows you to stay 00:10:55.289 --> 00:10:58.070 updated with the posts from the users you follow. 00:10:58.649 --> 00:11:01.210 When a client starts up, it queries data from 00:11:01.210 --> 00:11:03.590 all the relays it knows for all the users it 00:11:03.590 --> 00:11:06.330 follows. This could include all updates from 00:11:06.330 --> 00:11:09.350 the last day, for instance. Once the data is 00:11:09.350 --> 00:11:11.909 fetched, the client then displays it to the user 00:11:11.909 --> 00:11:15.429 in a chronological order. A post on Noster can 00:11:15.429 --> 00:11:18.190 contain any kind of structured data. However, 00:11:18.330 --> 00:11:20.789 the most commonly used post formats will eventually 00:11:20.789 --> 00:11:23.570 be standardized so that all clients and relays 00:11:23.570 --> 00:11:26.350 can seamlessly handle them. Now let's explore 00:11:26.350 --> 00:11:28.690 how Noster solves some of the problems that other 00:11:28.690 --> 00:11:30.970 networks struggle with, such as users getting 00:11:30.970 --> 00:11:34.350 banned and servers being closed. In Noster, a 00:11:34.350 --> 00:11:36.570 relay can block a user from publishing anything 00:11:36.570 --> 00:11:39.250 on that specific relay. However, this doesn't 00:11:39.250 --> 00:11:42.149 mean that the user loses their identity or their 00:11:42.149 --> 00:11:45.080 follower base. Since each user is identified 00:11:45.080 --> 00:11:47.820 by a public key, even if they get banned from 00:11:47.820 --> 00:11:50.440 one relay, they can still publish their posts 00:11:50.440 --> 00:11:53.580 on other relays. To make the process of switching 00:11:53.580 --> 00:11:56.740 relays easier, Nostr allows users to automatically 00:11:56.740 --> 00:11:59.159 add relay addresses recommended by the users 00:11:59.159 --> 00:12:02.059 they follow to their list of relays. This means 00:12:02.059 --> 00:12:04.100 that whenever someone you follow suggests a new 00:12:04.100 --> 00:12:06.580 relay, your client will automatically include 00:12:06.580 --> 00:12:09.580 it in the relays it queries. If someone wants 00:12:09.580 --> 00:12:12.419 to migrate from one relay to another, They can 00:12:12.419 --> 00:12:14.620 simply publish a server recommendation to the 00:12:14.620 --> 00:12:17.759 previous relay and make the switch. Even if a 00:12:17.759 --> 00:12:20.120 user gets banned from multiple relays and can't 00:12:20.120 --> 00:12:22.799 broadcast their server recommendations, they 00:12:22.799 --> 00:12:24.899 can still inform a few close friends through 00:12:24.899 --> 00:12:27.220 other means about the new relay they are using. 00:12:27.980 --> 00:12:30.580 These friends can then publish the server recommendations 00:12:30.580 --> 00:12:33.539 to the new relay, helping the banned user rebuild 00:12:33.539 --> 00:12:36.759 their follower base. The same process applies 00:12:36.759 --> 00:12:40.149 if a relay ceases its operations. Users can continue 00:12:40.149 --> 00:12:42.649 to publish their updates on other relays and 00:12:42.649 --> 00:12:44.789 gradually inform their followers about the new 00:12:44.789 --> 00:12:47.529 relay through server recommendations. NOSTER 00:12:47.529 --> 00:12:50.509 also prioritizes censorship resistance. Every 00:12:50.509 --> 00:12:52.230 user has the freedom to publish their updates 00:12:52.230 --> 00:12:54.830 to any number of relays. Relays can charge a 00:12:54.830 --> 00:12:57.389 fee for users to publish their, ensuring censorship 00:12:57.389 --> 00:13:00.190 resistance. In other words, even if certain relays 00:13:00.190 --> 00:13:02.669 might be inclined to censor content, there will 00:13:02.669 --> 00:13:05.389 always be options available. including servers 00:13:05.389 --> 00:13:07.850 in countries like Russia that may be more willing 00:13:07.850 --> 00:13:09.710 to accept your money in exchange for serving 00:13:09.710 --> 00:13:13.929 your posts. Overall, Noster's design allows for 00:13:13.929 --> 00:13:16.169 users to have control over their content and 00:13:16.169 --> 00:13:19.809 identity, even when facing bans and server closures. 00:13:20.730 --> 00:13:23.450 It fosters a decentralized and censorship -resistant 00:13:23.450 --> 00:13:26.610 environment where users can freely exchange information 00:13:26.610 --> 00:13:30.230 and connect with their followers. So let's talk 00:13:30.230 --> 00:13:32.870 about spam. We all know how annoying and frustrating 00:13:32.870 --> 00:13:35.769 it can be, right? Well, in Noster, there are 00:13:35.769 --> 00:13:37.730 a few measures in place to tackle this issue. 00:13:38.169 --> 00:13:40.889 One way is to require some sort of authentication, 00:13:41.230 --> 00:13:43.649 such as an email address or phone number, before 00:13:43.649 --> 00:13:46.309 allowing publication on a relay. This ensures 00:13:46.309 --> 00:13:48.730 that only legitimate users can post their content. 00:13:49.570 --> 00:13:52.470 Additionally, spam can also be prevented by utilizing 00:13:52.470 --> 00:13:55.490 other anti -spam techniques like Hashcash or 00:13:55.490 --> 00:13:58.409 CAPTCHAs. These methods help to filter out unwanted 00:13:58.409 --> 00:14:01.539 spam and keep the network clean. Now, when it 00:14:01.539 --> 00:14:03.600 comes to the number of active relays needed for 00:14:03.600 --> 00:14:06.220 the network to function properly, it's actually 00:14:06.220 --> 00:14:09.080 not as many as you may think. In fact, just a 00:14:09.080 --> 00:14:11.779 handful of relays can do the job just fine. The 00:14:11.779 --> 00:14:14.059 beauty of Noster lies in its ability to easily 00:14:14.059 --> 00:14:16.480 create and spread new relays throughout the network 00:14:16.480 --> 00:14:20.200 if needed. So even if some relays start misbehaving, 00:14:20.639 --> 00:14:22.860 new ones can be quickly brought in to maintain 00:14:22.860 --> 00:14:25.399 a healthy network. This means that the amount 00:14:25.399 --> 00:14:28.460 of data storage required is relatively less compared 00:14:28.460 --> 00:14:31.340 to other similar software like Mastodon. But 00:14:31.340 --> 00:14:33.940 what if we consider a different scenario? One 00:14:33.940 --> 00:14:35.879 where there are hundreds of niche relays run 00:14:35.879 --> 00:14:38.820 by amateurs, each relaying updates from a small 00:14:38.820 --> 00:14:41.500 group of users. Well, even in this case, the 00:14:41.500 --> 00:14:44.340 architecture of Nostr is quite scalable. Data 00:14:44.340 --> 00:14:46.940 can be sent from users to a single server, and 00:14:46.940 --> 00:14:49.139 from there, directly to the users who need that 00:14:49.139 --> 00:14:51.399 information. It doesn't have to be stored by 00:14:51.399 --> 00:14:53.840 anyone else. This means that even if there are 00:14:53.840 --> 00:14:56.539 numerous amateur servers in the mix, it's not 00:14:56.539 --> 00:14:58.799 a burden for any single server to handle updates 00:14:58.799 --> 00:15:02.000 from others. So, having amateur servers is not 00:15:02.000 --> 00:15:04.139 an issue at all. Now let's turn our attention 00:15:04.139 --> 00:15:06.460 to video and other heavy content that may be 00:15:06.460 --> 00:15:08.840 shared on Noster. The platform makes it easy 00:15:08.840 --> 00:15:11.580 for a relay to reject large content or charge 00:15:11.580 --> 00:15:15.059 for accepting and hosting such content. By making 00:15:15.059 --> 00:15:18.000 the information and incentives clear, market 00:15:18.000 --> 00:15:20.340 forces can play a role in solving this problem. 00:15:20.960 --> 00:15:23.539 Users who want to post heavy content would need 00:15:23.539 --> 00:15:26.820 to pay for its hosting, ensuring that only those 00:15:26.820 --> 00:15:29.940 who are willing to invest in it can do so. This 00:15:29.940 --> 00:15:32.580 approach helps to control the flow of large files 00:15:32.580 --> 00:15:35.539 and prevents any potential overload on the network. 00:15:36.500 --> 00:15:39.139 When it comes to tricking users, Nostr gives 00:15:39.139 --> 00:15:42.080 the power back to the clients. Each client can 00:15:42.080 --> 00:15:44.399 decide how they want to show posts to users. 00:15:44.830 --> 00:15:47.330 Whether it's through an AI algorithm that decides 00:15:47.330 --> 00:15:49.649 the order of updates or simply displaying them 00:15:49.649 --> 00:15:52.289 chronologically, the choice is in the hands of 00:15:52.289 --> 00:15:55.669 the user. This level of customization ensures 00:15:55.669 --> 00:15:58.190 that users have control over the content they 00:15:58.190 --> 00:16:02.110 consume and how it is presented to them. Finally, 00:16:02.490 --> 00:16:04.549 let's address the question of why no one has 00:16:04.549 --> 00:16:07.120 done something like Nostra before. Well, it could 00:16:07.120 --> 00:16:09.240 be because social networks are typically developed 00:16:09.240 --> 00:16:12.720 by companies aiming to make money or by P2P activists 00:16:12.720 --> 00:16:15.759 who want to create a serverless network. In both 00:16:15.759 --> 00:16:18.460 cases, they fail to see the unique combination 00:16:18.460 --> 00:16:21.419 of both worlds that Nostr brings to the table. 00:16:22.240 --> 00:16:24.879 Nostr strikes a balance between being a decentralized 00:16:24.879 --> 00:16:27.440 network and providing a user -friendly experience, 00:16:27.840 --> 00:16:30.279 something that hasn't been fully explored before. 00:16:30.860 --> 00:16:33.720 And there you have it. Nostr takes a proactive 00:16:33.720 --> 00:16:36.450 approach to combat spam. ensures scalability 00:16:36.450 --> 00:16:39.110 with a limited number of relays, handles heavy 00:16:39.110 --> 00:16:42.049 content effectively, gives users control over 00:16:42.049 --> 00:16:44.769 their feed, and brings a much needed blend of 00:16:44.769 --> 00:16:46.830 decentralization and convenience to the social 00:16:46.830 --> 00:16:49.429 networking space. No wonder it's making waves 00:16:49.429 --> 00:16:52.769 in the world of social media. Finding people 00:16:52.769 --> 00:16:55.350 to follow on a social network can be an exciting 00:16:55.350 --> 00:16:57.669 step towards building your online community. 00:16:58.149 --> 00:17:00.830 So how exactly do you go about finding these 00:17:00.830 --> 00:17:03.720 individuals? Well, the first thing you need is 00:17:03.720 --> 00:17:06.259 to know them and somehow obtain their public 00:17:06.259 --> 00:17:09.039 key. This can be done by asking them directly 00:17:09.039 --> 00:17:11.200 or by discovering their public key reference 00:17:11.200 --> 00:17:13.720 somewhere on the platform. Once you are inside 00:17:13.720 --> 00:17:16.279 a Noster social network, you can start exploring 00:17:16.279 --> 00:17:18.960 and interacting with others. You'll be able to 00:17:18.960 --> 00:17:21.119 see the people you know already following and 00:17:21.119 --> 00:17:23.220 interacting with each other, which can give you 00:17:23.220 --> 00:17:25.980 a starting point. From there, you can begin to 00:17:25.980 --> 00:17:28.359 follow and engage with these individuals as well. 00:17:29.039 --> 00:17:31.660 Now let's talk about relays. How do you find 00:17:31.660 --> 00:17:33.519 them and what happens if you are not connected 00:17:33.519 --> 00:17:36.539 to the same relay as someone else? Relays play 00:17:36.539 --> 00:17:38.579 a crucial role in facilitating communication 00:17:38.579 --> 00:17:41.420 between users on a social network. They act as 00:17:41.420 --> 00:17:43.440 intermediaries, allowing data to be transferred 00:17:43.440 --> 00:17:45.640 between users who may not be directly connected. 00:17:46.440 --> 00:17:48.420 If you are not connected to the same relay as 00:17:48.420 --> 00:17:51.200 another individual, you won't be able to communicate 00:17:51.200 --> 00:17:54.079 with them directly. However, there are ways to 00:17:54.079 --> 00:17:56.779 address this limitation. Nostr provides hints 00:17:56.779 --> 00:17:59.099 on events that can be used to enable your client 00:17:59.099 --> 00:18:01.759 software, or even manually connect to the other 00:18:01.759 --> 00:18:04.920 person's relay and interact with them. This helps 00:18:04.920 --> 00:18:06.779 overcome the challenge of not being connected 00:18:06.779 --> 00:18:09.440 to the same relay. It is important to note that 00:18:09.440 --> 00:18:11.700 while there may be ideas on how to further improve 00:18:11.700 --> 00:18:14.460 this in the future, it is impossible to promise 00:18:14.460 --> 00:18:17.819 perfect reachability for every user. No protocol 00:18:17.819 --> 00:18:20.680 can guarantee seamless connectivity in all situations. 00:18:21.599 --> 00:18:23.640 Now let's discuss if you can know how many people 00:18:23.640 --> 00:18:26.359 are following you on a social network. Unfortunately, 00:18:26.539 --> 00:18:28.759 you do not have direct access to this information. 00:18:29.299 --> 00:18:31.980 However, if relays cooperate outside of the protocol, 00:18:32.500 --> 00:18:35.319 you may be able to gather some estimates. This 00:18:35.319 --> 00:18:37.839 extra protocol cooperation can provide you with 00:18:37.839 --> 00:18:40.240 insights into the number of people following 00:18:40.240 --> 00:18:43.420 you. Moving on to the question of what incentives 00:18:43.420 --> 00:18:46.740 there are for individuals to run relays. It is 00:18:46.740 --> 00:18:48.519 important to note that the assumption behind 00:18:48.519 --> 00:18:51.359 this question is somewhat misleading. Relays 00:18:51.359 --> 00:18:54.259 are not merely dumb pipes. that exists solely 00:18:54.259 --> 00:18:57.180 for the purpose of data transfer. In the context 00:18:57.180 --> 00:19:00.039 of NOSTER, relays serve as essential infrastructure 00:19:00.039 --> 00:19:03.000 for the social network. They enable communication 00:19:03.000 --> 00:19:06.059 and data exchange between users. Incentives for 00:19:06.059 --> 00:19:08.339 running relays can vary depending on the specific 00:19:08.339 --> 00:19:11.220 context and goals of the social network. However, 00:19:11.339 --> 00:19:13.240 it is important to understand that relays are 00:19:13.240 --> 00:19:16.039 more than just providers for moving data. The 00:19:16.039 --> 00:19:18.400 comparison to DHT nodes and other peer -to -peer 00:19:18.400 --> 00:19:20.940 networks is relevant here. In those networks, 00:19:21.220 --> 00:19:24.019 similar questions arise. What incentives do people 00:19:24.019 --> 00:19:27.539 have to run DHT nodes? The answer lies in the 00:19:27.539 --> 00:19:29.680 functionality and benefits that these nodes bring 00:19:29.680 --> 00:19:32.680 to the network, beyond acting as mere data carriers. 00:19:33.380 --> 00:19:35.279 Now let's address the question of using different 00:19:35.279 --> 00:19:37.359 server relays and the difference between using 00:19:37.359 --> 00:19:41.140 relays on platforms like AWS or Azure. It is 00:19:41.140 --> 00:19:43.420 important to note that there are numerous VPS, 00:19:43.700 --> 00:19:46.779 virtual private server, providers available worldwide, 00:19:47.160 --> 00:19:51.240 not just limited to AWS or Azure. While AWS and 00:19:51.240 --> 00:19:53.900 Azure are popular choices for large -scale centralized 00:19:53.900 --> 00:19:56.740 service providers, they are not the only options. 00:19:57.319 --> 00:20:00.019 For smaller relay servers, any VPS provider can 00:20:00.019 --> 00:20:02.680 effectively serve the purpose. Noster allows 00:20:02.680 --> 00:20:05.160 users to switch between server relays or even 00:20:05.160 --> 00:20:07.880 utilize multiple relays. The key difference lies 00:20:07.880 --> 00:20:10.119 in the underlying infrastructure and the specific 00:20:10.119 --> 00:20:12.900 needs of the social network. Whether a relay 00:20:12.900 --> 00:20:16.339 is hosted on AWS, Azure, or any other VPS provider, 00:20:16.750 --> 00:20:19.250 The primary consideration is that it is capable 00:20:19.250 --> 00:20:21.690 of efficiently handling the network's requirements. 00:20:22.349 --> 00:20:25.089 Now, if you are looking for more detailed information 00:20:25.089 --> 00:20:27.930 about the NOSTER protocol, you can explore the 00:20:27.930 --> 00:20:31.730 NIP's, NOSTER Improvement Proposals, and specifically 00:20:31.730 --> 00:20:35.710 refer to NIP -01. This provides a reasonably 00:20:35.710 --> 00:20:38.190 detailed explanation of the protocol specification. 00:20:38.970 --> 00:20:41.490 It's worth mentioning that the protocol specification 00:20:41.490 --> 00:20:44.890 is concise, short, and relatively straightforward. 00:20:45.650 --> 00:20:48.049 Lastly, if you are interested in the software 00:20:48.049 --> 00:20:51.069 being built using Gnoster, you can find a comprehensive 00:20:51.069 --> 00:20:56.170 list on GitHub. The repository, https://github 00:20:56.170 --> 00:21:00.630 .com -aljaskaru -awesome -n -oster, contains 00:21:00.630 --> 00:21:02.890 an almost complete compilation of the software 00:21:02.890 --> 00:21:05.529 projects utilizing Gnoster. Remember, these are 00:21:05.529 --> 00:21:07.730 the key aspects to consider when it comes to 00:21:07.730 --> 00:21:10.269 finding people to follow, understanding relays, 00:21:10.430 --> 00:21:12.869 and exploring the Gnoster protocol and software 00:21:12.869 --> 00:21:16.410 ecosystem. Join the conversation and discover 00:21:16.410 --> 00:21:19.190 new connections in the Noster social network. 00:21:35.029 --> 00:21:38.049 Today's episode covered the creation of a censorship 00:21:38.049 --> 00:21:41.250 -resistant social network using Noster protocol. 00:21:41.589 --> 00:21:44.410 highlighting its advantages over Mastodon and 00:21:44.410 --> 00:21:47.930 SSB, the role of clients and relays, and the 00:21:47.930 --> 00:21:50.869 unique features that set Nostra apart, including 00:21:50.869 --> 00:21:53.730 spam prevention and user customization. Thanks 00:21:53.730 --> 00:21:55.430 for listening to today's episode. I'll see you 00:21:55.430 --> 00:21:57.329 guys at the next one, and don't forget to subscribe.