Yes, that's true, but I think it's obvious, the topology of the architecture has different approaches, for bitcoin redundancy is a requirement, while in nostr it's something recommended but not mandatory, in any case I think it's something also due to the current state of youth of nostr, I think as it continues to evolve solutions will come out that will fill the gap and can make nostr a more homogeneous network, I'm talking about merkle trees and the proposal of hornet, what do you think about that?
From 1h12m. Great listen. nostr:npub1w69ya7xs697hk3hky3gllryz8rwverfa0ylz89chf9qnhfcskc2s64zltw says nostr is not censorship resistant in the same way as bitcoin. He's right, it's only really censorship resistant if you run your own relay. A wonderful lesson in how to think for yourself and present a counter viewpoint.
Discussion
I havent followed hornet too closely, but I think relays are good for transmitting, bad for storing. For me, the advantage of nostr is owning your own identity
My take is that the core innovation of #nostr is the combination of: 1) generating your own identifier (.i.e., owning your identifier), and 2) signing every event you transmit.
Relays are great, but not absolute necessary. I could create a standalone platform that only does 1) and 2). Might not be useful for the wider world, but that might be ok for my purposes.
If i get time I will build #nosdav out which uses #nip98 to give nostr many orders of magnitude more storage. But too many projects to manage, right now.
Yes! I like nosdav! Would love to understand it better and self host a server, can be interesting, lately i was thinking that this kind of solutions can work as a coordinator to allow users communicate in a more private way. Nosdav can work as a totp server true?
Btw what do you think about nostrcheck-api? Its the backend used in nostrcheck.me that its open source now, it uses nip 98 for auth too. It have the same direction of a nosdav server