We got some questions about the gossip/outbox model, so I’ll clarify Primal’s position. We like the outbox model. We think it will help nostr scale and become more censorship resistant. Primal will roll out support for the outbox model in several steps. We recently upgraded all Primal clients to manage relays per NIP-65. We are currently in the process of upgrading our clients to leave relay hints on all published events to make sure that outbox clients work well with the content published by our clients. Next we will randomize the default list of relays for new users to help spread content out. The final step will be to implement reading content directly from relays, which will be used in conjunction with our caching service. Imho, the winning approach involves using the outbox model together with caching nodes, giving us the best of both worlds. I described this approach a year ago when we launched the preview of Primal:

Habla

Scaling Nostr via Open Caching Services - miljan

Given today’s network topology, it is not clear how Nostr could support 100M users. Let’s consider an approach that might help with scaling, UX...