From the protocol README section "The problem with SSB (Secure Scuttlebutt)" - it lists a few small things but is mostly complimentary of SSB. One of the big issues I always had with SSB is efficiency/scaling/message size/db size. Is this something Nostr addresses or considers, or is it likely to suffer from similar scaling issues with heavy use?
* Media itself is not stored, only links to media.
* Relays are free to limit usage, charge a fee or require proof of work.
* There are many kinds of messages with different storage standards i.e ephemeral messages are not stored at all.
I'm not an expert but the SSB scaling issues seem related to the architecture being tied to the sigchain, & general feed immutability. This makes it very difficult for pubs to, for example, accept/process subsets of posts or do anything out-of-order. It also makes it impossible for clients to limit local database storage, especially mobile clients where that might be at a premium.
Even just the existence of ephemeral notes seems to indicate there's no such architectural limitation so that sounds really hopeful.