3 ms·

The comparison here is to something like TCP/IP. TCP/IP never goes down. TCP/IP is a protocol, the servers may go down and cause disruption, but the protocol do

by nout 6mo ago

The comparison here is to something like TCP/IP. TCP/IP never goes down. TCP/IP is a protocol, the servers may go down and cause disruption, but the protocol doesn't really have the ability to "go down". Nostr is also a protocol. The communication on top of Nostr is pretty resilient compared to other solutions though, so that's the main highlight here. If tens of servers go down, then some people may start noticing a bit of inconvenience. If hundreds of servers go down, then some people may need to coordinate out of bound on what relays to use, but it still generally speaking works ok.

arter45 6mo ago
That's because TCP/IP is a protocol, not a (centralized or decentralized) server. A protocol cannot go down. It can trigger failures, it can be abused, but it cannot go down. It's like saying "English never burns". Sure, you can't burn English but you can burn specific books, newspapers and so on.
- nout 6mo ago
  That's... literally the point I just made in my reply?
  - ramblejam 6mo ago
    Right but that's kind of meaningless, saying the nostr protocol never goes down, because the AT Protocol didn't go down in this bluesky case either. Protocols don't "go down". Stuff making use of protocols does.