no scaling issue with nostr, technologically speaking.
it's just sockets, end of the day. the proof is, there are enterprise grade market firehoses that serve 100 price feeds a second to millions of listeners at once.. this has already been solved and is just an infra issue
issue is with how the relays will sync and filter and handle merge logic on their end. there should be some expectation that you and i can find each others post and we're not necessarily on the same relay configuration
anyways... no technological scaling challenge, but more of a race to see who builds the best UI/UX experience 🫡
stat
npub1aj…wxcwg
2023-02-12 08:13:29
Author Public Key
npub1aj8h9lefxlqe0jcdqvk6ufa6upe6u6jwr0f23ch0z4uxx6e4jh9sqwxcwgPublished at
2023-02-12 08:13:29Event JSON
{
"id": "61282c7ea39dda05acb70c8da20a1397ebda5110cd7223fa1295742d833c8940",
"pubkey": "ec8f72ff2937c197cb0d032dae27bae073ae6a4e1bd2a8e2ef1578636b3595cb",
"created_at": 1676189609,
"kind": 1,
"tags": [],
"content": "no scaling issue with nostr, technologically speaking.\n\nit's just sockets, end of the day. the proof is, there are enterprise grade market firehoses that serve 100 price feeds a second to millions of listeners at once.. this has already been solved and is just an infra issue\n\nissue is with how the relays will sync and filter and handle merge logic on their end. there should be some expectation that you and i can find each others post and we're not necessarily on the same relay configuration\n\nanyways... no technological scaling challenge, but more of a race to see who builds the best UI/UX experience 🫡",
"sig": "0958ca170f02e2c57f1a8c817179002e9224383f0e85e929c036001663b1026e78fc7caf2d90467302a978c65b4d17d2cd94119e16677e136d4f17c02828dab2"
}